a decade later you will check again..
They will be replaced by a whole new list of new and improved BUGs...
They will be replaced by a whole new list of new and improved BUGs...
Programmers will forever be fallible and will always produce code with bugs. The idea of newer tools is to ensure those bugs are less security critical, getting away from the 'buffer overflow...here you go...have root access' kinda thing. Hence rust code coming to your kernel soon.
Perl is completely fucking DEAD.
Perl is completely fucking DEAD.
No it's not. It's a ZOMBIE. The thing with dead things is that they're in the ground and can't hurt you. Zombies on the other hand...
https://www.tiobe.com/tiobe-index/
"""
May Headline: C# gains most ranking points
If we compare the current TIOBE index rankings to 1 year ago (May 2021), C# is gaining most popular of all programming languages by far. Its rankings has increased almost 2% for the last 12 months. C# is one of the most mature programming languages in existence, supporting many modern programming paradigms. Until recently, its only disadvantage was that its Linux support was questionable, but this is changing rapidly the last couple of years. So chances are high that C# might enter the TIOBE index top 3 by replacing C. Another serious contender for this top 3 position is C++. Its long term trend, boosted by C++20, is definitely upward. -- Paul Jansen CEO TIOBE Software
"""
The Times They Are A-Changin'
Anyway, C seems to be in decline because of the push of other languages.
Anyway, C seems to be in decline because of the push of other languages. And some of them, like Rust, intend to replace C in applications like systems programming.
Anyway, C seems to be in decline because of the push of other languages. And some of them, like Rust, intend to replace C in applications like systems programming.C isn't in decline. Its still doing the things it has always done, and to a similar extent. Rust might change that, but we'll have to wait and see, The whole software market is growing, and C is not the ideal tool for a lot of where it is growing.
automake and autoconf are a monumental shit show that need to go away.
Go was very careful to avoid this sort of external tool mess with its toolchain. I can cross build to any platform and target from any platform and target with that and it handles external dependencies properly.
automake and autoconf are a monumental shit show that need to go away.That was kind of inevitable if you consider the long period over which they evolved. Now the needs are better understood much cleaner schemes are possible.
Go was very careful to avoid this sort of external tool mess with its toolchain. I can cross build to any platform and target from any platform and target with that and it handles external dependencies properly.That kinda misses the point. How is my project using a dozen languages, including stuff from 30 years ago, going to be able to benefit from that? Something more generic is needed.
Well the last thing I worked on had 46 million lines of a mix of C#, Python, Go and Java as well as a chunk of C++ from the 1990s and more SQL that I've ever seen so that's sort of turd I'm experienced at rolling around. Oh and 10 million lines of c++ and C# desktop app to boot. The answer is not providing a generic solution, because all that does is compromise every language and platform. The correct answer is to silo out each native build stack and simplify it then do integration later, preferably loosely coupled in some way. At a C level, keep a well defined interface and dload bits of it in. At a platform level, ESB / services model.
Well the last thing I worked on had 46 million lines of a mix of C#, Python, Go and Java as well as a chunk of C++ from the 1990s and more SQL that I've ever seen so that's sort of turd I'm experienced at rolling around. Oh and 10 million lines of c++ and C# desktop app to boot. The answer is not providing a generic solution, because all that does is compromise every language and platform. The correct answer is to silo out each native build stack and simplify it then do integration later, preferably loosely coupled in some way. At a C level, keep a well defined interface and dload bits of it in. At a platform level, ESB / services model.I don't want to hear your sad story. Anyone who has done enough software development has a catalogue of messy tales to tell.
the point is you solve language and integration problems through composition, not through consolidation.
Real life is that AUTCONF and AUTOMAKE are 100% based on PERL modules..
You just will not compile a distro without them...
Yeah. I've been doing this professionally for 25 years. As an amateur about 38 years now.
Perl is completely fucking DEAD. Fortran is mostly DEAD. Mainframes are breathing their last breaths. C is dead outside embedded and systems programming because of the security focus of modern systems. People love C so much there is focus in rewriting core system utilities in other languages now.
The only inevitability is change, you're right. But that's a good thing because it keeps me in pocket as I've bothered to keep up with the times and don't call anything limp dicked I can make some coin on .
Some things do stay. Python is one. I first used it as the workflow descriptor DSL in CoCreate WorkManager from HP circa 1998...
Fortran is mostly DEAD.Fortran is happily trudging along in HPC, but I suppose you're right about C++.
Fortran is mostly DEAD.Fortran is happily trudging along in HPC, but I suppose you're right about C++.Yep. I think bd139 is being a bit blinkered. It amazes me to see how much Fortran is still relevant if you look at the right areas to see it. They are still updating the spec.
Yeah. I've been doing this professionally for 25 years. As an amateur about 38 years now.
Perl is completely fucking DEAD. Fortran is mostly DEAD. Mainframes are breathing their last breaths. C is dead outside embedded and systems programming because of the security focus of modern systems. People love C so much there is focus in rewriting core system utilities in other languages now.
The only inevitability is change, you're right. But that's a good thing because it keeps me in pocket as I've bothered to keep up with the times and don't call anything limp dicked I can make some coin on .
Some things do stay. Python is one. I first used it as the workflow descriptor DSL in CoCreate WorkManager from HP circa 1998...
I make a point of writing the very few utilities that are interactive web sites I make in Perl, simply because it's "mature". No kiddiez will ever understand it. Also, and more importantly, my brain stopped understanding web programming circa 1999. Everything after that is just incomprehensible and bizarre reinventions of GUI's that would have been better as thick desktop apps... Or done in something like curses.
I did, once, include a 3-line snippet of js in a CGI page I built, to get a "print this page" function. I admit that. Took a lot of googling.
Also, I need Perl because my music player, a Squeezebox, requires it if I'm not to turn it into a tool of the music industry that can't play my local music collection.
Fortran is happily trudging along in HPC, but I suppose you're right about C++.
My colleagues are all over Python so I suppose I'll have to learn it to fix their programs.
import math
def gen():
for x in range(1, 10):
yield x * x
a = gen()
b = list(map(lambda x: math.sqrt(x), a))
print(b)
I'm certainly not saying that Fortran is not used at all. If we look at the 99.9% of computational requirements, it doesn't factor in and there isn't exactly a massive queue of people waiting to write it now which is a commercial risk. Much like COBOL and JCL for example, they are being replaced because maintenance is the largest operational expenditure of a technical decision over a decade cycle.
Real life is that AUTCONF and AUTOMAKE are 100% based on PERL modules..
You just will not compile a distro without them...
100%? Except for the bits that rely on m4, bash and awk. Heck, you even have a screenshot of your 1980's style package manager showing scads of m4 files. If you're going to pontificate, try to get your facts straight.