Stackoverflow-Survey-Analysis VS FrameworkBenchmarks

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.

Neat. Thanks for sharing!

Interestingly, may-minihttp is faring very well in the TechEmpower benchmark [1], for whatever those benchmarks are worth. The code is also surprisingly straightforward [2].

[1] https://www.techempower.com/benchmarks/

[2] https://github.com/TechEmpower/FrameworkBenchmarks/blob/mast...

ntex was formed after a schism in actix-web and Rust safety/unsafety, with ntex allowing more unsafe code for better performance.

ntex is at the top of the TechEmpower benchmarks, although those benchmarks are not apples-to-apples since each uses its own tricks: https://www.techempower.com/benchmarks/#hw=ph&test=fortune&s...

Ruby is slow. Very slow. How much you may ask? https://www.techempower.com/benchmarks/#hw=ph&test=fortune&s... fastest Ruby entry is at 272th place. Sure, top entries tend to have questionable benchmark-golfing implementations, but it gives you a good primer on the overhead imposed by Ruby.

It is also not early 00s anymore, when you pick an interpreted language, you are not getting "better productivity and tooling". In fact, most interpreted languages lag behind other major languages significantly in the form of JS/TS, Python and Ruby suffering from different woes when it comes to package management and publishing. I would say only TS/JS manages to stand apart with being tolerable, and Python sometimes too by a virtue of its popularity and the amount of information out there whenever you need to troubleshoot.

If you liked Go but felt it being a too verbose to your liking, give .NET a try. I am advocating for it here on HN mostly for fun but it is, in fact, highly underappreciated, considered unsexy and boring while it's anything but after a complete change of trajectory in the last 3-5 years. It is actually the* stack people secretly want but simply don't know about because it is bundled together with Java in the public perception.

*productive CLI tooling, high performance, works well in a really wide range of workloads from low to high level, by far the best ORM across all languages and back-end framework that is easier to work with than Node.JS while consuming 0.1x resources

Although that seems to have improved in recent years.

https://www.techempower.com/benchmarks/#hw=ph&test=json§...

RoR and whatever C++ based web backend there is count as a valid comparison in my book. But comparing the languages itself is maybe a bit off.

On a side note, you can actually compare their performance here if you’re really curious. But take it with a grain of salt since these are synthetic benchmarks.

https://www.techempower.com/benchmarks

Most benchmarks you'll find essentially have someone's thumb on the scale (intentionally or unintentionally). Most people won't know the different languages well enough to create comparable implementations and if you let different people create the implementations, cheating happens. The TechEmpower benchmarks aren't bad, but many implementations put their thumb on the scale (https://www.techempower.com/benchmarks). For example, a lot of the Go implementations avoid the GC by pre-allocating/reusing structs or allocate arrays knowing how big they need to be in advance (despite that being against the rules). At some point, it becomes "how many features have you turned off." Some Go http routers (like fasthttp and those built off it like Atreugo and Fiber) aren't actually correct and a lot of people in the Go community discourage their use, but they certainly top the benchmarks. Gin and Echo are usually the ones that are well-respected in the Go community.

There is certainly a lot of speculation in Techempower benchmarks and top entries can utilize questionable techniques like simply writing a byte array literal to output stream instead of constructing a response, or (in the past) DB query coalescing to work around inherent limitations of the DB in case of Fortunes or DB quries.

And yet, the fastest Ruby entry is at 274th place while Rails is at 427th.

https://www.techempower.com/benchmarks/#hw=ph&test=fortune&s...

oh what machine? with how many workers? doing what?

search for "node" on this page: https://www.techempower.com/benchmarks/#section=data-r21

JustJS would like a word https://www.techempower.com/benchmarks/#section=data-r20&tes...

In terms of RPS, this web service is more-or-less the fortunes benchmark in the techempower benchmarks, once the data hits the cache: https://www.techempower.com/benchmarks/#section=data-r21

Or, at least, they would be after applying optimizations to them.

In short, both of these would serve more rps than you will likely ever need on even the lowest end virtual machines. The underlying API provider will probably cut you off from querying them before you run out of RPS.