[coldtea]

>I’m not really that into the idea of JS-as-a-platform, but it obviously emerged because it fulfilled certain requirements that weren’t covered elsewhere.

Maybe they weren't covered for a reason?

The ability to have your web team churn out lowest common denominator bloated JS based mobile/desktop apps was not a real requirement, more like a wish of some.

Now businesses do that just because they can.

[fvdessen]

They do it simply because it's the most cost effective solution overall.

[kziizijd]

Typical capitalism outcome.

Cheapest to produce AND worst quality. In this case by bad performance and unneeded cellphone battery drain.

These products will be dominated by superior options eventually.

[TeMPOraL]

> These products will be dominated by superior options eventually.

Would love that to happen, but all the other market sectors suggest otherwise. "Cheapest to produce and worst quality" seems to be all that's available to majority of the population.

[StreamBright]

Like Apple, Lexus and Infiniti products. Totally.

[TeMPOraL]

Yes. It's the most cost-effective solution, because:

- we haven't figured out how to make companies care about "delivering value" part of the "delivering value in exchange for money" work, and

- we allow them to dump externalities on users without consequences or compensation.

So the most cost-effective solution in this scheme will be a half-assed product that's barely good enough to be sellable, and which makes my computer use more electricity while being less capable of running software simultaneously.

[Can_Not]

And the whole point of native components in Vue/react is to reduce those negative externalities, but the first thread I see in this post is criticizing Vue for sharing from react's ecosystem instead of inventing an indentical solution from scratch?

[qaq]

At the current rate we will soon have phones with 8GB RAM and who knows how many cores not having to rewrite same code 3 times in 3 lang. will def. be catching on more.

[TeMPOraL]

If by soon you mean in 2 years on flagships (looking at current specs, I don't buy it), then for regular users buying regular smartphones it'll be ~7 years from now.

I don't feel like this is a valid justification for being wasteful, though.

[throwaway413]

The OPO 6 is out now with 8GB RAM, so no not in two years, let alone 7.

[TeMPOraL]

That's an outlier, pretty niche one at that.

(Personally, I didn't even realize OnePlus phones still exist - I thought they died out somewhere around OnePlus 3.)

[Raphmedia]

> The ability to have your web team churn out lowest common denominator bloated JS based mobile/desktop apps was not a real requirement, more like a wish of some.

Come on, the requirement has always been there. It is "Shit out that underbudgeted project in half the promised time". Those small frameworks where you can hire a cheap front-end guy and have him manage the entire project alone or in a small team are perfect to fill that niche.