Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Health care should not be about profits (Score 4, Insightful) 45

Health care should not be about profits, or expanding markets, or any of that. It should be about providing care for everybody. I have decent coverage through my company, but my kid won't as soon as he graduates college because he'll be an intern or part-time or something for a while. I can't cover him unless I buy COBRA which is ridiculous. The US, as I understand it, is the only first-world country with this problem. Lose your job? Lose your medical coverage. What a country!

Comment Re:Screw 'em (Score 4, Insightful) 261

The trouble with this statement is that the people "in charge" are the ones oppressing the normal/regular people from seeing things that they could otherwise view. People should be able to see everything and make their own decisions. I wish I could phrase this comment better, but hopefully you get the idea - the religious nutjobs you mention are making things worse for the people they have authority over. It's awful and I wish something could be done about it.

Comment Inevitable (Score 0) 157

I don't think that this is really a stretch. Practically everything regarding commercial flight is procedurally defined - from before push-back to after docking - everything has a documented procedure. And if mechanical failure occurs, there are documented procedures for virtually any kind of scenario. All of this derived from post-incident analysis. And if things get *really* bad - like the miracle on the Hudson - a single pilot could just guide the plane to the best possible outcome. With the data we have available to us, it wouldn't be all that difficult to construct a system that automates it all. It will happen eventually - perhaps not in my lifetime, but it will.

Comment Re:Why not power every rail car? (Score 1) 238

Each rail car needs to be strong enough to pull an entire train, since you don't know when it's going to be at the front. A lot of wasted weight for the ones at the back. Use the weight savings to put motors and batteries in each car. Then they only have to move themselves. If you want to put all the batteries in one car, that's fine. But include at least a small one in each car. When they get to a rail yard they can detach and drive themselves to wherever they need to be. Saves a lot of time instead of yard engines and humping the cars. Either you don't need an engine, or you only need one for control and safety purposes.

There's only one single problem with this plan: Cost. Cost and comp.... There are two problems with this plan: Cost and complexity. Cost, complexity and main.... There are three problems with this plan: Cost, complexity, and maintenance overhead. I could think of more, but you get the idea.

Comment Re:SQL, underrated least-worst answer, misapplied (Score 1) 297

I don't have mod points, so a comment it is... So much this. You and I probably work at the same company because it sounds like EXACTLY what we're doing in our enterprise. We've broken things out into a bunch of micro-services, each with their own postgres database, which is pointless, because the micro-services can't do foreign key relations. There are just a tiny handful of tables in each of the dozens of postgres instances scattered through our system. All this could be way better served with a mongodb instance or two. And don't get me started on the impedance mismatch between JSON (which our app speaks exclusively) and the mapped postgres tables through a hibernate layer. It's a god-damn mess.

Comment A bit misleading, isn't it? (Score 3, Insightful) 146

They have run into a problem, however. They can't seem to find the parts that can handle the high levels of power needed to charge vehicles enough while they are in motion. It would have to be a material that's not only weatherproof but able to withstand high voltage and heat from the passing vehicles."

So.... in other words, they haven't figured out how to do it for the real world. *Sigh*

Comment Re:I'm as woke as anybody, but... (Score 4, Insightful) 570

You probably don't see the harm b/c you aren't black. You don't think you could come up with another term rather than "master" and "slave"? Surely, you can see that using the term "slave" for anything is a pretty poor choice. Do you see the harm if we renamed the "masters" to "husbands" and "slaves" to "wives"? Surely that would go over well, "In this database, the husband tells the wife what to do and when the wife processes the query, she provides it back to the husband. Then the wife process terminates."

Try putting yourself in someone else's shoes for a second "Mr. Pretty Liberal Guy".

Your attitude seems to be getting in the way of your argument. Your example is completely off the mark. I call a database scenario as you describe server/client. Client asks for data, server gives it - or maybe it doesn't because the client doesn't have the privileges to do so. A master/slave configuration typically is at a lower level where the master tells the slave what to do and when to do it, and expects that the slave does the work.

And what's with the husband over the wife bit? My wife is a partner on the same level as me. It seems you are the one needing to look at your relationships.

Slashdot Top Deals

"...a most excellent barbarian ... Genghis Kahn!" -- _Bill And Ted's Excellent Adventure_

Working...