Dragory

[1] https://github.com/js-temporal/proposal-temporal-v2/issues/5

That said, the article does indeed seem to focus entirely on dependencies.

I have lots of music that is not available on streaming services, so being able to upload and stream songs is a must for me. Spotify only offers syncing between devices which is definitely not the same.

For anything more complex, I agree. But for the common case of fetching simple and often (depending on your project) nested relations, I definitely enjoy the abstraction provided by ORMs.

For me, being able to load relationships (and especially nested relationships) with little boilerplate and few queries is probably the most useful feature in an ORM (usually explicitly eager-loaded), so I'm sad to see it's not supported.

As far as date formats go, apart from the ISO format, "21 Jul 2020" is definitely my favorite and always unambiguous. The only downside is that it's language dependent.

I don't know about this one. For example, I'm not going to invite every one of our clients to our Slack as a single-channel guest, nor am I going to be joining their Slack workspaces (if any of them even have one - most of them are in the Microsoft ecosystem). I'm also not going to do that with every vendor I'm in contact with, and so on — email is much more convenient. That being said, most of our internal communication within the company is on Slack, but that's a small slice of what emails are used for.

That being said, the commenter above them could've also been referring to old old JavaScript where no transpilation is needed to reach practically every target environment.

When the margin works, the logic makes sense. 50vw sets the padding of the side in question (e.g. left) to the middle of the screen, 50% subtracts half of the containing element's width (<body>) from it. Doing this for both left and right and then negating it with equal negative margins results in the content area in the header being centered and having the same width as body, but the padding stretching out to the edges of the window.

These are not the only two options. What about multiple authorities, but not random individual developers? That's basically how it works with e.g. game stores on PC (though Steam is certainly the largest), or package repositories on Linux.

Like you, I like being able to trust an authority to vet the software I install rather than having to judge the trustworthiness of each individual developer, but I'm not a fan of there only being one authority by design (as it is on e.g. iOS). It introduces a single point of failure and gives that authority full control over all software on that platform - for better or worse. Many package managers specifically deal with the issue of consolidating updates to a single system while not relying on a single authority.

Unless we completely abandon small font sizes or switch exclusively to high-dpi screens (will likely happen eventually, but we're not there yet), subpixel AA can look much sharper than grayscale AA if properly configured and you're not sensitive to the color fringes (personally, sitting at about an arm's length from my monitor, I don't notice them at all). And I'd rather not have text rendering quality suddenly downgraded on my existing peripherals before that happens.

I might be wrong, but with WebRender, isn't scrolling now done asynchronously so it doesn't stutter while things are loading? I certainly haven't experienced any scroll stutter since I turned it on.