![]() I expect to bring down our company's core count significantly next year by adopting. But most importantly, it is fast and efficient. It works from front-end to back-end using Blazor WASM. It has multiple IDEs for all three major desktop OSs. It runs on both ARM64 and 圆4 architectures. NET 6? Because it is the most mature, most widely supported. It won't be that hard for a good developer to switch to. And these languages, as well as TS/JS have incredibly similar structure these days. For PHP developers, minimal APIs will look familiar to many. For C# veterans, focus is on minimizing the amount of boilerplate code one has to write. NET 6 has syntactic sugar for all comers. If you gained something from this article, take a minute of your time, hit the share button and share this piece with your network on social media, also give me a follow on all social media platform via my official blog via After that, the second language will be easier, and so forth. The first language will be hardest, because you're learning how to program for the first time. This are noticeable trends anyways, so dig in choose your area of relevance (e.g Frontend), research more about a technology to learn maybe Python or JavaScript, start learning and start building things. So in that respect, Rust may be more likely to be a major language in the future. Rust is strictly better for anything that you might want to start in C today. But except in narrow cases I don't see C as being a good language for new development. Like COBOL, there's a crap ton of code written for it, so it won't just vanish. But Rust seems to have a strictly better type system, which provides better compile-time code verification with equivalent or better performance.Ĭ is the low level language of the past. C++ has ruled this roost for two decades, and has received some recent updates that look great. On the high performance end, it's a hard call. I frankly don't see that changing any time soon.Ĭ# is probably going to persist in some enterprise companies, and as the language of Unit圓d and Xamarin. Scala has had its chance, but it appears to have failed in garnering market share. But it doesn't seem likely to make the jump to anywhere else. Swift is likely to stick around as the Apple platform language for the foreseeable future. Go might survive due to strong Google backing, though I have a hard time recommending it. ![]() Java is pretty well embedded in the enterprise space, but there are cracks around the edge of its dominance. Julia could come up from behind and displace Python in Machine learning. Python is nailing machine learning, but losing momentum on servers. TypeScript is catching up as the best way to use JavaScript. JavaScript is taking over almost everything. Talking about the language of the future, first we need ask how far in the future are we talking? When choosing a language to learn as a starter you should choose the most promising, when I use the word promising I mean acquiring a tech skill that is in high demand today and will be tomorrow, yes that's possible.Įvery developer wants to remain relevant in the Tech space and the best way to achieve that today is to identify the language of today and of the FUTURE. It's important to first know if you would love to be a frontend or backend developer, before choosing a programming language to learn. These different fields have different programming languages, libraries and frameworks people have learned to use for them, take for example frontend engineers often use Javascript and maybe ReactJS or Vue. In the Tech space you can decide to be a frontend dev, backend dev, machine learning expert, etc. Let's get the point straight, am not saying you shouldn't look out for a promising tech skill to acquire on the contrary am saying the tech space is hug and if you must be relevant in that huge tech space you need first choose which part to function in that huge tech space and then learn the most promising technology for that part. Often times when we make up our mind to become a software developer most of us think like this, but the simple truth is that things are more complicated than anyone thinking of the technology to start their software career with, just to be an instant hit in no time. I did my research and I felt why not Java. The advice I got was to learn Java, because during that period Java was reigning in my geographical location at least. To me then I would always want to be relevant and so I wanted to learn a language that would keep me in the relevant zone for decades to come. There was a time in my life when I made up my mind to be a programmer, I had a very big problem deciding which technology to learn.
0 Comments
Leave a Reply. |