scottlamb

I agree: there is no precise, objective way to compare the utility of two arbitrary wealth distributions, and redistribution does not always maximize the total well-being of society.

Yet I assert it's useful to ask if the status quo—one person has >$1T and many others don't have enough for basic needs like shelter, medicine, and food—is optimal or if it'd be better to redistribute some of this.

* We don't need the ability to quantify or rank all wealth distributions, just compare some of immediate relevance. That's much easier, in the same way that even though the halting problem is undecidable, we can prove some realistic program A will halt and some realistic program B may not.

* We don't need objectivity. Democracies decide many subjective things by majority vote (sometimes 2/3rds or whatever), directly or through representatives. I don't always agree with the outcome, but it's the system we have here in the US/California, and I assert it's better than a dictatorship or requiring 100% consensus to take any action.

> The people behind wealth taxes generally handwave explaining how their system will be better at allocating than the people who make a living of allocating wealth effectively because it is all just obvious that it doesn't need to be justified. Poor people will get more money if rich people have less, duh, QED.

Even your straw man version of this argument is pretty convincing to me alongside graphs showing the extent to which our inequality is growing. https://inequality.org/facts/wealth-inequality/ see the "The Top .01% Don't Pay Their Fair Share as They Hoard More Wealth" graph in particular.

This is more a disagreement of values than facts, I think. Some people see the richest man's net worth go from $100B to >$1T and think he deserves that for starting these companies, and taking any of it from him is class warfare. Others think that rich people's pissing contests and lifestyles would be essentially the same if their wealth capped out at say $100B instead, we're morally obligated to use that money to try to meet Americans' basic needs, and using other's taxpayer dollars to allow him to reach those heights (see <https://en.wikipedia.org/wiki/You_didn%27t_build_that>) is class warfare.

