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.
No Markdown support in Google Drive after all these years
71–80 of 107 posts
Re: No Markdown support in Google Drive after all these years
#72Earlier quoted context omitted.
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 unabl…
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.
Re: No Markdown support in Google Drive after all these years
#73Why 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.
Re: No Markdown support in Google Drive after all these years
#74Simple: 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. Addition…
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.
Re: No Markdown support in Google Drive after all these years
#75They'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.
Re: No Markdown support in Google Drive after all these years
#76Why 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.
Re: No Markdown support in Google Drive after all these years
#77Not 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."
Re: No Markdown support in Google Drive after all these years
#78Solution: use Obsidian and save in Drive.
Re: No Markdown support in Google Drive after all these years
#79Why 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.
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.
Re: No Markdown support in Google Drive after all these years
#80Simple: 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. Addition…
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.