smrq

He'd better. It would be a pretty severe embarrassment for a layman to know more than you about your own industry.

The trap he and many other smart idiots fall into is believing that having a high degree of expertise in one area qualifies you to speak authoritatively in unrelated areas. These days maybe you could call it Claude-smart: pairing situational brilliance with unwarranted confidence at other times. The really properly smart people I've met are good at tempering their statements with their degree of certainly based on their own qualifications.

My pet peeve is esolangs that are just a few find-and-replaces away from traditional languages. I'm not really sure what people find interesting about them; it's the CS equivalent of inventing a new Pig Latin, instead of a new Latin.

Indeed. Based, largely, on synthesizing the opinions of experts in the field. And, since they're smart, they naturally realize that there are few fields where their own opinion is an expert one.

"Common" is doing some heavy lifting there. You're still talking about the top 2-3% of earners (roughly, 10m 401k-maxers out of 350m Americans, based on data from Vanguard and napkin math).

It can be both. Said developer can be arrogant and insufferable and also brilliant and insightful, with some deplorable opinions and some admirable ones. The world would be a better place if people as a whole were more able to embrace dialectical thinking.

+1 to Baba is You, fwiw. In my own humble opinion it's the best puzzle game ever made, full stop.

I don't know how you can simultaneously believe that open source is prevalent enough to kill paid software but also non-existent enough that it doesn't itself fill the void it supposedly created.

Modular PSU cables never go in the big box. They go back in the PSU box if I'm being smart. Then I know which PSU they came from and can throw them out in ten years along with the PSU itself.

(I'm rarely smart and have a second big box of modular PSU cables that I maybe ought to get rid of.)

Your loss. The token dump is more interesting than the endless majority of "correct" LLM slop I've had the misfortune to read.

That would be pretty anachronistic; jQuery didn't come around until six years later.

I'm sure everyone in the hospital and with collapsed houses would agree with your assessment that it's not a big deal.

It's kind of funny and also kind of insulting. I'd laugh if a friend said it but said seriously by some rando on the Internet, nah, find a better way to put it.

Admittedly, HN is suffering the same fate to some extent.

Imagine gatekeeping learning. I suppose the blind are incapable of it, then? Or is taking in information via the fingers somehow more valid than via the ears?

It's quite literally a second order effect. The first order effect is light generation, and a consequence of that effect is heat generation via light absorption.

Explain the attack that gets mitigated by reading the diff of a lockfile?

Every major npm attack I can think of essentially follows the pattern of "version X.Y.Z is secretly evil". How does seeing package@X.Y.Z in your lockfile alert you to that?

This really seems like the exception that proves the rule, given how few Facebooks came out of that era. We had a social contract, but it turned out that being sociopathic is a winning strategy when everyone else is playing by the implicit rules. See also: modern politics.

Everything about that readme quote screams LLM. All it's missing is the user responding, "that doesn't make any sense, this won't work at all", and Claude responding back, "you're absolutely right".

More like they will climb even higher on the lighting-dollars-on-fire leaderboard.

Everyone loves to say this... because it's everyone's experience. I stopped using SO as a resource years ago (well before the advent of LLMs) because it got to the point where almost invariably, when I found a post that managed to perfectly articulate my question, it was closed as a duplicate of some other, distinctly unhelpful question. But it wasn't always that way. There's a fine line between strict moderation and draconian moderation, and at some point they crossed from the former to the latter.

The 4 packing takes up 100% of its square; it's trivially optimal. The 6 packing only takes up 2/3 of it, so it's not necessarily obvious that you can't do better.

"Just"

Spoken like someone who's never had to work on a date picker.

This may come as a shock to capitalists, but some artists don't want to charge their fans more. Fugazi famously capped their ticket prices at $5 because they wanted their shows to be affordable.

People didn't leap from jQuery to React. It's a lot easier to imagine an AI looking at jQuery and [insert any server side MVC framework] and inventing Backbone.

Posing OpenSCAD as an alternative to the likes of Fusion is like posing MS Paint as an alternative to Photoshop. It's not even the same class of tool.

"We made merging to main silently drop some commits from main" was another good one recently. If GH had only one job, not doing that would be it.

This is more or less my take, but at least for me it's not about the level of difficulty exactly. It just feels very transparently like exploring a state space, where the "a-ha" moments just boil down to breaking into a different neighborhood of that space. To be clear, the puzzles are very well designed, and also very hard; but I don't find solving them satisfying at ALL. Compare with Baba Is You, where the "a-ha"s feel to me more like having a grand insight than finding the right very specific sequence of moves.

Put another way, it's been years since I played Baba and I can still remember the key insights to some of the sneakier puzzles. I couldn't even begin to do that for SSR.

Swipe through the "Major Events Timeline". It would be funny if it wasn't so sad how petty it is.

I believe the intended turn order is:

1: P1 selects 2: P2 selects 3: P1 reveals 4: P1 selects 5: P2 reveals 6: GOTO 2

I.e. each player always selects immediately before their opponent reveals.

I doubt he would have much to say on the subject these days.

The most NixOS comment I've seen yet was when I was trying to find out about `mkOutOfStoreSymlink`, which lead me to this thread:

https://discourse.nixos.org/t/how-to-manage-dotfiles-with-ho...

> Hi, I just wanted to know, where can I find the documentation to know more about this contrib.lib.file.mkOutOfStoreSymlink option ?

> Well, since is a very simple function, no documentation is really needed.

I've been gradually transitioning everything to NixOS, starting with my homelab mini PC, then my Framework laptop, and now my daily driver desktop. It's hard to imagine going back because the pros are so strong compared to the cons, but the docs situation is truly dire.