[1] https://github.com/toml-lang/toml/blob/master/README.md#L8
530 karma · joined June 24, 2019
[1] https://github.com/toml-lang/toml/blob/master/README.md#L8
edit: I see similar examples on the og hn thread https://news.ycombinator.com/item?id=1627342
[1] https://github.com/redwoodjs/redwood/commit/e2ceb0dcdffe4c28...
I don't think it was meant to impress. On the contrary I think the overarching point of the whole article was that it's okay to not know things outside of your domain that may seem trivial to other CS folks.
> Not knowing modern CSS - how can this person possibly work in any sort of cutting edge web development and not know about that?
Well, I don't know how he does it anymore than you do. But it looks like he's still working on cutting edge web development and it seems to be working out, so my takeaway is that he doesn't need to know about it plain and simple.
I can relate to that a bit, especially CORS since I never bothered to see what was up with that at a deep level either. Honestly just used a module for Flask when needed to get it working there and set up a CORS proxy on a cloudflare worker for a different project and called it a day.
Maybe that's how it went with him too. I'd call this something like "Laze Driven Development"—learning just enough to solve the problem (like my experiences with bash scripts).
I will say, however, that NYT looked quite aesthetic in dark mode.
I remember some university doing something similar as a workshop, but I can't recall which.
Over the course of classes, sometimes they do require you to use the command line but then they will just give you the commands to copy paste, without explaining what any of it does.
I feel like it's the opposite, vim is my swiss army knife for working with rust or cpp or python whenever I want whereas the IDE is something I open to work on specific, more complex projects where I just care about getting something done (like my homework).
Only qualm would be line number color contrast being mostly terrible, but I don't really need it as much.
What would be kind of interesting is if it would read vim colorschemes, so your cat output is syntax highlighted like if you were editing it.
[1]: https://gitlab.com/fuck-capitalism/spotifykeydumper/-/releas...
For what it's worth, I just took a glance at required PyCharm specs.¹ They recommend 8GB and minimum 2GB ram, which seems a bit dumbed down. I can't imagine anyone being able to properly run it without at least 4 gigs of ram even if they have nothing else running.
[1] https://www.jetbrains.com/pycharm/download/#section=windows
I've been slightly switching the opposite way, using vim more and more for smaller stuff and opening the IDE only for larger projects or work stretches. I definitely love the value of vim as a nifty tool, my workflow is noticeably faster.
As an aside, that cheeky :wq is not missed by me at all, :x all the way!
[1] https://about.gitlab.com/devops-tools/github-vs-gitlab/#comp...
probably an unpopular opinion but I really like fish scripting more than bash, the syntax is way more intuitive and I don't find myself missing bash at all.
[0]: https://z.cash/technology/zksnarks/
[1]: https://www.getmonero.org/get-started/faq/#anchor-different
that's not very interesting because when I find an interesting read I rarely bookmark it. For me bookmarks are links that I visit often.
> b)
that is a fair point, however I think the wayback way is still not too shabby an idea. It ensures there's a copy snapshotted just in case, and yes it might not last forever but it's done a fantastic job so far so not trusting it now just because it'll not survive sounds a minor risk imho.
from a programming perspective, you might want to split it into multiple files, definitely separate test cases from the main file.
Being unhappy with a service doesn't mean you get your subscription cancelled.