I went and read Rob Pike's comments in the thread linked (I'm not a Go person so don't see anything he normally says). It's crazy that this person is listing his comments as a pro, or that he gets any reverence whatsoever. he seems absolutely insufferable.
brian
joined 2 years ago
I'm not sure to what extent anymore, but theia does depend on some vscode components, at least monaco. it's a little distance but still the same family.
if they're against vscodium I'm not sure if theia is significantly better
Bob Martin himself having moved to a different category
yeah, it's a setting in the official rpi imager nowadays
No, CI validates that the hooks or formatter ran, and fails if not. in theory it shouldn't ever fail but it's to catch the stuff that couldn't have passed the commit hook.
the hooks are easy to turn off and can be hard to get to reliably run (90% of the time they're fine, but all of the tools that run git commands sometimes do weird things), but they're a best effort kind of thing.
unit tests on precommit are a little annoying, especially when it takes that long. that's better suited to running in ci afterwards since there's no advantage to running before you commit. formatter takes like 200ms max for affected files? you won't notice, and it ends up as part of the one commit
pre commit hook and ci task. even with common formatters like prettier I do that on anything somewhat large
are there not just 2 main libraries or so that all the compositions implement it via?
I'm so confused. this is neither helpful for a beginner nor correct for anyone.
there are more aggressive css "resets" that set the default display type to flex. there's no problem making anything a flexbox if it displays the way you want it to
objectively the one with the cult is a good recommendation for a beginner since there's a strong community making content, arguably the most important factor in choosing something
godot also has a lot of stuff baked in, so the community tends to use the built in solution for everything. you won't end up with one tutorial recommending a collision engine that makes assumptions that don't work with the other tutorial for different pathfinding or whatever. they all start with basically the same assumptions.
pygame is a little intimidating since you start with an empty file and a pygame import. there's no real enforced or even commonly followed structure beyond that. beginners can figure it out but it leaves a lot of architecture questions open for you so your tutorials probably won't line up well.
and I say all of that as someone who doesn't particularly enjoy godot, especially gdscript.
yeah but like, his other comments are purely inflammatory, there's even a "you can't hold me accountable, I was quoting the bible!" line
sorry, entirely unrelated to the original post, just bothered me that this guy was being discussed in a positive light lol