-
- In this world, since ancient times, users have driven capital, capital has driven change, and change has created an ecology. **
Back then, DOS programmers madly despised the behavior of dragging and pulling a mouse to operate a computer, as if visual operations were to alienate the relationship between the program ape and the machine. All programmers were proud to know how many interrupt instructions they thought were the future. The password, but later they all learned that the visual Window system was popular around the world, and no one wanted to bother with it, so they chose it. Then the program ape had to change careers and learn programming under the Window. Change to recite the message type under Window.
Is the original DOS technology stack bad? I think TC2.0 is also very easy to use, but it's not useful. A technology stack, or ecosystem, must have a handle to carry it. Unfortunately, the visual operating system ruined the life of the first-generation DOS technology stack, or the underlying technology and user choices ruined the life of the first-generation DOS technology stack. Under excellent circumstances, no one used it unknowingly. This is very similar to Keda.
The emergence of the Window operating system has attracted the PC era, stand-alone games, home audio and video, engineering computing, etc. The needs of the PC era have created the form of stand-alone programs in the PC era. With this, VB, VC, VF, and Delphi have shown their talents. Strive for stand-alone performance optimization, development simplicity, and a program to discuss heroes. The key is that users care about and like these. In that era, if Warcraft takes 1 minute to launch, Then there would definitely be nothing going on in World of Warcraft. Those technologies were the ecology at that time, but they are no longer used now. It is not that these technologies are outdated, but that the user model that carries these application layers is outdated. In other words, what is outdated is the PC era, not these technologies. In fact, there are some underlying technologies. The research results of that year are still used by big shots, but ordinary application layer developers don't use them.
Html was born in 1990, and Java was born in 1994. Why these languages were lukewarm and used by few people in the first 10 years is because they were born for the next generation. Although they are forward-looking, they determine their status. The era of the bottom has not yet come. At that time, many people who used it also used it with the attitude of early adopters, and complained happily when they used it. Compared with C/C ++, the performance was too poor and it was nothing. Now, the eyes of the masses may not be sharp.
-
- Time flies to 2007, and smartphones are born... **
The common people bid farewell to mobile phones and suddenly found that this thing can be, which I like. It is more advanced, convenient and classy than computers. Therefore, the common people who do not understand technology once again decided on the arrival of a new era of IT technology, that is, the Internet era!
Two major characteristics of the Internet era:
Diversified front-end equipment and fragmented versions;
Interactive services are complex and server-side services are carried out in a huge amount;
The new demands triggered by these two characteristics have directly confused the technology stacks (VB, VC, Delphi) that were once dominant on PC.
Facing the client: Those static compilers that seem to be accurate to the instruction level need to compile several versions, or even a dozen versions, at once. Moreover, deployments often report errors due to lack of weight in the system environment, and then the user scolded them. What a joke.
Facing the server: Previously, there was no corresponding research on interconnection, communication, carrying huge amounts of data processing, and clustering association because it was not the focus.
Then everyone understood that you are excellent, but we don't need you anymore. It's time for the heroes of that era to end.
On the other hand, Java and Html, these two little brothers, had a cross-platform design from the beginning and were themselves the design of communication carriers. In the Internet era, many advantages immediately emerged. As a result, the salted fish turned around and bronze became the king. At that time, no one praised Java to the sky, let alone blindly worshiped Html/JS, but the big shots all began to study how to better implement them as easy-to-use solutions in the Internet era. So a new ecology began to take shape...
Microsoft seems to have some hindsight this time. Although Bill Gates finally saw the future and started to poach people crazily in the late 1990s, it was not until 2002 that the first version of. NET 1.0 was released. The key point is that it is oriented to this era. The underlying use of Java has been realized.
If competing products are roughly the same, it is not a dimensional-reduction attack, it is not a dimensional-reduction attack, then we will fight for the details!
PK1: For PC,. Net beats Java. (But it doesn't matter, because the PC era is over)
PK2: Cross-platform,. Net failed Java. (Everyone thinks that it is a sin to cross-platform. In fact, it is not. At that time, the Window Platform's poor performance on web servers was a sin. Who would use charging + instability?)
PK3: For mobile,. Net completely defeats Java (specifically, the era of 2002 - 2016)
PK4: With the above three points, is it important to move forward...
As a result, the general environment naturally tends to be Java, and many people begin to learn Java, and the era of kings belonging to Java has finally arrived.
So in China, a very magical logic began to be produced. Java is strong because there are many people learning Java, Java has a good ecology, and Java can copy many solutions...
-
- However, in the technical field, the right to speak always lies in the underlying technology. In terms of the pure application layer ecology, no matter how optimized and enriched it, it is a quantitative change rather than a qualitative change. **
The underlying technology creates new user forms and triggers the underlying revolution. At the same time, it will ruthlessly destroy the life of application-level technology, whether you are willing or unwilling; unfortunately, Java and C#, and later Python, GO are just application-level languages. In fact, they have no say in the face of the dimensions reduction attacks of the times.
In 2008, the concept of cloud began to emerge, and then artificial intelligence and the outbreak of the epidemic in 2020 triggered a craze for virtualization. Currently, the concept of the metaverse is in full swing, which shows that this restless world is about to change again.
The future will definitely be a highly artificial intelligent cloud world!
-
- Why do you say that? **
First, don't people like smart machines? The answer will definitely be a warm welcome.
Second, don't people like more realistic and illusory experiences? The answer must be to like it very much, or even be addicted to it.
Third, relying on the current framework, can each company realize the reality of artificial intelligence applications on its own? The answer is definitely unrealistic. In the future, we can only call the cloud interface of intelligent cloud providers.
Fourth, don't you aspire to the future Internet of Things world supported by artificial intelligence? The answer is that I wouldn't believe it even if I was beaten to death. I really yearn for it.
-
- As a result, you will find that when writing programs in the future, you will gradually start to call cloud interfaces to implement functions, and then slowly and even start to call cloud interfaces, cloud functions, and cloud systems... **
You may ask, why are big shots so willing to develop the cloud? Brothers, the cloud charges by the number of times and by the duration of time. Once your number of users increases, it is so full, and there is also a competitive threshold. Who is not willing to do it? Why is capital not willing to spend money?
Therefore, we are now seeing the crazy fighting between domestic and foreign bigwigs in the cloud field and artificial intelligence field, and now we feel that we don't have much to do. That's just because their status is still unstable and their foundation is not yet solid, so they don't dare to show their fangs too early.
-
- Back to the theme, what kind of language do we need when the real future world comes? **
The answer must be a language that suits the intelligent cloud era. Then look back, in the face of the future era, are all the cross-platform advantages of Java, C#, and Html5 still important? I don't think so, because these advantages will be reduced to the same performance advantages as the former C/C ++ static compilation, which is great but not important.
In 2010, Microsoft started developing the Azure cloud platform. In 2016, Microsoft started developing. NET Core across all platforms. Then it seemed that it was willing to sacrifice copyright and give up only blessing on Windows. Then it suddenly seemed to become open source, inclusive, and free., and it also spared no effort to optimize performance. It continues to update version after version, and is currently updated to. NET 6, and then it immediately launched. NET 7. Why?
-
- Some people say that this is Microsoft's attempt to compete with Java and occupy the development market. **
So, yes and no, it seems right, but in fact, in this environment, what are the benefits of fighting Java regardless of cost?
Moreover, have you found that. NET Core includes new. NET 5,. NET 6... In the version, Microsoft's proportion of cloud development support is increasing rapidly. High-profile publicity is being made. At the development tool level, Microsoft is even determined to lose money and build a good job. Even on the mobile client side,. Net has begun to almost full platform support, even including closed systems such as IOS, Microsoft does not let go. On the server side, the performance of. NET Core continues to be optimized and the framework is being built for all to see and is constantly improved...
显然，近几年画风突变的.Net 战略是有深层次原因的， 这是微软在为未来的云时代、元宇宙时代做铺垫，现在与 Java PK 胜败与否，微软甚至都不是十分在意，关键是打好基础，立足未来。
-
- The cloud era of artificial intelligence has arrived. Now the so-called server will become an interface calling client in the cloud era. Now the web-based 2D client will likely be replaced by a new 3D browser based on virtual reality! **
所以前后端又一次面临新的革命，在那个时代，众云云集，虚幻与现实交错， 现在的 Html5 和 Java 沉淀的厚厚的生态还重要吗？ 只能再套用一次台词：对，很优秀，但是不重要。
As a result, C#and Java are once again at the same starting line, and this time, even C#has some advantage. Html may be the worst, because the 2D browser ecosystem it relies on may be marginalized in the 3D world. Without soil, Html may be completely revolutionized.
In this competition, the details have undergone fundamental changes:
Detail 1: Cross-platform C#and Java
Detail 2: Concise and efficient C#beats Java
Detail 3: Cloud Ecosystem C#beats Java (. NET Core built-in cloud support)
Detail 4: 3D layer ecosystem C#beats Java (In the downturn of C#, it relied on the development of Unity 3D to support an article)
In contrast, the advantages are so obvious. In the future, with continuous strategic support and re-practice by foreign tycoons, a new meta-universe ecology will quietly rise. When this ecology is transmitted to our side, you may be surprised to find that, er, the king this time is actually C#.
Of course, everything is developing, and every technology will innovate itself. It is the same saying. As for who is the so-called king in the end, it actually depends on who carries the underlying technology, is closer to users, and leads the future!
-
- The quality of language is related to language. **
-
- Language success or failure has nothing to do with language! **
This article comes from reprint
Original author: Evil binary
Original title: Bold speculation: The future king, or belonging to C#
Original link: https://www.example.com