TerrorBite

@LainTrain That would be @soatok@furry.engineer. The blog itself is also federated at @soatok@soatok.blog

[tagging @vzq @programming for Mastodon->Lemmy federation]

@Lynxtickler ahh, I misunderstood what you were referring to. Didn't realise you were talking about JSON Schema and not the JSON syntax itself.

It's the other way around. The YAML schema supports JSON because YAML was designed as a superset of JSON.

@Lynxtickler @canpolat

@trk Coming from Mastodon, I have already learnt that it's not worth putting up with the negatives just to get a few extra users.

@Zagorath

Oh absolutely. I can think of several situations where that wouldn't work well or at all, for example, a switch statement that sets up variables to be used in the rest of the function.

@zib @UnRelatedBurner @programming

Also, good luck using switch without any breaks, but I'm guessing that's not quite what your teacher had in mind.

The teacher, probably: “You must always put a switch in its own function! Then use return at the end of each case.”

@zib @UnRelatedBurner @programming

@mike@thecanadian.social @tchambers@indieweb.social Those already on there (and not already paying) won't be affected, it sounds like it's only going to affect new users. The stated intent is to stop spambots by requiring a valid payment before you can tweet. Though I would not be surprised if they force some existing users to pay if they "exhibit bot-like behaviour" (i.e. if they say something critical about Overlord Elon).

@btaf45 tagging @programming so that this federates properly from Mastodon to Lemmy

@nous That's a good way of putting it!

@btaf45 in my case, we as a team could have done that, because we didn't have management dictating how we did anything. It was our choice to do what worked for us, and it was a valuable tool for dealing with whatever got thrown at us.

Now I'm working in a different place that dictates Agile and Scrum to be done Their Way, on top of a project that's largely waterfall-like to begin with, and I'm starting to see why people say it doesn't work.

It works, BUT, only when you're using it as the right tool for the right job and not when management decide to misapply it as a hot new planning methodology.

@btaf45 @mspencer712 The whole point of Scrum is to use the retrospective to stop doing what doesn't work and start doing what does.

At one point, when my team's workload changed to less-timeboxable work, we threw out the entire concept of sprints and just used kanban instead, and stayed like that for a year. We still did retrospectives on the old sprint cadence though.

@verdare @lysdexic they are, but you have to be an enterprise customer.

https://ubuntu.com/blog/real-time-ubuntu-is-now-generally-available

https://learn.microsoft.com/en-us/windows/iot/iot-enterprise/soft-real-time/soft-real-time

RTOS are not going to become consumer operating systems, because there's too much value in selling it as a capability to enterprise customers (who are largely the consumers who REQUIRE a RTOS, rather than it merely being a convenience).