blocks allocated by malloc are of fixed size, there is nothing new here
Wrong. The size of allocated blocks are typically computed at runtime to match the needed length of the input data. That's a big difference from defining some fixed-size buffers at compile time, then hoping or forcing all of the eventual input data to fit.
When the developer avoids allocation headaches by using fixed-sized strings and data structures, users are often saddled with arbitrary truncations and the need to make up funky abbreviations all throughout their data sets. This can be a major source of errors in itself.
Jesus that is scary as fuck. It's certainly not the oil, aluminum, food, flight attendants, or pilots that have gotten any cheaper, so I assume most of the cuts have been to safety.
Oil: Wrong Aluminum: Wrong Food: What food? Flight attendants: Wrong Pilots: Way wrong
Not to mention: Much smaller seats Odds of sitting next to an empty seat to spread out onto: used to be good, now nearly zero.
As for safety, there used to be major air disasters in the USA about once per year. How long has it been now? I don't recall one in the last decade.
What would happen if someone wrote, say, a kernel, in C!?!
The users would probably be subjected to an endless treadmill of updating their kernel packages and rebooting each of their machines every couple of weeks.
We should all be thankful for the phenomenal advances in computer technology that have made it possible to accommodate the extra bandwidth and storage that will be needed for this.
This is no worse than back in the 1960s when Ma Bell used to have its people listen in on all phone calls and write down the topics discussed on decks of index cards for each phone account. They then sold stacks of these cards to outfits like Montgomery Ward and S&H Green Stamps, which helped them to mail out coupon offers tailored for customers' interests. They only sent copies to J. Edgar Hoover when he said there was a good reason.
The U.S. Post office enhanced their revenues with a similar program steaming envelopes (note that stamps only cost a couple of cents back then, so it sure was effective at holding down prices). It was a win-win for everybody; what's the big deal?
There has been A LOT of added functionality since Windows 3.1 days! Not just changes in the UI, but changes to security, API's, and so on. Windows, and for that matter other operating systems, are far more complex than they have ever been.
Possibly, but at least developers don't have to deal with the segmented memory model and other 16-bit limitations from Windows 3.1. Writing programs to run in the original 16-bit Windows API was one of the most byzantine things I have ever done.
The ONLY way that they wouldn't be is if the whole network is owned by one company and they were charging some "sheep IP licensing fee" from a low tax country.
Well, having one animal that's both woolly and tasty is certainly innovative. I'm sure that somebody must have patented it.
Java would only complain if you used integer literals that big, but such literals are usually unrealistic. Most often, problems like this happen because of results of calculations.
The fact is, Java would silently overflow computing an integer value of 99999999999999999999 unless you use BigIntegers or the equally awkward new APIs such as Math.addExact().
C# would also overflow unless you compiled with non-default settings.
JavaScript is actually superior in those cases because the floating point result would be approximately correct instead of way off like the integer results.
That's a problem because, for example it means 9999999999999999 is equal to 10000000000000000. Floating point comes with all kinds of errors. You're actually not supposed to ever compare to floating point numbers for equality, you're supposed to check whether the difference between them is small.
To be fair, in most other languages, 99999999999999999999 == 7766279631452241919, or maybe even == 1661992959. No matter what language you're using, you have to be aware of when and how your results may overflow.
Also, if you do calculations using exact integer values as inputs, assuming you avoid overflow, you can directly compare floating point representations as long as you use operations that stay strictly in the integer subset (such as +, -, *, but not/).
That's not an option. Unlike the park service, we can't put the genie back in the bottle and go back to the old ways, because nukes are already spread all over the world and they're not going away.
However, if there were no nukes, killing tens of millions every few decades would be preferable to introducing nukes and then eventually killing off most of the human race in a big holocaust every century or two., which is what's almost certainly going to eventually happen now.
Maybe you should go sit in a dinghy without any supplies in the middle of the Pacific ocean for a few days so you can find out just how useful all that "unlost" water really is.
Those figures aren't talking about drinking water for cows. That's a drop in the bucket compared to the water required to grow the corn that the animals eat.
And yes, a good fraction of the water used to grow corn is unsustainably mined from ancient aquifers.
but now that we know it's propped up with the human equivalent of dead leaves and brush, can we really continue?
We may not continue that long if people like Donald Trump and Kim Jong Un stay true to their nature and start acting like kids playing with Zippo lighters.
My analogy is spot on. 70 years of fortunate luck (despite multiple very close calls) proves nothing.
The 50 years of post WWII peace and stability in the world that these tests have blessed us with is well worth the 'poison' it generated, which has had minimal measurable impact on the world. In exchange, millions of lives have been saved that would have otherwise been lost in wars.
Relying on nuclear weapons to suppress human conflict is like when the National Park Service meticulously suppressed every forest fire.
Things went great for a while, until unburned fuel built up and got out of hand in a catastrophic conflagration that was far worse than what the sum of all the smaller fires would have been.
We're trying to buy up a few new operator stations for a very large chemical plant before the only thing left with which we can control the plant is... Windows 10.
You should make the migration now. Then you would get informative pop-ups that could help you improve your manufacturing process:
It looks like you're synthesizing "polycaprolactone". Users of that compound were also interested in: polybutadiene, polymer initiators, reaction vessels, and industrial tubing. Click [here] to shop now.
By 1990, shortly after Reagan left office, almost 20 million people had 401(k) accounts. Today, they hold $4.8 trillion in assets.
Thus creating a huge moral hazard for Wall Street. Every time the stock markets tank like they did in 2008, they will be bailed out by the taxpayers in order to save all of those 401(k)s owned by retirees. The net effect of this implicit insurance policy is one of the largest social programs ever created.
Slashdot Mirror
blocks allocated by malloc are of fixed size, there is nothing new here
Wrong. The size of allocated blocks are typically computed at runtime to match the needed length of the input data. That's a big difference from defining some fixed-size buffers at compile time, then hoping or forcing all of the eventual input data to fit.
Everything in life is a tradeoff.
When the developer avoids allocation headaches by using fixed-sized strings and data structures, users are often saddled with arbitrary truncations and the need to make up funky abbreviations all throughout their data sets. This can be a major source of errors in itself.
You realize that was exactly point I was making, right?
So you're saying that the railroad industry has been greenwashing ever since the early 20th century with the term "diesel-electric locomotive"?
Jesus that is scary as fuck. It's certainly not the oil, aluminum, food, flight attendants, or pilots that have gotten any cheaper, so I assume most of the cuts have been to safety.
Oil: Wrong
Aluminum: Wrong
Food: What food?
Flight attendants: Wrong
Pilots: Way wrong
Not to mention:
Much smaller seats
Odds of sitting next to an empty seat to spread out onto: used to be good, now nearly zero.
As for safety, there used to be major air disasters in the USA about once per year. How long has it been now? I don't recall one in the last decade.
What would happen if someone wrote, say, a kernel, in C!?!
The users would probably be subjected to an endless treadmill of updating their kernel packages and rebooting each of their machines every couple of weeks.
We should all be thankful for the phenomenal advances in computer technology that have made it possible to accommodate the extra bandwidth and storage that will be needed for this.
We can rid ourselves of this $1e11 white elephant by entering a few simple commands:
Destruct sequence 1 code 1 1a
Destruct sequence 2 code 1 1a 2b
Destruct sequence 3 code 1b 2b 3
Destruct sequence code 0 0 0 destruct 0
This is no worse than back in the 1960s when Ma Bell used to have its people listen in on all phone calls and write down the topics discussed on decks of index cards for each phone account. They then sold stacks of these cards to outfits like Montgomery Ward and S&H Green Stamps, which helped them to mail out coupon offers tailored for customers' interests. They only sent copies to J. Edgar Hoover when he said there was a good reason.
The U.S. Post office enhanced their revenues with a similar program steaming envelopes (note that stamps only cost a couple of cents back then, so it sure was effective at holding down prices). It was a win-win for everybody; what's the big deal?
There has been A LOT of added functionality since Windows 3.1 days! Not just changes in the UI, but changes to security, API's, and so on. Windows, and for that matter other operating systems, are far more complex than they have ever been.
Possibly, but at least developers don't have to deal with the segmented memory model and other 16-bit limitations from Windows 3.1. Writing programs to run in the original 16-bit Windows API was one of the most byzantine things I have ever done.
The ONLY way that they wouldn't be is if the whole network is owned by one company and they were charging some "sheep IP licensing fee" from a low tax country.
Well, having one animal that's both woolly and tasty is certainly innovative. I'm sure that somebody must have patented it.
Java would only complain if you used integer literals that big, but such literals are usually unrealistic. Most often, problems like this happen because of results of calculations.
The fact is, Java would silently overflow computing an integer value of 99999999999999999999 unless you use BigIntegers or the equally awkward new APIs such as Math.addExact().
C# would also overflow unless you compiled with non-default settings.
JavaScript is actually superior in those cases because the floating point result would be approximately correct instead of way off like the integer results.
That's a problem because, for example it means 9999999999999999 is equal to 10000000000000000. Floating point comes with all kinds of errors. You're actually not supposed to ever compare to floating point numbers for equality, you're supposed to check whether the difference between them is small.
To be fair, in most other languages, 99999999999999999999 == 7766279631452241919, or maybe even == 1661992959. No matter what language you're using, you have to be aware of when and how your results may overflow.
Also, if you do calculations using exact integer values as inputs, assuming you avoid overflow, you can directly compare floating point representations as long as you use operations that stay strictly in the integer subset (such as +, -, *, but not /).
That's not an option. Unlike the park service, we can't put the genie back in the bottle and go back to the old ways, because nukes are already spread all over the world and they're not going away.
However, if there were no nukes, killing tens of millions every few decades would be preferable to introducing nukes and then eventually killing off most of the human race in a big holocaust every century or two., which is what's almost certainly going to eventually happen now.
Maybe you should go sit in a dinghy without any supplies in the middle of the Pacific ocean for a few days so you can find out just how useful all that "unlost" water really is.
Those figures aren't talking about drinking water for cows. That's a drop in the bucket compared to the water required to grow the corn that the animals eat.
And yes, a good fraction of the water used to grow corn is unsustainably mined from ancient aquifers.
And watch it scream as you tear it off and cook it? Yeah, I'm down for that!!!
That's still not as cruel as the lives of all those boneless chickens they've been raising lately.
but now that we know it's propped up with the human equivalent of dead leaves and brush, can we really continue?
We may not continue that long if people like Donald Trump and Kim Jong Un stay true to their nature and start acting like kids playing with Zippo lighters.
My analogy is spot on. 70 years of fortunate luck (despite multiple very close calls) proves nothing.
No, I'm just pointing out what's probably going to end up happening to those who think that nuclear weapons are some kind of fix for human behavior.
The 50 years of post WWII peace and stability in the world that these tests have blessed us with is well worth the 'poison' it generated, which has had minimal measurable impact on the world. In exchange, millions of lives have been saved that would have otherwise been lost in wars.
Relying on nuclear weapons to suppress human conflict is like when the National Park Service meticulously suppressed every forest fire.
Things went great for a while, until unburned fuel built up and got out of hand in a catastrophic conflagration that was far worse than what the sum of all the smaller fires would have been.
Still worth investigating sufficient response that's more economical.
Maybe they could contract with that shotgun-toting old woman from Virginia.
... this conclusively disproves all of the naysayers who claim that the Patriot missile doesn't work.
So what exactly did you think "support" was?
Up until now, nobody thought that "support" was the logical inverse of "sabotage".
We're trying to buy up a few new operator stations for a very large chemical plant before the only thing left with which we can control the plant is ... Windows 10.
You should make the migration now. Then you would get informative pop-ups that could help you improve your manufacturing process:
It looks like you're synthesizing "polycaprolactone". Users of that compound were also interested in: polybutadiene, polymer initiators, reaction vessels, and industrial tubing. Click [here] to shop now.
By 1990, shortly after Reagan left office, almost 20 million people had 401(k) accounts. Today, they hold $4.8 trillion in assets.
Thus creating a huge moral hazard for Wall Street. Every time the stock markets tank like they did in 2008, they will be bailed out by the taxpayers in order to save all of those 401(k)s owned by retirees. The net effect of this implicit insurance policy is one of the largest social programs ever created.