No, "most of the western world" typically actually means "the whole western world, except for exactly one country, which is ass backwards on the issue", most of the time, that country is the USA.
More than that - this software only exists because Microsoft continues to support it. If Microsoft simply dropped support, then they would end up in a situation where people actually made sure their code was maintained, and ran on modern systems correctly without hacks.
But the average case application runs more quickly due to the increased number, and size of registers, and increased number of operations that are guaranteed to be available on the CPU.
In the UK, any more recent law that contradicts an older one is deemed to be correct. In this case, if this law says you can make backups, and the (older) EUCD says you can't, this law wins out.
That is so not true that I think you are trolling. If not you must be an engineer because you are worrying about levels of precision that simply rarely matter.
As mentioned above, 1 "cup" of flour can vary by 30%, simply from the humidity of the air, and the compactness of the flour. Add to that a ~10% variation simply from exactly how level your cup is, and you're at around a 40% variation in how much flour you're putting in a recipe. That's enough to go from a bread that's fucked up because the dough is liquid all the way through to a bread that's fucked up from the flour not incorporating properly.
Almost all baking requires precision, almost all deserts require precision, and many main courses require at least more precision than "you can be 50% out with the quantities".
Metric is no more accurate than US customary units.
No, the issue is that the use of it is much more accurate, as expressed above, the americans have a deer love of using the wrong units even within their own system.
They use volume units for compressible things
They use volume units for undeformable things
They use volume units for things with large air gaps between them and inconsistent shapes They use the same words for volume and mass units (oz in the US can interchangeably mean ounces or fluid ounces for example)
In general, trying to follow a US recipe that needs some level of accuracy is basically impossible. If you're trying to bake bread, you'd better have a metric recipe, or you're screwed.
The reason is, 125ml and 250ml have no practical relationship, while "1 cup" and "1/2 cup" do. So when a recipe calls for 1 cup of anything, you can measure that quickly. If it's half a cup, then you use half a cup, or if you have it calling for 1.5 cups, you use the 1/2cup 3 times.
Actually, cooking is the one place that US imperial measurement drives me up the fucking wall. 1 cup of something trivially measured by volume isn't so bad, though 100ml is just as easy to measure. The big issue is when you get to "1 cup of flour" or "1 cup of butter" - things that are much more easily measured by mass, or things like "1 cup of cherry tomatoes" where the amount you get will vary based on the size and density of the particular tomatoes you have today.
Basically, no, the kitchen is exactly the place I want metric measurement - it is if anything the best example around a house of where you need accurate scientific style measurement.
We do now know why the Russians and Americans are starting to posture over Eastern Europe though... They know there's the potential for a war, and are positioning themselves for it.
No, the JEDEC standard actually agrees with the IEC one - it states that for memory you can optionally use the SI prefixes with binary calculations, but that for storage you should use base 10 computations with the SI prefixes.
That was pretty silly of you, given that data isn't stored in powers of two. When was the last time you saw a hard disk with an exact power of two capacity?
No, a "traditional" GB is the one that was defined way before computer scientists got their hands on it –1000. The 1024 "definition" is actually simply a bug. Engineers working on early machines had a choice – take a bug that pretty much no one would notice on an early machine (because files over 1kB were very rare, much less ones over 1MB), or take a massive perf hit. It takes a long time to compute the size of 20 files when a division by 1000 takes 300 odd cycles on a 10kHz machine. It doesn't take such a long time when a right shift 10 takes 1 cycle.
Bottom line, early engineers decided a known bug was better than the enormous perf hit of getting it correct. That doesn't mean that what they did is now correct. It means it remains a bug in some OSes.
On the contrary, 4Mb/s is almost certainly not enough (by the time you take into account contention etc) to stream video. Something like netflix will not work over that, and frankly, I expect any definition of broadband to include the ability to use a video streaming service.
There's no particular reason to not have comparable values of different types
Sure there is - they have different types, therefore they're not equal. It's a ridiculous, useless operation, because it doesn't actually do anything more than always return false.
That said, there's good reason to have an "isSimilarTo" function, but that's not at all the same thing as equality.
No, ultimately, their job is to carry passengers. That means they need to offer enough space for a passenger to sit in. The airline's only choice is to not shrink the seats any more. This may of course mean price increases for all seats.
Even if it were the original code. That would mean that the modder is the one violating mojang's copyright, not the reverse.
Re:bringing in more H1Bs will solve this problem
on
IT Job Hiring Slumps
·
· Score: 1
Actually, compiler theory is a great example of a language you can't easily learn in any language. The small lightweight structures it generates, and the referentially transparent transformations that you run those structures through lend it strongly to being done with functional languages, and if not, very close to the metal languages like C. Heavy weight OO languages tend to end up just causing you to write 3 tons of boiler plate, rather than actually learning the theory.
You shouldn't. You should (in all languages), explicitly convert the type, and then compare things of equal type. For bonus points, you should only use languages that enforce that the arguments to == are of equal type.
Slashdot Mirror
No, "most of the western world" typically actually means "the whole western world, except for exactly one country, which is ass backwards on the issue", most of the time, that country is the USA.
More than that - this software only exists because Microsoft continues to support it. If Microsoft simply dropped support, then they would end up in a situation where people actually made sure their code was maintained, and ran on modern systems correctly without hacks.
But the average case application runs more quickly due to the increased number, and size of registers, and increased number of operations that are guaranteed to be available on the CPU.
In the UK, any more recent law that contradicts an older one is deemed to be correct. In this case, if this law says you can make backups, and the (older) EUCD says you can't, this law wins out.
It doesn't –but measuring 100 grammes of cherry tomatoes makes things a lot easier ;).
That is so not true that I think you are trolling. If not you must be an engineer because you are worrying about levels of precision that simply rarely matter.
As mentioned above, 1 "cup" of flour can vary by 30%, simply from the humidity of the air, and the compactness of the flour. Add to that a ~10% variation simply from exactly how level your cup is, and you're at around a 40% variation in how much flour you're putting in a recipe. That's enough to go from a bread that's fucked up because the dough is liquid all the way through to a bread that's fucked up from the flour not incorporating properly.
Almost all baking requires precision, almost all deserts require precision, and many main courses require at least more precision than "you can be 50% out with the quantities".
Metric is no more accurate than US customary units.
No, the issue is that the use of it is much more accurate, as expressed above, the americans have a deer love of using the wrong units even within their own system.
They use volume units for compressible things
They use volume units for undeformable things
They use volume units for things with large air gaps between them and inconsistent shapes
They use the same words for volume and mass units (oz in the US can interchangeably mean ounces or fluid ounces for example)
In general, trying to follow a US recipe that needs some level of accuracy is basically impossible. If you're trying to bake bread, you'd better have a metric recipe, or you're screwed.
The reason is, 125ml and 250ml have no practical relationship, while "1 cup" and "1/2 cup" do. So when a recipe calls for 1 cup of anything, you can measure that quickly. If it's half a cup, then you use half a cup, or if you have it calling for 1.5 cups, you use the 1/2cup 3 times.
Actually, cooking is the one place that US imperial measurement drives me up the fucking wall. 1 cup of something trivially measured by volume isn't so bad, though 100ml is just as easy to measure. The big issue is when you get to "1 cup of flour" or "1 cup of butter" - things that are much more easily measured by mass, or things like "1 cup of cherry tomatoes" where the amount you get will vary based on the size and density of the particular tomatoes you have today.
Basically, no, the kitchen is exactly the place I want metric measurement - it is if anything the best example around a house of where you need accurate scientific style measurement.
We do now know why the Russians and Americans are starting to posture over Eastern Europe though... They know there's the potential for a war, and are positioning themselves for it.
How is a California company selling to an Iowa customer not interstate commerce?
The problem is that OOP languages rarely have more readable code. Instead, they typically have simply code with more boiler plate.
Given that he explicitly said he wasn't going to build the hyper loop... It seems to be working out pretty much exactly as he said.
Last I checked the prime factors of 125829120 were 2, 3 and 5, and it very much was not a power of two because of that ;).
No, the JEDEC standard actually agrees with the IEC one - it states that for memory you can optionally use the SI prefixes with binary calculations, but that for storage you should use base 10 computations with the SI prefixes.
Yes, because your OS incorrectly computes the number of GB. It computes the number of GiB, and then displays GB.
Notably, if you stick that same terabyte drive in a mac, or many linux boxes, it'll register as 1TB.
Why are you talking about memory at all in an article about permanent storage?
That was pretty silly of you, given that data isn't stored in powers of two. When was the last time you saw a hard disk with an exact power of two capacity?
No, a "traditional" GB is the one that was defined way before computer scientists got their hands on it –1000. The 1024 "definition" is actually simply a bug. Engineers working on early machines had a choice – take a bug that pretty much no one would notice on an early machine (because files over 1kB were very rare, much less ones over 1MB), or take a massive perf hit. It takes a long time to compute the size of 20 files when a division by 1000 takes 300 odd cycles on a 10kHz machine. It doesn't take such a long time when a right shift 10 takes 1 cycle.
Bottom line, early engineers decided a known bug was better than the enormous perf hit of getting it correct. That doesn't mean that what they did is now correct. It means it remains a bug in some OSes.
No, that would be MibiBytes and GibiBytes. A GB is 1000 times larger than a MB.
On the contrary, 4Mb/s is almost certainly not enough (by the time you take into account contention etc) to stream video. Something like netflix will not work over that, and frankly, I expect any definition of broadband to include the ability to use a video streaming service.
There's no particular reason to not have comparable values of different types
Sure there is - they have different types, therefore they're not equal. It's a ridiculous, useless operation, because it doesn't actually do anything more than always return false.
That said, there's good reason to have an "isSimilarTo" function, but that's not at all the same thing as equality.
No, ultimately, their job is to carry passengers. That means they need to offer enough space for a passenger to sit in. The airline's only choice is to not shrink the seats any more. This may of course mean price increases for all seats.
Even if it were the original code. That would mean that the modder is the one violating mojang's copyright, not the reverse.
Actually, compiler theory is a great example of a language you can't easily learn in any language. The small lightweight structures it generates, and the referentially transparent transformations that you run those structures through lend it strongly to being done with functional languages, and if not, very close to the metal languages like C. Heavy weight OO languages tend to end up just causing you to write 3 tons of boiler plate, rather than actually learning the theory.
You shouldn't. You should (in all languages), explicitly convert the type, and then compare things of equal type. For bonus points, you should only use languages that enforce that the arguments to == are of equal type.