There isn't really any RVA22 hardware you'd really want to run a desktop on anyway, so it's a very logical decision. RVA23 is a much more sensible base - it requires Vector and Hypervisor.
Yes I'm aware where Git came from.
Large files don’t work with git, as it always stores the whole history on your drive.
Not any more. That's only the default. Git supports sparse checkouts and blobless checkouts both of which only get a subset of a repo. And actually it has supported --depth for as long as I remember.
Yes this is true, but it's a little advanced for this level so I didn't mention it. Probably better for beginners to focus on good code style than optimal performance.
No but I think this is probably a great use case for AI. Haven't tried it though.
It doesn’t look like it would be hard to have (comment "foo bar baz") in an expression
That is pretty much what the official "solution" is for comments in package.json - add "//": "foo bar baz" keys to dictionaries and NPM will ignore them.
In practice it's terrible. You need real comments.
One nice thing about XML is that there's an official way to link to the schema from within the document. If you do that you can easily automatically validate it, and even better you get fantastic IDE support via Red Hat's LSP server. Live validation, hover for keys, etc.
It's a really nice experience and JSON schema can't really match it.
That said, XML just has the wrong data model for 99% of use cases.
I think either is probably fine. Apparently the French stress the syllables equally, not just the second so it's a minor difference.
Actually I just listened to the French pronunciation and it sounds more like they do stress the first syllable to me:
If that were really true then they would give users with 100k rep some benefit of the doubt when it comes to questions... but nope. Still get closed as "too vague" by people who haven't even heard of the thing you're asking about.
Does that not happen with Mercurial? If not that seems like a point against it.
That's exactly the same in git. The old commits are still there, they just don't show up in git log because nothing points to them.
This can work for junior devs who aren't stuck in their ways. Unfortunately there are too many "senior" devs who are happy making crap. It's hard to fight them constantly to do things properly (e.g. write actual commit messages rather than just "Fix #836") so using tools like linters where possible is definitely a big improvement.
FizzyOrange
0 post score0 comment score
joined 3 years ago
This comment perfect captures why I don't like Lisp. Essentially "it's simple, this easy to read code transforms to this AST". Lisp basically says "we can make parsing way easier if we force programmers to write the AST directly!" which is really stupid because computers can perfectly well parse syntax that is easy for humans to read and turn it into ASTs automatically.
It makes it easier to parse for computers at the cost of being much harder to parse for humans, which is really the wrong choice in most cases. (The exception is if you're DIYing your compiler, e.g. if you're teaching how to write a compiler then Lisp is a good target.)