Hacker Newsnew | past | comments | ask | show | jobs | submit | kemayo's commentslogin

You want Beats, which is owned by Apple. Your $200 budget pair is the Beats Solo 4: https://www.beatsbydre.com/headphones/solo4-wireless/MUW43/s...

It's a mismatch with our intuition about how much effort things take.

If there's humans involved, "I took this data and made a really fancy interactive chart" means that you put a lot more work into it, and you can probably somewhat assume that this means some more effort was also put into the accuracy of the data.

But with the LLM it's not really very much more work to get the fancy chart. So the thing that was a signifier of effort is now misleading us into trusting data that got no extra effort.

(Humans have been exploiting this tendency to trust fancy graphics forever, of course.)


It is not limited to graphics, better packaged products, better dressed / good looking well spoken person and so on. Celebrity endorsements depend on this thesis.

There has always been a bias towards form over function.


Once good form becomes commoditized, hopefully function starts taking priority


> Developers would often write helper functions that accidently mutated the original Date object in place when they intended to return a new one

It's weird that they picked example code that is extremely non-accidentally doing this.


An example that is hard to follow defeats the point. It's just showing what pattern is possible and you can imagine the abstraction layers and indirection that would make it happen accidentally.


It's a mediawiki feature: there's a set of pages that get treated as JS/CSS and shown for either all users or specifically you. You do need to be an admin to edit the ones that get shown to all users.

https://www.mediawiki.org/wiki/Manual:Interface/JavaScript


As an aside, it does seem like a bit of a bad sign for a feature that you know up-front that it'll be so polarizing that you need to have an always-visible top-level "hide this forever!" button.


Why? Shouldn't polarizing features be done exactly this way? The people on one pole use it, those on the other remove it. Perhaps you meant "unwanted" or "unpopular"?

If you never add any features that could be polarizing, then you end up with a lowest common denominator interface that offends nobody and is useful to (almost) nobody.


I dunno, I think that multiple people doing a workout together in the same at-home room is a bit of an edge case for this app. I have a not-tiny house, and I don't have a space where I could do that without having to move heavy furniture around first. People who live in apartments are really out of luck.

They do support syncing up the workouts of people who're each using their own device: https://support.apple.com/en-us/101979


Though, just to be clear, the per-user ones are also public. They're just a convention where if you make a subpage of your user page and call it "Sandbox", nobody is going to complain about the encyclopedic value of your edits.


If you really want something private, there is https://en.wikipedia.org/wiki/Special:ExpandTemplates (or of course just hit preview and dont save)


True , though I just discovered category scans still hit your user sandbox. Kind of silly


Here's a representative news article about it (WaPo because they were first in the search results): https://www.washingtonpost.com/immigration/2026/01/22/ice-me... (paywall-avoiding: https://archive.is/bsdv9)

They've come up with a memo saying that non-judicial warrants can let them break in. This has historically been very much not allowed.

Edit: As a quick explanation, this is more or less a separation-of-powers thing. The rule has been that for the executive to enter someone's home they need a warrant from a judge, a member of the judicial branch. They now say that an "administrative warrant" is enough, issued by an immigration judge -- but immigration judges are just executive branch employees, so this is saying that the executive can decide on its own when it wants to break into your house.


A lot of words to say "it's quicker when you allocate three large arrays rather 1,000,000 objects"

That feels sufficiently intuitive that describing it as "a JavaScript performance issue" is a bit confusing.

(There's other optimizations they're applying, but that's the only one that really matters.)


To elaborate slightly, note that "reliable" is sort of Wikipedia jargon. When it applies to a news organization, it means that statements of fact are likely to be correct... or at least, not intentionally incorrect, because errors do happen. So a source can be reliable and biased at the same time, which means that if it says a thing happened you can largely trust that it really did happen... but any interpretation of that might be slanted, and so shouldn't be trusted.

The New York Post isn't "reliable" because it's a tabloid that doesn't care overmuch about fact-checking what it publishes (and, worse, has a history of just making stuff up sometimes). So the Wikipedia position is that you can't trust a citation to the NY Post without finding something else to corroborate it -- at which point you might as well just cite the corroborating reliable source instead.

Whereas Mother Jones will absolutely mostly publish articles which say good things about progressives and bad things about conservatives, but those things will all be true. Their bias comes in the form of selectively presenting these things -- they're unlikely to bother posting a "Ted Cruz just did a good thing" article -- and in their color commentary / opinion pieces, not in the form of just making things up.

See: https://en.wikipedia.org/wiki/Wikipedia:Reliable_sources


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: