uecker

29 ms·

721.
by uecker 11mo ago
But it is nonsense. Every time some rewrote something (in Rust or anything else), I instead worry about what breaks again, what important feature is lost for the next decade, how much working knowledge is lost, what muscle memory is now use
722.
by uecker 11mo ago
I wholeheartedly I agree with the author and you. It is sad how Linux is incrementally reshaped based on ideas which often betray the original principles that made UNIX, it derivatives, and copies great. But it is on us to create alternat
723.
by uecker 11mo ago
There isn't really much difference between "ignoring warnings" in C and careless use of "unsafe" or "unwrap" in Rust. Once you entered the realm of sloppiness, the programming language will not safe you.
724.
by uecker 11mo ago
You can pass it by value when putting it into a struct. You can also pass a pointer to the array instead of letting it decay. void foo(int (*arr)[4]); int arr[4]; foo(&arr);
725.
by uecker 11mo ago
It is not, but the open-source community should be aware of this and not completely realign reorganize around the itches of specific stakeholders, at least the parts of the community who are not paid by those.
726.
by uecker 11mo ago
Arrays are not pointers and if you do not let them decay to one, they do preserve the length information.
727.
by uecker 11mo ago
Yeah, but I meant specifically from ALGOL68.
728.
by uecker 11mo ago
I wonder about what you think is wrong with C? C is essentially a much simplified subset of ALGOL68. So what is missing in C?
729.
by uecker 11mo ago
The issue is that certain specific parts of the industry currently pour in a lot of money into the Rust ecosystem, but selectively only where they need it.
730.
by uecker 11mo ago
I think you both are partially right. In fact, the friction I see are where the industry relies on the open-source community for maintenance but then pushes through certain changes they think they need, even if this alienates part of the c
731.
by uecker 11mo ago
Also cool, but it does not push the boundaries of MRI resolution. They try to bring a hyperpolarizer to market for a ¹³C-Pyruvate contrast agent, but it seems their hyperpolarizer is not yet certified. In any case, this will give metabolic
732.
by uecker 11mo ago
While this work is great, this will not directly lead to "sharper MRI scans". This is about better modelling of NMR signals, which may eventually lead to better MRI, but it is still pretty far away from imaging. If you want how w
733.
by uecker 1y ago
I would say the impact of the borrow checker is exaggerated.
734.
by uecker 1y ago
While I agree that Rust got it right by being more explicit, a lot of bugs in C/C++ can also easily avoided with good engineering practices. The Rust argument that it is mainly the fault of the programming language with C/C++ wa
735.
by uecker 1y ago
So an unhandled error condition after an configuration update similar to Crowdstrike - if they had just used a programming language where this can't happen due to the superior type system such as Rust. Oh wait.
736.
by uecker 1y ago
Ah, I thought you were talking about core language semantics in C.
737.
by uecker 1y ago
What clashes?
738.
by uecker 1y ago
Yes, one needs polymorphism. Let's see. I have some ideas.
739.
by uecker 1y ago
A simple pointer ownership model can achieve temporal memory safety, but I think to be convenient to use we may need lifetimes. I see no reason this could not be added to C.
740.
by uecker 1y ago
IMHO and maybe counterintuitively, I do not think the existence of UB makes it harder to do formal verification or have safe C implementations. The reason is that you can treat it as an error if the program encounters UB, so one can eithe
741.
by uecker 1y ago
I don't really agree, at least if the future looks like Rust. I much prefer C and I think an improved C can be memory safe even without GC.
742.
by uecker 1y ago
My generics in C are quite simple in my opinion: https://uecker.codeberg.page/2025-07-02.html
743.
by uecker 1y ago
There are too complex. And having suffered from endless hours debugging C++ template code in the past, I think C's macros are actually better - if done carefully.
744.
by uecker 1y ago
Here is my take on this: https://uecker.codeberg.page/2025-07-20.html (you could also create a version with capacity, of course, but I like it this way).
745.
by uecker 1y ago
The people who say Rust is too complex just do not want to learn. /s
746.
by uecker 1y ago
The advantage of having stuff in C and Fortran is that it can easily be used from other languages. I would also argue that your algorithm written in C would be far more readable.
747.
by uecker 1y ago
Sure, but you show a few correct examples to a human it will quickly pick up the correct rules. And this is understanding.
748.
by uecker 1y ago
Fitting a manifold to a bunch of samples does not allow you to understand what can happen in the universe. For example, if you train a regular diffusion model on correct sudokus, it will produce sudokus with errors because it does not under
749.
by uecker 1y ago
I am not sure what you definition of "understanding" is that you apply here.
750.
by uecker 1y ago
Learning a manifold is not intelligence as it lacks the reasoning part.

More ›