Or you can be Stephen Hawking and actually do something with your life instead of whining how much it sucks because you can't do pullups any more or even brush your teeth.
But does he go out twice a week to do 18 holes without a golf cart? No? Then he is like most of today's golfers, a vanishing breed. Easy to forecast that: lose millions a year as the clubhouse falls into ruins then sell at a fantastic loss to a subdivision developer. He's good to go.
Just don't run up my insurance premiums with your self-destructive habits, ok? Please just take up proximity flying instead, the cost of scraping you off a cliff face should not be too much.
Of course, I meant to write "they will reimagine it as Zen 5 skipping Zen 4", there's that confusion at work. To make that seem somewhat legit, they can go with "5nm means Zen 5, right?" Then just grin and go with Zen 6 for the 3nm generation.
What exist today is Zen 2 architecture on 7nm, and whatever product that uses it is not yet named
Pretty safe bet they will call it Ryzen 3, a change from their original plan which was on the dumb side. Confusion is not helpful. BTW there already is a 5nm Zen 3 on the roadmap, I bet that gets the damnatio memoriae treatment too, they will reimagine it as Ryzen 5 (skipping Ryzen 4 as originally planned because 4 rhymes with "dead" in Chinese)
As a project, Systemd is a hungry obnoxious octopus, but as a system its decently modular. Not a huge fan, but it has given me almost no trouble, and when I did go in to customize it to my tastes, like adding rc.local, it was a straightforward learning experience without follow-on maintainability issues.
During the April update this year, I had 3 W10 installations to get through the process. None of them worked, although one in particular went spectacularly wrong and wiped out files on the system's hidden boot partition, basically resulting in the system attempting to reboot and crashing out. There was no choice left but to perform a clean installation, then let that fresh image update.
In all my years of using Linux, 20 now, I have never once been forced to do a reinstall. I actually have one system that was continuously upgraded from Debian potato in 2003 through to Stretch today and is still running, having worked its way through three or four hard disks, one of which was a head crash salvaged by ddrescue. Some of the version upgrades were a little exciting in the old days in the sense that manual intervention was sometimes required even to the point of hand editing apt db files. It pretty much just automagically worked for the last dozen years or so, e.g., edit sources.list from Stretch to Buster, apt update then apt dist-upgrade.
I guess Windows users have a hard time imagining anything so reliable. BTW, the longest uptime for that server was about three years at one point. And it was 32 bit all that time, still is. Finally migrated all the services to a NUC running 64 bit Debian, but that old system, a Pentium M, is still running as a storage backup server. It runs KDE by the way, for the rare occasions I hook a monitor to it. Works perfectly well, that's something for the Gnome trolls to meditate on. Today, that machine is probably less powerful than my thermostat.
It just makes me shudder to think how unimaginably horrible the Windows 10 code base must have become to let a grade school bug like that through to production. What the hell! Did they lather a bunch of cloud pollution on top of the local file APIs to the point where nobody can read or understand their code any more? And on top of that, roughly zero regression testing? Do any adults remain at Microsoft?
Needless to say, Linux will not do that to you. Something about the Unix philosophy.
Tweaks, maybe. They just did not have time to do anything major. I just don't have a whole lot of confidence they closed up Meltdown definitively. Intel will need at least a few more months to do the job properly and copy AMD in time for the Cannon Lake ramp.
Yes, perhaps you should do that, I already did (2xxx).
I'm just going to have to go ahead and point out that your retort qualifies as kind of snippy, considering that you actually said "Ryzen 2 (2xxx)" which is wrong, or at best adds to the confusion.
Zen+ is Ryzen 2000 series, Zen 2 will be Ryzen 3000. It's a bit confusing. Ryzen+ means Zen+ mainstream desktop. I think AMD intended Ryzen 2 to mean Zen 2, not Zen+, but there's so much confusion about that now that it's better to stick to the thousands terminology.
Judging from the elongated production schedule and complete nonavailability of Cannon Lake, Intel must have bulldozed the first gen 10nm production line. Then they had to deal with the question of expanding 14nm production to fill the gap. That one must have been really tough, they needed to add the absolute minimum capacity at that already obsolete node. So Coffee Lake shortages would be because of trying to build less capacity, and also competing for resources with their own Kaby Lake and maybe even Skylake production.
these motherboards and chips are basically an *oh crap, we fell behind*
I would say so... i9-9900K is currently "out of stock" on Amazon. Invites the question, is Intel really producing these in volume or is this just a delay tactic hoping some folks will drop their 2700x plans? I'm thinking, Intel had to dust off their 14nm fabs to produce these, do they really have the capacity? If they don't, we're going to be seeing a whole lot of "out of stock" and asking prices will probably spike above MSRP like they did for first gen Epyc. A little voice whispers to me, they don't.
Anyway, you can build a 12 core Threadripper box for about the same bottom line as the i9-9900K and that's clearly superior in core count, PCI lanes and memory channels. Not sure Intel really has a point here.
Actually, i9-9900K is 90% more expensive than Ryzen 2700X. And Intel had to fiddle the gaming benchmarks to make it look faster than it really is. These are on Intel's 14nm process, they were hoping to be on 10nm by now but that isn't happening until some time next year. Meanwhile Ryzen 2 on 7nm will be out while Coffee Lake is still shipping, oops. Ryzen 2 will probably probably put AMD even in IPC and ahead in GHz. Intel's last remaining bragging points gone. And Intel isn't going to catch up any time soon, by the time they finally have 10nm online TSMC will already be sampling its next gen EUV process.
This is easy: go Ryzen and put that 90% Intel markup in your pocket, ready to spend on 7nm Ryzen 2 next year.
Spectre/Meltdown are a problem because they enable a bunch of exploits that let you get out of a hypervisor and into the host OS. If you're in a data center that's a huge deal. If you're a gamer it's, well, not.
The boneheadedness is strong in this one. I hope that nobody ever listens to you about anything.
In order for someone to even exploit the flaw, they would already have to have remote access to the system.
Completely wrong. Please stop spreading dangerous disinformation. Meltdown can be exploited by Javascript, meaning that any website you visit can end up owning any private data you have on your Intel machine. Meltdown is not just a problem for web host operators, but anyone running a browser with Javascript enabled.
Beastly 28 core Xeon W-3175X, obviously targeted at AMD's 32 core Threadripper 2990WX, which you can buy right now on Amazon for $1,720. I'd like to know Intel's price, I guess it's not remotely close.
Note that with these top heavy core counts you always get lower clock frequency because of bus contention. Not a stopper by any means, if you have the use case. But personally I'm a lot more interested in the higher clocked 16 core AMD parts, specifically the 2950X, $900. Slightly higher cost per core but clocked about 10% higher. Boost frequency 4.4 GHz, the technical term for that is awesome.
Right. There are supposedly some mitigations in this Coffee Lake release but I seriously doubt that they are real hardware mitigations, probably just microcode hacks that cost performance. I am highly skeptical that Intel had enough time to develop and qualify the fundamental cache circuitry changes they need to fix Meltdown properly, let alone changing all the masks.
Slashdot Mirror
The health insurance payout per person per year grows exponentially with age, and your premium is high chiefly because blah blah blah
I take it you don't have a family.
Or you can be Stephen Hawking and actually do something with your life instead of whining how much it sucks because you can't do pullups any more or even brush your teeth.
But does he go out twice a week to do 18 holes without a golf cart? No? Then he is like most of today's golfers, a vanishing breed. Easy to forecast that: lose millions a year as the clubhouse falls into ruins then sell at a fantastic loss to a subdivision developer. He's good to go.
what if I don't *want* to have a long life?
Just don't run up my insurance premiums with your self-destructive habits, ok? Please just take up proximity flying instead, the cost of scraping you off a cliff face should not be too much.
Of course, I meant to write "they will reimagine it as Zen 5 skipping Zen 4", there's that confusion at work. To make that seem somewhat legit, they can go with "5nm means Zen 5, right?" Then just grin and go with Zen 6 for the 3nm generation.
Oh, and another source of confusion: what is a Ryzen 3? Is that zen-3-formerly-known-as-zen-2 or is it the cheap budget PC bin?
What exist today is Zen 2 architecture on 7nm, and whatever product that uses it is not yet named
Pretty safe bet they will call it Ryzen 3, a change from their original plan which was on the dumb side. Confusion is not helpful. BTW there already is a 5nm Zen 3 on the roadmap, I bet that gets the damnatio memoriae treatment too, they will reimagine it as Ryzen 5 (skipping Ryzen 4 as originally planned because 4 rhymes with "dead" in Chinese)
I detect a troll.
As a project, Systemd is a hungry obnoxious octopus, but as a system its decently modular. Not a huge fan, but it has given me almost no trouble, and when I did go in to customize it to my tastes, like adding rc.local, it was a straightforward learning experience without follow-on maintainability issues.
Which of those deleted your files?
During the April update this year, I had 3 W10 installations to get through the process. None of them worked, although one in particular went spectacularly wrong and wiped out files on the system's hidden boot partition, basically resulting in the system attempting to reboot and crashing out. There was no choice left but to perform a clean installation, then let that fresh image update.
In all my years of using Linux, 20 now, I have never once been forced to do a reinstall. I actually have one system that was continuously upgraded from Debian potato in 2003 through to Stretch today and is still running, having worked its way through three or four hard disks, one of which was a head crash salvaged by ddrescue. Some of the version upgrades were a little exciting in the old days in the sense that manual intervention was sometimes required even to the point of hand editing apt db files. It pretty much just automagically worked for the last dozen years or so, e.g., edit sources.list from Stretch to Buster, apt update then apt dist-upgrade.
I guess Windows users have a hard time imagining anything so reliable. BTW, the longest uptime for that server was about three years at one point. And it was 32 bit all that time, still is. Finally migrated all the services to a NUC running 64 bit Debian, but that old system, a Pentium M, is still running as a storage backup server. It runs KDE by the way, for the rare occasions I hook a monitor to it. Works perfectly well, that's something for the Gnome trolls to meditate on. Today, that machine is probably less powerful than my thermostat.
It just makes me shudder to think how unimaginably horrible the Windows 10 code base must have become to let a grade school bug like that through to production. What the hell! Did they lather a bunch of cloud pollution on top of the local file APIs to the point where nobody can read or understand their code any more? And on top of that, roughly zero regression testing? Do any adults remain at Microsoft?
Needless to say, Linux will not do that to you. Something about the Unix philosophy.
Tweaks, maybe. They just did not have time to do anything major. I just don't have a whole lot of confidence they closed up Meltdown definitively. Intel will need at least a few more months to do the job properly and copy AMD in time for the Cannon Lake ramp.
Yes, perhaps you should do that, I already did (2xxx).
I'm just going to have to go ahead and point out that your retort qualifies as kind of snippy, considering that you actually said "Ryzen 2 (2xxx)" which is wrong, or at best adds to the confusion.
Zen+ is Ryzen 2000 series, Zen 2 will be Ryzen 3000. It's a bit confusing. Ryzen+ means Zen+ mainstream desktop. I think AMD intended Ryzen 2 to mean Zen 2, not Zen+, but there's so much confusion about that now that it's better to stick to the thousands terminology.
Judging from the elongated production schedule and complete nonavailability of Cannon Lake, Intel must have bulldozed the first gen 10nm production line. Then they had to deal with the question of expanding 14nm production to fill the gap. That one must have been really tough, they needed to add the absolute minimum capacity at that already obsolete node. So Coffee Lake shortages would be because of trying to build less capacity, and also competing for resources with their own Kaby Lake and maybe even Skylake production.
Right, i9-9900K currently available (maybe) from ebay scalpers for $650 - $1100.
these motherboards and chips are basically an *oh crap, we fell behind*
I would say so... i9-9900K is currently "out of stock" on Amazon. Invites the question, is Intel really producing these in volume or is this just a delay tactic hoping some folks will drop their 2700x plans? I'm thinking, Intel had to dust off their 14nm fabs to produce these, do they really have the capacity? If they don't, we're going to be seeing a whole lot of "out of stock" and asking prices will probably spike above MSRP like they did for first gen Epyc. A little voice whispers to me, they don't.
Anyway, you can build a 12 core Threadripper box for about the same bottom line as the i9-9900K and that's clearly superior in core count, PCI lanes and memory channels. Not sure Intel really has a point here.
I hope you don't work in any responsible position.
Actually, i9-9900K is 90% more expensive than Ryzen 2700X. And Intel had to fiddle the gaming benchmarks to make it look faster than it really is. These are on Intel's 14nm process, they were hoping to be on 10nm by now but that isn't happening until some time next year. Meanwhile Ryzen 2 on 7nm will be out while Coffee Lake is still shipping, oops. Ryzen 2 will probably probably put AMD even in IPC and ahead in GHz. Intel's last remaining bragging points gone. And Intel isn't going to catch up any time soon, by the time they finally have 10nm online TSMC will already be sampling its next gen EUV process.
This is easy: go Ryzen and put that 90% Intel markup in your pocket, ready to spend on 7nm Ryzen 2 next year.
Using your right of free speech to subvert democracy is roughly equivalent to using your right to own a knife to kill somebody with it.
To make good use of the micro code bugs you usually need root/admin. And if somebody's got that you're already boned.
And you are boned for being stupid.
Spectre/Meltdown are a problem because they enable a bunch of exploits that let you get out of a hypervisor and into the host OS. If you're in a data center that's a huge deal. If you're a gamer it's, well, not.
The boneheadedness is strong in this one. I hope that nobody ever listens to you about anything.
In order for someone to even exploit the flaw, they would already have to have remote access to the system.
Completely wrong. Please stop spreading dangerous disinformation. Meltdown can be exploited by Javascript, meaning that any website you visit can end up owning any private data you have on your Intel machine. Meltdown is not just a problem for web host operators, but anyone running a browser with Javascript enabled.
Beastly 28 core Xeon W-3175X, obviously targeted at AMD's 32 core Threadripper 2990WX, which you can buy right now on Amazon for $1,720. I'd like to know Intel's price, I guess it's not remotely close.
Note that with these top heavy core counts you always get lower clock frequency because of bus contention. Not a stopper by any means, if you have the use case. But personally I'm a lot more interested in the higher clocked 16 core AMD parts, specifically the 2950X, $900. Slightly higher cost per core but clocked about 10% higher. Boost frequency 4.4 GHz, the technical term for that is awesome.
Right. There are supposedly some mitigations in this Coffee Lake release but I seriously doubt that they are real hardware mitigations, probably just microcode hacks that cost performance. I am highly skeptical that Intel had enough time to develop and qualify the fundamental cache circuitry changes they need to fix Meltdown properly, let alone changing all the masks.