| ▲ | Dwedit 5 hours ago | ||||||||||||||||||||||||||||||||||||||||
Now RAM use is the main reason to prefer native APIs over web views. | |||||||||||||||||||||||||||||||||||||||||
| ▲ | mpweiher an hour ago | parent | next [-] | ||||||||||||||||||||||||||||||||||||||||
I am not sure WebViews are the actual problem, and fairly confident it is running the entire application + gargantuan frameworks as JavaScript is. I am currently working on something I call HTMXNative, which is what it sounds like: using HTMX in WebViews for hybrid apps. I haven't really looked much at memory consumption, but when I've looked so far it's been very comparable to equivalent apps using native UI. | |||||||||||||||||||||||||||||||||||||||||
| ▲ | enbugger 4 hours ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||||||||
A decision to move native because of the crisis seems like an expensive populist move to please not very solvent users. Why bother with that if many predict the RAM crisis will last merely until 2027? | |||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||