We sort of do

Jimmy Buffett is dead

Very not solar punk, but very cool. Love the vibe of super dense living.

And then another, where a trans woman is called “spam.”

Pretty clear they meant the PR was spam, not the person.

And then another, where a trans woman is called “spam.”

With comments like this it’s clear the author is just overreacting. They were clearly calling the PR spam, not the person. (And this is coming from someone who was definitely angry with them for denying the original PRs and stuff.)

Then the problem is the schema being under specified. Take the classic pet store example. It says that the I’d is int64. https://petstore3.swagger.io/#/store/placeOrder

If some API is so underspecified that it just says “number” then I’d say the schema is wrong. If your JSON parser has no way of passing numbers as arbitrary length number types (like BigDecimal in Java) then that’s a problem with your parser.

I don’t think the truly truly extreme edge case of things like C not technically being able to simulate a truly infinite tape in a Turing machine is the sort of thing we need to worry about. I’m sure if the JSON object you’re parsing is some astronomically large series of nested objects that specifications might begin to fall apart too (things like the maximum amount of memory any specific processor can have being a finite amount), but that doesn’t mean the format is wrong.

And simply choosing to “use string instead” won’t solve any of these crazy hypotheticals.

Open washing, which is to say the proliferation of licenses that look FOSS if you squint but don’t work if you look closer, and practices related to these licenses. Here we have big players like Elastic, Redis, MongoDB, and numerous smaller cases as well. The practice of building off of the lavish advantages of being in the FOSS ecosystem, then pulling the rug and seeking exclusive commercial monopolization of the end result.

Someone help me understand why this is a problem. I am willing to accept that I’m missing something. As I see it,

1. Strong copyleft licenses like GPL attempt to put restrictions on what you can do with the software because of ways that corporations have exploited more permissively licensed FOSS projects.
2. Examples include the “TiVo” stuff in GPL v3 which forces users to not lock people into specific executables or AGPL which prevents a loop hole of wrapping GPL software in something to allow usage over a network and not be considered distributing.
3. Some FOSS advocates go so far as to call permissive licenses derogatory things like “cuck licenses” because of how they potentially allow corporations to exploit your work.
4. Mongo, Elastic, and now Redis felt exploited by companies and that AGPL (what I believe is generally accepted as the most restrictive FOSS license) was not restrictive enough to meet their needs and switched to SSPL. Mongo in particular was even already using AGPL.
5. The SSPL was rejected by the OSI because it allegedly discriminates against would-be SaaS providers which would violate OSD #6. I don’t see how that’s any more true than saying GPL v3 “discriminates against DVR manufacturers” because it had a clause specifically to combat what TiVo was doing or even saying AGPL “discriminates against SaaS providers” because it requires network use to be considered distribution (Google specifically warns against it).
6. AGPL closed a loop hole in GPL. That’s a fact. I don’t think that’s debatable. I believe SSPL is closing a loop hole in AGPL and I am confused why others disagree.
7. Mongo, Elastic, and Redis are available under the SSPL but the requirements are strict enough that no SaaS providers want to use them. They are also available under commercial licenses which lift those restrictions for a price. The goal of this is to allow the benefits of open source without being exploited. While people disagreeing with me about SSPL being FOSS might say that this is intended to make it difficult for SaaS providers, I’d point out that dual licensing is common and acceptable. Take Qt for example. You can either use Qt and be bound by GPL (which means it is difficult for you and you have to release some of your would-be proprietary code) or you can pay for a commercial license and not be bound by GPL.

So… My question is, what’s different about SSPL?

• Why is SSPL not considered FOSS while other restrictive licenses like AGPL and GPL v3 are?
• How are companies behind FOSS projects meant to prevent their code from being exploited by SaaS providers?
• Is there some hypothetical lesser version of SSPL that still captures the essence of it while still being more restrictive than AGPL that would prevent exploitation by SaaS providers?

and a pronoun selector.

Which is sort of silly because Discord profiles themselves have a place for pronouns and you can customize them per server (without needing to pay for anything unlike other per-server profile customizations). So, if anything, that shows that these servers are trying to be inclusive.

grumpy and meaningless bad takes all day every day

You don’t sound grumpy at all though lol

This is what I was getting at here https://programming.dev/comment/10849419 (although I had a typo and said big instead of bug). The problem is with the parser in those circumstances, not the serialization format or language.

Wrong. Try this next time. https://open.spotify.com/track/2ovqH6tbNeNPa2oQ9rGp9N The sequel lol.

Even Flow by Pearl Jam. It’s a blast and always gets a laugh when you make it a little goofy. The only hard part is the ~one minute guitar solo. But that’s a great time to throw in a “What’s up (local city)!? Having a good night!?”

Also it’s fun to sort of shout “I know you know the words!” near the start because Eddie Vedder (the lead singer) is difficult to understand.

Can you give a specific example? Might help me understand your point.

You know, it’s sort of an interesting thought. If China uses my PC as part of some bot net that would suck, but that’s probably the worst that would happen. In the US though, the three letter agencies could “disappear” me. Not that I’m worth disappearing, but… I highly doubt China would send agents after me unless I visited and I don’t really plan on it.

I worked at Equifax during the big breach. (I did not know about it beforehand.) One morning I was chatting with coworkers about stuff and they were talking about a crazy massive breach and how stuff would need to change. At some point I said something like “who got hit?” I hadn’t checked my email (or the news) yet.

But, to be honest, I think hearing it like that may have actually been best. Hearing in on the train on the way to work would’ve been scary.

Ugh, while I agree games have too much monetization nowadays, please don’t give TF2 a free pass. It paved the way for so much of what we see today.

Especially disgusting when people show up to vote, aren’t registered, are instructed to cast a provisional ballot, then are still faced with (potential) jail time for not being allowed to vote.

https://www.nbcnews.com/politics/elections/texas-womans-prison-sentence-attempting-vote-illegally-thrown-rcna145573 (Searched for a followup to this, looks like she didn’t receive jail time, thank goodness.)

What we really need to know is how to make possessive plurals of proper nouns that are plural but refer to a single thing.

Imagine a club called The Backstreets. Is it The Backstreetses’?

What about how to make plurals of proper nouns that are possessive? Like a restaurant called Your Grandparents’. Is it Your Grandparents’es? What about the possessive plural? AYour Grandparents’es’?

I (think, at least) the point they’re making is that unless the API contract specifically differentiates between “present and null” and “absent” then there is no difference. (Specifically for field values.)

Just what every programming language needs, not one, but two types of null! Because nobody ever said one type was difficult enough.

If I see any of you make this distinction matter for anything other than “PUT vs. PATCH” semantics I’m going to be very angry.