No Markdown support in Google Drive after all these years
Why does Google not (want to?) support the full Markdown experience in Google Drive? I'm not talking about the limited, mostly useless support in Docs, but supporting opening, reading / editing real (.MD extension) files. Just, why? Simple: if you make your documents in Markdown, you won't be making them in Google Docs. Stuff made in Google Docs is sticky, increases your dependence on Google, and importantly has a valuable network effect due to their collaboration features. It is in Google's best interest to encourage you to rely on their proprietary services instead of offering you alternatives that allow you to switch provider easily. Additionally, the "people who know what Markdown is but also like trusting Google with their files" demographic is vanishingly small and not who Drive is targeting at all. "people who know what Markdown is" overlaps very much with "people who have to use google docs for work but would prefer a consistent editing experience". Basically every dev I know has to use either teams/sharepoint/office or google docs, but most are also more comfortable with using markdown and use it for technical docs. I'd love to have a google docs option of creating a "simple doc", that is backed by markdown and only supports the basics (headers, paragraphs, lists, maybe tables) and have a WYSIWYG for non-tech people and a (maybe git-based?) workflow for people used to markdown. Something like what azure devops and github does with their wikis. +1, I love google docs and also love markdown. If there was a shared markdown editor with the same collaborative features as google docs, i'd probably never use anything else. We use Slite extensively at work. Works pretty well to quickly create/edit documents with a nice editor. When you type Markdown, the content automatically resolves the styling/headers/lists. Multiple persons editing a document at the same time is (of course) supported. And every document can be exported as Markdown or PDF. Dropbox Paper should meet your requirements. I tried switching to it a few years ago, but the problem is that the other people I'm collaborating with always want to use Google Docs, and when I'm writing a document by myself, I'd much rather just write to a local file. Product with corporate lock-in, but Quip allows the user to use markdown in their documents, and export their documents into Markdown. Sounds a lot like something like Notion? Notion is very sluggish and feels very unlike a markdown file-based system to me. Agreed, I like certain aspects of Notion, but as a FE dev myself, I think what they’re trying to do is too complex. I don’t see how they could ever make it performant. Notion doesn't use Markdown. Just type in markdown :-). It mostly works for input. Sure, you can add asterisks around things and it will convert stuff to bold, etc, but Notion isn't actually a markdown-based app – the underlying representation of a Notion doc is stored as JSON. Yes, pretty much this. I use Sharepoint and teams because I have to, not because I would think they are good or because I liked them. Sharepoint in particular is horrible, Teams are only slightly better. I want markdown on sharepoint. Try Loop, if your organization has been enabled for it. It's exactly what people here are wishing Google Drive had. > Basically every dev I know has to use either teams/sharepoint/office or google docs I think there is another sizable set which heavily uses wiki. At my work, most people use it (a very small set of people use SharePoint for mainly PowerPoint or formatting heavy docs). Are those devs not ever collaborating with non-tech people on documents? Also when you say wiki, do you mean a mediawiki instance or the ones included in things like github? SharePoint pages can now be created with Markdown BTW. There is a Markdown web part out of the box. Not so sure how Markdown files themselves are handled though, pretty badly I suspect. Agree completely with the first paragraph and disagree completely with the second paragraph. There are lots of us who use Google drive at work that love md. Apologies, that part was primarily intended for home users. Google certainly isn't targeting that demographic, there are much larger ones to go after. If you're forced to use Drive at work, Google isn't targeting you either. It's targeting the C-suites above you who buy the software, and they don't know what Markdown is. The fact that engineers are lamenting the lack of Markdown in Google Drive shows how much influence they have over those decisions. I’m a developer working at a company that uses GSuite. My personal feelings about trusting Google aren’t really relevant, I’d love to use Markdown in GDoc, as would many of my coworkers! I'd be happy if only they supported the CommonMark format properly in GChat.. >Agree completely with the first paragraph and disagree completely with the second paragraph. There are lots of us who use Google drive at work that love md. That's not incompatible with the demographic being vanishingly small and not who Drive is targeting at all. "A lot of us" can still be an insignificant number compared to the Google Drive userbase and target demographic. Now, "more than 10% of Google Drive users" might start getting somewhere. But I doubt it's even close to 1%. Google Drive is not a tool targeted to developers especially, and developers are not that much of a demographic to matter for mass market services. I've seen virtually no use of Google Drive in the wild in my personal life. I've worked at 10k+ orgs that use it exclusively and every minute of every day. I'm not sure where you're getting those stats but a source would be nice. I would suspect that their customer base and/or core usage is made up of far more tech company employees via Cloud and Workspaces than it is average Joes backing up documents. >I've seen virtually no use of Google Drive in the wild in my personal life That's what I call a bubble. https://www.theverge.com/2018/7/25/17613442/google-drive-one... And that's in 2023. As for the numbers of organizational paying users in 2023 (corporate users) were 6 million, compared to "over a billion" (in 2023). And of those 6 million organizational users of course only a smaller share are developers. Regular file sharing and G-suite stuff for office workers is the order of the day. > I've seen virtually no use of Google Drive in the wild in my personal life. Really? I'm curious, are the people you know using Dropbox, OneDrive, or something else? Or are they just not sharing files in a public cloud? I started to retort "how do you even collaborate on spreadsheets with your friends?" before realizing maybe I just have some, err, unique friend groups. Our friend group also use spreadsheets to decide who is bringing what to the BBQ. In the non tech-centric groups of friends and family, filesystem solutions have been superceded by all-in-ones like Google/Apple Photos, Notes etc. Most people I know also use an iPhone meaning they're driven towards data storage that is built around an app use case, rather than simulating a desktop FS on another device. Many of them use Google or Microsoft solutions for work though. There are dozens of you. Outside of HN, people that actually avoid giving Google any data are almost nonexistent. People that use Markdown definitely aren't. There's a huge number of pragmatic developers that use Markdown and Google. Seems like people can't fathom that "developers" in general are an insignificant demographic. Google Drive is used by a billion or more (including most Android users). Developers are a handful of millions. Developers that use markdown outside of where they're forced to and actively want Google Drive to support it are even fewer. What's a good wiki with Markdown support? I hate how Confluence doesn't have it, and Jira sort of has it, even though they're supposed to be integrated. Preferably close to GFMD. Google docs can only represent a subset of the document formatting and features in markdown (yes, there are html literals in markdown, but even then it isn't enough). Markdown could be an import/export format... but I can't see it working well with the Docs editor. 'Additionally, the "people who know what Markdown is but also like trusting Google with their files" demographic is vanishingly small and not who Drive is targeting at all.' <--this 200% It's just not true at all. Knowing/using markdown doesn't make you some Richard Stallmann type. Maybe the original author implies that you don't need to be a Richard Stallman type anymore, not to trust Google. HN/Reddit is a bit of a bubble. Most people trust Google just fine with their files. People who think Markdown users are a demographic major enough to matter in the context of the Google Drive userbase are also in a bit of a bubble... Yep. I agree with this. Most people have know idea what markdown is, and if they do use it, it is usually the text format behind a WYSIWYG editor... Some examples: Slack, Github... docx is pretty portable as it goes. getting stuff converted (downsampled; in a sense) to markdown is easy enough. It's a bit like asking why Markdown isn't supported in Microsoft Word or Apple Pages. Environmental lock-in. that demographic is also likely to have an outaized effect on evangelizing cool new features and getting people to swap over from other products. how much google is trying to grow vs curb competition is the question. They have a whole app store for Google Drive. There are markdown editors in there as well as plenty of other niche things. https://support.google.com/drive/answer/2500820 Sure, if you are trusting 3rd party access to your data. Yet another layer of trust for a (niche) service that might just vanish into thin air. No, thank you. It's not like Markdown is some rare, unheard of format. I think it's the most used file format for technical docs / content / notes these days, and it's here to stay (because it's simple, it's easy and it's portable). Besides, most well-known note-taking services and apps are based on Markdown, or they export losslessly to Markdown. > I think it's the most used file format for technical docs / content / notes That's why Atlassian supports MD for Jira and Confluence. Google Docs is first and foremost a Word Online competitor. There are probably 1000 markdown editors out there ranging from a simple textarea that only lets you write text, to Emacs, and something like Msword on steroids. The nice thing about an open market is that when you no longer like a product you can just switch to another one. I however understand your issue with privacy as any app can just steal your content without you knowing. The solution for privacy is to sandbox/jail the app into an environment where it can just access a limited set of resources, for example you can use an apparmor profile where the app can just access a special folder, and disable all networking. That special folder could be your google drive mount. Why should they? For your use-case, and mine, sure by all means add it. For the average user: "Why is Google Drive showing my text big a bigger font when I start a line with #" There's zero benefit for them to add it, and the majority of people who want markdown probably aren't using Google Drive to render their documents. Probably so. I agree. From a simple UX/UI perspective, there's the "+" button (for creating new Drive items), so, adding "New Markdown Document" or "New Text Document" would bring some clarity. But still... that broad majority is probably using the service in a totally different way. Even in 2021, Google Workspace had more than 3 billion users. I believe that 99% of these individuals had no clue what Markdown was. If they had, perhaps third-party apps that can connect to Google Drive, such as StackEdit, would be much more popular now. I’d frame it more as just text files…I can edit Word documents (as Word documents, not converted) that are stored on Google Drive, in Google Docs. One that feature was added, support for plain text should have been added as well. That being said Google Doc’s support for Word documents is confusing as hell. I wish at least it was made to be more visually distinct since people (such as: me) get confused all the time between editing a Google Doc, a Word document converted to Google Docs (where now there are likely two branched versions of the same document), and just using the Google Docs interface to edit a Word document directly. Phrase it the other way, why would they want to support a markdown editor in google drive? I think lots of people would keep their (plain text markdown) notes in Drive instead of using yet another tool / app / service for that. Besides, having
unencrypted text files at your disposal (for... I don't know... peeking into?) would be an absolute win. There's already Google Keep for notes. I use that since day one, I love it as a product. But still, this is not about notes, it's about supporting a simple, text-based file format. Unencrypted would rather be a loss for data privacy. Besides the pure textual representation of such files (.md, .txt), you still have the same problem for any (natively) supported Docs file format. It is, somehow, in the user's own option to use Drive as a repo for ultra-sensitive info or avoid it (but, unfortunately, this informed opinion applies more often to the more tech-savvy people). Actually, Google drive does work with Markdown. I store markdown there all the time. (after all markdown is just text) I presume you're looking to add a .md file and have editor / docs support, but there is this in case anyone is looking to write a limited subset of markdown in a Google doc: https://support.google.com/docs/answer/12014036?hl=en It's not great, but you'll find it useful if you have the muscle memory of `* thing` for bullet lists and `## My section` for headings. Google Drive doesn't directly support editing of text files either. A lot of people making strategic arguments like “it’s for lock-in”. I don’t buy it; they ship features so slowly that even obvious basic product features to copy from Notion like infinite-scrolling pages only shipped last year IIRC. They have a huge backlog of features that are catch-up to a strategically threatening disruptive competitor, and they can’t deliver those. Markdown support is below all that in priority. Why store markdown files in Google Drive of all places and not a git repository? Google Drive, to me, is object storage with a consumer-friendly user interface. It does not sound like the right place for constantly-changing text files for which you'd want revision history and commit-oriented editing. > Why store markdown files in Google Drive of all places and not a git repository? Git diffing doesn't play nice with paragraph-based prose. Does it not? All of our docs are Markdown files maintained in GitHub and diffs have never been an issue. PRs in particular are great for collaborative updates because reviewers can jump straight to the paragraphs that changed instead of reading everything top to bottom. How do you handle text wrapping or otherwise manage long paragraphs? Do you use a newline per sentence or use soft-wrapping to write each paragraph on a single line? I thiiiink soft wrapping, but I'm not at my computer to verify. Live collaboration is a radically different experience than pushing branches. Pros and cons to each, really depends on what you're wanting with a given document. Google Drive is a perfect example of today's Google. "Good enough -- just barely". It could be a very fast, efficient file browser with lots of format previews. It's not. Doing basic "file manager" things such as viewing/extracting files from a .zip, editing a plain-text file, or viewing markdown… all those are just "too complicated" for a small indie company like Google. Drive is incredibly powerful, and yet it's just awful compared to what it could be. If someone one day makes a "better web UI" for Drive with better functionality, but that still uses google drive in the backend, damn I want in. Drive totally chokes if you have tons of tiny files. Lots of things do but Drive is the worst I have seen. I unwisely tried to put a full MAME set on Drive once, and then deleted it. The files never got “deleted” but rather were still in my drive, but not associated with any particular folder, so I could search for them but not see them any other way. Another time, lots of files ended up in Trash, but Drive was unable to ever actually empty the trash. One thing that bites me every few months is that on iOS, the Google Drive file provider extension does not support basic operations. Like I think I have tried to just save a file to Google Drive via Files and it never uploaded. It’s not just that this stuff works with iCloud Drive, but also with Dropbox, Box, and even SFTP shares mounted via Secure Shellfish. Indeed. The web UI is awful at this. If you look at the devtools when you select many files, you can see that there's one synchronous web request per file. It's not synchronous, sync xhr on the web is pretty rare these days. Solution: use Obsidian and save in Drive. It's definitely a workaround, but I use a Chrome extension to work around this a bit. I use "Markdown Here" to add a "turn Markdown text into rich formatted text" button to my Chrome bar: And then I use it on plain Markdown text in a GMail compose window. The rich formatted output it produces is useful for sending richly-formatted GMail messages, but it can also be copy-pasted into a Google Doc (e.g. via https://docs.new), and it comes out really nicely, including support for headers, sub-headers, links, code blocks, and the rest. The main issue is that this is a one-way process, but so long as you keep the .md source files somewhere else, this trick lets you share a richly-formatted doc with others for final commenting/editing/etc. in the GDocs interface. They've marginalized "the offering" as a hybrid office/consumer product with a fragmented vision, as shown by their uninspired rebranding/marketing efforts. Google Cloud could just create their project folders in drive, let drive open the code editors, and let you do all your coding from there, but that team knows how bad the UI is, and this team is excused because they're the "office/consumer" offering. Both are paid to make separate UX, neither trusts the other, and it's categorical, so not even a conflict. Except, then there's the user that is forced to be incompatible members of two categories when they're not. In an ideal googleverse, you'd login to chrome and it'd have everything. It would be one service, metered by resource consumption, and you'd never have to leave any single window opened for a purpose, to get that "computational" thing done. My guess is that the engineering required to turn Markdown into Docs/Sheets/Slides files is more expensive than the increased engagement that Google would get from doing this. I'm still waiting for the Google Drive app for Linux. Not sure about other platforms, but on macOS, copy/paste includes style information. So I write my document in Markdown in my preferred editor, preview it with Marked 2, copy from Marked 2, paste into my Chrome window. Works except for images which cause the Chrome window to spin forever with "Document offline." Even emacs has a markdown mode: Well, why should they? I find more critical that for all the dependecy on COM, the IDL editing experience in Visual Studio still sucks after about 30 years, and is basically like editing bare bones text files. Nor for simple text files. Maybe they’re planning to shutdown Google Drive as it is and focus more on the “Office suite” experience. More oriented towards business case, and MD is not a priority for this at all. If we're already there, what about SVG support in slides? You have a whole-ass computer that can run software made to read Markdown, what do you need Google Drive for? Adjust your workflow, the tools exist. I would imagine the author is asking a question from a company where Google Workspace is the default tool, and would like to produce document that can be shared with others in Google Drive? You can mount Drive to a drive or mountpoint and edit it with a local tool. You can style the document in some other form of markup. You can use the tools given to produce the result you want. It strikes me as modern cargo-culting to expect cloud providers like Google to cater to niche crowds. We already know they don't care very much about the long tail. If Drive isn't supporting markdown, it's pretty obvious by now that it is not a priority for them. And the tone of the title on here is pretty damn presumptuous. It's like new gamers complaining that some new game doesn't come with photo mode, cloud save, 100% customizable clothing, etc, all these optional things that used to be ancillary but are now somehow a requirement. Which Markdown flavor would they support? My issue with Markdown is that is at least a half dozen different ways of rendering Markdown. At least the default, non-opinionated flavor, without the tables and math formula support and stuff like that. Nobody gets promoted over supporting open source standards at google anymore... well except maybe in some parts of their backend. I don't think they'd actually remove the functionality of it was added but I bet adding it would be an uphill struggle No SVG support in Slides either. Adding a video sometimes takes hours. Google products are low-end adware. What, specifically, is "the full Markdown experience"? Both figuratively and literally. Get yourself an old-fashioned web-space, setup a nextcloud instance ... profit. Already using a Synolgy DSM server - and it's a great experience - but, most (the rest) of the world is running on Google services, this is the reality, so, when it comes to sharing and collaboration capabilities, you're kinda stuck on the outside. I don't really like spreading too thin by using a ton of (more or less overlapping) services instead of using just one (Drive). I dunno, why can't I add a WebP image to a google slides presentation? And no support for collapsing/folding text under headings... Markdown is a markup language. Google Docs is a WYSIWYG document editor. These are two fundamentally different approaches to the creation of written content. This question is kind of like asking why you can't edit Illustrator projects in Photoshop. This was not about Google Docs at all, but about Google Drive. As anybody knows, you can let 3rd party apps do extra stuff with your Drive content, but the point is: why not natively support Markdown inside Drive. Besides, text content is also content. You just open a markdown editor, that has built in Google Drive support. And edit from there. You are missing the point. I am spending most of my day inside VS Code, using it for writing Markdown content as well. Apples to oranges. I don't want the author of some 3rd party obscure app looking at my content without my consent. I don't say I trust Google 100%, but I trust Google more than 3rd parties that I know nothing about. Also see my other comment: https://news.ycombinator.com/item?id=36466406#36467459 Why do you trust Google and Microsoft, companies known to spy on their users, rather then some small company who would go under if someone found out they spied on their users? I'm not saying everyone that's using Google or Microsoft are stupid, I'm trying to understand why people trust Google and Microsoft, is it because so many are already using them, or is it that you have been using them for a long time because you had no other choice ? I rented to a meth addict once upon a time. After we finally evicted him, the house was strewn with several ambitious but abandoned projects. Almost as bad as Google.