Comment by seltzered_

Something missing from this article is more depth into the issues of doing a webkit-based os back in the late 2000s/2010s, and this goes back to 2008. From https://web.archive.org/web/20140110095058/https://www.theve... (2012, theverge) :

"The way Simon and Grignon saw it, using pure HTML and JavaScript would have a few key advantages. One, it would allow large chunks of functionality to be implemented very quickly because the underlying standards were simple, straightforward, and widely understood. Two, Duarte was intrigued by the notion that his designers would be able to apply their handicraft to apps, screens, and UI elements without extensive assistance from engineers, all of whom had other things to worry about. And perhaps most appealing, WebKit already existed — Palm just had to port it.

Of course, it wasn't that simple. WebKit simply wasn't created for doing this kind of thing. No one working on the core WebKit project had a mobile device with limited RAM, processor, and battery in mind — certainly not for the entire user interface, anyway. Granted, Nokia and Apple had already ported WebKit for use in their mobile browsers at that point, but what Simon and Grignon were spitballing was a considerably more ambitious idea.

One weekend later, though, the two believed they'd cobbled together enough of a mockup to prove that Matias' vision could indeed be realized using nothing more than a web engine. They took the demo to software boss Mitch Allen; Rubinstein saw it not long after. Allen was impressed enough that Grignon was given approval to peel off ten staff members and crank for a month with the goal of bringing up WebKit and basic functionality on a very early prototype handset called "Floyd," essentially a modified Treo 800w"

[...]

"Prototypes of the original Pre first started showing up in Palm offices around April of 2008. Luna was far from perfect, especially running in just the 256 MB of RAM shipped with the original Pre. The system would regularly exhaust the limited space. To help speed things up, the Luna team had decided to port Google's high-performance V8 JavaScript engine, making Palm the first company to ship V8 on mobile"

[...]

"Mercer was shuffled into a new role looking for ways to optimize WebKit, but sources tell us that it quickly became apparent he was only using it to advance his cause: he'd created benchmark tool after benchmark tool showing that the web "wasn't ready for primetime" on mobile. And in a way, he was right — at that time, it wasn't ready for primetime, but Palm's engineers were on the bleeding edge trying to get it there. "It was obvious that this stuff was the future," one senior-level source told us. As the saying goes, they were trying to skate to where they believed the puck was going; Mercer was trying to skate to where it was."

It still feels wild to think of Palm attempting all this while Apple iOS ecosystem developers were generally writing code in Objective-C (Swift came out in 2014).