Hacker News new | ask | show | jobs
by SantiagoElf 749 days ago
Never bothered to learn GraphQL - anything being pushed by big tech companies usually in 80% of the cases works for them, but its an overkill for smaller scale projects.

Stick to tried and true - monolith, asp.net, angular or blazor front-end, relational database.
1 comments
doctor_eval 749 days ago
> anything being pushed by big tech companies usually in 80% of the cases works for them, but its an overkill for smaller scale projects.

> asp.net, angular or blazor front-end

Since when are these not technologies pushed by big tech companies?

A company I worked with got badly burned by AngularJS.

link
SantiagoElf 749 days ago
I have used Angular since version 5.

I have never had any major issues or problems with it.

Think of it this way: GraphQL, Docker, and Kubernetes solve problems that very, very, very few GIANT tech companies have, but not every app will scale to millions of users.

link
doctor_eval 749 days ago
So you’re not familiar with AngularJS, the incompatible version 1? Angular 2 was effectively a complete rewrite - cleverly using the same name, thereby making it even more difficult for us - and the rewrite was done because Google Decided. Never again will I trust a Google front end library.

Because of my experience, I feel that your position is making a slim distinction based on your preferences. All the tech you use is built for big corporations, why pick on one set of tech just because you don’t have the specific problems it solves?

For me, for example, K8s properly solves a bunch of problems for my small SaaS business, not least of which is that I can upgrade my three piddly servers without taking my customers offline. My SSL certs get upgraded automatically without downtime. My CICD pipeline is simple. Logging is much easier. And so on.

I don’t understand the disdain for modern, managed K8s at all.

link