SDL Moves to GitHub
211–220 of 270 posts
Re: SDL Moves to GitHub
#212Earlier quoted context omitted.
If anything TLS has gotten easier since Lets Encrypt came along. You just install one of the clients for it, configure a domain and periodic renewal and you're done.
For a public facing computer, yes, for a private one, not so much[1]. I use mkcert[2] for this but it's still fiddly. [1] https://letsencrypt.org/docs/certificates-for-localhost/ [2] https://github.com/FiloSottile/mkcert
Re: SDL Moves to GitHub
#213Earlier quoted context omitted.
The majority of the world is on linux. A small remaining fraction is on windows, where there is no less cruft. Yes, there are embedded OSes (l4); ibm i&z; etc. (L4 and ibm i are actually super cool.) But those are tiny drops in the bucket and aren't replacing linux any time soon.
What world? ChromeOS and Android? POSIX APIs are not exposed to app developers. Cloud? Language runtimes and serveless make POSIX irrelevant. IoT? Linux is largely irrelevant in the world of real time OSes and bare metal language runtimes. Desktop? How is that 1% going?
Re: SDL Moves to GitHub
#214Earlier quoted context omitted.
Which is one of the reason's Stallman's ideas are fundamentally flawed as if there's a better product available even if it's only free as in beer, people will use it over the worse one, from the end user's perspective.
In the worldview of Stallman, your argument is analogous to saying that advocating for democracy is flawed because if an authoritarian regime or slave society provides a better product, people will choose it over worse democratic ones. To Stallman, your counter-argument is a non-sequitur. His goal is maximizing user freedom. UX may be one dimension of user freedom, but at best it's secondary to certain prerequisite f…
Very few people in the world, even most FOSS contributors and developers, share that belief that strongly. They might feel like FOSS programs give them certain advantages and rights, but morals? Stallman has mentioned that he would rather go homeless than run proprietary software. That level of devotion is exceedingly rare.
To approach someone, even a Linux user, and tell them that they need to give up their convenience for free software because what they are doing is immoral, that's a very hard sell. This is one reason GNU has mostly produced free software clones of better, commercial software, where practical concerns take a backseat to GPL.
Re: SDL Moves to GitHub
#215Earlier quoted context omitted.
The majority of the world is on linux. A small remaining fraction is on windows, where there is no less cruft. Yes, there are embedded OSes (l4); ibm i&z; etc. (L4 and ibm i are actually super cool.) But those are tiny drops in the bucket and aren't replacing linux any time soon.
What world? ChromeOS and Android? POSIX APIs are not exposed to app developers. Cloud? Language runtimes and serveless make POSIX irrelevant. IoT? Linux is largely irrelevant in the world of real time OSes and bare metal language runtimes. Desktop? How is that 1% going?
The underlying POSIX filesystem is still exposed to android developers via java's File. And via the C apis too, from the sounds of things. I think its the same on iOS.
But even if you're only using posix calls indirectly through complicated database abstractions and unix sockets, you're certainly still paying a cost. Plenty of benchmarks have been made over the years showing how better APIs can yield 20+% more filesystem & TCP socket performance on linux by bypassing write() and friends. If you spend $10k on a database or application server, think about it as $2k of that hardware wasted simply due to bad kernel APIs. And I'm sure there's plenty of features postgres and sqlite don't have because their devs instead needed to spend their days in a desperate struggling to make their software work correctly, at all.
Aside from performance, in my opinion a better API would also be transactional, at the filesystem level. Aside from dramatically simplifying every database, that could also would allow collaborative editing through simple network shares. I don't even think it would be that hard to do.
Re: SDL Moves to GitHub
#216Earlier quoted context omitted.
The majority of the world is on linux. A small remaining fraction is on windows, where there is no less cruft. Yes, there are embedded OSes (l4); ibm i&z; etc. (L4 and ibm i are actually super cool.) But those are tiny drops in the bucket and aren't replacing linux any time soon.
What world? ChromeOS and Android? POSIX APIs are not exposed to app developers. Cloud? Language runtimes and serveless make POSIX irrelevant. IoT? Linux is largely irrelevant in the world of real time OSes and bare metal language runtimes. Desktop? How is that 1% going?
IoT is even more of a niche than desktop.
And, I think you underestimate the amount of software written in c, directly against posix.
Re: SDL Moves to GitHub
#217Earlier quoted context omitted.
What world? ChromeOS and Android? POSIX APIs are not exposed to app developers. Cloud? Language runtimes and serveless make POSIX irrelevant. IoT? Linux is largely irrelevant in the world of real time OSes and bare metal language runtimes. Desktop? How is that 1% going?
You are making the great-grandparent's point (with which I was agreeing). Their concern was not only the cruft built up in the POSIX API, but the many layers of abstraction and behemoths of code that depended on said cruft, making it a compatibility nightmare to ever remove. That comprises the web browser that drives chromeos's apps; the java runtime that drives android apps; the language runtimes that drive serverle…
Since then, language runtimes have spared me the effort, and I am not alone.
Re: SDL Moves to GitHub
#218Earlier quoted context omitted.
Personally I find this far more worrisome signal of the health of foss ecosystem than the quibbles between elastic and amazon. To me the idea of software "by hackers for hackers" and scratching your own itch has always been one of the key attractions in FOSS ecosystem, but somehow now our itches seem to have outgrown our ability to scratch then. Doing almost anything yourself feels impractical these days. This is als…
Being a bit older this is no different than seeing the 70's hippies generation that helped fighting the dictatorship, working in capitalist right wing companies. Eventually other things in life are more relevant and all that idealism fades away. Even Linux will eventually be replaced by something else, when all the kernel engineers that helped its adoption are gone. It won't be tomorrow, but it will come.
I disagree. Linux has reached critical mass, the biggest tech giants depend on it heavily and are the main contributors. If some new fancy subsystem, interface or syscall would benefit Google's workload, they will implement it and it gets merged since even of Google will be the only one using it, that automatically means it has millions of users. You come along with a not completely polished and thoroughly tested Lego mind storms usb driver for Linux today, you'd get laughed of the mailing list, because security and who will maintain that? I mean security is good and stuff, but Linux is a commercial product today and nothing a curious 16 yo can get involved with like in the early 2000s.
> It won't be tomorrow, but it will come.
I mean if you're talking decades here you're probably right but then again that also will hold true for Windows, Chrome, HTTP/3 and basically everything.
Re: SDL Moves to GitHub
#219Earlier quoted context omitted.
What world? ChromeOS and Android? POSIX APIs are not exposed to app developers. Cloud? Language runtimes and serveless make POSIX irrelevant. IoT? Linux is largely irrelevant in the world of real time OSes and bare metal language runtimes. Desktop? How is that 1% going?
pjmlp, I don't know how you can keep claiming stuff like this. Android has fopen and pthread and you are allowed to use them in your app.
https://developer.android.com/ndk/guides/stable_apis
> Note that on Android, unlike Linux, there are no separate libpthread or librt libraries. That functionality is included directly in libc, which does not need to be explicitly linked against.
Better learn how much POSIX Android actually allows.
Re: SDL Moves to GitHub
#220Earlier quoted context omitted.
What world? ChromeOS and Android? POSIX APIs are not exposed to app developers. Cloud? Language runtimes and serveless make POSIX irrelevant. IoT? Linux is largely irrelevant in the world of real time OSes and bare metal language runtimes. Desktop? How is that 1% going?
> ChromeOS and Android? POSIX APIs are not exposed to app developers. Cloud? Language runtimes and serveless make POSIX irrelevant. The underlying POSIX filesystem is still exposed to android developers via java's File. And via the C apis too, from the sounds of things. I think its the same on iOS. But even if you're only using posix calls indirectly through complicated database abstractions and unix sockets, you're…
In fact, there are special derived classes to handle file system specific semantics, if one feels inclined to do so, but that doesn't mean they work all the time, as JVM runs anywhere.