Skip to content
loading...

re: Does your website really need to be larger than Windows 95? VIEW POST

TOP OF THREAD FULL DISCUSSION
re: As long as we're here, non-browser apps generally reach a smaller audience since there's a slightly higher barrier to entry. The user has to go and...

You write a webapp, it work on Windows, all Linux distributions that run a desktop and Firefox or Chromium, iOS, OSX, Android, and Chromebook. You write a desktop application, just making sure your application is portable to all of those operating systems takes careful design.

It had become much harder to target all major web browsers (with all major JavaScript versions...) than to target all major operating systems. JavaScript can break tomorrow. The Windows API probably won't.

Even with the disparity in abstraction level between desktop and mobile operating system development environments, making cross-learning and cross-development more difficult? Your first step in trying to generically cross all of those operating systems is surely to make a uniform abstraction layer. But that's what the web app platform is. To supercede the web app platform, you have to do it better and market it to developers really well. Maybe HTML5 is the answer, I don't know, I write embedded code for the most part. But I sure don't expect developers to abandon all the really nice JS frameworks in 5 years.

Also, even if what you say is taken for granted, that doesn't address how much more difficult the Windows API is to learn than JS.

Anyways, what I'm saying is, give us an open source framework better than Qt, and stop telling current JS developers what they already know.

Even QT and JavaFX are "polluted" by CSS. Like JS, CSS is not the perfect language but is the best we have for now for client apps.

Even with the disparity in abstraction level between desktop and mobile operating system development environments, making cross-learning and cross-development more difficult?

With the advent of FireMonkey (Delphi for Android/iOS) and Xamarin (.NET for Android/iOS), this can safely be considered a solved problem.

that doesn't address how much more difficult the Windows API is to learn than JS.

The Windows API was an example. Even if you use wxWidgets or (my favorite GUI framework) IUP, you can be sure that there will be no major OS upgrade in the next two weeks that breaks everything. This can not be said about Chrome's and Firefox's JavaScript interpreters.

Okay, well then evangelize your favorite cross platform GUI framework instead of lecturing JS devos about JS.

Lmao when have Chrome's or Firefox's JavaScript interpreters ever broken a single thing?

"Lmao" (please try to keep your questions at least relatively civil, "lmao" looks dumb and won't make you win this argument), you are aware that both V8 and SpiderMonkey (or whatever is the current name of that thing) are constantly updated and extended with non-standard "ECMAScript" features? You are aware that every single Chrome update has - so far - broken one or more websites?

Feel free to use your favorite search engine instead of lmao'ing at me.

I didn't realize I'm in any sort of argument right now
I was just requesting specifics, of which I received none so far.

Can you give me an example of serious breakage from a Chrome or FF update in recent history?

I googled the last 4 versions of chrome before I got bored and got one bug in timezones that was fixed within that same version.

I didn't realize I'm in any sort of argument right now

Neither was I before you started to laugh at me. That was not nice.

Can you give me an example of serious breakage from a Chrome or FF update in recent history?

This one?

code of conduct - report abuse