Hacker Newsnew | past | comments | ask | show | jobs | submit | dcu's commentslogin

tailwind is like Go, at first it seems like a bad idea but it works really well in practice


have you looked at zapsign.co? it's a good UX and it's not too expensive


I just tried it out and it was totally unintuitive how to add fields to a PDF. I tried to chat with support, but it wants you to use WhatsApp. (?!) Then I went to their youtube channel to see if I could see a walk through and every video is in Spanish. I guess they aren't interested in other geos like the US.


wouldn't that lead to analysis paralysis? it seems you're avoiding the decision which many people consider the worst decision


OOP is still here and microservices(especially since aws lambda) is just getting stronger and stronger every year


Yes and so is FP; but you don't have the same level of dogmatism for OOP that was prevalent in the mid 90s up to early 2000s.

As for microservices, the fact that it's great for cloud services nickel-and-diming you probably makes them likely to remain popular as long as the cloud computing propaganda continues to have effect.


Curious as to what constitutes MS on lambda? Because whether you have a dozen lambda functions where each function translates to one function vs one function with multiple features, the outcome is exactly the same.

API Gateway also muddies the water, it no longer makes sense for each lambda function to maintain stuff like services endpoint like in Kubernetes.

In fact, if you take away containers, you can completely achieve orchestration without Kubernetes. Simply use Step Functions to coordinate lambda functions or even better, avoid it altogether and have one lambda function coordinate the orchestration procedurally.

My bet is that as time goes on and companies realize the overhead from kubernetes and "cloud independence mandate", they will drive more business towards AWS, in particular Fargate is rapidly progressing, as well as ECS Anywhere allows you to run hybrid setups with complete ease and without the headache from Kubernetes.

Just realizing these things as I learn kubernetes and I keep thinking "wait I can just X from AWS and this bypasses the need for kubernetes altgoether" but seems like companies are already knee deep.


Clean Code is not bad in itself. The problem is that some people made it a bible, like the absolute truth (I guess it is written in that way), and that's where it fails.


yes, it's awesome. I also asked about this here: https://news.ycombinator.com/item?id=25267921

hopefully we'll see ML chips on Lambda soon too



let's hope generics doesn't become a over(ab)used feature, that'd make the code harder to read and my experience harder to maintain, especially because when you need to fix something it takes a lot of time getting in context so you can actually write the code for the fix.

I mostly write Go these days and haven't found many use cases where generics are needed but there are definitely cases where they would make the code nicer.


they mean safety, because using `interface{}` is like using dynamic languages (python, js, ruby, ...)


I buy the safety argument!


We use it for inference and it works fine. Now with EFS support it's even better.

We have used it successfully with both Tensorflow and Gorgonia


Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: