Readit NewsI'm not a programmer, though - engineering manager.
Power saws really reduced time, lathes even more so. Power drills changed drilling immensely, and even nail guns are used on roofing project s because manual is way too slow.
All the jobs still exist, but their tools are way more capable.
I don't know the details of DNG but even the slightest complication could be a no-go for some manufacturers.
As a summary: The most common way given in C textbooks to iterate over an array is "for (int i = 0; i < n; i++) { ... array[i] ... }". The problem comes from these three facts: (1) i is a signed integer; (2) i is 32-bit; (3) pointers nowadays are usually 64-bit. That means that a compiler that can't prove that the increment on "i" won't overflow (perhaps because "n" was passed in as a function parameter) has to do a sign extend on every loop iteration, which adds extra instructions in what could be a hot loop, especially since you can't fold a sign extending index into an addressing mode on x86. Since this pattern is so common, compiler developers are loath to change the semantics here--even a 0.1% fleet-wide slowdown has a cost to FAANG measured in the millions.
Note that the problem goes away if you use pointer-width indices for arrays, which many other languages do. It also goes away if you use C++ iterators. Sadly, the C-like pattern persists.
[1]: https://gist.github.com/rygorous/e0f055bfb74e3d5f0af20690759...
I'm afraid humanity is blowing it for good with this.
Reverse chronological is sacrosanct and it will always remain ad free to keep incentives aligned with it being a place I like to spend time. Every tag also has its own RSS feed.
It's still invite-only, but anyone reading this page is obviously a great fit so here's an invite link: https://lynkmi.com/accounts/signup/?invite_code=333ee833-e3d...
https://aosabook.org/en/index.html
Maybe that would be a good start. You can then pick a project to dive in.
As a more specific tip, I've done some hacks in Nginx long time ago and found it quite nice.