High marginal income taxes (it was 91% in 1963, 70% until 1981, there's your compelling case where they turned out to be right, inequality was not growing then like it is now) or a wealth tax are not the same as Soviet style socialism. They still give an incentive for entrepreneurs, innovators, and hard workers.

> The annual turnover for e.g. Apple stock is ~0.4%, so a 0.8%/year wealth tax would triple the number of sellers without adding any new buyers.

Is that assuming the tax money is going into the void? I agree it might force roughly 0.8% of shares to be sold in a given year. But as to not adding any new buyers: no one's being forced to buy stock in the same way, but shouldn't someone be getting the money and potentially using it to buy Apple stock?

Let's imagine for a second the wealth tax money is simply given to people who are below the threshold. Most of them may waste it on silly things like food and rent, but some might end up with a surplus and become investors. Same effect if say the income tax is lowered to make the wealth tax revenue-neutral. Or if say it's used to expand Medicare. It's hard to for me to imagine a way to spend taxes that doesn't help someone. Even if the money is used on war—a net destruction of value and lives—there are some people selling missiles better off a result.

Well, I qualified with "here in California", and I don't know if that's where tancop lives.

I think the current situation is not great, but I'd want to fix it by investigating why we're seemingly unable/unwilling to impose the punishment currently on the books. I think it would be plenty if we did—to me, more than six months jail time for stealing <$950 would be excessive. We could increase the fines and decrease / take away the jail option, but does it matter? It's not happening anyway.

> What do you think the chances of being caught shoplifting is? If it's less than 50-33%, then you have the same problem as the OP where it makes sense to shoplift.

Don't we already? Police and DAs at least here in California are not serious about punishing shoplifters AFAICT. I hear people say this is specifically because of the 2014 Proposition 47 (raising the threshold for felony theft from $400 to $950). Not sure that's true (misdemeanor theft can still be punished by up to six months of jail time and/or up to a $1,000 fine, and California's current thresholds are similar to other states) but there was a federal mandate to address prison overcrowding, and California chose to do that by not having as many prisoners instead of building a ton more prisons. Prop 47, and perhaps some policy changes made with far less fanfare, were intended to achieve that.

There's still more deterrent for misdemeanor shoplifting than for nationwide egg price-fixing though!

> I'd love to look into the Quick Access placement. It is supposed to appear on all spaces and sets an NSWindow property to do so. Is there anything particular that you think triggers it (multi-monitor, full screen apps, etc)?

Thanks! I haven't seen it in a while, so maybe it's been fixed by either a 1Password or macOS update or is specific to a setting I since changed. But I'll keep my eyes out for if it happens again. I do have a multi-monitor setup.

I do see right now that if I'm on a full-screen app, 1Password's quick access window doesn't show up; if I move to the next space over I see it for a moment and then it disappears. In contrast, Spotlight search will actually pop up directly over my full-screen app, though knowing Apple they could be using some private API for this behavior.

> These are tiny paper cuts that add up to pain, like the ones you mentioned that affect me/a tiny portion of the user base so they aren't worth fixing. Is the justification I'm sure that's being made.

I think it's not only that but also that making site-specific changes (as I did with a TamperMonkey script) is fragile and could get them into trouble if their changes do the wrong thing (immediately for everyone, for some users, or after some site change). Might be better from their perspective to honor the site's stated intent even if that intent is questionable. In my top example, the "password" field actually is a password if the user hasn't enabled 2FA, so the changes I made wouldn't work for 1Password to apply to everyone. They could detect the label "PIN + Token" to gate it, but what if that text changes in a redesign or is sometimes localized into another language? and so on.

In the broadest sense, I agree there are big UX problems, but how much should we expect the password manager to do unilaterally? fwiw even when a bunch of players got together to make broader changes, we ended up with passkeys, which are far from perfect in many ways. (The flows about scanning a QR code from one device to another, without necessarily even knowing which device has a working passkey for that site... the simultaneous confusing offers of different ways of signing in... try talking your vision-impaired father through that over the phone.)

> if the editor is on a different workspace on mac you have to go to the application space/desktop than three finger swipe back to the browser space/desktop and then back to the application space/desktop and then back-and-forth to fill in four different security questions.

Yeah, that sounds similar to my own complaint about quick access opening on the wrong Space, just applied to the main window instead. And of course when you have to use the security questions something else has gone really wrong, like the main password having changed on the site without having changed in your password manager.

* One way I've seen this is when people have overlapped usage in two different password managers (1Password vs either Google Passwords or Apple Passwords). They have import and export (except for passkeys), but it'd be nice if they had an incremental version to help you get out of this mess if you weren't disciplined in switching over all at once.

* Another is that when you change the site's password even while using the password manager, the actual site change and recording it in the password manager's database is hardly transactional. You can click the password manager's update pop-up even if it failed, or not notice it even if it succeeded. Again not really sure how they would address this unilaterally.

> I just hit one. Creating a new document in 1Password, the name of the document isn't preselected, so I have to hit delete to name it. Lots of little tiny shit like that.

Yeah, that's 100% on them.

Can you give me an example of a UX problem that you attribute to the password manager? That'd help me understand.

I often hit problems with 1Password's autofill on particular websites, but by and large I blame the website. Few examples:

* one website expects me to type the PIN then a Symantec VIP OTP token into a single field called "password". That's a (possibly deliberately) password manager-hostile design. I finally got annoyed with it enough to use an open source project called `python-vipaccess` to create a proper `otpauth://totp/...` URL I could add into 1Password and wrote a TamperMonkey script that added separate autofillable fields that would get concatenated automatically. Now 1Password works fine.

* frequently websites will complain about needing a valid credit card number after autofill. I have to go to the field, delete the last digit, add it back, tab away, then it works. I think they have just used the wrong event handlers and never tested it with autofill.

* they often will skip `autocomplete="new-password"` attributes, so my password manager will look for a (nonexistent) current password rather than prompting me for a new one, and/or they won't have the username and new password fields ever in the DOM at the same time so the password manager doesn't save it properly. (Even if it makes sense in terms of user-visible flow to do these in sequence, they can still leave the username in as a hidden form element for the benefit of the password manager.)

I've also hit UX problems in 1Password itself, for example the "quick access" pop-up doesn't reliably appear on the current Space in macOS. (Confusing and annoying to have to switch to another to see it.) But they seem less common.

ceejayoz> You want to let every merchant I swipe my card at know my age? To improve privacy?

Remember the site guidelines:

SG> Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize.

The obvious solution is instead of "every transaction comes with the user's birthday", the vendor can in some way set a minimum age enum of say (13, 15, 18, 21, 25) — a handful of ages that are significant with respect to some law or regulation. Then the transaction succeeds or fails.

As I understand it, Hawaii had environmental concerns with ferries (requiring a review that was never completed), specifically whale/ship strikes and the risk of car-carrying ferries transporting invasive species between the islands. [1] I'm unsure if other islands would have similar concerns about cargo ships or not or if the environmental review would have been satisfactory if they'd just done it on time.

I'd expect ferries and/or small cargo ships to be an attractive option if allowed.

[1] https://en.wikipedia.org/wiki/Hawaii_Superferry

I don't think people are upvoting this for the fact at the top of "say something surprising" [1], but it indeed surprised me:

> I can write 500MB/s to a hard drive? that's so much!

Turns out a Seagate 2X18 can write at 528 MiB/s according to its spec sheet. [2] My rule of thumb was that HDDs could do like 100MB/s (aka 800 Mbps) but I guess between density improvements and this new "dual-actuator" class, it's gotten a lot faster. HDD seek time has basically been stuck for 30+ years and probably will remain so but capacity has increased a lot, and the throughput for sequential access probably should scale with capacity [edit: times rpm, thanks Retr0id]. For a while I think it wasn't increasing, but I guess they decided to fix that?

SSDs of course can do way more than 500 MB/s, and you can do better by compressing as you write (depending on your data), and you can stripe across multiple HDDs, but it turns out none of those are necessary.

[1] as I write this, the title "no feigning surprise" suggests <https://wizardzines.com/comics/no-feigning-surprise/> but the link points to "say something surprising" <https://wizardzines.com/comics/surprise/>.

[2] https://www.seagate.com/www-content/datasheets/pdfs/exos-2x1...

> Or is this a building permitting issue where for some reason the bureaucracy surrounding a permanent structure is expected to drag on for years but somehow they got the tents permitted rapidly?

Good point; some permit loophole might make sense.

It occurs to me this also could still turn out to be a giant failure: these may all still be unpowered, empty tents. They might end up taking two to three years to turn on, might never get a critical permit at all, etc. I'm vaguely recalling some story from Google's past. They had an experimental datacenter (`pq` maybe?) built out of shipping containers. There was some way they had hoped this would be cheaper that (iirc) didn't work out at all because the local fire marshal declared each shipping container to be a full structure and thus an unexpected set of regulations applied. and/or each may also have been required to have an emergency power-off button for the entire facility, which were hit by accident more than one might hope. They never built a second datacenter with that design.

Also remembering that for a long while Google's Dalles, Oregon site had building 1, building 3, and an empty concrete slab between them called building 2. I suppose Meta could have done something similar and had the slabs ready to go long ago.

That makes sense. Although I have to pick on your example a bit: wouldn't they still need a concrete foundation for all that weight and thus still need bulldozers? Still unsure how much of the work they're actually avoiding.

Meta's first five buildings took between two and three years to build, but Williams is almost done building out 200 MW (additional) off-grid power plants in a year, and to match that they're putting their equipment in tents. That raises questions for me:

* Did they expect the next five buildings to also take between two and three years to build if done in the same manner? I'd hope it'd be significantly faster the second time because they've perfected the design, found good local contractors and suppliers, etc.

* How much of the time was the actual structure vs. all the stuff inside they still have to do with the tents?

* How long are they expecting to keep this? Are they anticipating extra problems like leaking roofs?

* What are the "off-grid power plants"? Is this basically a whole bunch of diesel or natural gas generators? [edit: oh, yes, "The site is also powered by 200 megawatts of modular gas turbines". I wonder if they're trucking in the fuel too.] If so, yuck.

I'm typing on a SoflePLUS2 right now. It's based on the Sofle v2 design, which is described as having a 5-key thumb arc per side. But I try to limit thumb use to the innermost 2 or 3 keys per side after experiencing fatigue. I use the outermost 2 or 3 as opposite-hand modifiers (ctrl, opt, cmd) and try to pull my whole arm in to use them with the same-column finger, instead of treating them as a thumb key that requires folding my thumb underneath my palm as I keep my hand in the home position.

It seems like many in the ergo keyboard crowd are trying to never move their hands from the home position, and I think that might be a mistake. Use a variety of muscles, avoid unnatural positions. More broadly, my understanding is that the research behind using a tented/splayed split keyboard is solid (better shoulder through wrist positioning) but there's nothing really but anecdotal experience supporting the idea that vastly reduced key counts (and associated need for complex layer setups) or column-staggered layouts reduce pain and plenty of confounders (going from unibody to split simultaneously, maybe switching from QWERTY at the same time too, reducing speed, often learning decent form for the first time, often regression to the mean because people switch when they are having problems).

My previous keyboard was a split with traditional row stagger (Goldtouch) that Google's ergo team advised me to try forever ago. I switched recently because I wasn't liking the mushy feel of the keys, that the two "space bars" weren't distinguishable, that it doesn't have an integrated pointing device, and that after such long use I'd worn down the homing indicator on the f/j keys and was struggling to orient my hands correctly. But row-staggered layout was fine IMHO. Made it easier to learn, to switch between it and other keyboards when I had to, and to hit keys further from the home position.

Here's something from Kinesis, who have been designing split ergonomic keyboards for a long time: https://kinesis-ergo.com/wp-content/uploads/Advantage360-ZMK... search for "If your thumbs are sensitive" and "Guidelines for using your thumbs". And note that while they have keys under z/x/c they do not describe them as thumb keys.

Totally agree. They even vibe-wrote the paragraph I quoted.

I'd go so far as to say people who prompt AI to do something they can't do themselves are essentially non-technical management. I'm not a fan of non-technical managers of humans and similarly not a fan of this approach to AI either when quality really matters. (IMHO it's actually great for prototyping.)

The idea you can only learn to prompt well if you learned prompting before learning how to do the work yourself is strange, maybe even completely backwards. I've never heard teachers say to learn how to do math with a calculator then memorize multiplication facts later. Or anyone say the best managers are ones who first started in management and then developed technical expertise. Why are they so committed to the idea that this skill is so different than all the others?

It's probably a very convenient fantasy though for management types to think these expensive later-career people are useless or even harmful. And maybe said managers are non-technical themselves and don't understand the problems this creates.

I think the distinction __s is making is between layer toggles (layer is active between layer key presses, described as stateful) vs layer modifiers (layer is active while layer key is held).

And there are definitely reasons to minimize keyboard state. I've been playing around with programmable keyboards (running RMK in my case) with several thumb keys. My thumb was getting fatigued, so I tried using a layer toggle to avoid having to hold it while using the nav layer. I would hit it by accident and then get confused about why my keyboard isn't doing what I expect ("mode confusion"). That gets awkward, unproductive, and embarrassing real fast. You can display the mode via per-key LEDs and/or an OLED display, but those only help if you actually look down at the keyboard, which is not my habit. (I have thought about using a companion app to display an overlay on my computer's screen when in a non-default layer.)

fwiw, I think most of my thumb fatigue was from using my thumb on modifier keys beneath z/x/c and equivalent on the right, which required folding my thumb underneath my palm. Bad idea.

These keyboard designs have some really interesting ideas, but the ideas aren't all unambiguously good. Some of what are described as thumb keys really shouldn't be used with the thumb. I'm still on the fence about column stagger. I think a lot of the reason people avoid the number row on these keyboards is because the purely vertical reach on a column-staggered keyboard is more awkward than the diagonal movement you make on a row-staggered keyboard. And the idea that column stagger is better because it forces you to use e.g. the ring finger for "c" is based on an idea that it's bad to use the index finger for "c" even with a row-staggered keyboard, and I disagree with that. I also think they're undervaluing muscle memory (or maybe were made for people who never learned to type well on a row-staggered keyboard and are really committed to always using the column-staggered keyboard).

In an earlier thread, I wondered [1] if "concentrating around AI-native talent" in a round of layoffs was code for "we're firing all the old people", if "AI-native talent" meant people who had never learned how to do things without AI. Many folks said no, of course not. Well, in this case digital ocean has removed all doubt; "AI-native" means exactly that:

> Most of the engineers in this cohort are early in their careers. That was intentional. ... Engineers entering the field today don’t think of AI as a tool they’ve had to adopt. It’s simply how they build. That fluency isn’t something you retrofit into someone; it’s something you hire for directly.

Ugh.

[1] https://news.ycombinator.com/item?id=48029631

Hmm. I don't do game development myself, so take this with a healthy dose of salt. But...not necessarily. I think game development might be one of the more varied of the domains I mentioned. If you want to actually focus on the game, rather than learn about engine development, you might want to start with the choice of engine (e.g. Godot or Unity) and learn a language they recommend for integration (e.g. C#) rather than the language the engine itself is written in, as the code you write won't necessarily be as resource-intensive as the engine code itself. Though you certainly could start by picking e.g. Rust and then looking at popular engine/framework options there (e.g. Bevy or Macroquad). It might also vary a lot based on the type of game you're interested in.

Is there a particular domain you'd like to get into? It sounds like you're wanting to build expertise in something other than CRUD app assembly, but my language recommendations might change based on whether that's embedded, game development, distributed systems, system administration, etc.

I don't think in your shoes I'd prioritize learning Zig for any of these domains, though, for a few reasons:

* It's not a pre-req for understanding some existing corpus of important software (which is a big reason for C and C++ in 2026) or the language of choice for some current hot domain (as Python is for AI).

* It's not memory-safe, which (whether via GC or Rust's borrow checker) is increasingly viewed as a critical security attribute.

* It's not stable yet, so I'd expect a certain amount of running to keep in place both in your learning and in avoiding bitrot in anything you write in it.

* From the outside, the community seems strangely hostile as well as elitist.

A few I might suggest instead: Rust (both as a language I personally like and as the most different from the ones you've already touched), Go (which is a good choice for employability), SQL (maybe you already know this one if you're doing CRUD stuff but you didn't list it), bash, and more Python and/or TypeScript.

There are folks who have added them to external keyboard builds: https://kbd.news/How-to-integrate-a-trackpoint-into-your-key...

> the original commit being 4-5 lines long (what did claude do then?)

I've said "rebase onto <newbase>" and let it handle all the merge conflicts. I wouldn't expect this particular commit to conflict with anything, but it could have been part of a big series where it'd be worth doing that instead of running the rebase command yourself. It wouldn't surprise me if I picked up some Co-Authored-By:s along the way.

> This is a good example of what slips through LLM attention. It forces all allocations to be calloc as if it is a strict upgrade.

I wouldn't assume Claude made that decision; it's not as if that was some incidental thing that it snuck into a large commit. The commit message starts with "zero all new memory from allocations", and that's exactly what the commit does. What do you imagine the prompt was?

It seems totally plausible to me that a human initially thought this was an improvement, then rethought after discovering the RSS regression. And it's not a law of nature anyway that this change has to increase RSS; calloc could special-case the case in which memory was freshly returned from the OS, knowing fresh memory mappings are zeroed anyway.

I blame AI for these regressions mostly in the sense that it caused a flurry of vulnerability reports. Those led to a flurry of quick fixes. Sometimes quick fixes cause other problems.

Ugh, yeah, gross for `thunderbolt-net` only support one link in total, though presumably fixable.

> - Intuition on why- I can't point you to the line number, but I think it has to do with a fixed 4kb page size when communicating with the NHI that ends up becoming a bottleneck, perhaps 16kb pages on aarch64 apple help here?

I'm used to page size making a difference (due to TLB pressure) but not a factor of 2. I'm not familiar with DMA, so maybe there's some reason it'd be that dramatic there, but I'm unsure.

If the total size vs the latency of draining is just so small that it frequently fills and stalls, or if the sender and receiver can't be accessing it at once (but I don't think should be true?), it might make more sense. I think if I were wanting to make this thing go more smoothly, I'd probably start by measuring fractions of the time the tx/rx buffers are completely empty and completely full.

Actually, I'm not sure I'm understanding the text "we only have a single DMA ring for tx and rx" either. Does that mean one for tx and one for rx? or really one ring in total? if the latter, does it have to say drain fully before switching modes? that would seem pretty crippling.

> https://github.com/y3owk1n/neru

...which supports Vimium-style hints mode as well as the grid-based approach shown in this "Mouseless (app) explained in 80 seconds" video. It also has a very responsive maintainer.

Personally I like vimium's approach much better than the grid. Unfortunately not everything has a good accessibility tree (Zed sadly doesn't), but I just realized loading neru's page that I'm behind in versions. I haven't tried the "Native Vision OCR" addition to hints mode yet.

I also like having a trackpad right on the keyboard (using a SoflePLUS2 right now though I'm not totally sold on column stagger). Then I can use a real pointing device with only a slight movement of one hand. In the Mouseless video, the creator has tried to minimize the distance by putting the mouse between the halves of his keyboard, but I think he's both compromised the keyboard position to ease using the mouse (arms wide and parallel with wrists turned inward rather than arms converging toward a more splayed keyboard with somewhat closer halves, untented to minimize vertical separation compared to the mouse) and might have an uncomfortably small mousepad to avoid doing this even more. Not a compromise I'd want to make.

When I get that, I just repeat the question "where did you look in the docs?", or just "go look at the docs now" if they're really dense. I can't help them until they have a better answer.

It takes a few tries before they internalize that they need to have a doc link before expecting my help. Once they do, I might take the next step to saying "here's the answer; can you update the docs so the next person doesn't have to ask?" And it might take a few tries before that sticks too. My goal is to eventually turn them into someone who evangelizes the docs themselves.

When I write peer reviews for my colleagues, I describe their attitude toward documentation. If that's "they refuse to open the docs, frequently wasting their colleagues' time", it's not gonna go well. If it's "they make nice doc edits after I ask them", a little better. If it's "they proactively maintain the documentation", better still.

Of course all this is for stuff that one could reasonably expect to be documented. Help thinking through a design problem or debugging their in-progress PR is generally a different situation.

When someone asks me a question that is or should be documented, I like to ask where they looked for it (link or search query).

* Sometimes, this prompt is enough for them to find the answer.

* Sometimes, they tell me a spot that makes sense to them, and I make it have the answer. (Maybe just by adding a cross-reference.)

* If they refuse to look at the docs, I can't help them.

> now you've re-introduced out-of-order delivery which complicates re-assembly of large packets, retries, handling loss etc.

Still confused though. For a standard TCP/IP networking stack, that support is all there anyway, as it's not meant for point-to-point links, and out-of-order delivery is a thing that happens on the Internet. I haven't tried thunderbolt-net, but it says it implements Apple's ThunderboltIP, so I'd expect it's IP-based networking on top, and so it'd all work? Is it that out-of-order delivery is far more common than usual, and this path is so much slower (by impairing LRO/GRO) that it's not worth aggregating at all?

I'd understand if each pair is logically represented as a separate networking device, and then you have to set up link aggregation on top of that. (And iirc at least with some forms of aggregation a particular flow is bound to one link, so you'd have to have a bunch of streams to actually get bandwidth benefits.) So caveats for sure but I'd expect something to be possible. But does it just not support using both pairs at all?

Even with using one pair I still don't understand why you'd only get about 10G rather than 20G on a pair. I do see chapter 4 of the (your?) article talks about the single DMA ring maybe imposing the 10 Gbps limit but I don't have any good intuition for why. I don't know say how large the rings are or what latencies to expect on their operations or what packet sizes are supported which might help me understand.

> traditional Thunderbolt networking protocol ... performance may be as low as that of a 10 Gb/s Ethernet interface.

Ouch. Why so much lower than the physical bandwidth (or what they've achieved here)?

I admit I might roll my eyes a bit if the first thing I ever learned about KDE were its mascot's pronouns. But...

* That's not what's happening. The pronouns are mentioned in a social media post (presumably targeted at people already way into KDE) during pride month. This kind of wink to the LGBT community was in not that long ago even for the stodgiest corporate brands. You can easily ignore it if you don't care. In contrast, the website's landing page is primarily about the software. There's a (presumably temporary) banner at the top about the anniversary with the mascot; if you click through, it still doesn't mention pronouns AFAICT. It's not as if you have to go through a whole pronoun discovery cosplay to download the software.

* Open source projects' priority is often building a community of contributors over seeking (often small by comparison) financial donations. I commend efforts to establish a welcoming community. To me this seems like a very gentle way of saying this is a community where LGBT folks are welcome and homophobic/transphobic behavior is not. And I'm a believer in the "paradox of tolerance"—you can't tolerate intolerant behavior and expect a tolerant (much less welcoming) community.

* To the folks this is appealing to, and who perhaps are behind this decision, the current (US) political climate of intolerance feels almost inescapable. Even looking at this at in the most Machiavellian "how do I maximize the contributions I get without actually caring about humans" way, aligning with this community of folks who don't feel welcome in many other places, including a lot of excellent software developers, makes a lot of sense.