Allow me to introduce my favourite toy from my childhood that I have been lucky enough to be able to buy for my son recently: https://www.reddit.com/r/auckland/comments/eymcks/do_you_kno...

It’s called the Humdinger set. Made by an eccentric guy in NZ with no online presence beyond resultantly keeping an email address.

Stumbled across him randomly at a market when we visited last and had to triple take - “is this THE Humdinger” type thing. My mum confirmed it was the real deal, so we bought it on the spot.

Son loves it. Connectable wooden stuff ftw

Yes these are the way. Use them to get cheap anker security cams to work as baby monitors while we’re in hotel rooms

Also see Feedback Analysis, by Peter Drucker from Managing Oneself - https://hbr.org/2005/01/managing-oneself

Trying to implement their gRPC api from their specs and protobufs for Live is an exercise in immense frustration and futility. I wanted to call it from Elixir, even with our strong AI I wasted days then gave up.

We are updating the API to be REST centric. Very fair feedback, see the new Interactions API we just shipped, very REST centric and all future work we do will be REST centric : )

The way the models behave in Vertex AI Studio vs the API is unforgivable. Totally different.

If you’ve spent any time with the vertex LLM apis you wouldn’t be so enthusiastic about using Google’s platform (I say this as someone who prefers GCP to aws for compute and networking).

been using it for years, no idea what you are getting at

I've never had the downtime or service busy situations I've heard others complain about with other vendors.

They did pricing based on chars back in the day, but now they are token based like everyone else.

I like that they are building custom hardware that is industry leading in terms of limiting how much my AI usage impacts the environment.

What do you think I shouldn't be enthusiastic about?

Then you actually use it! I dare someone to try and get Gemini live vertex app working.

Getting downvotes for this, but genuinely laughing over here

Moving from Python to Node for per-process fully-fleshed out async and share-nothing concurrency however is perfectly sane.

Using any of them for backend is insane, but what do I know, I have to suck it up and use Next.js for some SaaS extension SDKs, while I would rather be using JVM, CLR, or even Go with its spartan design.

JS haters could stand to understand the language has strengths even if it has well known warts.

That's the main reason to move. Same reason people moved from Java to Kotlin, except that might change now with vthreads.

Very long OR insufficient. Ah yes, the goldilocks Claude.md