

!principia@sopuli.xyz was developed as a commercial title a few years back. I believe, @ROllerozxa@sopuli.xyz contacted the devs to get it open-sourced.
!principia@sopuli.xyz was developed as a commercial title a few years back. I believe, @ROllerozxa@sopuli.xyz contacted the devs to get it open-sourced.
They’ve posted on Mastodon, that it is a (D)DoS: https://linuxrocks.online/@Codeberg@social.anoxinon.de/113995906036180301
Those regex crosswords ain’t gonna solve themselves…
Company-internal service where the users would write their desired configuration into an Excel file. Then they push that into a Git repo, which triggers a deployment of the service with the configuration read from all the Excel files.
(Other than things like locked down smart phone bootloaders, but that’s got nothing to do with the FOSS part of this discussion.)
See, I disagree on that. If I know something I could (help to) build will only ever be used by a few folks and can never help most people, then my motivation is significantly lowered. Well, unless I’m truly just scratching my own itch, but even then I might choose to not scratch my itch, because I’d rather quit using the platform, if possible.
And then, yeah, what the other person said about financing.
For Android, there are various small efforts in terms of forks, with the biggest being LineageOS. There are even some commercial efforts, like /e/OS. I think, Huawei also wanted to do a fork or something. No idea what happened with that.
But yeah, none of these efforts are hard forks, which can change more than superficial stuff. And it’s not for a lack of desire, but because it’s just such a ridiculous uphill battle to try to get anything noteworthy changed. Many times, LineageOS (and its predecessor CyanogenMod) had some cool features, which they later had to scrap, because they needed to follow what Google was doing and their features wouldn’t work with that anymore. If they would’ve seen any chance of a hard fork working out, they probably would’ve tried to go that route.
Well, any software needs to include a license of some form, if you want it to be usable by others. But if it’s not an open-source or libre license, then it’s a proprietary license. That’s not necessarily a bad thing. At that point, it depends on what’s actually written into the license. But it’s also not a good thing, as you miss out on various open-source benefits due to there being no proven legal compatibility with open-source licenses. Well, and if I remember correctly, FUTO’s license actively prohibits reuse of the code anyways.
I also like to use log statements or error messages as a way to describe what’s happening.
Comments are only visible in the exact spot where they’re written, whereas decent names or log statements become visible in a second place, which makes them more valuable, but also increases the chance of them being kept up-to-date.
Personally, I’m at the point where I try to only use community-developed software. I’ve seen it too often that even projects which are nominally open-source start becoming cunts…
Android, Chromium.
The problem is that:
And so long as a fork is unlikely, Google can do shitfuckery quite similar to proprietary projects.
Yeah, everyone else had already answered that, which felt like we’re picking apart that specific thought experiment, even though there is actually a much more fundamental reason why it won’t work.
Perhaps also worth pointing out that the speed of light is that exact speed, because light itself hits a speed limit.
As far as we know, light has no mass, so if it is accelerated in any way, it should immediately have infinite acceleration and therefore infinite speed (this is simplifying too much by using a classical physics formula, but basically it’s like this: a = f/m = f/0 = ∞
). And well, light doesn’t go at infinite speed, presumably because it hits that speed limit, which is somehow inherent to the universe.
That speed limit is referred to as the “speed of causality” and we assume it to apply to everything. That’s also why other massless things happen to travel at the speed of causality/light, too, like for example gravitational waves. Well, and it would definitely also apply to that pole.
Here’s a video of someone going into much more depth on this: https://www.pbs.org/video/pbs-space-time-speed-light-not-about-light/
Oh, that is actually the part I do agree with. I don’t think everyone will, but I do actually think JSON is easier to read and write (correctly) than YAML. I specifically wrote that JSON cares the least about that, because it was designed to just serialize JavaScript objects into strings and back. As far as its original purpose is concerned, no one would ever need to hand-edit JSON. Which is also why it doesn’t support comments (which is still somewhat of a dealbreaker for a configuration language, although I guess for your proposed workaround, one could potentially use a JSON flavor which supports comments; potentially, you can even write your JSON in the YAML file with comments directly and then not convert it, since YAML is a superset of JSON).
As for documentation, yeah, it is possible to convert, but it makes it more annoying, particularly also if you then can’t easily re-use configs in another project. And if you’re working in a team, having to explain to all your team members, how they can convert the official documentation, is also not really acceptable…
I love this comment. JSON is by far the format that cares the least about being human-readable or -writable, but you’re seriously proposing writing it rather than YAML. And I kind of don’t even really disagree. But a big problem with that strategy is that you won’t find documentation for how to write the configuration in JSON.
What comes sort of close, is that you can define so-called “schemas”, at least for JSON, TOML, YAML and XML. Here’s what that might look like for JSON: https://json-schema.org/learn/getting-started-step-by-step
I don’t know, if you can actually generate a GUI from such a schema, though. They’re intended for validating existing data, so I don’t know, if they give you enough data to work with to actually provide a GUI. For example, you don’t really have a human-readable name in these. The fields are rather called e.g. “productName”.
Yeah, some distros have GUIs for system settings, like openSUSE and Mageia, but advanced users will often even take that as a reason to not use those distros, because they themselves don’t need that on their system. And because not many advanced users use these distros, it’s hard to recommend them for noobs, because it makes it more difficult to find help resources. Kind of a stupid situation…
I’d argue it all started, because Microsoft is Microsoft: https://en.wikipedia.org/wiki/List_of_Microsoft_Windows_versions#Personal_computer_versions
They’re not saying to create Linux-exclusive games. Just games that run on Linux without WINE/Proton.
Very interesting, thanks. I kind of got stuck on Dungeon Crawl Stone Soup, which used to have a food clock until a few versions ago, now it’s just no respawns. They also scale XP amounts up for higher levels, so when there are more low-level enemies around than needed, they won’t give you a ton of extra XP.
I’ve played around with Angband and ToME a few years ago, and I tried to like Cataclysm: Dark Days Ahead multiple times, but yeah, I feel like that’s probably the reason then why they never clicked for me quite like DCSS. I am absolutely the worst for optimizing the fun out of games, if given the opportunity.
Cubuntu is also a thing.