They buy a device that's horribly insecure, the manufacturer sends out one security update, then abandons it, and it becomes part of a botnet. And you fine the person who bought it?
Actually, you're right. That's a great idea, because it will kill the whole 'Internet of Things' idiocy overnight. No-one will risk attaching anything to their network if they can't verify it's secure.
Many people who hail the gold standard ignore a simple fact: A gold standard for coins means constant deflation, which is bad in most economic situation, because it gives incentives for hoarding money instead of spending it.
Yes! The HORROR OF THINGS GOING DOWN IN PRICE! IT MUST BE BANNED!
Dude, we've had constant deflation in electronics prices since... well, forever, in electronics terms. Deflation is the norm in a free market, as productivity increases lead to lower prices.
Only governments think it's a bad thing, because they can tax inflation, but can't tax deflation.
SJWs are pushing these 'code of conduct' policies on open source projects so they can infiltrate and take over, just as they've done on everything else. This is why you never, ever, accept any of them into an open source project, and laugh when they suggest that you need a 'code of conduct'.
Of course, it doesn't really work with an open source license, since the coders they kick out of their own projects can just fork and start a new one. Except they'll presumably ensure that GPL4 has a section which prohibits cisgendered whitemales from using the code.
Yeah, but Jordan's already implied that FreeBSD will be going down a very similar path....
To be fair, I don't think people are complaining about the idea of systemd--getting rid of clunky old init scripts is a good idea--they're complaining that the implementation of systemd seems to be Pulseaudio 2.0.
I mean, my first experience of systemd was when I tried to install CentOS 7, and systemd crashed during the install. Not really a way to give me warm fuzzies.
The usual object to this idea is that no one will want to work, but I would imagine that a stipulation that you're required to do so many hours of community service every week if not working would probably help balance things out a little bit.
'Work or starve'?
Why should I have to work to get my 'basic income'? I have rights!
(And you have just reinvented the huge government bureaucracy you just said you were getting rid of)
Which is not what the submission says. You added that qualification.
Did you not read this thread before responding? Did you not even read the GP post that the post I responded to was responding to? The one that I directly quoted that from?
We had some NeXT machines where I worked in the 90s. From what I remember, they were both staggeringly slow (due to sticking a 24-bit display on a slow CPU) and staggeringly expensive. I think they were mostly used for viewing pr0n at more than 8 bits per pixel.
Actually, one of the server crash bugs was due to a debug printout which was only triggered by a leap second, and was buggy, so it crashed the kernel in a small number of cases.
Code that's only executed every few years, and at the same time all over the world, is a really, really, really big risk.
This is a large part of the problem. More often than not these issues stem from people trying to roll their own time handling code / int'l address code / i18n / etc rather than using one of the standard (and well-tested) libraries available in their language.
Uh, no. Not in the least.
Most of these issues stem from operating system bugs which are only triggered by leap seconds, which can't easily be tested before the leap second happens. We had to get special firmware from our GPS manufacturer to get it to send out NTP packets that simulated a leap second, so we could do that.
And even when you have backup systems, they fail at the same time, because the leap second happens everywhere at the same time.
They're a freaking disaster, and anyone who cares about them can deal with them in their code, rather than forcing everyone to deal with them.
To be fair, the second time I load a game, it's faster, as all the files are cached in RAM. But the fscking thing still makes me wait while it plays half a dozen stupid videos, so it doesn't make that much difference.
No, crippled. Most games aren't even 64-bit on Windows.
Even with a two-year-old PC, games barely use my CPU and barely use my RAM. They could do far more interesting stuff with modern hardware, if they weren't built for consoles with a fraction of the power.
Slashdot Mirror
So why does the media get all hyped up when Twitter goes down?
The media thinks Twitter is The Internet.
The real point of these attacks is that DNS, like any other centralized service on the Internet, is broken by design.
If the 'Internet Of Things' wasn't such a swamp of security holes, no-one would need to care.
And then what?
They buy a device that's horribly insecure, the manufacturer sends out one security update, then abandons it, and it becomes part of a botnet. And you fine the person who bought it?
Actually, you're right. That's a great idea, because it will kill the whole 'Internet of Things' idiocy overnight. No-one will risk attaching anything to their network if they can't verify it's secure.
Where legislators aren't keeping up -and it's having negative impact- is in drafting appropriate legislation while understanding its implications.
How are a bunch of lawyers going to understand the implications of new laws on technology?
Many people who hail the gold standard ignore a simple fact: A gold standard for coins means constant deflation, which is bad in most economic situation, because it gives incentives for hoarding money instead of spending it.
Yes! The HORROR OF THINGS GOING DOWN IN PRICE! IT MUST BE BANNED!
Dude, we've had constant deflation in electronics prices since... well, forever, in electronics terms. Deflation is the norm in a free market, as productivity increases lead to lower prices.
Only governments think it's a bad thing, because they can tax inflation, but can't tax deflation.
SJWs are pushing these 'code of conduct' policies on open source projects so they can infiltrate and take over, just as they've done on everything else. This is why you never, ever, accept any of them into an open source project, and laugh when they suggest that you need a 'code of conduct'.
Of course, it doesn't really work with an open source license, since the coders they kick out of their own projects can just fork and start a new one. Except they'll presumably ensure that GPL4 has a section which prohibits cisgendered whitemales from using the code.
System boot time is only important if the system is booting frequently.
And pretty much irrelevant when my servers take about five minutes to get out of the BIOS and start running the operating system.
Yeah, but Jordan's already implied that FreeBSD will be going down a very similar path....
To be fair, I don't think people are complaining about the idea of systemd--getting rid of clunky old init scripts is a good idea--they're complaining that the implementation of systemd seems to be Pulseaudio 2.0.
I mean, my first experience of systemd was when I tried to install CentOS 7, and systemd crashed during the install. Not really a way to give me warm fuzzies.
Systemd does make things easier for some people and some tasks, which is why it's been adopted.
Systemd is funded by Redhat, isn't it? How does it make server administration easier?
I've had to work with a Redhat 7 server at work, and all systemd does is force me to learn new ways to do the things I've been doing for years.
The usual object to this idea is that no one will want to work, but I would imagine that a stipulation that you're required to do so many hours of community service every week if not working would probably help balance things out a little bit.
'Work or starve'?
Why should I have to work to get my 'basic income'? I have rights!
(And you have just reinvented the huge government bureaucracy you just said you were getting rid of)
I know you're busy breathing through your mouth and that takes more brain activity, but think this through.
HATE SPEECH! HATE SPEECH! HATE SPEECH!
"Filter error: Don't use so many caps. It's like YELLING." - yes, I am yelling. That's what you should do when someone uses HATE SPEECH!
Which is not what the submission says. You added that qualification.
Did you not read this thread before responding? Did you not even read the GP post that the post I responded to was responding to? The one that I directly quoted that from?
Oh, no, of course you didn't.
No, sounds like they were harassed into reinstating the plans.
But SJWs always project.
Because NeXT didn't exist in the 90's.
Hint: "commercial CONSUMER operating systems"
We had some NeXT machines where I worked in the 90s. From what I remember, they were both staggeringly slow (due to sticking a 24-bit display on a slow CPU) and staggeringly expensive. I think they were mostly used for viewing pr0n at more than 8 bits per pixel.
In the future computers will be networks, applications will be distributed applications.
I still remember when that was the future twenty years ago! We've gone so far ahead in time that the past is now the future!
Of course it's a joke. iamacat is just talking about things that could be done on almost any Unix system.
The difference is that my Linux laptop cost about $1,000, whereas, if I remember correctly, the Sun workstation on my desk cost over $25,000.
The options for home users were basically DOS and its clones, Windows 3 and a couple of similar simplistic GUIs, OS/2, and... Linux.
Actually, one of the server crash bugs was due to a debug printout which was only triggered by a leap second, and was buggy, so it crashed the kernel in a small number of cases.
Code that's only executed every few years, and at the same time all over the world, is a really, really, really big risk.
Userspace code is irrelevant when your operating system blows up while trying to deal with a leap second.
This is a large part of the problem. More often than not these issues stem from people trying to roll their own time handling code / int'l address code / i18n / etc rather than using one of the standard (and well-tested) libraries available in their language.
Uh, no. Not in the least.
Most of these issues stem from operating system bugs which are only triggered by leap seconds, which can't easily be tested before the leap second happens. We had to get special firmware from our GPS manufacturer to get it to send out NTP packets that simulated a leap second, so we could do that.
And even when you have backup systems, they fail at the same time, because the leap second happens everywhere at the same time.
They're a freaking disaster, and anyone who cares about them can deal with them in their code, rather than forcing everyone to deal with them.
Well, duh. You didn't really think government regulations were meant to protect the little guy, did you?
I grabbed that "deal". After about an hour into the first game, I realised that it sucked hard and haven't played it since.
Hmm, an hour into the game? So just past the first cut-scene, then?
Trust me, you're lucky you quit there, and didn't get as far as the second one.
You mean 4 GB?
No. By default, Windows caps 32-bit applications at 2GB.
This is one reason heavily-modded 32-bit games crash a lot.
Ditto. These days, I usually only buy games when they're $5 in a Steam sale.
To be fair, the second time I load a game, it's faster, as all the files are cached in RAM. But the fscking thing still makes me wait while it plays half a dozen stupid videos, so it doesn't make that much difference.
Just optimised and unbloated I think.
No, crippled. Most games aren't even 64-bit on Windows.
Even with a two-year-old PC, games barely use my CPU and barely use my RAM. They could do far more interesting stuff with modern hardware, if they weren't built for consoles with a fraction of the power.