Just because the code is described as part of the WebDAV spec doesn't mean it's WebDAV-specific! Status codes are supposed to be generic.

Just because a movie is what people call "cliche", doesn't mean its inherently bad.

Just because you can create a plugin for any tool and manage its versions with asdf, does not mean that is the best course of action for that specific tool.

Calling a software convention "pretty 90s" somewhat undermines your position. Quite a lot of well-designed software components are older than that. If something is problematic, it would be more useful to argue its faults. When someone cites age to justify change, I usually find that they're inexperienced and don't fully understand the issues or how their proposed change would impact other people.

'...ee' is usually paired with an '..er', isn't it? Employee/Employer, Trainee/Trainer. I wouldn't use Coachee because to me, it implies you're a Coacher, not a Coach.

When mocking is deemed profitable:

Although echo "$@" prints the arguments with spaces in between, that's due to echo: it prints its arguments with spaces as separators.

Those sorts of complaints are like saying that someone is not a buddhist unless they speak Pali.

That such minimalism is possible does not mean that it is necessarily desirable

If you teach your users to trust that URL bar is supposed to not change when they click links (e.g. your site uses a big iframe with all the actual content), then the users will not notice anything in the future either in case of actual security vulnerability.

The point is, just because you don’t see it, doesn’t mean it’s not happening. It’s been more than two years and as far as I know, no one has ever noticed one of my requests. Maybe it’s been in your site this whole time

This is Sass based, and therefore doesn't require Svelte components

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

However, that really doesn't mean we should expose everything else in JSON too...

There are other features you *could* actually polyfill, such as Array.of, Number.isNaN or Object.assign, because those don’t introduce syntax changes to the language – except that you shouldn’t.

Although I’m trying to make a case against logic-less templates, that does not mean that I am advocating the other extreme