There are different uses for different tools, I understand that.
I'm just wondering if anyone got framework/buzzword fatigue and switched back to a less bleeding edge, and more boring tech stacks?
I'm trying to see if anyone has consciously done this and how they feel about that. This might be a fleeting thought for me given the release of Java 20.
Java/Spring is being used for the backend for a client at work. But it also uses Azure DevOps and Kubernetes and Docker and Terraform and React and all those other fun things, so it's not so 'boring' in other ways.
> Furthermore, after looking at the WT documentation it seems horrific to construct frontends in...
The front-end is jQuery and plain CSS or Bootstrap; and if JavaScript is not available then it falls back to complete server-side rendering, else it is hybrid server-client rendering.
> maybe not so bad for APIs though.
According to the creators of Wt, though you can write APIs, it is not yet architecturally optimised for REST API development.
Doesn't seem like it based on their comments, just a new account. They were replying to others with relevant comments.
Of course that doesn't guarantee anything nowadays, but that's about all we have nowadays. Just about anything can be faked online now, from pictures to video to audio to text.
While Scala isn't as boring as Java, I commonly work with PlayFramework which is our version for boring technology, it gets the job done, it is well-documented, not as nice as other libraries but it is rare to find an unsupported use case.
I have had to deal with html templates in Scala and Rust, to my surprise, I'm enjoying going back to these boring web apps.
Well Play was and is aimed mainly at people who are used to Java and OOP. You can take a look at http4s and ZIO Http for something more modern based on FP.
“Boring” technology isn’t boring if you’re using it for the first time.
Still get a kick out of playing old video games and seeing “19xx” or something on the screen and it’s the first time I’ve ever played it
I struggle to understand what do you mean with "boring" technology. For me, what could be boring is a project or a "vertical". I have of course preferences around which language or framework to use, but I wouldn't label a techology boring: rather unproductive or complicated or not suited for the task.
I've been building products on React, Node, and Postgres since 2016 - nice to not be the only one on the internet with a problem (I worked for a startup using elixir, this was a common occurrence back then)
I have settled on Go for all and any backend work and sveltekit for the UI. Over the last six or seven years have worked with many different technologies.
It is super easy to work with svelte (mostly typescript + html/css and a few svelte specific things) and Go has a nice balance between productivity and high performance. Both are super easy to deploy.
Not sure if that’s “boring” enough but I’ve done everything from pre official support angular 2 SSR to react, microservices and micro front ends. I just prefer simplicity and contracts.
Do Clojure, so I use Java (directly anyhow) sometimes...through the bars of a cell where I keep it in my attic. Despite that, I'm not big on chasing frameworks or trends, and I think plenty of the community is that way (Rich Hickey himself has described the language as somewhat being for old programmers who are tired of it all). I'm not sure I could go back full-time to a curly brace language, though.
I'm just wondering if anyone got framework/buzzword fatigue and switched back to a less bleeding edge, and more boring tech stacks?
I'm trying to see if anyone has consciously done this and how they feel about that. This might be a fleeting thought for me given the release of Java 20.