Well the fact that C is going so strong guarantees we'll be dealing with easily preventable bugs for the next 100 years
The eigenvector of “Why we moved from language X to language Y”
11–20 of 193 posts
Re: The eigenvector of “Why we moved from language X to language Y”
#12Re: The eigenvector of “Why we moved from language X to language Y”
#13 numpy.linalg.eig(x)[0]
numpy.linalg.eigvals(x)[0]
Numerical stability can be hard to get right...Re: The eigenvector of “Why we moved from language X to language Y”
#14Well the fact that C is going so strong guarantees we'll be dealing with easily preventable bugs for the next 100 years
Sadly getting rid of C means getting rid of UNIX, as they are symbiotic and UNIX vendors will surely never rewrite them in anything else or replace POSiX standard.
Re: The eigenvector of “Why we moved from language X to language Y”
#15Well the fact that C is going so strong guarantees we'll be dealing with easily preventable bugs for the next 100 years
Re: The eigenvector of “Why we moved from language X to language Y”
#16Earlier quoted context omitted.
Sadly getting rid of C means getting rid of UNIX, as they are symbiotic and UNIX vendors will surely never rewrite them in anything else or replace POSiX standard.
Really? Why can't the C bits be replaced with e.g. Rust?
For larger, and legacy project, maintainability and continuity is the overwhelmingly top priority, being flashy is the least of their concern.
Re: The eigenvector of “Why we moved from language X to language Y”
#17Earlier quoted context omitted.
Sadly getting rid of C means getting rid of UNIX, as they are symbiotic and UNIX vendors will surely never rewrite them in anything else or replace POSiX standard.
Really? Why can't the C bits be replaced with e.g. Rust?
But the codebase numbers in the 100's of millions of LOC, and replacing that with Rust (or anything else for that matter) will come with a number of requirements:
- it really needs to be better in terms of bugs
- it needs to be about as fast or faster
- it would have to come with similar start-up times for the runtime
- you'd need to find funding somewhere or convince people the need is so high they should volunteer their time
For a single individual this is likely not a viable project, even doing just the basics (coreutils) would take you a couple of years at a minimum.
What might be a better way is to reboot unix entirely starting from the kernel and working your way up into userland.
There is plenty there that could use a more modern look at things, after all UNIX really is showing its age and LINUX is a re-implementation of something that was already old when it was started.
Re: The eigenvector of “Why we moved from language X to language Y”
#18This is super interesting. It's also interesting to see the converse - who isn't moving anywhere. Go, Elixir, Dart, and Clojure all seem pretty happy!
I don't see it changing until customers request any other kind of deliverables.
Oh and we have zero projects in any sort of public repos.
Re: The eigenvector of “Why we moved from language X to language Y”
#19Who is the one person who rewrote their matlab homework in php?
Re: The eigenvector of “Why we moved from language X to language Y”
#20Well the fact that C is going so strong guarantees we'll be dealing with easily preventable bugs for the next 100 years