MurphyA/hacker-news huggingface dataset:
by pjerem | 2025-08-23 06:38:57+00:00
I’d say it’s barely 3 things :

- The trackpad (but other manufacturers now have tolerable alternatives and anyway you can work without it)

- The screen : at an equivalent price point (and even more), nothing comes close to Apple screens. The cheapest MacBook have a better screen than most high end PCs.

- The audio : Apple truly did some sorcery to get such an awesome sound from machines that are flat as sheet. It’s so good that you can watch a movie on your MacBook without earbuds and don’t be bothered.

Everything else like build quality is overall better than most other alternatives but a few other manufacturers are also good at it.

I say this as someone who uses a MacBook for work despite loving Linux and who hates what macOS have become. The hardware is really that good.
by usr1106 | 2025-08-23 06:39:15+00:00
Technically I have no big doubts about S3 Glacier.

But what happens if you don't use that stuff for a long time. You are in hospital when the bill needs to get paid. Your credit card gets stolen and the number needs to changed. Whatever personal crisis that you are not able to take care of life as usual for some weeks. They will just delete your data before you are back in business.

Does anyone know how long it takes, how many warning mails will come? I have very little data in AWS, but I more or less constantly feeling it might happen to me. Maybe not because of such big crisis, but just the simple fact that my bank will reject the automatic payment requiring a PSD2 second factor and I miss the email...
by andriamanitra | 2025-08-23 06:39:24+00:00
> For example, there is nothing wrong with an programming language that only allows ASCII in the source code and many downsides to allowing non-ASCII characters outside string constants or comments.

That's a tradeoff you should carefully consider because there are also downsides to disallowing non-ASCII characters. The downsides of allowing non-ASCII mostly stem from assigning semantic significance to upper/lowercase (which is itself a tradeoff you should consider when designing a language). The other issue I can think of is homographs but it seems to be more of a theoretical concern than a problem you'd run into in practice.

When I first learned programming I used my native language (Finnish, which uses 3 non-ASCII letters: åäö) not only for strings and comments but also identifiers. Back then UTF-8 was not yet universally adopted (ISO 8859-1 character set was still relatively common) so I occasionally encountered issues that I had no means to understand at the time. As programming is being taught to younger and younger audiences it's not reasonable to expect kids from (insert your favorite non-English speaking country) to know enough English to use it for naming. Naming and, to an extent, thinking in English requires a vocabulary orders of magnitude larger than knowing the keywords.

By restricting source code to ASCII only you also lose the ability to use domain-specific notation like mathematical symbols/operators and Greek letters. For example in Julia you may use some mathematical operators (eg. ÷ for Euclidean division, ⊻ for exclusive or, ∈/∉/∋ for checking set membership) and I find it really makes code more pleasant to read.
by gbalduzzi | 2025-08-23 06:39:30+00:00
I believe there is a similar situation in the mobile space with iphones, at least here is Europe where they are not ubiquitous.

Most people use cheaper android phones, that are slower and with a much shorted timespan. then they try a 1k€ iPhone and it is great and conclude they prefer the iPhone to Android: it is not an apple to apple comparison, you should compare it to a 1k€ android lol.

Same things happens on laptops. If you try to use a 500-600€ laptop as work main machine for multiple years it will fall apart. Than you try a MacBook and it feels great because after 5 years is still usable.
by Gigachad | 2025-08-23 06:42:15+00:00
Half of the time it’s because the companies “good” era was when it was running at a massive loss. And the other half of the time it’s because the whole online environment changed.

Google didn’t deliberately sabotage search results. The internet just became full of more slop than valuable content.

Facebook might have ruined their product, but people wouldn’t want to use the original site anymore either.
by JimDabell | 2025-08-23 06:42:26+00:00
> > Simple: xslt is a giant attack surface entirely in C, and no browser maintainer cares to expend resources on maintaining that

> And yet they have no qualms shoving huge attack surfaces in the form of WebUSB, WebSerial, WebMIDI, WebTransport, WebBluetooth

