timw4mail

It's not like most the popular existing ones are really good (or feel good to use). They mostly have the benefit of momentum.

I almost think there's no way to make a good build system...without making it far harder when you need to do something slightly different. Rust has a simple build system, but it really depends on the package manager, and custom build setup is a build script in Rust...so the build system has to build the build script...

Last I checked (a month or 2 ago), Steam still works on Windows 7, but is unsupported.

...and you have to know those exist to find them.

You can't take OpenRC away from me!

It really is more related to Sturgeon's law (90% of everything is crap). My complaints are about that 90%, not the 10% that actually is done well.

The biggest offense to me (as a web developer, even) is the jank of js-rendered websites. This commonly means a blank, or (in slightly better cases) a skeleton page, which then often makes more network calls to get page content, which then *eventually* renders.

The 'build' tooling is terrible too, with layers of build-steps (due to incompatible code module types) that result in excessive script sizes. Due to the nature of Javascript, each byte is more computationally expensive than HTML or CSS.

TLDR: Websites are slower, and the fanciness doesn't add much.

Cyrix before the VIA buyout was competitive on integer performance.

VIA (via Centuar, the CPU design firm), focused on low-power, lower-performance chips. They only used Cyrix for the name, and not for very long.

That can't be the case, as the Zhaoxin CPUs have the same kinds of instructions as similar Intel chips, including those cross-licensed from AMD, like the 64bit instruction set.

I've played modern games on CRTs through HDMI->VGA convertors, and still felt lower latency than LCD. OLEDs will eventually catch up, I think, but LCDs are always going to have some lag.

And it's not the refresh rate, it's the time from input -> display picture updates. With a CRT that can happen during the current field being displayed, but it will take at least one frame for any LCD.

If there's one thing I hate above all else its those stupid scrolling auto-playing videos on news sites!

I'm trying to read text, the video pops on top, I scroll, it gets in the way again...aaughgh!

IBM had at least two computers that used this concept: The PCJr, and the IBM Convertible "laptop".

One of the many problems with sidecars is that they make the computer footprint larger. While it hypothetically allows for unlimited expansion compared to a limited number of internal slots, this would be practically limited by physical space and electrical signaling issues.

It really is that simple.

Food and drink are allowed in the cockpit, especially for longer flights.

Even LaserDiscs, which are probably the format most prone to "laser rot" are mostly fine.

Laser rot is kind of a non-issue: it's generally down to manufacturing defects.

Except most of that stuff in Free Pascal doesn't really have documentation.

The first point is kind of silly: You can make rust-style constructor functions if you want, and have a private constructor to enforce the behavior.

Although it does require some boilerplate, which may seem like pointless extra work.

I use Firefox, but I still want more browser engine diversity. Blink and Webkit have a significant shared ancestry, and the only other major one is Gecko.

The library API itself might be stable, but the ecosystem is not. And that ecosystem has vulnerable libraries that should be updated.

And that's not even going into using a big component library, like Material UI, which might be its own nightmare.

This is something I've dealt with a lot personally, and I've made a good attempt to avoid unnecessary 3rd-party dependencies. But the huge churn continues in the build tooling, testing, linting, etc.

Most web standards are codifying existing functionality, not the other way around.

Chrome/Blink has exclusive APIs, that often are not on track to be a standard.

This makes Safari (Webkit) and Firefox (Gecko) look bad, because they end up having to implement the same APIs, and then, maybe, it's standardized. Browser extension APIs come to mind.

I wish the situation was more neat and tidy, but it's not.

I'm still surprised how many freeways are asphalt, when it leads to road construction and lane closures every few years.

Asphalt can be recycled, though. It's more reusable than basically any other option, and I doubt it will disappear any time soon.

Concrete is a more realistic replacement, although it has some of the same disadvantages.

Pavers are not practical on anything but low-traffic, pedestrian, historical, or vanity roads.

The idea is to enter in the Manufacturer name, and it auto-completes. The list is absurdly long to load directly.

Non-Cherry-compatible switches don't get enough love. But then again, most have been out of production for 20-30 years.

The distance is larger than you think, but it is spread over a lot of pins. Most of the pins on a CPU are for power and ground.

Low-end cards have historically had lower-end GRAM.

Plus, graphics-oriented RAM is just optimized differently: for bandwidth at the expense of latency.

I would still fly on a 737 MAX.

I've read about (and watched the Mayday episode) about dozens of air disasters. You can't be 100% safe, but I don't think the MAX is that much riskier either.

Cash App Taxes. Free federal and state.

They didn't have disc brakes in 1935.

Hypermiling in a gas car is my driving game.