I always try to find something that runs in web-assembly, but it's better to avoid nodejs altogether if you want high security. Go is much better for these kind of things overall.

I'm not quite sure OPs approach is the best tho, serverless is just somebody else's server.

Better to use something like Onionshare and run it on a device on-premise then transfer the files to an air gapped device for decryption.

Then the network will hard fork and we will have SETH (the sell-out ether) and regular good ole ETH.

It's up to Vitalik now to determine our fate , let's destroy em from the inside.

/sarcasm

Contrary to BTC, ETH is not deflationary if it's not traded on chain. The deflation comes from the burn mechanism.

So concentrating ETH in ETFs would decrease the price over time due to inflation since the ETH is traded without transferring it.

"it can be very hard to follow": I agree, if you are not a lisp developer it's really hard, but if you develop clojure everyday, it's as easy as anything else.

The answer is usually clean code when it comes to clojure. Keep your functions small.

"more memory intensive, and generally slower": yep, the JVM is more memory intensive than Go. No surprise there and Clojure adds up on top of that. Startup times are pretty slow too. But compared to python it's still fast. Apples to oranges.

I would say Clojure and Go are both great languages that tackle different problems so it's not a fair comparison.

For startups, subscriptions can stack up fast and it's the same as B2C, they can't afford it. Subscriptions are liabilities.

But for medium sized businesses or larger, it depends on how much value the tool provides but should be fine, especially if they can fire somebody now that a fancy AI does his job. Enterprise pricing is a thing for a reason.

But the most important thing is to get the product right.

I think you can get models to "think" if you give them a goal in the system prompt, a memory of previous thoughts, and keep invoking them with cron

It will be fully available in Eu with the GDPR compliance?

Stuff like parse some XML or JSON and output Go structs and functions and Typescript types and functions, HTML,React Components, SQL Tables, Stored functions, Pl/PGSQL.

Mostly to avoid writing boilerplate when I use the same data structures in the database, middleware, client. For simple CRUD apps, it works well. I use local KV to track changes so I don't have to rerun things I don't need.

But Deno is great for CLI reporting tools or Scheduled tasks, fetch and aggregate data.

I think of Deno as a little swiss army knife. It's a tool that got everything built in.

I use the Repl a lot, just for a specific task, get it done then move on.