I don't have any numbers, but we know that the Meta family of apps has ~3B users, and that most of them are on mobile. Let's assume half of them are on Android, and you're easily looking at ~1B users on Android. If you have a nullpointer exception in a core framework that somehow made it through testing, and it takes 5-6 hours to push an emergency update, then Meta stands to lose millions of dollars in ad revenue. Arguably even one of these makes it worth to move to a null-safe language! I know your point is that you need to have that sort of crazy scale to make it worth it and that's true, I'm just annoyed at the comments suggesting that the move to Kotlin is just to pad resumes or because Meta let a bunch of bored devs run amok.
I think its great for recruiting. This signals to the world their investment in making Devs happier (one of top two reasons mentioned was "devs were happier with Kotlin")
What a great project!
I hope stuff like this is still around when I retire, because right now it would just collect dust and make my heart heavy because I don't have the time to pursue such a hobby
If it's any peace of mind, the parts to build them should be available pretty much forever. It's possible I do more runs in the future :) Just for the sake of growing the Forth hardware community!
> the parts to build them should be available pretty much forever
I find that's the most interesting aspect of this board. It's an excellent addition to permacomputing-optimized designs. It's a simple digital civilisation landmark for the ages. Or if you're pessimistic, the ultimate fallback computer.
I somewhat agree, but I don't use tools like copilot integrated into my IDE at all (tried it in beta) and I just hate that the suggestions it made were even worse than what the IDE suggested before.
It was kinda what I wanted but like you said with small errors that were hard to findy because mostly it was working.
But what I reall like is using stuff like edge copilot and other chat-like ai tools to just ask questions and get some, mosty really well, summarized answers. Usually about tech I never used before, haven't used in ages or need to be migrated to much newee versions with breaking changes.
It saves me a lot of reading the docs, fiddling with it, reading the docs again, reading quite a few posts about it e.g. on stack overflow and than finally getting to work on the actual project.
I just ask my questions, try the suggested approach, fact check the docs and get to work
A CMS makes the backend inaccessible. Want to add inline styles to a page? You can't. Want to embed a script for some quick interactivity? You can't. Of course you could attempt to locate the theme files and edit them, and edit the configuration files to enqueue scripts but at that point you're no longer having fun.
The only thing you can do is write paragraphs in templated portions of the page. And that's who a CMS is for: people who are doing a job, and have no curiosity about looking under the hood and messing around.
That's not my experience working for CMS like TYPO3 for many years. Although actually using that power without proper training for the editors often results in chaos.
The only reason fb is able to do this, is the billions of $ behind it... For everyone else this is just pure idiocy
Sure if you like Kotlin, use it for new software, but rewriting milliona loc for some marginal gains... that how businesses fail more often than not
reply