it_depends_man

I don't think that there is an obligation with that kind of standard, no.

Banking and security, accessibility yes.

Specific choice of "user side software", probably not. And it's somewhat unlikely to happen too, because if you think about apps on phones, if suddenly a completely new phone OS were to show up and had 30% market share, it wouldn't make sense to have a law that would legally require them to offer an app on that platform

And Chrome isn't "officially bad" in a legal sense.

The internet standards themselves are a bit... imprecise too. Implementing them in browser is ultimately up to the companies, there is no legal body requiring a browser to have or not have features. They just usually sort of do the same things because going different paths would be stupid. Mostly. Sometimes they totally do that, though, e.g. calendars and contact info have a standard, but all implementations are a mess and transfer is a pain.

When things collide, they transfer their movement energy. If things collide like this >- They will continue in roughly the same direction. If they collide like this -> <- their movement will cancel out and they will fall into the sun.

Satistically, at the "beginning of time", in a random sphere around the sun, things will not be completely the same. So everything will either collide and fall. Or it will collide and continue in roughly the same direction. What we have now are the leftovers that were moving in roughly the same direction and colliding so little that they didn't fall into the sun because of that.

The same is true for the "disk": If you start with a roughly evenly distributed sphere of gases or something, there is a middle somewhere where there is a little bit more mass than anywhere else. That's where things will go.

It's not that they are unfriendly.

But they are 100% there to represent the company's interest and not yours. If there is any way, to... turn a situation into something where the company gets more money out of it and you get less, it's their job to make that happen.

In theory they should have employee retention in mind. In practice, nobody does their HR that way anymore.

All my interactions with HR have been "professional polite" and appropriately friendly. There is no reason to be unnecessarily mean, they are also just doing their job.

Some kind of general fitness testing?

You know, involving heart, lung capacity, performance?

Käpt'n Blaubär der Film is in German

but it's a bit culture specific. German children TV has a pretty long running show that does "how it's made" for children + small, probably only 5 minute animated stuff and at the end a puppet/animated show of this old bear telling his grandchildren weird made up stories that he claims are totally true.

Obviously this is feature length. So in this movie, his old archrival shows up, and kidnaps the kids. Grandpa has to roll up his sleeves, and go save them. And of course do wild stuff that sounds totally made up when he tries to tell the kids later.

It's wacky entertainment in the best way.

https://www.imdb.com/title/tt0215919/

That's a ridiculous take.

Cool article about bath houses though.

My bet would be that it would be easier to relocate every major city in the sub tropics and further, into the tropics where the solar energy is available, than to convince people to give up hot water at home.

We won't do either.

All the ones where the idea was to "just start something, grow grow grow, then figure out monetization later" is wild to me.

E.g. reddit. It worked. CEO is rich, site is still online. Somehow they got investors probably, presumably.

I get not having profit. I get not having income, if it's in some prototype phase. But having no plan or idea whatsoever for how to monetize and still getting VC? Wild.

I had a phase as a teen when I was constantly swearing. My parents told me that, it can't be that bad and it's really annoying.

And it's mostly an impulse reaction and we're kind of above that.

It doesn't mean that you can't express pain or anger. You're just not insulting people's ears if you scream "Aaaaah" when you bang your toe against a table leg or something. And your environment really doesn't deserve it. Most people are somewhat compassionate and you're just swearing while they try to help... that's not a pleasant environment for them to be in. It makes it harder to help you.

No to both questions. I just made a change and that was it. And it has never stopped me from expressing anything.

If anything, it lends more weight to the regular words.

A _______ criminal? Or a criminal?

You can still put the same emotion into the words, they're just not swear words. :)

Having an easy on the eyes markdown that is also easy to parse would be cool.

But YAML does these things:

https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell

which are not excusable, for any reason.

I'm not sure now that I think about it, but I find this more explicit and somehow more free than json. Which can't be true, since you can just

{"anything you want":{...}}

But still, this:

<my_custom_tag>
<this> 
<that>
<roflmao>
...

is all valid.

You can more closely approximate the logical structure of whatever you're doing without leaving the internal logic of the... syntax?

<car>
<tyre> air, <valve>closed</valve>  </tyre>
<tyre> air, <valve>closed</valve>  </tyre>
<tyre>      <valve>open</valve>  </tyre>
<tyre> air, <valve>closed</valve>  </tyre>
</car>

Maybe I just like the idea of a closing tag being very specific about what it is that is being closed (?). I guess I'm really not sure, but it does feel nicer to my brain to have starting and closing tags and distinguishing between what is structure, what is data, what is inside where.

My peeve with json is that... it doesn't properly distinguish between strings that happen to be a number and "numbers" resulting in:

myinput = {"1":"Hello",1:"Hello"}
tempjson = json.dumps(myinput)
output = json.loads(tempjson)
print(output)
>>>{'1': 'Hello'}

in python.

I actually don't like the attributes in xml, I think it would be better if it was mandatory that they were also just more tagged elements inside the others, and that the "validity" of a piece of xml being a certain object would depend entirely on parsing correctly or not.

I particularly hate the idea of attributes in svg, and even more particularly the way they defined paths.

https://developer.mozilla.org/en-US/docs/Web/SVG/Tutorial/Paths#curve_commands

It works, but I consider that truly ugly. And also I don't understand because it would have been trivial to do something like this:

<path><element>data</element><element>data</element></path>

YAML

To each their own indeed.

;)

It is very cool, specifically as a human readable mark down / data format.

The fact that you can make anything a tag and it's going to be valid and you can nest stuff, is amazing.

But with a niche use case.

Clearly the tags waste space if you're actually saving them all the time.

Good format to compress though...