But that's economics for you, inconsistent nomenclature.
I doubt you could find an economist who would agree with you that what Epic is doing is not considered incurring losses. Certainly not an accountant. This is more a case of you using terms differently than most people are using them.
You might want to check why 2038 is a problem before you say things that expose your ignorance.
You might want to reread my comment. I didn't mention the 32 bit 2038 issue; I was talking about a different problem. Someone else already explained the Y2038 problem.
If it means that 1st Amendment protected speech no longer gets 230 protections then, um, won't sites be much, much quicker to pull down all sorts of content? This would mean no 230 protections over abuse, harassment, hate speech, etc.
The other way around I think. It means if a platform elects to moderate speech that is not protected by the first amendment, they get to keep their 230 protections. If they moderate speech that is protected by the 1st, they lose those protections. Which is just an awful idea.
It gets easier when you mention that "nobody alive knows how to fix the system if a major catastrophe happens, and by the way I know the next date that will happen".
Yes, I would expect that is what it's going to take. Even such a scenario will not be enough to retire 100% of these legacy systems. Now I'm wondering when the last COBOL program will be permanently shut down.
I'd argue that hardware support for those systems will be a clearer problem than software before 2038.
They'll be moved to a VM if hardware support becomes an issue (if they haven't been already).
The problem is easily solved by switching to 64 bit architecture
The architecture is not the issue. Switching to 64 bit will do nothing to solve the problem of the underlying systems and databases using 2 digits to store years.
it's an easy sell to bean counters given the risks of not having the systems replaced in things like banking and other systems.
Replacing such a system is never an easy sell. If it's practical to update the system rather than replace it, that is almost always the correct path.
We still have 17 years to upgrade and replace affected 32 bit embedded system
The bigger issue will be any mainframes still in use.
But, once it's made clear to them that this is the case I'd expect a flurry of activity in 2035 or so to avoid the issues, for the few industries where this is still the case.
This is your regular reminder that Y2K was a very real problem that was fixed by competent professionals
Well, "fixed" in many cases. A lot of systems were updated to interpret two digit years differently. So 00-40, for example, are interpreted as 2000-2040, and 41-99 are 1941-1999. So we get this problem all over again if those systems are still around long enough to start getting dates beyond 2040. Since many have already been around 50 years, it's not impossible. And at that point, there is no easy fix like there was last time.
Fortunately many systems were actually fixed properly, with four digit dates. So (hopefully) no problem there until the year 10000.
Why, in this case, is YET so much worse than ACTUALLY HAS for you?
Let's just consider property damage. It gets much more thorny when you're talking about serious injury or death, because money is all that can be offered in recompense, but that is often incomplete at best.
So for the simple case, an insured driver causes an accident. Their insurance pays for it, the victim is made whole, and there is no lasting damage. An uninsured driver hasn't yet caused an accident. So from this point on, we have the case where the insured driver could potentially cause an accident, the insurance pays for it, and everyone is made whole after some variable amount of inconvenience. And the case where the uninsured driver could potentially cause an accident. Then maybe the victim has uninsured driver insurance, and maybe they do not. If they do, they have been paying this whole time for the possibility of someone else's error. If they do not, now their car is damaged, possibly ruined, and they are left to deal with the inconvenience and cost on their own.
Accidents happen. People make mistakes, even when they're trying to be careful. The responsible thing to do is to clean up after your own mistakes, which uninsured drivers do not do. Does that help?
Though digital instead of physical, they are at bottom communications networks, and they “carry” information from one user to another…
This is isn't even correct. The social media networks and other web sites host information. Telecoms (ISPs) carry the information from one to another. If Thomas wants to regulate ISPs as common carriers, I would be totally on board with that.
On the post: Morrissey Thinks Free Speech No Longer Exists Because He Can't Sue The Simpsons For Satirizing Him
Re:
Not blonde, it was Lindsay Lohan.
On the post: PlayStation Y2K-Like Battery Bug About To Become A Problem As Sony Shuts Down Check In Servers
Re: Re: Re: Re: Possible workaround
Right, so the problem isn't the presence of a "suicide battery". The problem is DRM.
On the post: PlayStation Y2K-Like Battery Bug About To Become A Problem As Sony Shuts Down Check In Servers
Re: Re: Re: Re: Re: Re: Re:
Firstly, it's COBOL. Secondly, are you suggesting that in the 1960s time zones were not something that came up much?
On the post: PlayStation Y2K-Like Battery Bug About To Become A Problem As Sony Shuts Down Check In Servers
Re: Re: Possible workaround
Are you surprised that your laptop or desktop has one too?
On the post: Platform Wars Update: Epic Store Losing $330 Million Per Year To Acquire Customers
Re: Re: Re: Re: Re: Loss??
I doubt you could find an economist who would agree with you that what Epic is doing is not considered incurring losses. Certainly not an accountant. This is more a case of you using terms differently than most people are using them.
On the post: PlayStation Y2K-Like Battery Bug About To Become A Problem As Sony Shuts Down Check In Servers
Re: Re: Re: Re: Re: Re: Re:
You might want to reread my comment. I didn't mention the 32 bit 2038 issue; I was talking about a different problem. Someone else already explained the Y2038 problem.
On the post: Mastercard Lays Down New Rules For Streaming Sites That Require Them To Review Content Before Publication
Re: Re: Bitcoin fixes this
Oh do tell, how exactly will that be accomplished?
On the post: Lying NYPD Narcotics Detective Just Cost Prosecutors Nearly 100 Convictions
Re:
Prosecution of cops is so rare that this is far from the biggest problem with the criminal justice system.
On the post: Republican's 'Big Tech Accountability' Platform Calls For Both More And Less Moderation, And A 'Not Fairness Doctrine' Fairness Doctrine
1st amendment
The other way around I think. It means if a platform elects to moderate speech that is not protected by the first amendment, they get to keep their 230 protections. If they moderate speech that is protected by the 1st, they lose those protections. Which is just an awful idea.
On the post: PlayStation Y2K-Like Battery Bug About To Become A Problem As Sony Shuts Down Check In Servers
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re:
I'm not saying you're wrong, but mainframe virtualization definitely exists.
https://en.wikipedia.org/wiki/VM_(operating_system)
On the post: PlayStation Y2K-Like Battery Bug About To Become A Problem As Sony Shuts Down Check In Servers
Re: Re: Re: Re: Re: Re: Re: Re: Re:
I think the popular ones already have VMs but I'm far from an expert.
On the post: PlayStation Y2K-Like Battery Bug About To Become A Problem As Sony Shuts Down Check In Servers
Re: Re: Re: Re: Re: Re: Re:
Yes, I would expect that is what it's going to take. Even such a scenario will not be enough to retire 100% of these legacy systems. Now I'm wondering when the last COBOL program will be permanently shut down.
They'll be moved to a VM if hardware support becomes an issue (if they haven't been already).
On the post: PlayStation Y2K-Like Battery Bug About To Become A Problem As Sony Shuts Down Check In Servers
Re: Re: Re: Re: Re:
The architecture is not the issue. Switching to 64 bit will do nothing to solve the problem of the underlying systems and databases using 2 digits to store years.
Replacing such a system is never an easy sell. If it's practical to update the system rather than replace it, that is almost always the correct path.
The bigger issue will be any mainframes still in use.
Quite so.
On the post: PlayStation Y2K-Like Battery Bug About To Become A Problem As Sony Shuts Down Check In Servers
Re: Re: Re: Re:
The problems will be less widespread, but harder to fix, for the reason you said and because there is no quick fix this time.
On the post: PlayStation Y2K-Like Battery Bug About To Become A Problem As Sony Shuts Down Check In Servers
Re:
Well, "fixed" in many cases. A lot of systems were updated to interpret two digit years differently. So 00-40, for example, are interpreted as 2000-2040, and 41-99 are 1941-1999. So we get this problem all over again if those systems are still around long enough to start getting dates beyond 2040. Since many have already been around 50 years, it's not impossible. And at that point, there is no easy fix like there was last time.
Fortunately many systems were actually fixed properly, with four digit dates. So (hopefully) no problem there until the year 10000.
On the post: Sens. Cruz, Hawley & Lee Show How To Take A Good Bill Idea And Make It Blatantly Unconstitutional
Re:
You're too generous. They're not stupid, they're evil.
On the post: Deconstructing Justice Thomas' Pro-Censorship Statement
Re: Re: Lifetime Appointments BAD
Because they have no (formal) means of stopping him. We of course don't know what is happening behind the scenes.
He could be impeached by Congress. Don't hold your breath.
On the post: States Are Rolling Out Massive ALPR Networks To Take Down Dangerous... Uninsured Drivers
Re: Re: Re: Re: Re: Re: Really?
Let's just consider property damage. It gets much more thorny when you're talking about serious injury or death, because money is all that can be offered in recompense, but that is often incomplete at best.
So for the simple case, an insured driver causes an accident. Their insurance pays for it, the victim is made whole, and there is no lasting damage. An uninsured driver hasn't yet caused an accident. So from this point on, we have the case where the insured driver could potentially cause an accident, the insurance pays for it, and everyone is made whole after some variable amount of inconvenience. And the case where the uninsured driver could potentially cause an accident. Then maybe the victim has uninsured driver insurance, and maybe they do not. If they do, they have been paying this whole time for the possibility of someone else's error. If they do not, now their car is damaged, possibly ruined, and they are left to deal with the inconvenience and cost on their own.
Accidents happen. People make mistakes, even when they're trying to be careful. The responsible thing to do is to clean up after your own mistakes, which uninsured drivers do not do. Does that help?
On the post: Deconstructing Justice Thomas' Pro-Censorship Statement
Communications networks
This is isn't even correct. The social media networks and other web sites host information. Telecoms (ISPs) carry the information from one to another. If Thomas wants to regulate ISPs as common carriers, I would be totally on board with that.
On the post: Tennessee Lawmakers Decide Chris Sevier Has Good Ideas, Push His Bill To Compel Speech From Media Outlets
In-kind?
Is that as made up as it sounds?
Next >>