Writing an app is like coding for LaserDisc

Re:Writing an app is like coding for LaserDisc by pjmlp on Monday September 05, 2022 @11:35AM (#32725454)

Blend is your friend.

The only reason I went back to cloud and Web development, is that pre-covid it was the best way to get 100% remote jobs, so I put up with it.

By the way, most of those iOS/Android users are using apps and not Websites.

[ Parent | on HN ]

Re:Writing an app is like coding for LaserDisc by YesWeWill on Monday September 05, 2022 @11:41AM (#32725557)

They might be using apps, but my customers don't want to pay for developing for four or more separate platforms (Windows, macOS, Android, iOS - also notice that nobody would develop for Linux), so they solve it by having a single platform - the web. Many of my customers previously had (only) a Windows app but found out that onboarding new customers is much faster (and thus happens more) with web apps.

.NET is dead to me, I simply don't trust the platform/libraries to continue existence and receive updates. Also the JS/NPM ecosystem is much larger and that's truly what's keeping me there.

[ Parent | on HN ]

Re:Writing an app is like coding for LaserDisc by pjmlp on Monday September 05, 2022 @01:04PM (#32726525)

Yeah we don't get NuGet packages that only offer a single function...

[ Parent | on HN ]

Re:Writing an app is like coding for LaserDisc by YesWeWill on Monday September 05, 2022 @01:05PM (#32726543)

Much better to have a bunch of one-function packages that you can simply avoid than to have a dead package registry with 1/10 of the useful stuff (so not the one-function packages).

[ Parent | on HN ]

Re:Writing an app is like coding for LaserDisc by pjmlp on Tuesday September 06, 2022 @12:57AM (#32733033)

With the difference that in 10 years those packages will still have support, just like VB 6 runtime and MFC are still shipping on Windows 11.

[ Parent | on HN ]