Stackoverflow-Survey-Analysis VS Graal

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.

For quite some time now, JavaScript (JS) has been the language that brings the Web to life. So it's no surprise that since 2014, of all programming and scripting languages, JavaScript has consistently been the most popular technology among software developers, according to Stack Overflow surveys.

Contrary to what vocal Kotlin advocates might believe, Kotlin only matters on Android, and that is thanks to Google pushing it no matter what.

https://spectrum.ieee.org/the-top-programming-languages-2023

https://snyk.io/reports/jvm-ecosystem-report-2021/

And even so, they had to conceed Android and Kotlin on their own, without the Java ecosystem aren't really much useful, thus ART is now updatable via Play Store, and currently supports OpenJDK 17 LTS on Android 12 and later devices.

As for your question regarding numbers, mostly Java 74.6%, C++ 13.7%, on the OpenJDK, other JVM implementations differ, e.g. GraalVM is mostly Java 91.8%, C 3.6%.

https://github.com/openjdk/jdk

https://github.com/oracle/graal

Two examples from many others, https://en.wikipedia.org/wiki/List_of_Java_virtual_machines

Pkl was built using the GraalVM Truffle framework. So it supports runtime compilation using Futurama Projections. We have been working with Apple on this for a while, and I am quite happy that we can finally read the sources!

https://github.com/oracle/graal/tree/master/truffle

Disclaimer: graalvm dev here.

That's pretty interesting. It's not as aggressive as Bee sounds, but the Espresso JVM is somewhat similar in concept. It's a full blown JVM written in Java with all the mod cons, which can either be compiled ahead of time down to memory-efficient native code giving something similar to a JVM written in C++, or run itself as a Java application on top of another JVM. In the latter mode it obviously doesn't achieve top-tier performance, but the advantage is you can easily hack on it using all the regular Java tools, including hotswapping using the debugger.

When run like this, the bytecode interpreter, runtime system and JIT compiler are all regular Java that can be debugged, edited, explored in the IDE, recompiled quickly and so on. Only the GC is provided by the host system. If you compile it to native code, the GC is also written in Java (with some special conventions to allow for convenient direct memory access).

What's most interesting is that Espresso isn't a direct translation of what a classical C++ VM would look like. It's built on the Truffle framework, so the code is extremely high level compared to traditional VM code. Details like how exactly transitions between the interpreter/compiled code happen, how you communicate pointer maps to the GC and so on are all abstracted away. You don't even have to invoke the JIT compiler manually, that's done for you too. The only code Espresso really needs is that which defines the semantics of the Java bytecode language and associated tools like the JDWP debugger protocol.

https://github.com/oracle/graal/tree/master/espresso

This design makes it easy to experiment with new VM features that would be too difficult or expensive to implement otherwise. For example it implements full hotswap capability that lets you arbitrarily redefine code and data on the fly. Espresso can also fully self-host recursively without limit, meaning you can achieve something like what's described in the paper by running Espresso on top of Espresso.

I'm also using GraalVM if that's of any help.

Quarkus is one of Java frameworks for microservices development and cloud-native deployment. It is developed as container-first stack and working with GraalVM and HotSpot virtual machines (VM).

Apologies, I didn't mean to imply DCEVM went poof, just that I was sad it didn't make it into OpenJDK so one need not do JDK silliness between the production one and the "debugging one" since my experience is that's an absolutely stellar way to produce Heisenbugs

And I'll be straight: Graal scares me 'cause Oracle but I just checked and it looks to the casual observer that it's straight-up GPLv2 now so maybe my fears need revisiting: https://github.com/oracle/graal/blob/vm-23.1.0/LICENSE

> to be compiled to a single executable is a strength that Java does not have

I think this is very outdated claim: https://www.graalvm.org/

https://github.com/oracle/graal/issues/7182