It is simply that I’m unaware of a streams implementation for postgresql. Although another comment is mentioning them, so I’ll read that in some more detail shortly.
I’ve always felt that streams should be implementable via stored procedures, and that it would be a fun project. I’ve just never quite had the driving force to do it.
Why would a future Liberal goverment restart it if the past one wanted to shut it down but didn't have the guts (or at least that's my understanding of the article)?
> If your workload is truly intermittent and stateless, and you want zero operational effort, serverless can work.
And it works pretty well. A lot of internal and external JSON APIs are a good fit.
I've found the article ok, but it would have been a much nicer read without all the emotional stuff and just kept - serverless is pushed as panacea but actually isn't a good fit because...
I believe your options are glucose–fructose syrup or aspartame - I'd lean towards aspartame as well. If sugar was an option I'd gladly cut the daily intake and go with that.
Could you share the stuff that you're working with which make feel that the issues you mentioned are completely ruining the language? It sounds quite intriguing. I have mostly used in the last decade for basic JSON APIs and desktop application where I haven't really encountered those.