no it doesn't, you just have to add them for apps yourself. the readme has a whole section dedicated to live tiles.
brian
wait until you hear about jazelle
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
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.
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?
they might ship a proprietary lib with their os, encourage developers to use it, then license it out of being distributed