Gotta have multiple AZs.

The server is probably running Python

Now I am waiting for time when they move us-east-1 physical security to run in us-east-1... Thus locking themselves out when needing some physical intervention on servers to get backup.

This is in SEA. They probably operate from ap-southeast-1 or 2. But yeah, if the internet goes down, the provider service goes down or AWS goes down they are cooked.

>than having to buy hardware to put somewhere in the building (with redundant power, cooling, etc.), and have someone deploy, install, manage, update, etc. all of that.

You don't need any of that. You need one more box in the electrical closet and one password protected wifi for all the crap in the building (the actual door locks and the like) to connect to.

> with redundant power, cooling, etc

The doors the system controls don't have any of this. Hell, the whole building doesn't have any of this. And it definitely doesn't have redundant internet connections to the cloud-based control plane.

This is fear-mongering when a passive PC running a container image on boot will suffice plenty. For updates a script that runs on boot and at regular intervals that pulls down the latest image with a 30s timeout if it can't reach the server.

The system was not built with resiliency in mind and had no care/considerations for what a shit-show will unfurl once the system or the link goes down. I wonder if exit is regulated (you can still fully exit the building from any point using the green buttons and I think these are supposed to activate/still work even if electricity is down).

> Yes, but still probably a million times easier for both the building management and the software vendor to have a SaaS for that, than having to buy hardware to put somewhere in the building (with redundant power, cooling, etc.)

A isolated building somewhere in the middle of the jungle dependent for its operation on some American data-center hundreds of miles away is simply negligence. I am usually against regulations but clearly for certain things we can trust that all humans will be reasonable.

Some Forths are dog slow such as PFE compared to GForth. Meanwhile others running in really slow platforms such as subleq (much faster in muxleq) run really fast for that the VM actually as (almost something slightly better than a 8086).

It's not really "interpreted", in the way that for example BASIC or Java is.

It's a list of jumps to functions.

I worked on a startup that was mostly powered by Tcl, the amount of rewriting in C that we had to do between 1999 and 2003, when I left the company among all those dotcom busts, made me no longer pick any language without at least a JIT, for production code.

The founders went on creating OutSystems, with the same concepts but built on top of .NET, they are one of the most successful Portuguese companies to this day, and one of the few VB like development environments for the Web.