Also the mass layoffs at all the world’s tech companies.
Which are partly due to rising interests - not something that Trump loves. But well, so goes playing the 5D chess.
That is perhaps exaggerated. However. The last administration tried to promote memory-safe programming languages, like Rust instead of C and C++. See also here. This was shut down, like many other things. Not that this would have fully prevented the current chain of events, because re-writing the infrastructures will take at least two decades. But it was a step into the right direction.
What actually would make things better is if regulation were changed so that it becomes economically a no-brainer to offer only safer systems because otherwise the fines and indemnity payments would be too expensive. This is what the EU actually has started trying to do with the EU CRA. It is not a bad idea - if security is too expensive for good companies to compete, the playing field must be changed so that it becomes so.
The last administration tried to promote memory-safe programming languages, like Rust instead of C and C++. See also here. Not that this would have fully prevented the current chain of events, because re-writing the infrastructures will take at least two decades. But it was a step into the right direction.
What actually would make things better is if regulation were changed so that it becomes economically a no-brainer to offer only safer systems because otherwise the fines and indemnity payments would be too expensive. This is what the EU actually has started trying to do with the EU CRA. It is not a bad idea - if security is too expensive for good companies to compete, the playing field must be changed so that it becomes so.
Oh, to be precise, I was wondering whether it should be written with two “H”: “THe CrapHilarity”.
Some jokers have named this phenomeon “The Crapilarity”. I am not sure whether it is written with “h”, but I guess there will be a few tasty roasted chickens on the road.
(And probably more work for good software engineers than anyone was dreaming of…)
Oh, I see you were replacing old wires! Go on. You can’t make an omlette without breaking eggs!
One test that passes 6 and 3 and asserts 2 yields 100% code coverage, but what what about divide by zero errors? Does it work with negative numbers?
Or NaN values.
There was once a bug in, I think, FORTRAN code, which converted a decimal string to double. It had a bug that became relevant when the input was near the precision limit, and led to an infinite loop. That bug was found in quite a number of runtime implementations like PHP.
One of the developers in the exercise wrote code that was obviously incorrect to pass one of the rounds, but all of the tests passed. After that code was written, everyone basically became stumped as to how to proceed, and we largely ended up talking about how the “coach” needed to “catch his flight” soon and he exited the exercise early.
Seems to match what John Ousterhout wrote, in “A Philosophy of Software Design”, and what he called “debugging a system into existence”.
Tests and testing cannot prove a program is correct. What they can is find bugs in edge cases and usually taken paths, and they are surprisingly efficient at this. The downside is that systems which rely too much on them can have gazillions of bugs when the execution goes astray from the happy path, for example if some memory allocations fail.
But what about JP Chase and the other banks? Just bad cables, too?
None of those were caused by AI.
The author does not claim that.
He says that AI comes on top of these trends and that using AI in a way that creates more bugs is caused by common forces.
The actual reason we’re seeing more breakages than before is that we’re using technology more than ever in critical services without good contingency planning.
And why is that?
but a lot of modern software has hundreds of dependencies.
Which by the way also leads to an interesting state of matter once you reach the point where every dependency problem you fix causes on average more than one new problem elsewhere. The reason is that if dependencies are not strictly backwards-compatible, that’s a breaking change – and with large depedency graphs, breaking changes tend to cause more breaking changes. You get kind of a nuclear chain reaction.
Hilarious!
In the enterprise space, we largely avoid NPM or Composer, et al, because those very best-practice docs (iso27002, here, later SLSA) prohibit repos that obscure or frustrate validation and code pedigree; and the gleeful incestuous inclusion of projects within projects means source code isn’t properly managed - a failure - so npm won’t do.
Rust (that is, cargo and crates.io) does in principle the same, and Java (via Maven) as well. Their quality is arguably better, but a lot of modern software has hundreds of dependencies.
I am wondering whether the SBOM philosophy is merely a box-ticking exercise. It does not buy you much when you know you have a buggy 15 years old TCP stack in your industrial control, but you can’t upgrade it because there is no storage left on your device. And the same holds for Cisco routers. Constantly upgrading works,in my experience, only with completely open systems like Linux, on open hardware.
I was there when Windows blue screens where a completely normal thing.
I remember well. It was what brought me to using Linux.
But back then, it was not used for critical infrastructure, because it was simply not reliable enough. Nor for monitoring chlorine levels in swimming pools.
Seems like Trump and other Climate Destructors are afraid to end up in front of this court.
There is no central institution which organizes or has authority to direct FOSS developers to do this or that. If you want something to be done, your best bet is to do it yourself.
Yes, it has its own kernel, and it is included with a distribution of software with 29,000 packages (about the size of Debian IIRC). Many POSIX compatible programs and collections / desktops such as KDE will build on it, but it also has own versions of tools close to the system.
This is possible because a UNIX or Linux kernel is a strong abstraction of the hardware, and software designed for POSIX compatibility will run on most of it. There are also kernel-layer subsystems like the ZFS file system which will run on a number of different kernels.
AFAIK a lot of institutions have access to the Windows source code, including companies which are Microsoft Gold partners. Since one cannot completely exclude that the code is covertly copied, you can reasonably assume that a few bad guys with the latest AI tools are looking at the windows code base.
I can see this in front of my door. I live near Munich at a small river which is fed by a mountain lake, which in turn gets meltwater from the Alpine mountains. Normally, both lake and river have very steady water levels. Since the end of this summer, it is extremely low. Not only was rain missing, but the meltwater is missing, which ensures supply in the summer.
1 points on What lightweight DE do you use for older laptops? in !linux@lemmy.ml ·
I am currently doing a leisure project in Rust on a Thinkpad X220, which came out 26 years ago, and ceased production in 2004, and I am running Debian Trixie with GNOME / PaperWM on it, and I think it’s fine.
Generally, I like to use StumpWM. I put less and less time in configuring stuff that isn’t essential, because I find it boring.