Julian (the author) is a genius. v4 has been in the making for some time, but, boy, is it worth the wait! I have used v3 (I am using it on my landing page and even built a small game engine with it), but this version is on a whole new level. Congrats to the author! Keep up the good work!
Yes. Yes. Yes. A million times, yes. I can't stress this enough: always put visible timestamps on all content (be it web or otherwise, online or offline) and current version number for any kind of software (apps, libraries, frameworks, etc.) on their info / landing / documentation pages.
It should be immediately visible if a certain content is dated or not.
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.
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.
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).
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.
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.
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.
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).
'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%
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.
Tried "transparent dog", got rickrolled. Why is this NSFW? ...anyway, I disabled the filter and... it's pretty neat! Calling all AI Overlords, soon. :))
OP, please, spellcheck your articles. I found so many typos and spelling errors in that article, I don't even know where to start. So, I'll just start with this: please use a spellchecker - they're free! Otherwise, keep up the good work and be free (self-host / own your stuff)! There's a back-to-roots movement going on, where people want to own their stuff. The more, the better!
angular, react, vue, svelte, lit, oh boy, so much bloat.
how about getting a hold of your sanity and allowing yourself a few hours to learn https://riot.js.org/ - almost no learning curve, only pure awesomeness. even if you won't use it in the enterprise (because policies, bla bla), it is still worth knowing things can be done differently - in a good way.
good things come in small packages.
:) who said anything about react? react has been aggressively advertised for so long that it's the "default" in devs' minds when talking about JS framweorks/libs. There's lots of other frameworks and tools these days to choose from (if not dictated by corporate policies), the World is a very big place. Anyway, though, I quit developing angular since v6, good to see solid progress.
...wait! are you guys still using this in 2021 (almost 2022)? :) Jokes aside, I hear less and less people (friends from the dev scene) using Angular these days. Wonder if it's just what happens to stuff (especially, software-related) after it matures... it gets out of sight, does the job, but nobody talks about it anymore.
It's as if Epic invented the (unheard-of - pun intended) word "unreal"... it's like saying yoga people (yogi?) should bring Lucasfilm to court for the fact that Yoda sounds a lot like Yoga... this world is more f**ed by the day...
Thanks! That's kinda what I need - some hierarchy of a lot of components of various kinds, maybe from a working (preferably big/huge) project with tons of nested pieces. Usually, methodologies like BEM, OOCSS work for a certain direction, but those are more like guidelines, not actual directory/filesystem-wise organization.
I use my own system dubbed NL0 (N = Now, L = Later, 0 = Never). I keep a Trello board online with these 3 columns, and once in a while I clean it up (maybe once every month, but it's not a rule - whenever I feel like it).
I also write things and ideas on paper, but, eventually, I sync it all up in the Trello board (I also have Trello on my phone, so, it's usually around when I need it). The [Now] column is for things I need to do / learn now (highest priority); the [Later] column is for things that I need or would like to do / learn later, in the medium-term future; the [0 (never)] column is for things that I am sure I won't do / need, or things that represent no meaningful value (for me) anymore, including things from the other 2 columns. It's been working for me for years now.
P.S.: I keep talking about things that you need to "learn" / "do". Actually that sums up everything we do in our lives. We either learn something or we use what we already learned. Keep learning, keep doing!