invalidname

We have that in Codename One, yes it's not really "Java" but it compiles bytecode AOT and cross compiles to some of the platforms.

You're thinking of Google as a single top down company. It isn't. Think of it as an anarchy of warlords where each pulls the strings and management doesn't really know what's going on.

Flutter made a lot of sense during the Oracle lawsuit when Google needed a way to show Oracle that it can pivot from Java. Now it no longer makes sense but the inertia is too deep.

My guess is that flutter is sold internally through the Huawei support as a leg within China.

Sure and I don't argue that. But it also wasn't fully there. This past couple of weeks Codename One introduced some big missing pieces:

* Level builder/game designer * Proper 3d that works natively everywhere (direct 3d on windows, metal on iOS/Mac) * Support for native win32, Linux and mac - real native with no JVM, 5mb binary * Native performance for some edge cases (low level SIMD API etc.)

You're right that mindshare is a huge part, but there were also many important missing pieces especially on the deployment front. I think that with good tooling and a royalty free pitch this might open some doors that were previously closed to Java.

Getting to major studios would be an uphill battle but since they acquire indie studios the path goes through there.

You should check out Codename Ones recent gaming related features...

They give us Dell Linux machines from work. They suck so bad and we have so many problems. Overheating, camera is terrible, performance is bad relatively to the huge weight of the device. Everything is a huge step down from Macs.

Whenever I see Linux people comparing Linux and Mac I'm amazed at the audacity. They are not in the same league. Not by a mile. Even the CLI is more convenient on the Mac which is truly amazing to me.

As a maintainer of a medium size OSS project I agree. We've been running the produce for over a decade and a few years back Google came out with a competitor that pretty much sucked the air out of our field. It didn't matter that our product was better, we didn't have the resources to compete with a google hobby project.

As a result our work on the project got reduced to maintenance until coding agents got better. Over the past year I've rewritten a spectacular amount of the code using AI agents. More importantly, I was able to construct enterprise level testing which was a herculean task I just couldn't take up on my own.

The way I see it, AI brought back my OSS project that was heading to purgatory.

EDIT: Also about OPs post. It's really f*ing bug bounties that are the problem. These things are horrible and should die in fire...

Predicting the future is futile, but I would guess this would be exactly the opposite. LLMs make it remarkably easy to generate a lot of code so they can easily generate a lot of Rust code that looks good. It probably wouldn't be, and for us it would be unreadable when something goes wrong. We would end up in LLM debugging hell.

The solution is to use a higher level safer, strict language (e.g. Java) that would be easy for us to debug and deeply familiar to all LLMs. Yes, we will generate more code, but if you spend the LLM time focusing on nitpicking performance rather than productivity you would end up in the same problem you have with humans. LLMs also have capacity limits and the engineers that operate them have capacity limits, neither one is going away.

Well... 64kb isn't exactly enormous for the type of functionality it offered. It did support copy and paste you just had to enter editing mode. The underlying APIs didn't offer access to copy and paste directly.

Having said that, it doesn't really matter if you didn't like it. It was a pretty big part of the J2ME ecosystem at the time and it's a huge omission.

No LWUIT?