The fact that it compiles is better the the cursor dude. "It Compiles" is a very low bar to working software.

My thoughts:

1) It's fragile. As xml is so dynamic small changes in the data can mean your transform doesn't work or worse that it does run but doesn't transform to the correct thing anymore

2) Hard to actually make xslt work. Like there are no decent debugging tools the best you'll get is a site you can plug in data and it will auto run the transformation. The devex here is really really poor which is why I'm baffled anyone would build this. As you say it's a transform language so you can't really step through it you just have to run it and see

3) Very hard to test properly. The amount of times something small would change in the data and then the transforms wouldn't work was awful. The "unit testing" we done was produce a bunch of XML and then run the transforms and check the XML. Like I couldn't actually test parts of the transform as I was going

4) Most importantly was maintenance. XSLT seemed to be a write only language as in hardly anyone as able to pickup someone elses transform and figure it out.

The people who liked it normally only used it for toy applications.

Never met a non autistic child who would spit or drool out calpol. I'd take the stuff myself as an adult it tastes brilliant.

> Total culture shock for me, as in Europe the default for children is rectal ingestion (which is probably a culture shock as well for Americans)

Huh are you talking about new born babies or something? I've been to a few different EU countries and you can buy liquid stuff for kids in the chemists. (Spain, france, germany, italy) source me as a child getting the stuff when I was sick abroad and the local doc sold my parents basically some off brand calpol.

So if you're going to off yourself you'd have to stock pile or roam around shops picking up.

There is a not insignificant number of suicides where people just say fck it I'll just kill myself but they don't want to go out to any real bother to do it i.e. they don't pre-plan it it's just spur of the moment. A bottle of kill yo self pills is pretty easy. Cupboard, swallow, drink down some water, die. But having to go out and buy a bunch over a few days or like drive around in your car just buying as many as you can. Like you'd have to look it up to check you're going to buy enough.

Back when that law came in when they didn't reduce the total amount you could buy at one time so if you went in and bought like 10 packs at the supermarket then the person at the till would be like ok this person's going to kill themselves so again that would require a bit of balls from the would be kill yo selfer.

I think you can buy a bottle of like 100 x 500mg for like $20 in the USA. That's like over 2 weeks swigging at the max amount. Like you don't need that many, 3-4 days is enough shouldn't be taking that much of the stuff.

Not throwing any shade just don't want to be suggesting stuff you've already tried.

Many people have lived very long over the years without resorting to that many pills.

Corporate companies are totally baffling Hasbro is no different.

Used AWS Aurora Serverless v2 (MySQL) and it worked pretty good actually never used the postgres version but it's now available.

I already said my points about the problems your follow-up comments have not addressed those.

Also there is no such thing in s3 as a cold GET there is a cold startup for a lambda. The latency from s3 on a get is orders of magnitude poorer that EBS or LSSD and should be used "infrequently".

I think what you mean is what we have implemented a side channel DBMS which holds a copy which you use for the transactionality. It's a terrible approach I would not do this at all you don't get any benefit from using s3 here.

This is not to say you can't use s3 to pull large blob storage off the DB and reference it in the DB I'm talking about the entire DB as s3.

Why are more and more devs trying to use s3 as a general purpose DB?

Working on a system right now where the architects have made this mistake it has insanely poor performance (High latency) and lack any proper ACID compliance. I've now been asked to "make it faster" and the answer is to switch back to an actual DBMS.

> Top tier SaaS services like S3 are able to deliver amazing simplicity, reliability, durability, scalability, and low price because their technologies are structurally oriented to deliver those things. Serving customers over large resource pools provides unparalleled efficiency and reliability at scale

In terms of simplicity using s3 is anything but simple. Sure the CRUD api is simple but there are a bunch of gotchas. What about transactionality, partial updates, running multi document queries, consistency of the whole set of documents. You have to rewrite a whole DBMS on top of s3 itself or use redshift to get these things.

In terms of scalability there are, limits 3500rps per key prefix.

It's actually not lower price than a DBMS when you have a lot of data.

"perfectly"? I mean this sounds dubious. ChatGPT gives interesting suggestions and advice when it comes to coding but I've never been able to get any close to a perfect solution.

I don't think coding AI assistant's are meant to be used in that way anyway...

I think this is just another fluff piece about how coding is now dead (long live coding). That's basically not true. LLM have gave us a leg up but they haven't removed the need for a competent programmer.

If you mean can we simulate a brain inside a computer the answer is no we can't it's unlikely that we can without building something similar to the brain which is why this product is a thing.

The physicality is important here.