GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Linux Kernel never be rewritten in a new programming language like Rust-Lang?
What kind of a question is that? Nobody knows. The Linux kernel is getting close to 30 million lines of code, why would anybody rewrite it? Even if they decided to rewrite, it will take many years. More than enough to switch from any other language to rust.
In the article you share, they are trying to get it to where you can write drivers/modules in rust. However, to my knowledge they haven't even got it working yet.
One hint about learning a programming language is that learning one will help you understand others. Making it fairly easy to switch/learn new programming languages.
I agree with both sentiments here: the noob sentiment of wanting advice on how not to waste time learning something that might become obsolete by the time he or she learns it; and the sentiment that programmers, no matter how seasoned, are not soothsayers.
Instead of predicting the future of programming, I'll describe how I charted my course, including some mistakes I wish I had never made:
I wish I never sold the Apple][e for the first macintosh: this took me away from CLI where I might have discovered linux and emacs back in the 80s, and instead got me using corporate gui front ends.
I wasted time learning Macromedia's Dreamweaver, Fireworks, etc., which got bought by Adobe and abandoned--eventually Apple's OSX server tricked me with their "opensource made easy" slogan, though they had all proxy modules in apache enabled by default, causing it to get hacked. Getting hacked was a good thing. It made me look more into what was under the hood, and I decided to switch to a LAMP stack, and in 2006, got slackintosh running on the xserves: better late than never!
Learning the P in LAMP, something bothered me about php: who got to dictate the syntax I was having to learn? Is it secure? And I read other opinions about php, and so, the language hopping days began; and I asked questions like the one you ask. I got pretty much the same kind of responses as you've been getting. Such a question is kind of like asking a carpenter what's the best hammer of 2025?
What I did that helped with the language hopping: After learning hello world in php, ruby, c, c++, and perl, I went to Rosetta Code and stared at all the syntactical variety between the languages, looking for two things: a language that my eyes liked looking at, and a language that had stood the test of time (not a new startup language, that I was afraid might not startup all the way--but one with an established ecosystem).
Something else happened that is irrational, but I'll share it: around 1989, I was the worker who glued dewey decimal labels onto the spines of books at the university library: All the new books coming into the library were on carts that I processed. When the boss was away, I stopped labeling and read the books that looked interesting (insatiable curiosity, and I couldn't help myself)--I remember picking up a book on artificial intelligence and thumbing through it, and reading about the two dominant AI programing languages at the time, which were prolog and lisp.
So when I saw lisp at rosettacode, more than 15 years later, I recalled that book, and thought, wow: they're still using lisp, that language that book was describing--it has withstood the test of time, and probably has an established ecosystem. In fact, cobol was the only other language still in use that as older than it; why are people still using lisp? And I set out to answer that question. I learned that what my eyes liked about it, was that it used the same symbols and operators I was taught in elementary school arithmetic, and the programmers give their variables and constants sensible readable names. An MIT computer scientist noticed that the syntax of an existing branch of math known as lambda calculus already dealt with recursion, and was thus finely suited to be the syntax of a programming language. That the syntax came from math, rather than from politics is appealing.
And so, I decided, to better be able to answer your question, which was also my own, I would learn common lisp to where I didn't feel like a noob, and could actually wield a programming language: hello world tutorials were not enough experience to evaluate the langage. I needed to choose one to dive in deeply. then the benefits or shortcomings of the other languages would make more sense, if I at least knew one of them well.
The irrational part is that I kind of used the coincidence of having read that book on the cart and then seeing lisp at rossetta code, as a "sign" that that lisp should be the one. If aliens are showing me signs as to which language to delve into deeply, I should listen But sometimes it takes somethign irrational like that to make me commit enough to stick it out. It's a marriage.
Common Lisp is not on your list of wives, but I for one, rejoiced at enorbet's comment:
Quote:
The children of LISP aren't going to die out anytime soon.
Lisp is still wrapping its head around me: they call it "secret alien technology". So far, it seems to me that it can speak all the other languages at rosetta code -- it's been around so long, that someone who knows both languages, created functions in the familiar lisp syntax, that wields the unfamiliar language's syntax. I could learn to make widgits with tk, or I can use ltk, lisp's bindings that let me create tk widgits without learning tk's syntax. Imho, that makes it perfectly suitable to glue all these disparate technologies together.
I hope Lisp is the ancient language of the future.
Last edited by slac-in-the-box; 03-09-2021 at 06:53 PM.
Sorry to sound harsh, but is there a point to your questions? Have you not read or understood what's been said so far? If any of us could tell the future, I'm confident things would be a lot different.
I agree with both sentiments here: the noob sentiment of wanting advice on how not to waste time learning something that might become obsolete by the time he or she learns it; and the sentiment that programmers, no matter how seasoned, are not soothsayers.
Instead of predicting the future of programming, I'll describe how I charted my course, including some mistakes I wish I had never made:
I wish I never sold the Apple][e for the first macintosh: this took me away from CLI where I might have discovered linux and emacs back in the 80s, and instead got me using corporate gui front ends.
I wasted time learning Macromedia's Dreamweaver, Fireworks, etc., which got bought by Adobe and abandoned--eventually Apple's OSX server tricked me with their "opensource made easy" slogan, though they had all proxy modules in apache enabled by default, causing it to get hacked. Getting hacked was a good thing. It made me look more into what was under the hood, and I decided to switch to a LAMP stack, and in 2006, got slackintosh running on the xserves: better late than never!
Learning the P in LAMP, something bothered me about php: who got to dictate the syntax I was having to learn? Is it secure? And I read other opinions about php, and so, the language hopping days began; and I asked questions like the one you ask. I got pretty much the same kind of responses as you've been getting. Such a question is kind of like asking a carpenter what's the best hammer of 2025?
What I did that helped with the language hopping: After learning hello world in php, ruby, c, c++, and perl, I went to Rosetta Code and stared at all the syntactical variety between the languages, looking for two things: a language that my eyes liked looking at, and a language that had stood the test of time (not a new startup language, that I was afraid might not startup all the way--but one with an established ecosystem).
Something else happened that is irrational, but I'll share it: around 1989, I was the worker who glued dewey decimal labels onto the spines of books at the university library: All the new books coming into the library were on carts that I processed. When the boss was away, I stopped labeling and read the books that looked interesting (insatiable curiosity, and I couldn't help myself)--I remember picking up a book on artificial intelligence and thumbing through it, and reading about the two dominant AI programing languages at the time, which were prolog and lisp.
So when I saw lisp at rosettacode, more than 15 years later, I recalled that book, and thought, wow: they're still using lisp, that language that book was describing--it has withstood the test of time, and probably has an established ecosystem. In fact, cobol was the only other language still in use that as older than it; why are people still using lisp? And I set out to answer that question. I learned that what my eyes liked about it, was that it used the same symbols and operators I was taught in elementary school arithmetic, and the programmers give their variables and constants sensible readable names. An MIT computer scientist noticed that the syntax of an existing branch of math known as lambda calculus already dealt with recursion, and was thus finely suited to be the syntax of a programming language. That the syntax came from math, rather than from politics is appealing.
And so, I decided, to better be able to answer your question, which was also my own, I would learn common lisp to where I didn't feel like a noob, and could actually wield a programming language: hello world tutorials were not enough experience to evaluate the langage. I needed to choose one to dive in deeply. then the benefits or shortcomings of the other languages would make more sense, if I at least knew one of them well.
The irrational part is that I kind of used the coincidence of having read that book on the cart and then seeing lisp at rossetta code, as a "sign" that that lisp should be the one. If aliens are showing me signs as to which language to delve into deeply, I should listen But sometimes it takes somethign irrational like that to make me commit enough to stick it out. It's a marriage.
Common Lisp is not on your list of wives, but I for one, rejoiced at enorbet's comment:
Lisp is still wrapping its head around me: they call it "secret alien technology". So far, it seems to me that it can speak all the other languages at rosetta code -- it's been around so long, that someone who knows both languages, created functions in the familiar lisp syntax, that wields the unfamiliar language's syntax. I could learn to make widgits with tk, or I can use ltk, lisp's bindings that let me create tk widgits without learning tk's syntax. Imho, that makes it perfectly suitable to glue all these disparate technologies together.
I hope Lisp is the ancient language of the future.
Thank you for your time and great advice.
I looked at Lisp syntax and it is not OK for me. I think you forgot job positions. The job positions for C\C++ is better or Lisp! I want to learn a language that many projects using it and have a good position.
Thank you for your time and great advice.
I looked at Lisp syntax and it is not OK for me. I think you forgot job positions. The job positions for C\C++ is better or Lisp! I want to learn a language that many projects using it and have a good position.
You realize this also depends on where you are - like in where you live; unless you are willing to move?
Personally, I feel like there is always going to be demand for (and currently is demand for) C; java; .net and several others. So, find the one YOU like and get better at it. Instead of thinking about which programming language is popular...
You realize this also depends on where you are - like in where you live; unless you are willing to move?
Personally, I feel like there is always going to be demand for (and currently is demand for) C; java; .net and several others. So, find the one YOU like and get better at it. Instead of thinking about which programming language is popular...
Thank you.
In my opinion, C\C++ and Scala syntax looks good and as I said, I read something like Rust-Lang will die C\C++ and...
I like C, but the future for this language is not clear!
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Quote:
Originally Posted by n00b_noob
Thanks.
Can you tell me the result of his words?
Why don't you actually watch the video if it interests you so much?
Why don't you actually learn to do some actual research of your own, instead of being a help vampire?
...or just pay someone for their time and effort if you just can't be bothered?
The job positions for C\C++ is better or Lisp! I want to learn a language that many projects using it and have a good position.
It is still nonsense.
You can choose whatever language you want regardless of its popularity and position and you can use it in your whole life. It depends only on you.
From the other hand if you really want to be a professional developer you need to learn more [several different] languages.
Your later contributions to this thread are hinting to me that you’re not taking this discussion seriously (no, obviously no-one here is in touch with Linus).
You still want want a serious answer?
The serious answer is that you are expected to be good enough to pick up new languages as needed.
The way it works is that you start with, say, an OOP language, then you’ll be able to pick up any other OOP language afterwards.
As of ten years ago, universities would start you off with Java and Scheme, which would give you a background in both object-oriented and functional languages. That essentially covers everything.
And if you have a good idea of how computers and operating systems work, well, that helps even more.
Do you know who "Uncle" Bob Martin is? Maybe not if you think he can be paraphrased or summarized. It's a deep dive symposium and well worth any coders time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.