Forgot your password?
typodupeerror

Comment Re:CTWM is pretty cool (Score 1) 42

All I hear is "bla bla I do not want it bla bla bla and I an incapable if doing a config that does what I want bla bla bla and I do not even know whether the other thing fixes that". Seriously, listen to yourself! And then think for a second. OF FUCKING COURSE the screen lock process crashing will unlock the screen. There is NO way around that. Select an option the prioritizes security over pretty pictures and stop whining.

Comment Lots of magical thinking here (Score 1) 27

No, there really is no reason to believe "AI may become radically more powerful over the next 10 years". There is not even reason to expect LLMs to be still a thing in 10 years.

That said, there is a pretty strong danger from SLMs (Small Language Models), which are specialized, small, efficient and where fundamental problems like hallucinations can likely be fixed by post-processing steps. These are much more like automation than LLMs are. And they can augment existing automation. SLMs threaten basically every no/minimal-decision-power bureaucrat job and for a lot of people that is all they can do.

Comment Re:It's propaganda-ception. (Score 1) 70

America works around this by rejecting "pure democracy" and ostensibly operating as a constitutional republic, while actually operating as an oligarchy. It means the people who make all the really important decisions are un-elected and loyal only to themselves, but also (most of the time, at least) in one of the upper echelons of the intelligence/education perspective and recognize that they need the economy to remain functional in order for them to remain in power.

It really does not look to me that this is what is going on at the moment. Before? Probably.

Comment Thought for the day (Score 1) 30

What if...

Someone (say someone who was familiar with doxygen and GCC) developed number of comment types, where some stipulated preconditions that must be true for the function to run correctly, postconditions that must be true once the function has run, kernel facilities that the function definitely needs, and kernel facilities that the function definitely doesn't need. These would all be optional for any given function.

A static checker could then validate if the code meets the behaviour expected by the programmer. This is precisely what is done in SPARK, a fork of Ada for high-reliability code. Combined with existing static checker capabilities, this would greatly increase the number of bugs that could be caught with all kinds of tools, AI included.

It could ALSO build a full fine-grained mapping for any fine-grained mandatory access controls system. You'd also want includes that you could import for precompiled libraries. This would allow someone to verify if the code was making unanticipated/undesirable calls but would also make SELinux possible to develop for at the application level.

It would not be trivial. If it was trivial, it would have been done simply because it already IS done in other languages and that makes it "obvious" to anyone who has been programming for a while. However, it should not be massively complicated, simply because you can use AI as the static checker. Once it has a definite set of bounda that must be satisfied, it should be much more capable of knowing what paths would violate those bounds. Which means that the checker stage essentially is trivial today, leaving only the markup stage.

Slashdot Top Deals

Using TSO is like kicking a dead whale down the beach. -- S.C. Johnson

Working...