

Yup, just look at what happened to De Blasio. Mild criticism and they kidnapped his daughter.


Yup, just look at what happened to De Blasio. Mild criticism and they kidnapped his daughter.


Seems like it’s mostly error handling, which makes total sense to me.
In a function with a lot of error conditions, where it also takes more than return <nonzero value> to report that error, the code would get very cluttered if you handle the errors inline.
Using goto in that case makes the normal case shorter and more readable, and if proper labels are used, it also becomes clear what happens in each error case.
Sure, you can do that with functions too, but it’s much nicer staying in the same scope where the error occurred when reporting on it. Putting things in a function means thinking about what to pass, and presents extra resistance when you want to report extra info, because you have to change the function signature, etc.


Not unless you choose really slow hard drives, or stream very high bitrate media. Most hard drives can easily do 100MB/s sequentially (i.e. reading a large file, such as long video files). Meanwhile high-bitrate 4K video is only about 50Mbit/s, so about 6MB/s.

*they’re fiscally conservative with redistributing money to the poor. All governments redistribute money, you can’t run a government without doing that. We should be making that clear, and then argue for redistribution to regular people, instead of the rich which is happening now.


C on Morello (or any other capability machine).
And much before that it was rule-based machine learning, which was basically databases and fancy inference algorithms. So I guess “AI” has always meant “the most advanced computer science thing which looks kind of intelligent”. It’s only now that it looks intelligent enough to fool laypeople into thinking there actually is intelligence there.
Just zip-tie them to a cnc mill and let fusion360 generate a toolpath. Do check for collisions with the “workpiece” though…