blog/metal-default-new-build-cloud-and-a-new-format/

[giscus[bot]]

blog/metal-default-new-build-cloud-and-a-new-format/

The iOS Metal renderer is now the default, the new Build Cloud console is wired into every Dashboard link on the site, and the weekly release blog is moving to a shorter format with deeper follow-up posts during the week.

https://www.codenameone.com/blog/metal-default-new-build-cloud-and-a-new-format/

[jsfan3]

The new communication strategy for the blog makes a lot of sense. Thanks for explaining it. It’s also impressive how much you’ve managed to implement in Codename One in such a short time.

You made me laugh with: “you just had to drop into Xcode or Android Studio and jump through a depressing number of hoops”. Yes, “a depressing number of hoops” is exactly right! ;-) I’m looking forward to tomorrow’s post. I think it’s especially important that the new workflow for testing and debugging on real devices is documented very clearly, so that AI agents don’t start inventing generic paths instead of following the Codename One approach. That’s related to what I commented yesterday here: #5059

The other upcoming topics also sound very interesting.

Since you mentioned “searchable titles”, I have a small suggestion about the search page: https://www.codenameone.com/search/. Sometimes I remember something you wrote recently and want to read it again, but the search results tend to surface older posts that are not what I was looking for. A “newest first” sorting option, or a date filter, would be very useful.

Also, the “Loading search index...” message suggests that the search index is loaded client-side. That probably makes sense for a static site, but it can become slow when the connection is not ideal, especially because the index has to be loaded again whenever the search page is opened or reloaded. It loads fairly quickly for me now (“quickly” still means a half-minute wait), but a few nights ago it was extremely slow (this means a wait of a few minutes). Stronger caching or a smaller incremental index could help in general, but it would not really solve the problem in my case, because I usually browse in private/incognito mode, so the browser cache is cleared when I close the browser. For this reason, a server-side search would be the more reliable solution.

[shai-almog]

Thanks. It loads for me in seconds but I'm on a fast network. It is cached but since we update the index a lot that can still be a delay. I can sort it by dates which I agree is the best approach.