Stackoverflow-Survey-Analysis VS Graal

Stack Overflow Developer Survey 2024

Neither StackOverflow's tags quantity nor their yearly developer surveys can provide meaningful insights about market share, and they can't provide meaningful advice about what tech will be good for your specific situation, for the same reason that SO doesn't like questions that are likely to attend "opinionated answers".

No the author didn't read the methodology of the Stack Overflow Survey nor did they notice they can get the historical CSV of the survey going back to 2011 [1] which literally tells the number of respondents per language (as-in how popular it is; no secondary population from TIBOE needed). Nor do they seem to understand (unlike you who does understand) that Loved and Dreaded have very specific meanings and Loved does

They did shoddy work and I'm calling them out on it.

The question of "If Java and Ruby appeared today, without piles of old rails apps and old enterprise Java applications to maintain, would they still be dreaded or would they be more likely to show up on the loved list?" is answer.

It's a no. For 2020, Ruby was 4.5% and Java was 8.8% of developer's "Wanted" languages while Go (17.9%), Rust (14.6%), TypeScript (17.0%), Python (30.0% !!). Sure a lot of people would like Ruby and Java (there already are actually a lot of them) but when you're not at the top of the Wanted it's going to be very hard to get to the top of Loved.

[1]: https://insights.stackoverflow.com/survey/

- Dataset: https://insights.stackoverflow.com/survey

For seven years now, the Rust programming language has been voted the most loved programming language, according to a survey by Stack Overflow. Its popularity stems from its focus on safety, performance, built-in memory management, and concurrency features. All of these reasons make it an excellent choice for building web applications.

I might be able to show you the direction.

Since you are looking in those 3 factors, please study the following findings of the Surveys.

https://insights.stackoverflow.com/survey/

https://www.hackerrank.com/blog/category/industry-insights/

https://www.jetbrains.com/lp/devecosystem-2021/

https://www.jetbrains.com/lp/devecosystem-2022/

https://redmonk.com/sogrady/2022/03/28/language-rankings-1-2...

https://redmonk.com/sogrady/2022/10/20/language-rankings-6-2...

You could tinker the above links to get your choice of month/year.

Now, don't be tempted to lock down your decision because there is rarely any good resource to learn( or get help when you are stuck) in that choice you made. This is because learning is always best done via colleagues and bosses.

Simply pause yourself on that and resume with learning Python + FastAPI + JavaScript (or Go + JavaScript). Garnish with Tailwind CSS and you are ready!

This is the easiest way to translate your learning into your choice of stack. In the long run, you will learn Typescript + React for sure. It is as if the right of passage into the market, haha!

A couple more links that you can search on hn.algolia.com

https://news.ycombinator.com/item?id=34530052 https://news.ycombinator.com/item?id=34551770

At a certain point, you get a feel for it, but I'd use the Stack Overflow Developer Survey as a good starting point (and you can compare year over year to see what the trends are) https://insights.stackoverflow.com/survey

I don't know if there's a rigorous study on this subject but Stack Overflow Developer Survey 2022's data lists 18 083 male vs. 756 female developers without a degree (96% vs. 4%) on a quick glance. This result isn't published directly in their summary, you have to download the dataset and filter it yourself.

Stack Overflow developer sruvey is much better than TIOBE.

Here's a link to the raw CSV data on Stack Overflow.

The Secret Weapon: GraalVM

In this application, we will create products and retrieve them by their ID and use Amazon DynamoDB as a NoSQL database for the persistence layer. We use Amazon API Gateway which makes it easy for developers to create, publish, maintain, monitor and secure APIs and AWS Lambda to execute code without the need to provision or manage servers. We also use AWS SAM, which provides a short syntax optimised for defining infrastructure as code (hereafter IaC) for serverless applications. For this article, I assume a basic understanding of the mentioned AWS services, serverless architectures in AWS, Micronaut framework and GraalVM including its Native Image capabilities.

To test a real-world scenario, I compiled and ran Drools - a Business Rule Management System and rules engine. In a standard JVM setup, Drools compiles DRL into .class files at runtime, loads them and uses them for validation. Because native images cannot load classes dynamically (though this may change soon), I moved DRL rules into a separate module and precompiled them with kie-maven-plugin. I also adjusted Drools to handle resource reading inlined into WASM. As usual, I added classes and resources to reflect-config.json, resource-config.json and native-image.properties.

• GraalVM Official Website: https://www.graalvm.org • Native Image Documentation: https://www.graalvm.org/reference-manual/native-image/ • Spring Native Project: https://spring.io/projects/spring-native • Quarkus Framework: https://quarkus.io • Micronaut Framework: https://micronaut.io • Oracle Substrate VM Paper: https://www.vldb.org/pvldb/vol10/p1138-vincent.pdf • “Fast Startup for Java” by Cristiano Betta (Conference Paper) • OpenTelemetry Java Native Image Support: https://opentelemetry.io/docs/java/nativeimage/

GraalVM compiles Java applications to native executables, reducing startup time and memory usage. Here’s how to compile your Spring AI app.

Quarkus is a Kubernetes-native Java stack tailored for GraalVM and OpenJDK HotSpot. Quarkus offers incredibly fast boot times, low RSS memory consumption, and a fantastic developer experience with features like live coding.