If you believe in ADTs, limiting mutation, & a type system that goes beyond Rust’s affine types + lack of refinements (including a interleaved proof system), you could be writing kernel code in ATS which compiles to C.

Nostalgia is a hard drug. You can still appreciate games from you childhood & not buy games or consoles from a evil company.

There’s a small learning curve I wish some bothered to understand first. Does this app help? The part of this I don’t like is vacationers leaving useless names like ‘Mango lady’, ‘many street vendors’ for a block, or ‘local restaurant’ since they can’t read the sign as opposed marking up the cuisine type, maybe adding an English description, & leaving the name blank. Nobody expects uploads to be perfect but Bangkok is littered with this noise that makes it hard to follow or find things.

Duckstation license choice of CC BY-NC-ND is dumb for software for a number of reason—wouldn’t argue that. But there are software licenses in a similar vein, inspired by CC NC but actually for, ya know, software, that do what they want without being fundamentally problematic—and these were the “such licenses” I was talking about the whole time & should be tested/trialed. I think you misunderstood my phrasing.

No modification is a bummer, but I could argue for in either direction more strongly a) some source you can modify but you can’t contribute (like Microsoft’s closed-off Language Server Protocol) which is different level of restriction that flies in the spirit of having a open license making ‘modification’ not open enough since you can’t really get all downstream implementations to support your fork or b) I would be happier being able to see the code such as the encryption used that would be better than nothing (like whatever Discord is trying to tell users it’s definitely-not-back-doored E2EE setup is… trust us). “ND” is better than nothing & imperfect, but it can be seen as a spectrum.

Flimsy awkward adapters + having to choose between charging or audio? But they had matching earbuds with irreplaceable batteries to sell…

Why are you talking about Creative Commons? Everyone knows this isn’t for code (hence Fedora kicking out CC0 code) & everyone knows NC has a loose definition (& good intentions). There are plenty of options in licenses in the post-open source, copyfair, copyfarleft, & such that work for software that are not considered “free” or “open” (where open is more corporate than free, which free is obviously the better one) but still allow users to modify read & usually modify the source. These have their flaws—specifically the incompatibility with free software—but the heart is in the right place in trying to address the exploitation; I encourage the research & development of licenses in these spaces to help the commons. I, as a non-corporation, wish to defend not shame developers from choosing non-‘free’ licenses in these & similar categories for their software. This defense of alternative licensing isn’t moving a goalpost & always was the primary premise.

Embrace your forefather ALGOL: 🤚‍ and, && 👉 ∧

Some of these license are very clear about what is commericial. Some leave it to be ambiguous for the sake of allowing a case by case determination. The goal is often to help workers & the commons—say you as an individual are free to use it for, or others for places where folks have equal pay or say, or less than 10 seats. To say that since a software license says Amazon can’t use this but you can means it’s all proprietary means you are either Amazon or a goober to think these are equivalent. Something something baby out with the water fallacy [^1].

I am not sure reliance on the state is the best way, but it would be interesting to see the results.

What’s wild is the banshees here rarely acknowledge how AGPL works similar to these now adding restrictions instead of laying out what you can do, but daddy OSI approved it so it must be good.

1: Wikipedia

There’s limited vocab to choose from & source available isn’t an appealing one

Not what I am arguing, but we do have two issues: 1) naming/branding for these types of licenses 2) FOSS banshees acting like these licenses aren’t acceptable & the whole idea is binary good or evil

And there is nothing wrong with folks choosing such licences—especially if trying to get paid or not exploited.

5a is EoL so no headphone jack for you. This is a nonstarter for portable devices to me.

Responding broadly to the thread of folks talking about userScripts & add-ons. This effort would be better put to getting folks to a different protocol where client modification & alternate clients are the norm.

Pretty standard for Mozilla logic if you have watched the features cut over the years.

You last me at teabags. What are you doing‽ Loose-leaf hea is cheaper, easier, is almost always high quality, doesn’t impart a taste of bag, better flavor on multiple steeps, & isn’t literal trash (plastic ones are real bad for the environment). You get higher quality leaves & now you don’t need to carry around milk or sugar to mask the bad flavor too.

Why put the effort into such a hostile service?

I would be mad if this would be next to fall since I use it. I don’t self-host Matrix since it is too expensive being built on a fundamental ‘eventual consistency’ model mirroring all text & attachments for all users in every DM & room to your storage—not to mention the Python implementation server & even the Rust one use much more system resources than other open chat options. It’s the same for Mastodon specifically too which but Ruby this time—with eventual consistency chewing up GiBs of storage making small players shut down instances. I would not be surprised tho if their Matrix server fell next just based on hosting cost.

Wanting to get folks off proprietary garbage like Slack, Telegram, & Discord was the right idea but moving to Matrix will prove to be a mistake as nodes are too expensive to run therefore leads to the centralization we need to escape. With the poor performance of the flagship Element client too, casual users think it is too damn slow (literally takes 2 minutes to even get to a screen with text in my browser & it isn’t even done syncing). There are more mature technologies with lower running costs that could have/should have/can be embraced.

SSB was killed after it sat behind an about:config flag, then their telemetry (that most power users disable) reported folks weren’t using. But what average users would be using a setting they would need to poke around to find. It’s a real shame too since I want to say it was PeppermintOS that was largely built around PWAs.

I literally used to say this last decade, but as I grew experienced with more languages/paradigms/systems, it became 3rd best, then 4th, until I realized it actually not really great at anything other than there is an large ecosystem around it (wildly varying in quality). To some that might be enough, & going outside what you know isn’t typically the most wise thing to do, but it’s not particularly simple, or readble, or performance, or composable, or offering great patterns. Anything that used Python in Nixpkgs tend to be the most unreliable software for actually building & using.

This is so true & unfortunately everyone keeps telling beginners to start at Python