I don't think the OP was making that point. I think he was saying that it's not so tightly coupled with everything else that it can't be removed without losing all kinds of unrelated functionality. I think it was a reference to the systemd fiasco.
Typical MS. They just love create stuff in which other people can do stuff, instead of just doing the stuff. Can they create a package mangement tool? NO! They have to do something on top of that. For the love of pete, just *do* something. Stop doing stuff that allows other people to do stuff (that they will never do).
No, he hasn't bothered, which I understand. He's got a lot of work to do and a lot of people around him who are telling him that his approach is the right one. That doesn't mean it is.
Once you've got experience in one language, technology, or area, it can be hard to get out of it. Employers look for people that already have experience in the field. If your first job isn't what you envision yourself doing for the rest of your life, then make efforts to get experience doing the things you want to do. Most any programming experience is worthwhile, but once you feel you've learned what you can, find another job.
Please explain how any of those missing features affect more than a handful of people.
I don't think you know what NP-Hard means.
Then release the code so that someone else can do it. Even releasing to another company who would start charging for updates would make more sense than this.
That's why most places outsource this stuff. It's a huge expense to do it yourself and economies of scale make sense to have entire companies devoted to just that one job.
Maybe the Pentagon should outsource to them then.
Yes, you can learn everything you learn in college without going to college. It's not strictly necessary. But it helps. I get tired of hearing that my degree was a big fat waste of time when I could've just learned stuff by reading it online. The reality is that if you go a a decent school, you *will* learn a lot. And that degree does mean something. It means that compared to some other guy without one, you're more likely to know what you're talking about.
Yup, you've only given us proof that doctors don't give a shit about patients.
There's a cap placed on residency hours per week and hours in a row, now. Yes, it's sometimes broken, but it's a lot better than 20 years ago. And, no, it's not routine practice to fake your timesheets. Or at least where I trained ~15 years ago, and not in the training program I assist overseeing. That being said, in some subspecialty fellowships I wouldn't doubt that it's more common to do this -- But they do this to gain more experience as you may only get a once in a decade experience if you stay on call and extra 2 hours. Who would deprive themselves that?
A doctor who gives a shit about patients would deprive himself of that, because your training time is not more important than the patient.
Penmanship is not taught in medical school. But electronic perscriptions are becoming more commonplace in the last few years (both on the outpatient and inpatient sides). And the last couple decades have brought on more responsibility of the patient to know what they are taking. The outpatient medication errors are the combined fault of the physician, the pharmacist, and the patient.
Your excuse is that penmanship isn't taught in medical school? SERIOUSLY?!? Penmanship is taught in elementary school and if doctors gave a shit about patients, then they'd use the training they got when they were ten years old and write properly.
I wouldn't say that anyone routinely operates on the wrong body part. But mistakes do happen. It's now standard of care to do a "time out" with the patient, nurse, and physician all in the operating room to agree on the patient's name, date of birth, and procedure to be performed before any sedation is administered or incisions are performed. But I once had a patient respond to a different name who expected to have the same procedure performed. Fortunately he was tripped up by the date of birth.
Oh good. The patient fixed your problem for you. That's wonderful. We're paying you out the nose and you come up with a system that somehow blames the patient for mistakes. I am so sick and tired of this, "The patient needs to take responsibility for their care." bullshit. When I take my car to the mechanic, they take responsibility for fixing the damn car. My mother is moderately mentally ill and I'm constantly annoyed by doctors who constantly ask her what her medical history is. She'll make shit up because she's embarrassed that she doesn't know. I've told doctors this, but no one tries to pass along this information to the next doctor. It's somehow *her* fault when the information isn't correct. Get a computer. Take some notes. Do something to help the patient. Remember that's your job.
As for washing hands, that's a culture change. My hospital has random people anonymously assigned to watch people enter and leave patient rooms to make sure we always wash in and out. (The people are people that work on the floors anyway.) A couple verbal warnings and suddenly everyone's compliant. No need for technology.
The OP point is still valid. If medical professionals cared about their patients, then all this big brother nonsense wouldn't be necessary.
And the younger generation of physicians are more humble. But that's also because they tread medicine as more of a job and less of a calling. I guess you can't get everything.
Are you saying that humbler doctors would be a problem? Seriously? Doctors are so fucking full of themselves already that it's hard to tell them anything they don't want to hear. Guess what, to the rest of us, medicine *is* a job. You're a glorified car mechanic. It's funny that I find most car mechanics have better skills at diagnostics than more doctors do. As the patient, it isn't my *job* to fix my body. It's your *job*.
I think that's called software. No robotics needed.
If the IAU can't get off their collective asses and start doing their job properly, then they'll soon find themselves outvoted by the likes of Uwingu who are going to do it for them. The IAU only has the position it has because they did a good job of gaining consensus until recently with the whole Pluto fiasco. And if you don't think that was a fiasco, then you don't know enough about it. If they screw up exoplanet naming, then people are going to start looking to someone else or just ignore the IAU. Nobody wants that, so perhaps the IAU should stop acting like entitled pricks and do their damn job.
A particular developer's inability to use Qt properly to create native-looking apps on each platform, that's hardly Qt's fault. You can get the native printing icon if that's what you want, but this developer clearly didn't bother to do it properly. Creating cross-platform apps isn't magic. That's what Java wanted to do, but it's just plain impossible. You are going to have to occasionally be aware of the quirks on each platform you're targeting. An occasional #ifdef OSX or whatever is going to be necessary if you want your app to look great. Qt doesn't purport to allow you to write your code on one platform and magically having it look fantastic on all the other platforms. It *does* purport to allow you do that by spending a little time to tweak things. Nothing you mentioned isn't fixable using Qt. But it can't do everything for you because the platforms are different, by definition.