|
this attitude the author uses, that tech is only valid if used for some scenarios but not others, is quite scary to me. adopting an anti-flexible, narrow view of prospective uses is against the free form, ingenuitous, creative spirit that I hope tech can embrace. these days though I feel like a really radically conservative outlook is on the rise, that doubt & mistrust & denial are selling strong. and, as usual, it's scary inuendo & dogpiling that makes the case, not numbers or specific contentions: > Think of the thousands of security patches and workarounds, the intricate DOM optimizations, the multi-webpage inter-process resource sharing. None of that will benefit an Electron app and will only slow it down. meh. I don't think there's much to worry about here author. I think there's more to gain by having a well tread, versatile, robustly optimized, secure platfo underfoot. and I don't believe your claim that this comes at some great speed cost. > To put it shortly, you’re misusing the software. nahhhhhhh. you just have weird hang ups dude. chill. I do really appreciate them acknoding that devs like the development environment. the declarative model is really good (although react & many others murky this assertion). react-native to me seems like a natural continuance of this idea, of giving the devs what they know and want. I'm unsure why it hasn't succeeded more, but it's so always felt like it was kind of sticky, that there were long cimixated fights with the many underlying is layers & that in general native platform boggery set in. electron continues to offer that great web native platform plus well known cross-os node platform, and trying to beat that is exceedingly hard. |