Hacker News new | ask | show | jobs
by sdevonoes 1547 days ago
Looks very painful, or at least it looks to me like doing programming in the 60s: we need to connect to the "mainframe" in order to be able to do our jobs.

So much vendor lock-in, so much dependance on internet connectivity, so many buzzwords around... so much magic (as the post's title describes). I really dislike having to deal with a lot of third-party magic when doing programming.
2 comments
wooque 1547 days ago
It is very painful.

Serverless Stack framework is not bread and butter as they describe it, it often locks up and CPU going to 100% on my machine, misses debug breakpoints, breaks with weird error messages pointing to compiled JS code that are hard to trace back to TypeScript, etc, etc. And you are right, you are locked in, there is too much magic, you are dependent on internet connection.

Maybe I just inherited shitty serverless project, but it is painful.

link
jayair 1547 days ago
Sorry to hear that you've had some bad experiences with SST. Recently we shipped some updates to fix the CPU issues with apps that have a large number of functions. The missing breakpoints I think is related as well.

That said though, we often work with teams in our Slack to get their setup working well. If you haven't, I'd recommend popping in and posting about it. Or just send me an email: jay@serverless-stack.com and we'll figure it out.

link
gigaflop 1547 days ago
It's also an AWS-only tool, as far as I can see. As someone who's exploring more of Azure (due to choices of the company, where I'm mostly ambivalent on cloud choice), I have 0 use for something like this.

I'm currently working on using Terraform in Az DevOps Pipelines and Releases, to stand up an instance of something that has multiple 'cloud object' requirements. The Release process is frustrating, because the default assumptions made by Azure's tooling want me to format my variables a certain way. But, it would probably be like 'magic' if I just caved in and reworked our variables to be more Azure-friendly naming style.

Why should the tool have influence over the product? I know it's taking me more time to get it to work 'my' way, but I feel like I should force the system to adapt to my needs, instead of the other way around.

link