Hacker Newsnew | past | comments | ask | show | jobs | submit | invalidname's commentslogin

The whole build in rust nonsense has gone too far. It's a great systems language, but it isn't great for apps e.g.: https://github.com/shai-almog/cn1-wordprocessor/


Other posters here seem to misunderstand what AOT means in today's Java. It just means caching some state. There's still a JIT involved, it's just warmer.

There are other solutions that give you MUCH faster startup with lower memory e.g.: https://foojay.io/today/java-server-work-before-startup/

Edit: it seems I missed that 28 added the actual native code compilation phase so it will probably be closer to the GraalVM numbers in the link above.


Like yourself, because depending on which JVM we are talking about there are various kinds of AOT options.

OpenJDK, OpenJ9, Azul, PTC, Aicas, microEJ, ART (even if not Java TM), GraalVM, Bluesoft,..


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.


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


Which was my last sentence.

The issue isn't that it isn't there, it is mindshare among game developers, especially when it isn't part of the official SDK.

This isn't unique to Java, and that is why outside indie games, it is always the same languages that get used among all major studios.


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.


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.


How is the Mac CLI more convenient? There isn't even a package manager in the box, they ship loads of old outdated tools too. Plus there's the whole BSD/GNU convention thing you have to watch out for.

I don't find my ThinkPad running Linux overheats, nor is it particularly heavy. And performance is comparable to the similarly priced MBP at the time. Camera sucks, but compared to my Surface so do the Macs...


Prefer my Konsole setup on KDE and I use both interchangeably all day tbh. Camera yea. The irony is heating issues become less of an issue with arm.


We are lucky in that we can choose our machines (within reason, and no real support if things get broken) and run an arch flavour.

I use thinkpad x1 carbons and have nearly 0 issues. The hardware is not quite as nice as a macbook but it does the job and is nice enough.


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.


No LWUIT?


Thanks for pointing out the omission. I have added it. It certainly deserves it place there.


LWUIT wasn't particularly awesome, in my opinion. It was enormous and hideous and couldn't integrate with the native cut-and-paste functionality offered by some phones.


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.


Cloud companies will charge you if you use their features without limits: news at 11...

Observability solutions of this type are for the big companies that can typically afford the bill shock. These companies can also afford the routine auditing process that makes sure the level of observability is sufficient and inexpensive. Smaller companies can just log into a few servers or a dashboard to get a sense of what's going on. They don't need something at this scale.

Pretty much every solution listed lets you fine tune the level of data you observe/retain to a very deep level. I'm personally more versed in OneAgent than OTel and you can control everything to a very fine level of data ingestion.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: