Comment Re:The key to Bitcoins creator and author are in t (Score 1) 10
What you're trying to say is that it was created by the NSA, and that it's a honeypot.
What you're trying to say is that it was created by the NSA, and that it's a honeypot.
Hahahahaha.
The 80186 existed, but the problem was the 80186 integrated various components such as the clock generator and interrupt controller directly into the CPU, but did so in a way that was incompatible with how IBM built the IBM PC. So the 80186 found its way into some not-quite-IBM-compatible computers like some Tandy models and a few other oddballs including some early PDAs. Otherwise, it it was used mostly for embedded applications.
They define 133-400k "family of 3" as "upper middle class".
Which is just patent bullshit.
All it is, is they keep the same old income brackets for "middle class" while inflation pushes wages and COL higher. There are actually far fewer people able to maintain a 1990s "middle class" lifestyle, and I'd argue most of these "upper middle class" people are living month to month. "Middle class" used to mean you were financially secure and had investments and retirement. That's a joke for most people under 50.
They're defining upper middle class as " family of three earning $133,000 to $400,000 per year". So that's 2 middle aged adults + an adult child as the upper barrier.
What's that mean for your typical "family of 2"? Do they normalize on 3 incomes and play funny with the figures, using extrapolation for the third?
Because the cost of living has increased. $133k is going to just barely buy you a house in most of the country. Is starter home ownership "upper middle class"?
Absolutely not.
This is just inflation, and a disingenuous bullshit article in the NYT (as you can expect, at best). The middle class is markedly smaller, not larger, and they're just using old income brackets to define "upper middle class".
Pretty much exactly my point.
The fact that every dev seems to just install the latest whatever from npm doesn't help. There's really no "staging", "stable", or "security" branches, and effectively zero vetting outside what the package developer did. That's a lot of trust.
I never said they were new. I, instead, inferred that they're the kind of problems which shouldn't exist, because it's a mindset out of the 90s when the Internet was still comparably high-trust. They're inexcusably negligent.
You can experience over 40 years of UI design differences in Windows still, today: UI dialog panels from 3.1 days still exist in the latest Windows builds, and everything in between.
I don't think you can honestly say Windows has more polish. It has more bloat - yes. But that's not the same thing.
Meanwhile, Windows games (newer titles!) run better on Linux and Mac, emulated and passed through additional translation libraries, than on Windows.
You also grossly misunderstand how prefetch/caching works, both on Linux and on Windows. It does not change the baseline experience, or that the start bar can quickly eat up 10GB+ of memory due to memory leaks and perform worse than a Windows 95 machine deep into swap.
"Overall experience" is also nonsense - most people don't have the capability or wherewithal to switch. They use what is given to them, and have only mild preference in that they want it to work for what they're doing. Nowadays, that means "a web browser" for well over 50% of all users being the primary requirement, if not the exclusive one.
The baseline computers on the shelves have always been under spec'd for whatever Windows requires, and the experience will be poor. This is why so many people are buying Macs.
This is likely a paid advertisement, brought to you by the same people who are trying to avoid the continued fracturing and disillusionment of the remaining non-professional Windows users who aren't hardcore gamers. It's right in line with the "make Windows better again" agenda (I'd argue, propaganda campaign - there's zero chance of it happening) out of Redmond.
Windows hasn't been usable on less than 16GB of RAM since the tail end of the hard drive era (around Windows 7 SP2/3). Windows Vista was never usable with less than 8GB. Since the tail end of W7 around 2010, after W10 was released, things have only gotten worse: slower, more bloated, and more faulty. There are bugs in Explorer which will balloon memory use to 10s of GB just sitting idle for just that process (and many others).
npm is a problem. It's this massive, unvetted self-publishing repository without any easy way to verify the origin of packages, and the packages largely get installed directly to production on billions of sites every day without any vetting or review.
It's crazy, like something out of the 90s.
Yes, supply attacks like those carried out against npm are pretty common in general, at the state actor level. There've been a couple fun ones in recent years. But the openness and lack of basic precautions surrounding npm in conjunctions with common development practice just makes it a recipe for disaster.
If you read this post it shows that AMD stole Intel's design and reverse engineered it.
If you dig deeper, you'll find that AMD originally reverse engineered the *8080*, not the 8086. The two companies had entered into a cross-licensing agreement by 1976. Intel agreed to let AMD second-source the 8086 in order to secure the PC deal with IBM, who insisted on having a second source vendor.
There would have been no Intel success story without AMD to back them up.
(That actually would have been for the best. IBM would probably have selected an non-segmented CPU from somebody else instead of Intel's kludge.)
"lossy compression"
Yes, just like human memory.
If I read a bunch of books from a series and extrapolate based on them to form something similar, it's not plagiarism.
If I read your book, then write a book using a similar voice, style, and plot, and do it in a different language - it's not plagiarism if I offer citation. Likewise, if I do so with a verbatim copy in another language. It's an independent effort.
Ultimately, it boils down to what you can get away with. Considering how trivial it is now to re-implement things, I'd say the chance of license enforcement is close to zero for anything open source except in extremely rare situations where there's a lot of money involved.
It baffles the mind that Microsoftware - known for decades for being unreliable shit - is allowed on space missions at all, no matter how uncritical the role. The potential for malware alone is ludicrous. "Hey, pay us 2500 bitcoins if you want your space capsule back".
Then again, I figure the days when NASA did the right stuff are long past.
If you can substantially distinguish how tokenized abstraction is any different than natural learning, I'd buy it. But as it's not, I don't think that's a meaningful argument.
He has not acquired a fortune; the fortune has acquired him. -- Bion