This is not true. Both Mozilla and Apple rejected WebUSB, WebSerial, and WebBluetooth, and Apple rejected WebMIDI as well. Your list is mostly Blink-only APIs that Google have failed to convince other rendering engines to implement. And they all had lengthy discussions about security beforehand. So yes, browser maintainers definitely do have qualms about shoving those huge attack surfaces in there, and those qualms are a matter of public record you can read at your leisure.

> most of which have as much usage as XSLT

It doesn’t make sense to compare the usage of proposed features to a feature that has been implemented by all browsers for 25 years. Being available for 25 years and going almost entirely unused is a very strong signal that XSLT is not worth keeping around.
by immibis | 2025-08-23 06:43:10+00:00
They don't need to. If only 1% of the people are able to access censored content and therefore hold censored ideas, the majority will treat them as crazy pariahs.

It's the same mechanism that makes us consider the 1% of flat earthers crazy. Sadly the mechanism works based on how many people believe a thing, not whether it's true, so it can also block true things if only 1% of people believe them.
by ZeroGravitas | 2025-08-23 06:43:37+00:00
Clean processes generally use less power than dirty, inefficient fossil based processes.

Full electrification would halve energy needs even if it doubled electrical usage.

One country stands out starkly if you look at the pace of electrification over the last decade or so, and it's China.

https://www.nakedcapitalism.com/wp-content/uploads/2025/05/0...
by JumpCrisscross | 2025-08-23 06:43:41+00:00
Folks on the spectrum are different in a way I can’t quite explain. I’m talking about full-blown can’t have a conversation or express an interest in anything.

The iPad kids are more prevalent and highly recognisable. They’re also highly concentrated in the lower and lower-middle classes. (The country’s richest communities and private schools are banning devices in schools.)
by felipeerias | 2025-08-23 06:43:56+00:00
This is a very informative article, a good starting point to understand the complexities and nuances of integrating these tools into large software projects.

As one commenter notes, we seem to be heading towards a “don't ask, don't tell policy”. I do find that unfortunate, because there is great potential in sharing solutions and ideas more broadly among experienced developers.
by hunglee2 | 2025-08-23 06:44:45+00:00
Incredible how fast Trump is changing political culture - wasn't so long ago that protectionism, economic coercion, military-civilian fusion, state owned enterprise s was denigrated as 'communism' and hence beyond the pail. He's even mooted the possibility of redirecting tariff revenue directly to the people, an act of Chavez-esque socialism which would have been unthinkable a year ago. Anything can happen with this administration, I suspect that is the reason why the American people elected him
by JimDabell | 2025-08-23 06:44:57+00:00
> XSLT accomplishes what json-ld and semantic html never managed.

What are you talking about, it’s accomplished practically nothing‽

XSLT is a way to write code that takes one XML file and turns it into a different XML file. Its primary use case is to make RSS feeds look nicer in browsers. That’s it. It hasn’t solved the Semantic Web.
by silisili | 2025-08-23 06:44:59+00:00
Yes, well, sometimes. My wife used to shop there a lot. Some items 'came' from the US, which were little more than headshops and small warehouses, but shipping was much faster. Still, many items shipped directly from China to your mailbox.

What feels really gross is that they could ship a trinket from China to your door for less money than it would cost me to send it to someone in my own state.
by thisisit | 2025-08-23 06:46:15+00:00
Government now has a vested interest in seeing Intel succeed. And as much as RW debate in bad faith about cutting public funding being good and private entities should pick up the slack etc. there is no bigger catalyst than government policy. Intel can now get preferential policies like bigger tax breaks/holidays, preferential treatment in government contracts, cheaper access to Federal land etc.

