11/8 postscript: Since the original article disappeared for each account, I changed the link to that of the web archive.
The comment section of the article Programming languages needed in the future is very busy. In the comment section, the article author
If you want to dig in all the lines, you can write the same theme yourself as a trackback and POST it.
I was commenting, so I will post an article with all the lines. By the way, I haven't touched all languages, and I'm a back-end engineer, so my knowledge may be insufficient. I would like you to skip Masakari further for that part.
~~ It's not the end of every line, but ~~ Before we mention the content of the article, let's think about the premise of this article.
I'm only talking about Java main development, so that's probably the premise. Therefore, it is better to write ** "I will describe the programming languages required other than Java for system development in Java." If you do not write it, it will be taken as a story of all programmers and all development projects. ** **
Basically, ** Every article has a preface, in which assumptions, title supplements, grounds, etc. are included. ** For example, in 5 languages that all developers should learn, which is a little closer to the original article, "I translated it because there was such an article", The preface of the translation says, "For this reason, I chose these five languages." ** I think the preface becomes more important as the title becomes more exaggerated and humorous. ** ** Others often describe who should read this article. For beginners or front-end engineers. However, this is often omitted. I can't write "Dedicated to all engineers ...". By the way, if the reader is omitted, almost all of them will be interpreted as such.
** No need for those prefaces! Even in such a case, it is better for the reader to write something in one or two lines, which will be a cushion and easier to read. ** **
First of all, it's a trivial matter, but I feel uncomfortable with the term "program language". Of course, there is a way to call it, but if you google for "programming language", "programming language" will be lined up ... But the name is people's preference, so there is no problem. ** The real problem is that the headings have changed the term "master language". Why did you change it? ** ** I haven't heard how to call the master language, but I think it's called. Even if I googled with "" master language "" with double quotes, only the original article came out.
Postscript: I forgot the important thing. ** I don't need "future" in the title because the language that mentions the content is old even though I say "future". ** **
It's nice to list the languages, but I want you to write the rationale. The reader will be worried about it and will read while eating the memory in the brain. A novel may be a good technique, but a technical article should stop.
Java ** Why is JavaScript included? ** ** This is too strong to get the content of the honest article in my head. ** Applet is a deprecated technology ** or ** not related to OS and Java ** or ** Java has a high backend share but is not unified ** or ** There are many things I would like to say that Servlet is one of the realizations of typical HTML, but it is not the only one **, but all of them have such a strong impact that they seem to be trivial problems. If you don't know what's wrong, it's been talked about about 20 years ago, so please google for "Java JavaScript Differences".
By the way, in the comment section, the reporter creator
JAVA and JS are not confused. This does not mean that you can use JAVA by ignoring JS.
However, you can use Java even if you ignore ** JS. The reverse is also true. ** I know that I need to touch Java and JS because I often use them in combination with Web systems, but I haven't talked about Web systems.
Ruby I've written Java subroutines and alternatives to C ++, but I think it's better to sit down with Mr. Matz. ** ** Ruby is not a language that was born just for that purpose. ** Ruby is used in a wider variety of places. ** So I think it's a good idea to write on that premise. At the very least, put a preface that says, "In the world of Java-based development."
Also, I think you should stop using the tag Ruby On Rails even though you have never mentioned Ruby on Rails. Or rather, if you disregard Ruby, you don't even need Ruby tags.
If the written content is correct, why would a language used only as a Java subroutine become a "programming language that will be needed in the future"? In terms of Java, I feel that Java is fine.
C++
"There is no reason to learn C ++ alone," he says, but ** I think it's better to sit down with all the C ++ engineers. ** ** Below, I will omit it because it overlaps with all the contents described in Ruby.
** Basically, there is no relationship between upper and lower programming languages. ** There is no such thing as Java being greater or more advanced than Ruby. (If you are not using it in that sense, please correct it.) By the way, there is a concept of high level and low level. This is not a high degree or prestige, but whether it is close to a machine.
I'm talking about "alternatives", but I feel like I'm talking about whether or not alternatives work in a unified manner and language, not whether or not alternatives work in terms of system and language. If you put in, there is no such thing as great because the share rate is high, or that it should be unified. (Is it the upper management of some Japanese companies?) ** The programming language is originally to select the language that suits your purpose. ** **
PL/SQL ** Why did you line up with Java, Ruby, C ++? ** **
** Java (including JavaBeans) + PL / SQL + JavaScript development is not everything. ** ** There are various services such as web services, games, smartphone apps, and embedded systems in the world, but this form is only used as part of the web services. I think we should experience a little more other sites. Also ** "There is no reason to acquire or read about other languages" is not an outrage here. ** On Qiita, the site where you post your articles, Python is ranked 1st and 2nd in the tag ranking. Do you know Python? If you want to talk about the future, I think you should touch it a little without learning a new language in earnest. It is careless to just care about the share rate and cut it off without touching it.
I dared to enumerate the contents of Tsukkomi, considering that the development of Java main is the premise. However, even if the premise is not there, it will be summarized in ** Get to know other development sites **. Certainly Java is a language with a reasonably high industry share and versatility, and will be needed "in the future". However, looking at recent trends in Java, it is expected that it will decline later, so it is not recommended to stick to Java alone in the future.
I don't talk about the topic of "programming languages needed in the future" itself. In general, the learning order of 5 languages that all developers should learn and Ruby-> Go-> Scala will help engineers grow explosively. I think it's all about the best reason, and in the end, what he wants to aim for and what he made. I think it will be important.
11/7 pm Addendum: I made minor corrections to the parts of this article that are strange in Japanese and that should be added. (The added part is mainly the summary (of this article) and the handling part of Java) If you read it carefully, the technical story is only published in Java, but it seems that there is no content other than Java, so I dare to leave it as it is. Also, I will not plunge into the rice field.
Recommended Posts