Embed Notice

@smallcircles@social.coop But if you had a codebase that uses e.g. Redis and an AWS object store,I didn't have a local-first application in this situation to begin with, so we're already off to a terrible start. You're right that this "new tech" is an improvement over the absolute worst state of garbage we have, but setting that as the baseline is simply disingenuous to me. Rather than lowering the barrier so we can pretend everything is an improvement, I'd suggest we stop pretending atrocious development practices are good and start calling them out on it. Better yet: stop using it when you can!And your builds need not worry about all the different processor architectures.But anything implementing WASM still needs to, and those builds will get more complex. You're not "fixing" the complexity, you're shifting it outside your viewpoint.Performance is near-native. Wasm is low-level stuff.This is marketing speech for "performance is worse". Keep doing cycles of getting "near" the thing we already have, and with time your performance is just absolutely atrocious. #Javascript is littered with things that get "near" to what we want, and what we've gotten is piles and piles of badly performing garbage requiring me to use several gigabytes of ram just for my browser to read documentation for my #day-job.