Uhm, nope. Only those two models have a fix issued. On everything else, you do need to disable HT, which obviously takes a massive performance hit.
Those OCaml guys merely noticed and diagnosed the problem first -- your average mouth-breathing Windows user will have a game crash, a browser corrupt a Twitter page or MS Word lose data yet again, but that's what such users are used to. Yet that their systems are already crashy doesn't mean this extra source of crashes and data corruption doesn't matter.
As for your legendary "BIOS/UEFI updates", those can be relied on about as much as $YOUR_COUNTRY'S_PARLIAMENT to stop bribes towards their own members. Most of those "system vendors" don't pass fixes, and when they do, they're anything but timely.
The fix doesn't disable hyperthreading, the fix fixes the bug.
The fix works only for some models of Skylake (models 78 and 94, stepping 3). On any other Skylakes and all Kaby Lakes there's no way other than disabling hyperthreading entirely.
A fix might or might not be released in the future, Intel doesn't say a word about the issue.
At this point, I quite don't see a rational person hosting their data in the US or at a company with US presence. Because, you see, you got the 4th Amendment, we don't, right?
In fact, just to troll, I use KiB = 1000 occasionally.
Hell yeah. ~10 years ago I argued with a co-worker who thought I'm bullshitting him and that no one could be stupid/malicious enough to redefine such a fundamental unit that's in use for decades. And it was painful as he was a guy who used to bring me old punched tape for playing when I was in kindergarten (in commie land we had punched paper ribbon instead of punched cards).
With the program I had on screen (Debian-installer partitioner) saying "MiB", the old guy believed it's millions bytes, as obvious counterpart to 1MB=1048576. Mega vs million, the abbreviation looks pretty clear to me.
You don't want the filesystem to be misaligned wrt erase blocks, trust me -- especially on cheap flash. Measuring in actual GB means a naive user will get good performance without any special steps.
As for those "600MB videos on 9 GB" -- both real MB/GB and those silly millions bytes will be off. The filesystem has to store metadata somewhere. Videos can use large extents so we're talking about a fraction of a percent, but for smaller files the difference can be far bigger. And you really want to err on the safe side or that 1000th photo won't fit.
What if your filesystem has 1GB block groups, 4MB erase blocks, etc? With real gigabytes it's all nicely aligned. On the other hand, if you use drivemakers' units, either your partitioning program needs to ignore what it's told to do and do large rounding, or, even worse, the user needs to give really unfriendly numbers.
Not being able to hibernate 8GB ram into 8"GB" disk space is another problem.
1KB meant 1024 bytes for 70 years, it's no time to break everything just because some marketroid wanted a bonus.
the fact that no persistent storage device ever made has had any natural relation to 2^20, 2^30, etc.
How come? Disks use 512/4096 byte sectors, erase blocks of powers of two, etc -- not a single power of 10 around. And non-sleazy manufacturers who provide sizes in actual rather than marketing gigabytes do exist.
I got an unopened SD card whose back writing includes "1GB = 1,073,741,824"; I remember a few disks that mention their capacity in real giga/terabytes too.
We're not really going to find any place significantly better than a few of locations in the Solar System. Giving a planet a breathable atmosphere and letting that atmosphere stay will upset its heat budget so much the current values hardly matter. Not in comparison in what we can do by making that atmosphere more opaque or more greenhousey.
And we don't need FTL: if you want to get there in the flesh, I guess it's 50-100 years before we get a breakthrough that defeats aging. We'll then see a lot of health conditions that don't matter today but are fatal by the age of 200. Once we figure those out, there'll be another iteration at 1000 or so.
But then, hard AI can also be expected within those 50-100 years. That's a form of earthlings who don't suffer from biological limitations and can be beamed as a stream of bits as soon as you get a suitable receiver to the destination.
So while engineering issues on the way will be quite interesting, no fundamental research is needed to colonize the galaxy. Then we'll proceed to the Local Group, then shake our fists at the redshifted ghosts of galaxies that are not gravitationally bound to us.
You can still run 36-year-old programs just by double-clicking them on 32-bit Windows - and, of course, it still runs legacy 16-bit Windows programs too
Except that no one sane runs 32-bit Windows anymore (except expressly for compat purposes).
These days it's more likely an arbitrary Windows program runs on Wine than on the newest real thing.
If the toaster requires Internet connectivity to make toast, it will be returned ASAP and I'd post a warning online to keep others from buying that model.
Then your fire insurance won't get that 90% reduction (obviously paired with a 2000% bump of the base rate) as the data collection will be somehow marketed as a safety feature. A few years on, it'll be plain illegal to sell, then to own, a toaster without an Internet connection.
It does (C11 7.20.1.1.3) if the implementation supports any 32/64 bit integer types. I can't think of any incoming architecture in foreseable future lacking those. Even if not atomic, the compiler will emulate them. Otherwise, the fraction of our available corpus of software that will work on such an architecture would be uselessly small.
And even there, [u]int_least64_t are required, even in freestanding environment.
There's almost no reason to use "long". The only non-bogus things I can think of from the top of my head are memcpy implementation, bitwise operations and similar things on a block of memory when you want to handle a word at a time -- where doing it byte-by-byte would work just as well, merely slower.
Either your program needs to handle values >= 2^31/2^32, or it doesn't. In the first case, you use [u]int64_t, in the latter it should be int. Anything else introduces a pointless portability problem: int works as fast if not faster on 64-bit than long, too (at the very least by taking fewer cache lines when stored in memory).
As for values that deal with structure sizes, there's [s]size_t/[u]intptr_t.
The only nasty thing is printf() -- when using arch-independent types, you need that ugly %" PRId64 " stuff. It even breaks in C++ where some bright person had the idea to break compat and require a space after the " -- and your C code may be included into C++ when you don't expect.
From a technical point of view, only because it was more convenient and less costly.
But the real reason is, in almost all countries this tends to be "good enough" as no one will dare to attack you -- even if the attack itself can be easily anonymized, "cui bono" makes the attacker obvious (and a false flag operation would be pretty risky).
Except for Ukraine -- a country with a big powerful enemy it's currently at war with, and has no friends. It's beyond obvious who wants to destroy their power grid, but at this moment Russia has no real downside in revealing their hand. Thus, this is a show of strength.
Nope, not only he is (fulfils every requirement of not only the definition of fascism I quoted, but also pretty much any of them that's not specifically tailored to regime X), but is also specially notable here as he calls everyone else a fascist (usually not directly, but it's his propaganda machine's favourite insult).
Unlike what certain parties tell you, if you're A but claim to be B, you don't stop being A nor start being B. Whether it's communism "not a religion", christianity "not a polytheism" (4 main gods, thousands of minor deities), a pre-op trans (real)man a "woman", campaign donations "not corruption", a $SCRIPTURE-thumper a "good person", etc, etc. Call a spade a spade.
And unlike some of those who are merely deluded, Putin is highly intelligent and does his thing fully consciously.
On the other hand -- Russia is immune here, as they don't even know the concept of a fair election. They did not have a single one during their whole history -- not by the tsars, not by the soviets, almost had one by Yeltsin, then back to the usual. They don't even bother with any semblance of propriety: Chechnya voted 99.5% for One Russia (Putin's party) with 99.4% turnout; just 11 years after a second war against them led by said Putin.
You're using Bluetooth for something it wasn't designed for. You want regular WiFi instead.
As for playing music, why would you even consider using crap tinny headphones while at home? I have yet to see non-crappy bluetooth ones, and good ones are too heavy to be comfortable mobile (note: heavy doesn't imply good -- case in point: Apple's Beats are weighted to resemble good gear). Thus, for decent music you either use proper headphones when sitting or speakers. Speakers do not suffer from any wireless issues.
And even when mobile, attaching tinny headphones is much better done with a wire. You don't lose them once a week, get better sound quality, have them working non-stop without charging downtime every a short while, etc.
Those with fascist ideals are the fascists. It's that simple.
Yeah, let's find a definition: dictatorial power, forcible suppression of opposition, and control of industry and commerce. Of these, Apple doesn't wield a dictatorial power (yet?), but the rest are spot on. On the other hand, I don't see anything that would match that definition among people you want to apply that label to.
Racism != fascism, they're completely orthogonal. Of the three main regimes that were strongly fascist (Mussolini, Hitler and Putin), only the Nazis really cared about race.
like the sanctity of one's personal property and the benefits of strong copyright
You do realize you just contradicted yourself? Either you hold actual property dear, or believe in imaginary one. Putting restrictions on what I can do on hardware I supposedly own deprives me of a good part of that possession's value.
Slashdot Mirror
Uhm, nope. Only those two models have a fix issued. On everything else, you do need to disable HT, which obviously takes a massive performance hit.
Those OCaml guys merely noticed and diagnosed the problem first -- your average mouth-breathing Windows user will have a game crash, a browser corrupt a Twitter page or MS Word lose data yet again, but that's what such users are used to. Yet that their systems are already crashy doesn't mean this extra source of crashes and data corruption doesn't matter.
As for your legendary "BIOS/UEFI updates", those can be relied on about as much as $YOUR_COUNTRY'S_PARLIAMENT to stop bribes towards their own members. Most of those "system vendors" don't pass fixes, and when they do, they're anything but timely.
The fix doesn't disable hyperthreading, the fix fixes the bug.
The fix works only for some models of Skylake (models 78 and 94, stepping 3). On any other Skylakes and all Kaby Lakes there's no way other than disabling hyperthreading entirely.
A fix might or might not be released in the future, Intel doesn't say a word about the issue.
Take a look at this propaganda piece against Scaleway (that they're somehow inferior for obeying the speed of light).
At this point, I quite don't see a rational person hosting their data in the US or at a company with US presence. Because, you see, you got the 4th Amendment, we don't, right?
You haven't seen Progressives of this decade in action, have you?
In fact, just to troll, I use KiB = 1000 occasionally.
Hell yeah. ~10 years ago I argued with a co-worker who thought I'm bullshitting him and that no one could be stupid/malicious enough to redefine such a fundamental unit that's in use for decades. And it was painful as he was a guy who used to bring me old punched tape for playing when I was in kindergarten (in commie land we had punched paper ribbon instead of punched cards).
With the program I had on screen (Debian-installer partitioner) saying "MiB", the old guy believed it's millions bytes, as obvious counterpart to 1MB=1048576. Mega vs million, the abbreviation looks pretty clear to me.
You don't want the filesystem to be misaligned wrt erase blocks, trust me -- especially on cheap flash. Measuring in actual GB means a naive user will get good performance without any special steps.
As for those "600MB videos on 9 GB" -- both real MB/GB and those silly millions bytes will be off. The filesystem has to store metadata somewhere. Videos can use large extents so we're talking about a fraction of a percent, but for smaller files the difference can be far bigger. And you really want to err on the safe side or that 1000th photo won't fit.
What if your filesystem has 1GB block groups, 4MB erase blocks, etc? With real gigabytes it's all nicely aligned. On the other hand, if you use drivemakers' units, either your partitioning program needs to ignore what it's told to do and do large rounding, or, even worse, the user needs to give really unfriendly numbers.
Not being able to hibernate 8GB ram into 8"GB" disk space is another problem.
1KB meant 1024 bytes for 70 years, it's no time to break everything just because some marketroid wanted a bonus.
the fact that no persistent storage device ever made has had any natural relation to 2^20, 2^30, etc.
How come? Disks use 512/4096 byte sectors, erase blocks of powers of two, etc -- not a single power of 10 around. And non-sleazy manufacturers who provide sizes in actual rather than marketing gigabytes do exist.
I got an unopened SD card whose back writing includes "1GB = 1,073,741,824"; I remember a few disks that mention their capacity in real giga/terabytes too.
We're not really going to find any place significantly better than a few of locations in the Solar System. Giving a planet a breathable atmosphere and letting that atmosphere stay will upset its heat budget so much the current values hardly matter. Not in comparison in what we can do by making that atmosphere more opaque or more greenhousey.
And we don't need FTL: if you want to get there in the flesh, I guess it's 50-100 years before we get a breakthrough that defeats aging. We'll then see a lot of health conditions that don't matter today but are fatal by the age of 200. Once we figure those out, there'll be another iteration at 1000 or so.
But then, hard AI can also be expected within those 50-100 years. That's a form of earthlings who don't suffer from biological limitations and can be beamed as a stream of bits as soon as you get a suitable receiver to the destination.
So while engineering issues on the way will be quite interesting, no fundamental research is needed to colonize the galaxy. Then we'll proceed to the Local Group, then shake our fists at the redshifted ghosts of galaxies that are not gravitationally bound to us.
I mean the one doing field testing.
Will it autonomously crash in a parked trailer ?
That's why you run such a prototype 390 million km from the nearest trailer.
You can still run 36-year-old programs just by double-clicking them on 32-bit Windows - and, of course, it still runs legacy 16-bit Windows programs too
Except that no one sane runs 32-bit Windows anymore (except expressly for compat purposes).
These days it's more likely an arbitrary Windows program runs on Wine than on the newest real thing.
I'd not be be surprised if Google was actually a Delaware company, merely having offices in SV...
Let's check. Duh. A big US company not incorporated in Delaware? Ain't such thing.
If the toaster requires Internet connectivity to make toast, it will be returned ASAP and I'd post a warning online to keep others from buying that model.
Then your fire insurance won't get that 90% reduction (obviously paired with a 2000% bump of the base rate) as the data collection will be somehow marketed as a safety feature. A few years on, it'll be plain illegal to sell, then to own, a toaster without an Internet connection.
So please edumacate me: what's be bad with grammar in that clause?
Parses clearly to me: (development of (the Linux 4.14 kernel series)) ((did not even) start).
If you're after the verb phrase, "did not even", it's correct and widespread: 1 2.
It does (C11 7.20.1.1.3) if the implementation supports any 32/64 bit integer types. I can't think of any incoming architecture in foreseable future lacking those. Even if not atomic, the compiler will emulate them. Otherwise, the fraction of our available corpus of software that will work on such an architecture would be uselessly small.
And even there, [u]int_least64_t are required, even in freestanding environment.
There's almost no reason to use "long". The only non-bogus things I can think of from the top of my head are memcpy implementation, bitwise operations and similar things on a block of memory when you want to handle a word at a time -- where doing it byte-by-byte would work just as well, merely slower.
Either your program needs to handle values >= 2^31/2^32, or it doesn't. In the first case, you use [u]int64_t, in the latter it should be int. Anything else introduces a pointless portability problem: int works as fast if not faster on 64-bit than long, too (at the very least by taking fewer cache lines when stored in memory).
As for values that deal with structure sizes, there's [s]size_t/[u]intptr_t.
The only nasty thing is printf() -- when using arch-independent types, you need that ugly %" PRId64 " stuff. It even breaks in C++ where some bright person had the idea to break compat and require a space after the " -- and your C code may be included into C++ when you don't expect.
WORD should be enough for anybody! Pah, who needs DWORD...
32-bit iStuff need dwords, apparently -- a 31 bit word (pointlessly signed) just overflowed.
Unless you mean the Microsoftish way where a "word" is only 1/4 of the actual machine word, that is.
From a technical point of view, only because it was more convenient and less costly.
But the real reason is, in almost all countries this tends to be "good enough" as no one will dare to attack you -- even if the attack itself can be easily anonymized, "cui bono" makes the attacker obvious (and a false flag operation would be pretty risky).
Except for Ukraine -- a country with a big powerful enemy it's currently at war with, and has no friends. It's beyond obvious who wants to destroy their power grid, but at this moment Russia has no real downside in revealing their hand. Thus, this is a show of strength.
Putin isn't fascist.
Nope, not only he is (fulfils every requirement of not only the definition of fascism I quoted, but also pretty much any of them that's not specifically tailored to regime X), but is also specially notable here as he calls everyone else a fascist (usually not directly, but it's his propaganda machine's favourite insult).
Unlike what certain parties tell you, if you're A but claim to be B, you don't stop being A nor start being B. Whether it's communism "not a religion", christianity "not a polytheism" (4 main gods, thousands of minor deities), a pre-op trans (real)man a "woman", campaign donations "not corruption", a $SCRIPTURE-thumper a "good person", etc, etc. Call a spade a spade.
And unlike some of those who are merely deluded, Putin is highly intelligent and does his thing fully consciously.
On the other hand -- Russia is immune here, as they don't even know the concept of a fair election. They did not have a single one during their whole history -- not by the tsars, not by the soviets, almost had one by Yeltsin, then back to the usual. They don't even bother with any semblance of propriety: Chechnya voted 99.5% for One Russia (Putin's party) with 99.4% turnout; just 11 years after a second war against them led by said Putin.
You're using Bluetooth for something it wasn't designed for. You want regular WiFi instead.
As for playing music, why would you even consider using crap tinny headphones while at home? I have yet to see non-crappy bluetooth ones, and good ones are too heavy to be comfortable mobile (note: heavy doesn't imply good -- case in point: Apple's Beats are weighted to resemble good gear). Thus, for decent music you either use proper headphones when sitting or speakers. Speakers do not suffer from any wireless issues.
And even when mobile, attaching tinny headphones is much better done with a wire. You don't lose them once a week, get better sound quality, have them working non-stop without charging downtime every a short while, etc.
Right, Franco is fourth, I've forgotten about him.
As for Putin, that's pretty ironic as "fascist" is his propaganda machine's favourite insult.
Those with fascist ideals are the fascists. It's that simple.
Yeah, let's find a definition: dictatorial power, forcible suppression of opposition, and control of industry and commerce. Of these, Apple doesn't wield a dictatorial power (yet?), but the rest are spot on. On the other hand, I don't see anything that would match that definition among people you want to apply that label to.
Racism != fascism, they're completely orthogonal. Of the three main regimes that were strongly fascist (Mussolini, Hitler and Putin), only the Nazis really cared about race.
like the sanctity of one's personal property and the benefits of strong copyright
You do realize you just contradicted yourself? Either you hold actual property dear, or believe in imaginary one. Putting restrictions on what I can do on hardware I supposedly own deprives me of a good part of that possession's value.