Earlier quoted context omitted.
File System API is a baseline feature supported across all major vendors. https://developer.mozilla.org/en-US/docs/Web/API/File_System...
Ya, it's odd to say it's not on other browsers when they all have it just to variable degrees... it's almost as if there are comment bots here that are trained on outdated data ;)
I'm done making desktop applications (2009)
81–88 of 88 posts
Re: I'm done making desktop applications (2009)
#82Earlier quoted context omitted.
Developers like you and I are a dying breed. We remember writing applications for operating systems that had straightforward APIs, and OS developers that worked hard to ensure any app which used those APIs would not break. Most "full-stack" developers I know that write web apps have literally never written a line of C++ in their life, let alone written a rich text editor using an object oriented desktop GUI API. They…
But C++ hurts, a lot. My first foray into C++ was trying to write exactly a GUI app for Win32 back on Windows 98, it hurt, a lot.
Re: I'm done making desktop applications (2009)
#83Would be interesting though to repeat this analysis today because the rise of AppStores considerably simplified the shareware model for those who use them (while they have huge drawbacks too). 1. Land on the site by searching 2. Click on the preferred/compatible AppStore link 3. Optional step for tech savy users : Read commitments and review to check if something is dubious 4. Use the app for X weeks of trying period…
I actually find myself actively avoiding getting anything from application stores without prior outside knowledge. Why? Because given no other context I cannot tell apart the decent from the bullshit, let alone the good. There are no differentiators because the storefront obviously accepts everything including the bull-est of shits, being paid-for or free-beer is hardly a useful measure these days (and $5 is nothing)…
There are app stores that are curated. F-droid and Linux repositories.
Re: I'm done making desktop applications (2009)
#84Also, from a end user point of view, unless you are downloading from a known and reputable software company, you assume the exe contains spyware and viruses by default. That has been the main reason for me to download desktop apps sparingly.
Re: I'm done making desktop applications (2009)
#85Earlier quoted context omitted.
But C++ hurts, a lot. My first foray into C++ was trying to write exactly a GUI app for Win32 back on Windows 98, it hurt, a lot.
“Modern” C++ is completely different to the pre-2000 or even pre-2010 C++.
Re: I'm done making desktop applications (2009)
#86Earlier quoted context omitted.
In ignoring this subthread because you introduced the “pre-2k” filter which I never mentioned and turned this into a no-true-Scotsman debate.
... what ? how is 90s not pre 2k? you do know what timeperiod the 90s is, right? oooh, i see. you edited it out of your initial comment back then and i didn't notice. I guess you realized how dumb that statement was and couldn't man up to it.
> Developers like you and I are a dying breed. We remember writing applications for operating systems that had straightforward APIs, and OS developers that worked hard to ensure any app which used those APIs would not break.
> Most "full-stack" developers I know that write web apps have literally never written a line of C++ in their life, let alone written a rich text editor using an object oriented desktop GUI API.
> They don't know it's not supposed to hurt.
HN doesn't allow editing comments outside of a very short edit window.
Re: I'm done making desktop applications (2009)
#87Earlier quoted context omitted.
“Modern” C++ is completely different to the pre-2000 or even pre-2010 C++.
For those of us who were last paid to write C++ in a different millenium, suggestions for a book to catch up?
(Less snark: just browse cppreference.com. The standard library is updated to make use of new features, so just check out the changes between C++14, C++17, C++20, etc.)
Re: I'm done making desktop applications (2009)
#88Earlier quoted context omitted.
We just moved the responsibility of security off the desktop, to the web. We abstracted the problem as an industry, hooray.
Well we did more. By moving the compute and core to the other side of the fence within control of the seller it becomes hard(er) to pirate. Whereas as soon as you provide a working binary it is only a matter of time somebody has pirated it.