@tk Why even though?
Like, literally? Just shove the whole pot in the dishwasher afterward if you can't be bothered to wash it by hand.
@tk Why even though?
Like, literally? Just shove the whole pot in the dishwasher afterward if you can't be bothered to wash it by hand.
@lanodan The original compiler used to compile the GCC GNAT was proprietary, and while you can go back to earlier GNAT versions to compile the chain... the original one is obviously missing for a "from source" bootstrap.
@lanodan Yeah... languages without a sane bootstrap path are obnoxious.
#Ada #GNAT still lacks one, for instance. They're working on it last I heard, but for now it's a problem.
@kaia *Prepares to unleash a broadside*
@hyphen @ghast @georgia @pluralistic You cannot enclose #FreeSoftware, by design the licenses forbid it.
#OpenSource misses the point specifically because it was *made* to be succeptible to corruption by corporate interests.
(And also it ignores all the ethical and freedom stuff, but that amounts to much the same.)
Permissive licenses are accordingly even worse.
@hyphen @ghast @georgia The difference though is that with #FreeSoftware, particularly when there is refusal to be influenced (helped by the Ulysses' pact embodied by adequate licenses, @pluralistic mentions those a few times, if you want some fun reading) you can just sidestep the corposcum and just benefit all the same.
Nestle water exploitation, for one infamous example, is usually present as a #monopoly backed by state violence. A rather different scenario.
@georgia If they cannot enclose it, it isn't a transfer of value *to the capitalist class*.
As it so happens, it has been a transfer of value *to everyone*. It just so happens that capitalists still exist and haven't yet all walked into the sea, so they're also part of "everyone".
@allison @SebinNyshkim You're supposed to use the #malware browser editions.
Well except Visual Studio, that one just has *way* too much legacy to reasonably port so they'll probably bundle it in a weirdo static wine bundle eventually.
@SebinNyshkim I guess they're just admitting plainly their OS is the least of their priorities at this point and isn't their main revenue cow anyway.
@aral Ah yeah, sorry about that. I actually was wrong and it's just one of your older articles that's been doing the rounds again.
I was wondering why elfeed wasn't catching it.
@aral By the way, I think your RSS feed might be broken.
It doesn't contain any article newer than the 2023-02-20 Kitten Chat one.
@ezio @devious @allison That sounds quite possible.
Rust diverse platform support is bad.
@ezio @devious @allison Well yes, but I don't think that necessarily says much about ArcaOS, I think that says more about how much OS-dependent stuff Firefox depends on.
Their compatibility layer is probably what you tried to run Firefox with, right?
@ezio @devious @allison The early versions were.
And it lost because they didn't intimidate OEMs into bundling it and cost a pretty penny to get otherwise so users didn't care about them.
@ezio @devious Command Lines aren't jank, they're necessary interfaces on basically all systems that aren't properly integrated with self-programming features (so basically everything other than Lisp OS/Lisp Machine and Smalltalk systems).
@vriska @Rasp Some people seem to forget the Ace spectrum and particularly the "sex-repulsed" part.
Now, do I post stuff on my timeline? Yes. Do I go out of my way to ping people with it, particularly after they've told me they don't like it? No.
As for chats, I'm just used to the old-school tagging nsfw stuff as nsfw. As one does.
@tk Isn't that USB-only?
@tk Well, awful OSes have certainly made it more difficult.
"tar c some-dir | netcat endpoint port" and "mkdir some-dest && cd some-dest && netcat -q 5 -l destination port | tar x" still works.
Good luck doing that on Android.
magic-wormhole is one of the least terrible ways I've found (if you set it up properly transfer will use LAN only, otherwise it'll use the relay).
@izaya @tk PXE has some major cost drawbacks if you want to use it securely, as its lack of authentification/authorization means you have to setup an isolated link for every device (VLANs are an option, though fallible).
@iska I guess you've never heard of #InterlispD?
Though I guess you'd argue that a bytecode VM implemented as microcode isn't a kernel or something.
Outside of machines specifically designed for Lisp, a lot of Lisp OSes didn't run on baremetal per se.
Programmer and Free Software proponent.Extra Pins:Software and Assumed Privilege, common problems: https://mastodon.top/@lispi314/111253066257920146Writing Privacy-preserving software & services 101: https://mastodon.top/@lispi314/110849018589421824#Kopimism #FreeSoftware #CommonLisp
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.