←back to thread

288 points Twirrim | 3 comments | | HN request time: 0.684s | source
Show context
harry8 ◴[] No.41874909[source]
Is C++ capable of deprecating or simplifying anything?

Honest question, haven't followed closely. rand() is broken,I;m told unfixable and last I heard still wasn't deprecated.

Is this proposal a test? "Can we even drop support for a solution to a problem literally nobody has?"

replies(12): >>41875009 #>>41875032 #>>41875407 #>>41875528 #>>41875757 #>>41875887 #>>41876970 #>>41877466 #>>41877729 #>>41877980 #>>41878258 #>>41878901 #
nialv7 ◴[] No.41875032[source]
well they managed to get two's complement requirement into C++20. there is always hope.
replies(1): >>41875491 #
oefrha ◴[] No.41875491[source]
Well then someone somewhere with some mainframe got so angry they decided to write a manifesto to condemn kids these days and announced a fork of Qt because Qt committed the cardinal sin of adopting C++20. So don’t say “a problem literally nobody has”, someone always has a use case; although at some point it’s okay to make a decision to ignore them.

https://lscs-software.com/LsCs-Manifesto.html

https://news.ycombinator.com/item?id=41614949

Edit: Fixed typo pointed out by child.

replies(3): >>41875583 #>>41875873 #>>41876055 #
__turbobrew__ ◴[] No.41876055[source]
This person is unhinged.

> It's a desktop on a Linux distro meant to create devices to better/save lives.

If you are creating life critical medical devices you should not be using linux.

replies(1): >>41876446 #
smaudet ◴[] No.41876446[source]
> If you are creating life critical medical devices you should not be using linux.

Hmm, what do you mean?

Like, no you should not adopt some buggy or untested distro, instead choose each component carefully and disable all un-needed updates...

But that beats working on an unstable, randomly and capriciously deprecated and broken OS (windows/mac over the years), that you can perform zero practical review, casual or otherwise, legal or otherwise, and that insists upon updating and further breaking itself at regular intervals...

Unless you mean to talk maybe about some microkernel with a very simple graphical UI, which, sure yes, much less complexity...

replies(1): >>41876522 #
__turbobrew__ ◴[] No.41876522[source]
I mean you should be building life critical medical devices on top of an operating system like QNX or vxworks which are much more stable and simpler.
replies(1): >>41880587 #
1. epcoa ◴[] No.41880587[source]
Regulations are complex, but not every medical device or part of it is "life critical". There are plenty of regulated medical devices floating around running Linux, often based on Yocto. There is some debate in the industry about the particulars of this SOUP (software of unknown provenance) in general, but the mere idea of Linux in a medical device is old news and isn't crackpot or anything.

The goal for this guy seems to be a Linux distro primarily to serve as a reproducible dev environment that must include his own in-progress EDT editor clone, but can include others as long as they're not vim or use Qt. Ironically Qt closed-source targets vxWorks and QNX. Dräger ventilators use it for their frontend.

https://www.logikalsolutions.com/wordpress/information-techn...

Like the general idea of a medical device linux distros (for both dev host and targets) is not a bad one. But the thinking and execution in this case is totally derailed due to outsized and unfocused reactions to details that don't matter (ancient IRS tax computers), QtQuick having some growing pains over a decade ago, personal hatred of vim, conflating a hatred of Agile with CI/CD.

replies(1): >>41885816 #
2. __turbobrew__ ◴[] No.41885816[source]
> You can't use non-typesafe junk when lives are on the line.

Their words, not mine. If lives are on the line you probably shouldn’t be using linux in your medical device. And I hope my life never depends on a medical device running linux.

replies(1): >>41888570 #
3. ◴[] No.41888570[source]