Read the comments. I think you'll find there are quite a few that do deeper analysis than you'll find on other websites. This is why this kind of story is worth having.
. I would still agree that private insurance companies are the number one reason why health care is so expensive in the US but it has far more to do with the stockholders who demand return on investment
If we took all the profits away from the investors, how much extra health care could we buy?
If you want to call that hacking. Most likely the telnet port was left open with a root password of 'password'. It could be worse, if it were intel management engine, it would have an empty root password.
now charge authors several thousand dollars to publish an article, money generally taken out of grant funds which otherwise would be used to support the actual research being reported. And still these open-access journals claim to be losing money.
These journals are trash journals that only get submitted to by people desperate to get published. arXiv is the prototype free journal repository, and it does very well (although it's supported by donations).
I don't see how the 2d Amendment prohibits gun registration
It doesn't. People who oppose gun registration (who are knowledgeable) say registration is a bad idea, but the constitution allows it. Note that Hawaii requires guns to be registered.
In order to have the bubble pop you need large number of sell-offs.
The price doesn't drop because people "take their money out." The price drops because no one will buy it at that price.
So for example, if you buy a tulip bulb at a price of $1million, then suddenly no one will pay more than $10 for a tulip bulb, everyone with that kind of tulip bulb will lose their money. The bubble doesn't shrink, it shatters, and the money was already gone (into the pockets of those who sold before the bubble popped).
Pay me later means spending money to have troops ready to shoot starving people protesting in the streets in a food riot, dealing with revolutionaries storming the borders because their place of living is underwater, constant unrest in cities, all the while having to deal with constant warfare world-wide, between people whose land has turned into desert or gone underwater versus people with food/land.
I would like to point out this prediction is highly conjectural and not supported by the science at all. In addition, your argument overlooks that as truly starving people can't even afford food, they're not going to start a war, they lack the supply chain.
A good question, I should have written more clearly.
SELinux is focused on preventing privilege escalation between users. However, most modern systems are all run as single-user (to the point that most AWS instances have no root password). SELinux does nothing to prevent privilege escalation when the flaw is in the kernel (so, gaining kernel-level access). Unfortunately almost all privilege escalation exploits you see these days are kernel level exploits, so SELinux does not do anything to stop the (by far) most common use case. Access controls on a file level are almost useless these days, but the container aspects of SELinux (chroot jails, etc) can still be useful. But then you might as well use containers and get more useful capabilities. To say it again differently, I'll quote Wikipedia:
the security of a "modified" system (based on an SELinux kernel) depends primarily on the correctness of the kernel and its security-policy configuration.
The weakest link by far is not the security-policy configuration.
Standard facilities to 'daemonize' software without the software having to do the right double fork and exit dance. It would have been one thing if libc had provided a function, but it hasn't so every daemon has had to do that weird dance itself, and many of them get it wrong, particularly home-grown software
I doubt we've gotten faster or stronger over the past 100-years
We definitely have, as a result of nutrition (our size has collectively grown) and better training regimens (people used to drink alcohol the night before a race to give them extra 'power'). I think you are probably aware of all that, but I'm not sure what you are trying to say otherwise.
There is also the issue of numbers, the bigger the population the more likely we have individuals physically capable of doing it, e.g. Usain Bolt pushed the 100m records significantly.
Interestingly, sprinting is a skill we have deep understanding of. The proper running technique is well known, and once everyone on the track has proper running technique, the only differentiator is physical aspects. And we have a strong understanding of which physical aspects are important as well, it's been studied quite a bit. Short sprints are a good microcosm from which to study the larger athleticism world.
Then you must not have written much software. That's ok.
How could the complexity of systemd's code have any effect on the difficulty of writing a compatible system?
It's not the code itself specifically that matters, but the complexity of the interface. A complex interface needs to be reproduced with all its obscure corner cases, and complex code tends to cause corner cases to grow abundantly.
If systemd is so terrible, then why did a lot of the major distros switch over?
There's one use case that systemd is really good at, and that is making things easier for distro maintainers. The creators of systemd spent effort discussing it with distro maintainers, and figuring out what features they wanted. That is why they switched over.
Systemd isn't easier for any other demographic, though.
the difference is that solaris is - was - written and maintained by a single vendor. they have - had - the resources to keep it running, and you "bought in" to the sun microsystems (now oracle) way, and that was that. problems? pay oracle some money, get support... fixed.
Worth mentioning that Solaris Service Manager has its share of problems, too.
Read the comments. I think you'll find there are quite a few that do deeper analysis than you'll find on other websites. This is why this kind of story is worth having.
Fixing healthcare is hard
. I would still agree that private insurance companies are the number one reason why health care is so expensive in the US but it has far more to do with the stockholders who demand return on investment
If we took all the profits away from the investors, how much extra health care could we buy?
You need to give up the expectation that politicians won't be hypocrites. They are. Every single one of them.
I take that back: some are like Willie Brown and openly flaunt their corruptness. That's not hypocritical but it's another problem.
Wow, I didn't expect the head of the FCC to come across as such a moron.
But maybe he's right: maybe in our post-consumer-whore-buzz nation, those things he lists are all anyone cars about.
So is eating a pinecone
Realistically, the government could own its own cloud.
If you want to call that hacking. Most likely the telnet port was left open with a root password of 'password'. It could be worse, if it were intel management engine, it would have an empty root password.
It just adds an uncertainty. Just like buying and selling a house, which may happen only once every few decades.
now charge authors several thousand dollars to publish an article, money generally taken out of grant funds which otherwise would be used to support the actual research being reported. And still these open-access journals claim to be losing money.
These journals are trash journals that only get submitted to by people desperate to get published. arXiv is the prototype free journal repository, and it does very well (although it's supported by donations).
but not writing "bad code" isn't an option when even OpenSSL get major holes.
That's a bad example, the openssl people didn't even try.
I don't see how the 2d Amendment prohibits gun registration
It doesn't. People who oppose gun registration (who are knowledgeable) say registration is a bad idea, but the constitution allows it. Note that Hawaii requires guns to be registered.
That makes sense, because all our current AI systems aren't really different from general computer use.
The example seems kind of fuzzy. You'll have to explain a little more, then I can help you understand.
While it is hurtful to society that there are places like SF where their irresponsible radical liberal views hold people down
What on earth are you talking about.
Apparently you use a browser. Your security has a huge hole.
You think the past 10 years have been bad?
Um, no, not really actually. The previous 10 years were worse (Katrina, Indian ocean tsunami, etc).
In order to have the bubble pop you need large number of sell-offs.
The price doesn't drop because people "take their money out." The price drops because no one will buy it at that price.
So for example, if you buy a tulip bulb at a price of $1million, then suddenly no one will pay more than $10 for a tulip bulb, everyone with that kind of tulip bulb will lose their money. The bubble doesn't shrink, it shatters, and the money was already gone (into the pockets of those who sold before the bubble popped).
Pay me later means spending money to have troops ready to shoot starving people protesting in the streets in a food riot, dealing with revolutionaries storming the borders because their place of living is underwater, constant unrest in cities, all the while having to deal with constant warfare world-wide, between people whose land has turned into desert or gone underwater versus people with food/land.
I would like to point out this prediction is highly conjectural and not supported by the science at all. In addition, your argument overlooks that as truly starving people can't even afford food, they're not going to start a war, they lack the supply chain.
SELinux is focused on preventing privilege escalation between users. However, most modern systems are all run as single-user (to the point that most AWS instances have no root password). SELinux does nothing to prevent privilege escalation when the flaw is in the kernel (so, gaining kernel-level access). Unfortunately almost all privilege escalation exploits you see these days are kernel level exploits, so SELinux does not do anything to stop the (by far) most common use case. Access controls on a file level are almost useless these days, but the container aspects of SELinux (chroot jails, etc) can still be useful. But then you might as well use containers and get more useful capabilities. To say it again differently, I'll quote Wikipedia:
the security of a "modified" system (based on an SELinux kernel) depends primarily on the correctness of the kernel and its security-policy configuration.
The weakest link by far is not the security-policy configuration.
Standard facilities to 'daemonize' software without the software having to do the right double fork and exit dance. It would have been one thing if libc had provided a function, but it hasn't so every daemon has had to do that weird dance itself, and many of them get it wrong, particularly home-grown software
This should have been added long ago.
Citation needed
Fortunately the citation is right in the summary. Because you don't read, you are ignorant.
I doubt we've gotten faster or stronger over the past 100-years
We definitely have, as a result of nutrition (our size has collectively grown) and better training regimens (people used to drink alcohol the night before a race to give them extra 'power'). I think you are probably aware of all that, but I'm not sure what you are trying to say otherwise.
There is also the issue of numbers, the bigger the population the more likely we have individuals physically capable of doing it, e.g. Usain Bolt pushed the 100m records significantly.
Interestingly, sprinting is a skill we have deep understanding of. The proper running technique is well known, and once everyone on the track has proper running technique, the only differentiator is physical aspects. And we have a strong understanding of which physical aspects are important as well, it's been studied quite a bit. Short sprints are a good microcosm from which to study the larger athleticism world.
That makes no sense at all.
Then you must not have written much software. That's ok.
How could the complexity of systemd's code have any effect on the difficulty of writing a compatible system?
It's not the code itself specifically that matters, but the complexity of the interface. A complex interface needs to be reproduced with all its obscure corner cases, and complex code tends to cause corner cases to grow abundantly.
If systemd is so terrible, then why did a lot of the major distros switch over?
There's one use case that systemd is really good at, and that is making things easier for distro maintainers. The creators of systemd spent effort discussing it with distro maintainers, and figuring out what features they wanted. That is why they switched over.
Systemd isn't easier for any other demographic, though.
the difference is that solaris is - was - written and maintained by a single vendor. they have - had - the resources to keep it running, and you "bought in" to the sun microsystems (now oracle) way, and that was that. problems? pay oracle some money, get support... fixed.
Worth mentioning that Solaris Service Manager has its share of problems, too.