Ask HN: Has anyone gone back to boring technology (ex: Java/Spring)?
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.
34 comments
[ 3.9 ms ] story [ 81.0 ms ] threadI can spool up a prototype in lightning speed.
[0] https://webtoolkit.eu
[1] https://www.foundationdb.org
[2] https://grpc.io
Furthermore, after looking at the WT documentation it seems horrific to construct frontends in... maybe not so bad for APIs though.
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.
- Next.js, Vercel, Node.js, Java (Spring Boot) - JavaScript, Tailwind, React, Angular - Microservices, REST APIs - Docker, Nginx, Postgresql - AWS - EC2, S3, RDS, Lambda, VPC, IAM - Docker, GitLab, Github
Everyone seems to be enjoying it so far! mbowen_ivajob4u
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.
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.
I appreciate using a single language between my backend and frontend.
Not mucking around with containers and K8s either. An optimized VM can go a long way.
Java (Latest LTS), Tomcat, EclipseLink, Apache ActiveMQ, CDI (via Apache TomEE), and JSF.
Working to try to do the same thing on Quarkus: ActiveMQ, CDI, JSF.
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.