In the long term though, at least in hands of the government like the current admin, they will ensure Intel slows down innovation. They will push for every company in US to use Intel chips in one way or the other - national security and what not. Without competition companies often get complacent - not many can match the might of a government and US govt at that. So, yay for national security and nay for Intel becoming innovation powerhouse.
by recursivecaveat | 2025-08-23 06:46:37+00:00
This is already done in Valorant at least (and presumably other games I'm not as familiar with). Unfortunately you are strongly limited by network latency. Imagine you're standing up against a wall next to a door. You expect if you step 1 foot sideways to instantly see the entire room and everyone within it. Hence your client already has to know everyone's locations in the room or you will get pop-in. You can limit people's ability to get truly implausible free information, but pretty much any-time someone is rounding a corner there is an unavoidable period of game-breaking free information you have to give the client.

If you look at the bottom gif in this post you can see what a huge advantage a wall-hack still is: https://technology.riotgames.com/news/demolishing-wallhacks-...
by Klonoar | 2025-08-23 06:47:49+00:00
Look man, Flash was not the same thing and people need to stop bringing this up.

Flash was a third party plugin that got way out of hand. It wasn’t (necessarily) the job the browser vendors created for themselves and offered for years.

Flash was also moreso removed on a fledgling platform first that grew to be a dominant platform; it wasn’t killed off on an existing dominant platform first.
by troupo | 2025-08-23 06:49:20+00:00
> Your list is mostly Blink-only APIs that Google have failed to convince other rendering engines to implement. And they all had lengthy discussions about security beforehand.

Indeed. And now Google cites lack of resources, complexity, a large attack surface, and small percentage of page views, and barrels forward with removing XSLT. Without a single lengthy discussion.

> Being available for 25 years and going almost entirely unused is a very strong signal that XSLT is not worth keeping around.

Yes, if a feature is deliberately ignored, let's remove it. That's exactly what happened to SVG for example. Oh wait...

On top of that XSLT is used on more web sites than, say, WebSerial which managed to climb to a whooping 0.000596% this year https://chromestatus.com/metrics/feature/timeline/popularity...

To quote Chrome's own document:

--- start quote ---

As a general rule of thumb, 0.1% of PageVisits (1 in 1000) is large, while 0.001% is considered small but non-trivial. Anything below about 0.00001% (1 in 10 million) is generally considered trivial. There are around 771 billion web pages viewed in Chrome every month (not counting other Chromium-based browsers). So seriously breaking even 0.0001% still results in someone being frustrated every 3 seconds, and so not to be taken lightly!

https://docs.google.com/document/d/1RC-pBBvsazYfCNNUSkPqAVpS...

--- end quote ---
by Gigachad | 2025-08-23 06:49:57+00:00
At least in Australia the phone ban doesn’t mean you can’t have a phone in your pocket, you just can’t take it out.

Taking your phone out when I was in school meant having it placed on the teachers desk until the end of class, and possibly some other kind of penalty if they particularly didn’t like you. But you always got your phone back before leaving the class.
by Animats | 2025-08-23 06:50:26+00:00
> US not accepting "duty-unpaid" postal shipments. This is VERY unusual.

To maintain the illusion that the sender pays for tariffs?

Keep receipts and customs declarations on everything imported. There's a lawsuit underway and it may well be decided that Trump doesn't have the authority to levy tariffs at all under the Emergency Economic Powers Act. In that case, importers will be due a refund.[1] The Constitution says that Congress sets tariffs and the Emergency Economic Powers Act doesn't mention tariffs. As usual, Trump's strategy is to stall, probably until 2026 when this is expected to reach the Supreme Court. Congress could enact Trump's tariff schedule to resolve this, but that would lock it into law.

[1] https://www.reuters.com/legal/government/what-happens-next-u...
by chrismorgan | 2025-08-23 06:50:41+00:00
Firefox and Chromium had in-built FTP protocol handlers. I believe extensions could depend on this in such a way that the removal might break things for them, but general web content couldn’t—it was just an external link.

Safari and IE didn’t have integrated FTP: rather, they could hand FTP links over to the OS for something outside the browser to handle.

Now Firefox and Chromium can hand FTP over to the OS too.

XSLT, on the other hand, is integrated, a true part of the web platform. XSLTProcessor on any page, <?xml-stylesheet?> on XML files loaded directly… it works everywhere. The case is quite different from FTP.

If they remove XSLT, this will be the first time a major baseline-available feature has been removed. (One or two minor features have been removed: SharedArrayBuffer was temporarily dropped very shortly after landing across the board, for solid security reasons, taking up to 4 years to return with suitable limitations; and mutation events came in 2011 before quickly being replaced with mutation observers in 2012–2013, finally being removed in the last year or so; and the unload event which has been known to be unreliable and a bad idea for at least a decade is in the process of being removed. But all three of these are likely to be very minor in their effects, where XSLT removal just breaks your entire page.)
by lelanthran | 2025-08-23 06:51:44+00:00
> You end up with a really bad waterfall where it can take a long time for a page to load because it's going back to the server constantly, whereas if you did it on the server it would be a single round trip.

These are all static file downloads, though. The first page load will take long, but if these are header/footer type includes, every subsequent page will use the cached file.

It's a trade-off between longer times for landing page and shorter times for every other page. The developer will decide whether or not to make the trade-off.
by globnomulous | 2025-08-23 06:52:10+00:00
"Reduce by 97%" is simple, clear, and accurate.

"Reduce 33x" and "make 33x smaller" are ambiguous, unclear, and inaccurate. Is something that's "33x smaller" or "reduced 33x" 1/33 of the original total or is it 1/34? The question can't be answered in the absence of more information.

These are common expressions, sure. They're also awful, belonging to the same category of error as:

* The price is expensive

* It's a good-quality piece

* All but one of my friends speaks like this.

* Here's an author whom we know cares about language.

* As well, this is how some people write.

That is, they're the errors of a normal native speaker.
by north_creao | 2025-08-23 06:52:31+00:00
Fair question, I understand that 15-20 person sounds like a lot for a startup. However our product is not just a UI tool wrapped with Claude code, the reality is that making AI generate actually working full-stack apps with MCP/API integration in one shot required way more infrastructure than people thought.

If you test out lovable, you will notice that they require more than one round of conversations to build full-stack apps like asking you to config supabase manually. And it 's very hard to connect with existing systems either through MCP or customize API. If you can take a look at the use case video link I put in post, you will get a better understanding of what I mean by the capability differentiation.
by nkantar | 2025-08-23 06:53:35+00:00
Author—though not OP—here. I’ll try to broadly address the questions, which are all fair.

Broadly speaking, I explicitly wanted to stay in the Coolify world. Coolify is a self-hostable PaaS platform—though I use the Cloud service, as I mentioned—and I really like the abstraction it provides. I haven’t had to SSH into my server for anything since I set it up—I just add repos through the web UI and things deploy and show up in my browser.

Yes, static sites certainly could—and arguably even should—be done way simpler than this. But I have other things I want to deploy on the same infrastructure, things that aren’t static sites, and for which containers make a whole lot more sense. Simplicity can be “each thing is simple in isolation”, but it can also be “all things are consistent with each other”, and in this case I chose the latter.

If this standardization on this kind of abstraction weren’t a priority, this would indeed be a pretty inefficient way of doing this. In fact, I arrived at my current setup by doing what you suggested—setting up a server without containers, building sites directly on it, and serving them from a single reverse proxy instance—and the amount of automation I found myself writing was a bit tedious. The final nail in the coffin for that approach was realizing I’d have to solve web apps with multiple processes in some other way regardless.
by JimDabell | 2025-08-23 06:53:36+00:00
> The suggestion to move the RSS/Atom feed links to a hidden link element is a horrible one for me and presumably others who want to copy that and paste it into their podcast applications. With that suggestion it adds another layer of indirection an application has to fetch and inspect.

This has already been the norm for years. Feed auto discovery is decades old at this point.

> Part of the reason HTML 5/LS was created was to preserve the behaviour of existing sites and malformed markup such as omitting html/head/body tags or closing tags.

This is not true. It has always been valid to omit html/head/body tags and the closing tags of several elements. This is a valid HTML 4.01 Strict document, it follows all of the parsing rules of HTML 4.01 correctly, it is not malformed, it parses correctly in every browser, there is no ambiguity, there is no error handling taking place, and there is nothing incorrect at all about it:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <title>Valid</title> <p>This is a valid HTML 4.01 Strict document.
by frm88 | 2025-08-23 06:54:14+00:00
I second mapy. I've replaced Google maps with this one ~5 years ago and never looked back. You can download specific maps for a country and within that specific federal states to reduce space consumed. I use it mostly for biking and hiking - you can plan tours with scaling duration/kilometers which is nice for a region you are unfamiliar with. Like parent wrote, offline access, routing, RT traffic. Can recommend.
by syntacticsalt | 2025-08-23 06:55:06+00:00
Are you referring to the first figure, from Smith, et al, 2007? If so, I couldn't evaluate whether gwern's claim makes sense without reading that paper to get an idea of, e.g., sample size and how they control for false positives. I don't think it's self-evident from that figure alone.

One rule of thumb for interpreting (presumably Pearson) correlation coefficients is given in [0] and states that correlations with magnitude 0.3 or less are negligible, in which case most of the bins in that histogram correspond to cases that aren't considered meaningful.

[0]: https://pmc.ncbi.nlm.nih.gov/articles/PMC3576830/table/T1/
by rock_artist | 2025-08-23 06:55:08+00:00
There are two points I feel are worth focusing and I’ve experienced similar:

- Linux is fast. Few years ago I wanted to run Linux and used my MacBook Air 2013 (one of the best machines I’ve had). It was amazing how Ubuntu ran so sleek especially comparing to the MacBook Pro 2018 with macOS.

- x86_64 feels less portable than arm. Since I got MBP from my work I’ve also got another machine for Windows. I’ve went with 13” MSI Perstige with 125H which was the latest back then offering hybrid cores (performance + economy). It’s 1kg is amazing and the OLED is also nice. But in order for the machine to actually compile and be snappy I need to ensure it’s not dropping to 0.4-0.8Ghz and then it easily gets warm and noisy.

The MBP 2021 also shows age. But even with more frequent fans and 80% of original battery it outperform the younger MSI since day one.

TL;DR

* Unless you need specific software, Linux distros are great and fast. Much more joy (imho) than Windows.

* SoC/ARM is still rare but it would be much more interesting comparison to current Macs in terms of portability (fans, battery life)
by penteract | 2025-08-23 06:56:33+00:00
From the report:

> To calculate the energy consumption for the median Gemini Apps text prompt on a given day, we first determine the average energy/prompt for each model, and then rank these models by their energy/prompt values. We then construct a cumulative distribution of text prompts along this energy-ranked list to identify the model that serves the 50-th percentile prompt.

They are measuring more than one model. I assume this statement describes how they chose which model to report the LM arena score for, and it's a ridiculous way to do so - the LM arena score calculated this way could change dramatically day-to-day.
by prmoustache | 2025-08-23 06:56:46+00:00
So what are the probability that those 4 kids and their parents are all disabled and unable to move to the coral, and how do they manage to get a shopping cart AND be able to do their actual shopping inside the supermarket with that low amount of mobility?

People having newborns typically use baby carriers and strollers and when using the later use the storage space of the stroller to carry a significant amount of groceries. Nobody with a sane mind woud grab 2 newborns in the same arm and throw them in an unsafe shopping cart.
by Arnavion | 2025-08-23 06:56:52+00:00
(From that link, about adding new subscriptions)

>The only real trick is that most YouTube channels use a vanity URL and it’s more complicated to get the channel ID in those instances.

Go to the channel's videos page ( https://youtube.com/.../videos ) -> right-click -> View page source -> search for "rssUrl" . It'll look like https://www.youtube.com/feeds/videos.xml?channel_id=UC...

Bonus: Replace the "?channel_id=UC..." with "?playlist_id=UULF..." to get a feed without shorts and livestreams.
by Wistar | 2025-08-23 07:00:56+00:00
In the early 90s a friend bought a five or six chamber Aga. He had lived in a house in Europe that had had one and he loved it. It cost a fortune to acquire and to install as the house had to be structurally reinforced to accommodate the weight of the oven. I remember that it took at least a couple of days to come up to a stable temperature across the whole oven. Each of the cooking chambers had a different temperature.

I thought the whole thing was ridiculous.
by yonatan8070 | 2025-08-23 07:01:06+00:00
Good question, I haven't tried to browse from abroad, so I have no idea, but it could be the case since they only operate in Israel.

I don't have a VPN to test, but I did ask ChatGPT [1] to try browsing it from its IP and it also failed. Afterwards I asked it to tell me what it sees from https://icanhazip.com, and it returned `74.7.36.81`, which is in London according to [2]

[1] https://chatgpt.com/share/e/68a9670d-d44c-8008-9a78-0d89662b... [2] https://whatismyipaddress.com/ip/74.7.36.81