Chromium had it behind a flag for a while, but if there were security or serious enough performance concerns then it would make sense to remove it and wait for the jpeg-xl encoder/decoder situation to change.

It baffles me that someone large enough hasn't gone out of their way to make a decoder for chromium.

The video streaming services have done a lot of work to switch users to better formats to reduce their own costs.

If a CDN doesn't add it to chromium within the next 3 years, I'll be seriously questioning their judgement.

No one's asking nor wondering why you find looking at things in the sky beautiful.

They're asking why you're ascribing meaning to an arbitrary number of days. Months aren't subjective, they're arbitrary.

I use git log --graph --all --remotes --oneline whenever I need to shell into another computer, but it's still too barebones for regular use.

What specifically do you think is legacy in that comparison? The coloring? The horizontal layout? The whitespace?

Note: I've changed the first link from https://github.com/cxli233/FriendsDontLetFriends/network to https://github.com/zed-industries/zed/network. Still the same view, but just a different repo to highlight the problems

1. It's in a small non-responsive box
2. Ridiculous spacing

• If you want to see the commit messages, you either need to hover over a dot which increases visual scanning durations or you need to go to the commits view which only shows the commits on a single branch

3. It doesn't show commit messages
4. It's scrolling horizontally
5. Branches cannot be collapsed
6. Branches cannot be hidden/ignored
7. No way to search for commits
8. No way to select multiple commits

• Which also means no way to diff any specific commits together
• And there's also no way to perform an action over a range of commits
• And there's also no way to start a merge/merge-request/pull-request/etc... between two commits

9. No way to sort by date/topologically
10. Keyboard controls only moves view instead of selecting commits

I'll stop here at 10 reasons (or more if you count the dot points), otherwise I'll be here all day.

The network view lays out forks and their branches, not only [local]/[local+1-remote] branches.

Yes, but the others can do that while still being usable.

I don’t know what IDE that miro screenshot is from. [...]

It's gitkraken

[...] But I see it as wasteful and confusing. The author initials are useless and wasteful, picking away focus. The branch labels are far off from the branch heads. [...]

The picture doesn't do it justice, it's not a picture, it's an interactive view.

You can resize things, show/hide columns, filter values in columns to only show commits with certain info (e.g. Ignore all dependabot commits), etc... Here's an example video.

[...]The coloring seems confusing.

You can customise all that if you want.

The windows 11 teams runs better, but if you're using a school or work account, you need to use the old AngularJS+Electron version, or the new React+Webview2 version.

So for the time being, the Windows 11 teams is more catered for personal use only. It's kind of like a modern reboot of Microsoft's old MSN Messenger. It was included in Windows 11 (rebranded as "Chat") but it's been unbundled from Windows 11 installs and I think rebranded again. But not having the school/work account support means not a lot of people use it.

The transition between the AngularJS+Electron version and the React+Webview2 versions is happening now. At some point soon, anyone who is running an OS too old to run the new teams will be forced to use the browser version.

So after their transition, we'll have to wait and see if they add the school/work account support to the native version because everyone using teams right now only uses those accounts.

Theo had a great video on this, and went through why jquery is still important for the internet (besides the older and/or inexperienced who use it):

https://www.youtube.com/watch?v=1bZYmpOOC8U

How would you mark a flag in your json settings file as deprecated?

DOM attributes are built for browsers and frameworks to take advantage of.

The style of some of those frameworks to stick symbols in there is downright weird. But that only goes against those particular frameworks. It doesn't impact how good DOM attributes actually are.

What about OkLCH?

Yeah, the obvious way would be to draw the text on a canvas, but you wouldn't get sharp text then.

I could nest a span with a negative translate or negative margin to overlap. It could be worth it to print each letter in a css grid (which would work since all the text is monospace) making it super easy to overlap text.

There may be a more hacky/elegant solution which would be to use weird unicode to overlap characters, but I'm not sure how feasible it would be.

I wonder if they’re lying about this. Maybe the fans are super loud or something and they didn’t want the reporter to know.

That's far too conspiratorial for me. Loud fans in an engineering sample aren't a reason to break a fan.

A fast fan blade on a laptop would snap easily if it was handled, which is exactly what would be happening on both a laptop where assembling and disassembling it is a feature and a laptop being actively tested.

If it was a blade that broke, that wouldn't stop the fan from working, so it was probably the servo, power, or bearings which is exactly what you'd expect to find broken in an engineering sample. Why? Because engineering samples almost always have issues in them. That's the whole point of the samples, to find out what the issues are so they can be fixed before mass manufacture.

What are you doing that makes having 64gb ram useful?