SebastianKra

I'm one of those. Excel's ease of use isn't relevant if you already know how to use Python / Jupyter / DuckDB / whatever.

The mental model of describing a series of reproducible transformations on normalized tables is more intuitive to me.

Excel lets you do too many things. As a result, I mostly see spreadsheets that aren't much more machine-parsanle than a word document.

We had to write a score-table at a party lately, and a while ago, and I managed to get it working with DataSpell faster, than it took us to figure out how Google Sheets stupid date-parsing works.

Explorer has

- no columns view

- no quick look

- freezes for 5 seconds when you accidentally drag over a disconnected network location

- when opening a files, doesn't let you drag in an file to select it.

- no shortcut for toggling hidden files

- no tabs until Win 11

- no tags

- no sorting by "date added"

This was mostly a check for myself to see if I had Stockholm syndrome. But I keep finding more reasons to prefer Finder.

I agree, but it's not that easy.

All UI's should be tab-able, but that's still a miserable experience for keyboard users. A keyboard-centric UI must provide instantly discoverable shortcuts. Possible methods:

- Put all elements on a grid so that they can be navigable with the keyboard. This is a significant restriction for the designer.

- Put keyboard shortcuts next to every button. It's not enough to put them in tooltips (*cough* Raycast). Common in games, but wastes space.

- Add a Command Palette. This is the easiest, but it requires mirroring every action, and is suboptimal when you have the same action for each item in a set.

When designing for technical users: all of the above please. But for average users it's less clear. I think there's still room for innovation, both on the software architecture and the UI side.

This may have been handwaved in the past, because config files don't take that much storage.

But Sequoia and up have strict management of background agents in "Settings / Login Items".

It fills up with so many broken references, duplicate entries, etc... I have no idea how a normal user is supposed to remove trash from that list. I pointed an agent at it, asking it to remove any broken references.

I agree that all of this is bikeshedding, but the cascade complaint is actually real.

It's so common, that there is an expensive runtime package, `tailwind-merge`, that is used by default in the most popular component library.

Are you suggesting to style the tag name directly? Because that would create chaos in a codebase. <button> is for semantics. It's possible that other design system components need the same semantic element.

When I walk around my increasingly billboard-infested hometown. I observe that almost every ad actually nudges me in some way: whether I should switch internet providers, whether my financial strategy is fine, what kind of scam this tabloid newspaper is running, etc...

I believe most people are influenced by these constant micro-impressions far more than they realize.

My best defense is to build a resentment towards the companies being advertised.

Standard practice in every decent frontend framework has been to create a component, that wraps the <button> without rendering its own dom node. This avoids the typical downsides of inheritance.

Can we not just do `:host { display: contents }` and use the same approach?

1. You can download & install PWAs for offline use too.

2. This isn't true for apps anymore. Server driven ui is a thing.

3. JS runs locally. You can inspect the network traffic more easily than you can with an app.

4. You can audit OSS websites too.

5. Your personal preferences have nothing to do with the fact that Apple makes tons of money from apps but not websites.

Whenever I'm bored, I go to the ant-design site to see how long it takes to find the first gross accessibility violation. This time it was the dropdown just above the fold, which wasn't keyboard controllable.

It's a combination of two things that never should have been normalized:

- Steam forces game updates, even for single player games.

- terrible delta updates. Baldurs Gate 3 had 8 patches in 3 Years. That's 800GB of updates.

If a patch drops on the afternoon you planned with your friends, you're not playing that night (actually happened to us). Both decisions should have caused outcries, but I guess people would rather overpay for fast internet contracts.

I wonder what you're doing that you need to type it so often. I almost never use it in application code (outside of tests and generic utilities).

There are some techniques that aren't immediately obvious. Look into...

- type guards

- pushing constraints up: `function print(i: Invoice & { issueDate: string })` is better than `assert(i.issueDate)`

- discriminated unions

Depends on the app, but mostly they're better than in the past.