The state of the ‘developer ecosystem’ in 2019 by software development company of note: JetBrains.
In the beginning of 2019, JetBrains -a software company whose tools are geared towards software developers and project managers- polled almost 7,000 developers to identify the State of the ‘developer ecosystem’. The resulting article can be found here, in all its glory, but we thought we’d break it down for ya and give you some of our thoughts…
-Java is the most popular language. “Most developers will use multiple languages, so …it’s kinda silly to get caught up in what’s the most [popular].
The VLOG goes into more detail, with more educated extrapolations and a sweet scenic boat or canoe ride. -Enjoy!
We make fun of Ruby a lot here: 1. because it’s fun and 2. … …okay, it’s just fun really, but a question did come up recently from an individual who was offered a job working with Ruby on Rails. They come from a PHP – Laravel background and while they don’t know how to use Ruby, per se, their potential employer also offered to pay them while they learn it. So the question was do they take the job knowing that the use of Ruby on Rails has diminished or should they look for something else?
Now Ruby aside, we’d like to answer this question in general terms if you ever find yourself in a situation like this and you’re on the fence… “If you don’t have other work and the job is high paying, why not? …A language or framework does not define you as a programmer… you [just] happen to be using those tools at that particular time”. Now, specifically regarding Ruby jobs: “…it’s not gonna disappear over night and in fact we’ll probably see Ruby development for the next five years, at least, so …you do that for one year, two years, 3 years; what have you…”
Another question we’ve been getting recently is if Java is dead? With Google making the switch to Kotlin for app development and Oracle charging for Java licensing, what will be happening to Java jobs? “Does that mean the whole Java-Android development is going to collapse overnight? Probably not: it won’t, it’ll probably take a couple of years.” That being said, “if you’re writing code for your android app using Java, you’ll be able to transition into Kotlin very, very quickly.”
Check out the VLOG for a more sensible and detailed answers to these questions, and remember, “you cannot lose learning any programming language.” -Enjoy!
The tech giant will still support Java but Kotlin is king for Android development.
A quick snippet to be sure, but Google has announced that when it comes to Android development, going forward it will use Kotlin. There will still be support for Java, “…but in terms of documentation, new libraries and so fourth…they said, ‘that’s it! Kotlin is our beast’.”
Without sounding like a broken record (probably a dated reference…), this does go back to what we were saying about a language that is easy to write in, generally gets more use/support and ends up winning out over more verbose/heavy languages. “Kotlin is an easier language to write in, it’s far more productive so…if you are looking for native Android development (and that I think is going to diminish over time…), …then I would lean towards Kotlin.”
The VLOG goes onto mention other casualties in the “simplicity wars” of languages and frameworks, like Apple’s ‘objective C’ being replaced by Swift. It’s worth a look just for the nostalgia factor alone. -Enjoy!
GitHub is a good indicator of how popular programming languages are.
GitHub is an American company that provides hosting for software development version control using Git and it is a subsidiary of Microsoft. The article we got this list from is here and it’s pretty much the usual suspects…
Check out the VLOG for our take on the list and a little bit of info on the entries. -Enjoy!
We’ve touched on this before in past VLOGS but maybe you haven’t seen that one or you want a more up-to-date take on this subject.
So, short answer: Java is really best for web application development, and Android client development. It never took off for desktop applications (we go into more detail in the VLOG).
If you don’t believe us, check out the job market. We would venture to guess that very little to zero jobs are going to have you building desktops apps with JAVA; “JAVA is not client-side, …it is server-side programming”.
The VLOG comes equipped with not only my lovable mug crooning to you about all the finer points about this, but I also offer solutions to in forms of other languages and options that will optimize your time and output for creating desktop apps. You should check it out, it’s less than 4 minutes!
First things first, a kick-ass opening for this vlog with a (literally, for those afraid of heights) breath-taking view of Montreal, and then back into the “studio” to check out my rig (drums), all to a slick tune in the background. Maybe we’ll call this segment, “Weeee, so fly.”
But let’s dive right into it… Should you use JAVA for back end web app development?
A very specific question deserves a very specific answer: “At the end of the day you have to always judge your technology stacks based on both technical implications of the choice and market implications.”
Technology implications: Do you have experience with the language you’re using? Are you comfortable as programmer? “It depends how nerdy you are, if you are very comfortable writing code, you’re very comfortable as a developer and you’ve done web apps before, yeah, JAVA, could be a good choice, but you gotta consider more than just the technical aspects of the language…”
In terms of market implications: “…are there jobs there? Is there a long road ahead for that particular technology stack?” Now, there are plenty of jobs in JAVA but they tend to be in or with larger businesses/ organizations. Even with smaller businesses or freelance work “JAVA would not be my first, second, or third choice…”.
Check out the video for a super detailed answer to this question and the more broad lesson that we’re trying to teach: What can you do Vs. what will the market pay you for. Also, did you find our RUBY diss(es)? Oh, yeah, there might be more than one! Enjoy!
Hard to learn, easy to write … but slow to code with
ALSO: It’s dog-slow at run time when writing desktop applications (never mind mobile apps).
So there you have it, from a guy that loves JAVA. It’s super verbose and heavily detailed in the writing (which also means less errors because you’re being explicit), and that writing code takes much more time, much more time means much more work and money/cost: “I wouldn’t do it.”
Check out the video for a more in-depth explanation PLUS what’s coming up with us with STUDIOWEB and other fundamental stuff we’re working on; super exciting stuff!
What Programming Languages do the Most Popular Websites Use? The results may surprise you!
So, I was on what the kids call wiki-wiki-pedia the other day and I thought I’d look up what programming languages the most popular websites use. I know, most people look for civil war factoids or if their favorite band from their teenage years is still around but I guess I’m just weird like that…
But seriously, check out the vid to put it all into context.
Also, blink and you might miss it: another quick dig at RUBY (mwahaha). Enjoy!
I’ve been asked many times (by web designers) about what programming language they should learn so that they can build database driven websites. My short answer is of course: PHP.
That said, I felt a little more detail was required: why do the competing technologies (ASP, ASP.NET, Ruby etc …) suck compared to PHP … in that regard?
From the article:
The articleâ€™s title (I admit,) will get some people little miffed at me. But, what can I say, the truth hurts!
Seriously, this statement is valid and is worth talking about because there are a lot of web designers out there who are considering the leap into building dynamic (database driven) web applications. And with so many choices (ASP, ASP.NET, Ruby etc â€¦) it can be very frustrating when trying to make that choice.
Of course, I believe (and know) that PHP is the choice language/technology for web designers. But why are the other technologies not a good choice for web designers?