Two corrections:
1. "Gateways can inject whatever they want into nsites, and by extension napps." This was erroneous and obfuscated, 44billion originally served "napps" but the "napps" ontology was c...
Anything I say will sound like I'm protecting 44b.
I'll just add that napplets running both on web and on native platforms is what would make napplets reasonable. Though when napplets use html and css, it forces the native shell to embed a full browser engine, thus not being really native anymore. Thus to me napplets currently are nsites with arbitrary constraints.
I didn't look too closely at Verdana napps, but I think it started walking the same path of napplets in this regard, but now it is moving to wasm and that would make much more sense. Although it may initially suffer from less adoption cause html and css is easier for devs, the profession is dying and everything is easy for AI.
I can switch or add support to the winning spec anytime. I just don't see a reason at the moment.
I'll just add that napplets running both on web and on native platforms is what would make napplets reasonable. Though when napplets use html and css, it forces the native shell to embed a full browser engine, thus not being really native anymore. Thus to me napplets currently are nsites with arbitrary constraints.
I didn't look too closely at Verdana napps, but I think it started walking the same path of napplets in this regard, but now it is moving to wasm and that would make much more sense. Although it may initially suffer from less adoption cause html and css is easier for devs, the profession is dying and everything is easy for AI.
I can switch or add support to the winning spec anytime. I just don't see a reason at the moment.
1