Hmm I'm not sure if this is solid parametric CAD. It let me draw a rectangle and then extrude that giving a zero-width tube... There doesn't seem to be any way to add dimensions either.
Definitely loads quickly though and feels snappy. But for actually getting stuff done FreeCAD is definitely the best FOSS option at the moment.
Yeah Pylint catches this. If you aren't using Pylint you are writing bad Python.
Can't downvoted truth.
It is hard, but what's the alternative? Does Linux want to be comically insecure forever?
I know Linus doesn't really care about security so it's kind of surprising that he is on board with Rust!
Rust async has quite a lot of footguns that other async runtimes don't have. There are some listed here:
Honestly if you're using an async Rust web framework (which they pretty much all are) it may be the path of least resistance to still use async. But in general I would strongly prefer scoped threads, channels, rayon etc.
many simultaneous requests
Unlikely to be so many that threads would be an issue.
I have 32 GB but it's not enough. Try opening 8 instances of VSCode, Firefox and Chrome with a few dozen tabs. Unfortunately my laptop doesn't support 64 GB of RAM.
It's significantly less of a nightmare and Deno is downright pleasant.
On Arduino it's 16 bits. (At least the original ATMEL ones; I dunno if they've finally moved to ARM yet.)
This lost me quite a lot of time when I tried to use their SD card library on a 32-bit Arduino and it hung due to some code assuming int was 16 bits.
That's a lot easily than learning the C to the same level and they "force" everyone to learn C.
Yeah that's pretty unreadable IMO. I think your second link isn't what you intended?
Yeah exactly that. Conceptually it's far superior to manyrepos. But it does have downsides:
git will be slower, and it doesn't really have great support for this way of working. I mean it provides raw commands for partial checkouts... but you're kind of on your own.git log --graph any more since there will be just way too many commits. Though tbf you can get to that state without a monorepo if you have a big project and work with numskulls who make 50 commits for a small MR and don't squash.Also it's not really a downside since you should be doing this anyway, but you need to use a build tool that sandboxes dependencies so it can guarantee there are no missing edges in your dependency graph (Bazel, Buck, Pants, Please, Landlock Make, etc.). Otherwise you will be constantly breaking master when things aren't checked in CI that should be.
What do you mean? I have yet to work for a company that's organised and sophisticated enough to actually use a monorepo but my understanding is you'd set up something like Bazel so it only builds & tests (and I guess deploys) things that depend on your change.