For that you would want to focus on free energy and food replicators because once you have that, there's not much reason to work anymore.
No matter what, you're still going to need someone in a red shirt to duck into the circuit bays and reverse the polarity.
Someone didn't live through the loss of the floppy drive, DB9 ports, and parallel ports.
In my day, to plug in a mouse: We took the box apart, installed a proprietary bus card, and then tried to figure out non-conflicting spots for the I/O and IRQ jumpers. Then we typed a bunch of gibberish into AUTOEXEC.BAT. And we liked it!
Not at all. Free citizens picking lettuce on a corporate-owned ranch is the American Dream!
It's better than medieval serfdom was because you're FREE!!! You could even prove it by wearing a giant bald eagle and flag T-shirt while you work!!!
A whole bunch of opportunities have recently opened up to US citizens for picking lettuce.
At least Nixon had the class not to force his minions to take all of the credit for the Apollo missions in their press releases.
That's what Trump did here: Same as usual he took all of the credit for other peoples' work.
You wonder why he gets under peoples' skin? It's because essentially everything he does is some kind of asshole move like this.
Yeah, that's why everyone gives Nixon credit for putting a man on the moon.
I meant using a pointer to the base of a buffer, then writing data beyond the end of the buffer the pointer refers to.
How are you going to get a buffer overflow on an integer or float scalar?
Those happen on arrays and pointers, whether on the stack, heap or global static spaces. You can also overflow the entire stack using unbounded recursive function calls, but that's a different issue.
Your seem to be totally ignorant about how different data types work.
Scalars on the stack are "automatic" variables. There is no explicit memory management needed by the programmer. They are pretty safe, as long as you don't do stupid C casting tricks.
The "certain things" you refer to includes using *any* pointer or array value in any way, including allocating, freeing, indexing and dereferencing. That essentially means any operations on items other than the automatic scalars I already covered. (For completeness, we can also consider "plain old data" structs lacking embedded pointers or arrays to be as safe as scalars, and globally allocated scalars and POD structs to be relatively safe, even if generally not good practice.)
So these things he says aren't true? He said that he was being forced to do memory safety when it wasnt even a concern and that the compiler was slow. Was he wrong about that?
Yes. Unless all of your variables are floats and integers on the stack, memory safety is always an issue when you write code in C. (If all of his values were actually floats and integers on the stack, he would have had no problem writing the Rust code either.)
Pro tip:
This article is not about ITER.
Basically, I want the government to have as few options for rewriting history or burn bagging documents without screwing up publicly accessible metadata as possible
Indeed, if they had implemented blockchain back in 2019, it would have been plainly obvious if someone had retroactively revised government hurricane prediction plots with a Sharpie.
Well, let's hope he fed the hungry.
The first fate that popped into my mind was:
#23 - Sichuan Pork with Egg Roll ***
At least in your information silo they aren't.
It sickens me that some of the most fertile land in the country, if not the world, is being covered by solar panels.
If a shortage of corn becomes a problem in the future, the panels can be removed. In the meantime, if the extra electricity speeds the adoption of EVs, then we can *burn* less of our food in ICE cars. We're currently dedicating more than a third of all those cornfields just for that. There's no plausible scenario where a third of all the cornfields would be converted to solar arrays anyway.
Their idea of an offer you can't refuse is an offer... and you'd better not refuse.
