Remix.run Logo
▲ sobiolite 3 hours ago

I think we are starting to see this in some areas: For example, for years desktop apps were built on top of slow and heavy cross-platform frameworks like Electron, because writing them natively was too burdensome. Now we're seeing rewrites in rust using native APIs and toolkits, resulting in lighter and faster apps.

Software engineering as a discipline is also shifting, and will continue shifting, to a process of continuous automated improvement. In the past, test suites were mostly a way to catch regressions. In future, they will be essential to provide a verified baseline of correct behaviour, and then you will have models looped in the background to continually merge performance and reliability improvements. Similarly you will have error and performance logs fed directly into agents to resolve incidents as soon as they arise.

We are in the baby steps of these changes at the moment, but I think in at most ten years, all non-hobbyist software will be built this way.

▲skydhash an hour ago | parent | next [-]

> For example, for years desktop apps were built on top of slow and heavy cross-platform frameworks like Electron, because writing them natively was too burdensome

It was not. Just by using QT you were on the fast track to support multiple platforms. And by 2010, most companies were only interested in Windows and MacOS. But today, it’s just laziness. Devs that only know web tech wants to use web tech everywhere, even when it does not fit the job. Hammer and nail style.

> In the past, test suites were mostly a way to catch regressions. In future, they will be essential to provide a verified baseline of correct behaviour?

And who will code these tests? To design good tests, you have to know the product quite well, and to know the product, you have to build it at least once. Because specs are full of knowns unknowns and unknowns unknowns. That’s why the best spec is the code itself.

Even when you know the requirements, you still have to design the test harness, and that depends on the products too. With the same caveat on knowledge.

▲puppymaster 2 hours ago | parent | prev [-]

Yep. iOS app landscape as well. /r/reactnative are pretty much dead now. Everyone write super optimized swift and objective c codes now :D. I'm not complaining. Some of my favorite niche ios apps are all under 10mb each post AI-renaissance.

▲dwayne_dibley 2 hours ago | parent [-]

If only someone would tell meta. WhatsApp, Facebook and Insta all over 400mb. Madness.

▲honeybadger1 36 minutes ago | parent | next [-]

I think the big issue is what the user sees and interacts with is like 4-5 of the products of the compilation of another 40-50 products that are underneath that spy on you to market, sale, and change the way you think. Without all of that the app would sure be 20-30 megabytes for posts, stories, messaging...or less.

▲yard2010 an hour ago | parent | prev | next [-]

They don't care.

▲phyrex 2 hours ago | parent | prev [-]

Not because of react native ¯\_(ツ)_/¯