Sounds like the whole AI movement.

Darts an amazing language too.

It is basically a revamped Java.

Google lost the opportunity to actually make it take off, had they replaced the Java stack with Dart, instead of staying in the Java world and adopt Kotlin.

However the Android team was never a great supporter from Dart in first place, hence why you won't find anything Dart on https://developer.android.com.

Google uses Flutter/Dart for their own apps fairly frequently. Obviously not the right choice for the most complex apps. Android system programming and cross platform apps are use cases that are divergent enough that trying to smash them together would result in nobody being happy about the outcome.

Pretty sure AdWords is built on dart too

Of course, they were the ones that saved Dart in first place, after DartiumVM was killed.

Having just finished moving from GWT into AngularDart.

Except for AdWords and Google Pay, which ones?

As far as I am aware, most teams would rather use J2Objc or KMM than Flutter.

Everything running on Fuchsia; NotebookLM; various dashboards and admin apps like Google Classroom, Google Analytics; Google Earth; Google Pay, etc.

They should have pushed dart instead of Go imo.

Google never pushed Go, the UNIX/Plan 9 and Oberon folks did, as means to avoid doing C++, with support of their line managers as their 20% project.

Kubernetes was originally written in Java, and Docker in Python, it was thanks to early Go advocacy, that those projects got rewritten in Go, and then they got lucky.

Just like the download server rewrite into Go, that was done by someone from Go team, as part of their advocacy.

Check how many public projects does Google do, outside anything related to CNCF project landscape.

I thought ai was writing all the code. What do they need engineers for?

FAFO

> I'm still not sure what the point of having the bot do it

Laziness. Why else?

Fits perfectly with typical capitalistic short sightedness.

AI fans would say “this is what the spec is for”.

An interesting take.

You get lots of things for free when targeting JVM bytecode. GCs, JITs, interop with one of the largest and most battle tested ecosystems.

Hilarious that Claude was used to make it.

LOL yeah, jokes on claude for helping me create something AI-unfriendly i guess!

I've noticed this a lot in LLM generated Java. Since it doesn't know what can or can't be null it tends to wrap everything in Optional<T>. Super strong type systems are becoming even more important.

You probably need to tell it to rip as many of those out as possible (and replace them with null annotations).

I've noticed LLMs sometimes pick a documented anti-pattern (passing Optional around in Java is not recommended), then amplify it (like a human might).