3 ms·
> well, perhaps with the only exception that now a 2 year old baby can make something shiny that you can click on with your mouse. Rudeness aside, this shouldn
by profmonocle 5y ago
> well, perhaps with the only exception that now a 2 year old baby can make something shiny that you can click on with your mouse.
Rudeness aside, this shouldn't be dismissed. The same designers you already have on staff who make your web sites look nice can make your desktop apps look nice using the skills they already have. Things like React Native mean that the engineers who make your web app can make your mobile apps (on both major platforms at once!), again using mostly the same skill set.
Yes, this leads to lower quality software! Electron apps use tons of memory and have huge binaries, React Native apps take longer to launch, etc. But the cost savings are hard to dismiss, especially for startups trying to get to market ASAP. And most importantly, the market doesn't seem to be punishing companies using these lower-performing technologies at all, so why would you not use them?
As someone who works with stuff the author hates (I work with Angular, NativeScript, and reverse proxies on a daily basis) I agree that it's all horribly inefficient and I'd love to to it the "right" way. I just love the time savings more.
- CRConrad 5y ago> The same designers you already have on staff who make your web sites look nice can make your desktop apps look nice using the skills they already have. Wrong way around. The opposite, yes, but not this way.