MurphyA/hacker-news huggingface dataset:
by rainsford | 2025-06-08 13:39:33+00:00
True, but at the end of the post the author also explicitly rejects the idea of the DoH protocol in general on questionable technical grounds, so clearly their objection isn't just Cloudflare. I think the argument would be a lot clearer if they didn't conflate "using Cloudflare for your DNS" with "using the DoH protocol for DNS" even if they think both of them are bad.
What is a modern successor to HyperCard?
by WillAdams | 2025-06-08 13:39:44+00:00
Livecode went closed source and is out of the reach of most folks due to pricing.

Decker is too like to the original in being limited to b/w pixel graphics.

Flash afforded vector graphics and scripting, but is moribund.

Scratch only makes games and game-like things, with no ability to make traditional GUI elements.

Tcl/TK and Python/Tkinter lack integrated graphical development environments where one could just draw, while tools such as Lazarus and QTdesigner are too integrated with traditional textual programming. Processing similarly lacks a graphical representation of code or a drawing environment.

Nodebox and Ryven and so forth separate pretty graphics made of standard components and output.

If a naïve user wanted to express themselves by integrating drawing and numbers and code, what modern environment facilitates this?
by diggan | 2025-06-08 13:40:53+00:00
Statements like these are useless without sharing exactly all the models you've tried. Sonnet beats O1 Pro Mode for example? Not in my experience, but I haven't tried the latest Sonnet versions, only the one before, so wouldn't claim O1 Pro Mode beats everything out there.

Besides, it's so heavily context-dependent that you really need your own private benchmarks to make head or tails out of this whole thing.
by nzrf | 2025-06-08 13:41:08+00:00
I still have my original Adam in the box, and I’ve been meaning to try and get it running. It was the first computer we had at home, and I have amazing memories of playing Buck Rogers on tape and other cartridge classics.

We ended up with two systems because the first one died along the way in 1983 or '84.

This brings back fond memories, including the desk my father built, which had a monitor stand and a cutout for the keyboard.

I feel lucky to this day that my parents invested in the Adam.
by skybrian | 2025-06-08 13:41:54+00:00
A deterministic algorithm can still be unpredictable in a sense. In the extreme case, a procedural generator (like in Minecraft) is deterministic given a seed, but you will still have trouble predicting what you get if you change the seed, because internally it uses a (pseudo-)random number generator.

So there’s still the question of how controllable the LLM really is. If you change a prompt slightly, how unpredictable is the change? That can’t be tested with one prompt.
by briHass | 2025-06-08 13:41:57+00:00
Personally, I didn't want to manage my management/virtualization layer. I wanted something that was an all-in iso that wouldn't tempt me to configure at all. I wanted to be able to restore just my container backups to a new PM install without worrying about anything missing at the host (to the extent possible).

I also like that Proxmox can be fully managed from the web UI. I'm sure most of this is possible with LCD on some distro, but Proxmox was the standard at the time I set it up (LXD wasn't as polished then)
Top Reasons F# Sucks
by reverseblade2 | 2025-06-08 13:43:19+00:00
#7. You start talking weird.

You say “computation expressions” and “railway-oriented programming” out loud, and suddenly your team stops inviting you to lunch.

#6. Nulls haunt you.

You used to live with null. Now when you see one, your eye starts to flinch, like a war flashback.

#5. Your buggy code won’t even compile.

F# refuses to run until you’ve handled every weird edge case.

#4. C# follows F# features from 10 years ago

and you’ll painfully watch it catch up, one keynote at a time.

#3. The job market is a desert:

You’re not unemployable, you’re niche.

#2. Making illegal states unrepresentable becomes an obsession:

Three months later… nothing compiles, and you cry in union types.

#1. You can’t go back.

Once you’ve written F#, every other language feels like hand-writing in Wingdings font.
by al_borland | 2025-06-08 13:44:30+00:00
This was to prepare you for navigating once there. I still have flashbacks to the Delhi Airport. Every time I turned a corner there was someone there asking to see the name on my itinerary (a random sheet of paper I printed out hat I didn't think I'd actually need) with my passport and ticket. It happened so many times I almost missed my layover.
by mathgeek | 2025-06-08 13:45:04+00:00
> So how do you ensure everyone keeps to that agreement?

There's nothing specific to using Claude or any other automation tool here. You still use code reviews, linters, etc. to catch anything that isn't following the team norms and expectations. Either that or, as the article points out, someone will cause an incident and may be looking for a new role (or nothing bad happens and no one is the wiser).
by more-nitor | 2025-06-08 13:45:21+00:00
I just don't get the fuss from the pro-LLM people who don't want anyone to shame their LLMs...

people expect LLMs to say "correct" stuff on the first attempt, not 10000 attempts.

Yet, these people are perfectly OK with cherry-picked success stories on youtube + advertisements, while being extremely vehement about this simple experiment...

...well maybe these people rode the LLM hype-train too early, and are desperate to defend LLMs lest their investment go poof?

obligatory hype-graph classic: https://upload.wikimedia.org/wikipedia/commons/thumb/9/94/Ga...
by kypro | 2025-06-08 13:45:56+00:00
Not really... If you're an average company you're not concerned about producing perfect software, but optimising for some balance between cost and quality. At some point companies via capitalist forces will naturally realise that it's more productive to not have humans in the loop.

A good analogy might be how machines gradually replaced textile workers in the 19th century. Were the machines better? Or was there a was to quantitatively measure the quality of their output? No. But at the end of the day companies which embraced the technology were more productive than those who didn't, and the quality didn't decrease enough (if it did at all) that customers would no longer do business with them – so these companies won out.

The same will naturally happen in software over the next few years. You'd be an moron to hire a human expert for $200,000 to critic a cybersecurity optimised model which costs maybe a 100th of the cost of employing a human... And this would likely be true even if we assume the human will catch the odd thing the model wouldn't because there's no such thing as perfect security – it's always a trade off between cost and acceptable risk.

Bookmark this and come back in a few years. I made similar predictions when ChatGPT first came out that within a few years agents would be picking up tickets and raising PRs. Everyone said LLMs were just stochastic parrots and this would not happen, well now it has and increasingly companies are writing more and more code with AI. At my company it's a little over 50% at the mo, but this is increasing every month.
by torgoguys | 2025-06-08 13:46:18+00:00
Framesets were great.

>If you right click a link and open in new window (or middle click), the frameset was gone and only the piece in the frame was visible.

Feature, not bug in my book. Same thing happens in today's iframes. But for situations where that is a problem, the spec could have been extended to support every page being able to identify a preferred parent frame. Or browsers could have changed behavior to by default duplicate a frame's parent and siblings when opening a frame in a new window.

>Also you could not bookmark anything.

Again a limitation of the spec that could have been addressed rather than throwing out a useful feature. We support have text fragment identifiers in URLs these days; surely we could have supported URLs with multipart frame targets.
by gavinray | 2025-06-08 13:46:34+00:00
See also: "lincheck" by Jetbrains

https://github.com/JetBrains/lincheck

Toolkit for automatically deriving linearizability proofs for Concurrent Data Structures/Primtives.

https://blog.jetbrains.com/kotlin/2021/02/how-we-test-concur...
by AshamedCaptain | 2025-06-08 13:47:14+00:00
In addition, your ISP can also extract whichever metadata it wants from your communications, incl. a very likely perfect guess of the hostnames you visit at which times _even if you don't use DNS at all_, just by looking at IP traffic metadata such as addresses and packet sizes.

So you already have to trust your ISP anyway -- but there was no need to trust Cloudflare *. DoH to Cloudflare is almost certainly a net loss in privacy compared to using your ISP's DNS over clear text.

* Right until they became hosters of half of the WWW. So Cloudflare can pretty much also guess your activity even if you don't do DNS with them anyway.
by rainsford | 2025-06-08 13:47:56+00:00
Even ignoring the question of the technical merits of DoT vs DoH, the way the author transitioned from "Cloudflare bad" to talking about DoT made no sense since DoT as an alternative does not solve the problems raised earlier in the post. Is the author opposed to DoH as a protocol or opposed to sending DNS requests to a company they don't like?

If we're getting into the technical part of the discussion though, I personally don't think DoH or DoT are great protocols for DNS. Security is fine, but it's a lot of overhead for relatively small requests where latency matters. I wish DNScrypt had gained more traction as an encrypted protocol designed specifically for DNS.
by michaelmrose | 2025-06-08 13:48:28+00:00
Actually the defense production act provides a perfectly viable path actually supported by law to ensure that the governments interests are served.

An injunction would be entirely logical as it prevents irreparable harm based on a fanciful understanding of the law unlikely to prevail and hurts the government not at all.

Certainly the government trying to steal like a common criminal puts anyone in an uncomfortable position but the only real risk is the fact we live under incipient fascism.
by skeeter2020 | 2025-06-08 13:48:47+00:00
>> LLMs make learning new material easier than ever.

feels like there's a logical flaw here, when the issue is that LLMs are presenting the wrong information or missing it all together. The person trying to learn from it will experience Donald Rumsfield's "unknown unknowns".

I would not be surprised if we experience an even more dramatic "Cobol Moment" a generation from now, but unlike that one thankfully I won't be around to experience it.
by thebigspacefuck | 2025-06-08 13:49:32+00:00
Someone at my work posted that because they have ADHD they were able to get a free lifetime pass to National Parks because being in nature calms them. I can’t believe some people. If you have the money to support national parks, pay for the pass. Don’t you realize if everyone does this we won’t have any more National Parks? They are at a Director level, they can travel, and somehow ADHD is a disability? You wouldn’t know it if they didn’t tell you every time they introduced themselves. They’re like, “Ugh ADHD made me so driven I got to the Director level it’s so stressful…”.
by creata | 2025-06-08 13:49:53+00:00
The author seems to mostly be talking about the aliasing rules, but if you don't want to deal with those, can't you use UnsafeCell?

Imo, the more annoying part is dealing with exception safety. You need to ensure that your data structures are all in a valid state if any of your code (especially code in an unsafe block) panics, and it's easy to forget to ensure that.
by awfulneutral | 2025-06-08 13:50:48+00:00
Yeah, the AI-generated bugs are really insidious. I also pushed a couple subtle bugs in some multi-threaded code I had AI write, because I didn't think it through enough. Reviews and tests don't replace the level of scrutiny something gets when it's hand-written. For now, you have to be really careful with what you let AI write, and make sure any bugs will be low impact since there will probably be more than usual.
by asnyder | 2025-06-08 13:51:11+00:00
His legacy still exists and continues today. Even updated to modern sensibilities, cross-platform, and compatible with all your legacy Hypercard stacks!

As far as I remember, progression was Hypercard -> Metacard -> Runtime Revolution -> Livecode.

https://livecode.com

I was a kid when this progression first happened, my older brother Tuviah Snyder (now at Apple), was responsible for much of these updates and changes first at Metacard and then at its acquirer Runtime Revolution.

I even wrote some of my first programs as Hypercard compatible stacks. Was quite fun to see my apps on download.com, back in the day when that meant something :).

I always joked it required please and thank you due to its verbosity, but was super simple, accessible, and worked!

How nice, that even today one can take their legacy Hypercard Stacks and run them in the web, mobile, etc. Or create something new in what was more structured vibecoding before vibecoding :).
by ayushkcs | 2025-06-08 13:51:11+00:00
Intro: Ex-YC Engineer @ Tennr (W23) | Former SDE Intern @ Neuralix Inc. | Senior Undergrad (Class of 2025)

Location: Anywhere in the World

Remote: YES (Worldwide)

Willing to Relocate: YES

Technologies: Python, Django, Django DRF, FastAPI, PostgreSQL, MongoDB, Redis, AWS, Docker, Git

Proficient with next gen AI tools like Cursor & Claude Code.

Resume: https://drive.google.com/file/d/1fjRDe08C33KmQSXJqm4wp31Crpq...

LinkedIn: https://www.linkedin.com/in/ayushkcs/

Email: kayush2k02@gmail.com

Ps: Recently completed a work trial with Mercor — one of the fastest-growing AI startups in the Bay Area.
by dabacaba | 2025-06-08 13:51:22+00:00
DoH does wonders against ISPs which filter DNS traffic (including traffic to third-party DNS servers). This happens more often than many people realize. My ISP blocks traffic to a couple of random websites (perfectly safe and legal) just because their security system doesn't like them, and they can't do anything about that. I only wish for more websites to deploy ECH, because they are using SNI filtering as well.
by rimunroe | 2025-06-08 13:51:46+00:00
> It really depends what I'm building, and I find that these are often additional tasks that are done later after the core functionality is validated. I've most often built apps used internally or to test concepts for early user feedback, that had a relatively low bar.

Prototyping and internal tooling are both obviously things with far different bars for quality (much as I wish internal tooling wasn’t treated like that). I’ve not felt much difference in prototyping endpoints on the backend versus new pages in the UI in terms of difficulty. Internal sites usually have dramatically lower quality bars than production apps, though hopefully you’re not treating accessibility any differently for them. A company can mandate that their employees use a specific browser. The company knows which hardware/OS are used. They also can often support only one language unless they’re large. Most tools don’t have to worry much about turning away customers.

Earlier you mentioned sneaking architectural issues. Frontends are rife with these, and this is part of why there’s so much churn in frontend frameworks and APIs. It’s often incredibly easy to make a UI which appears to work and satisfy the requirements as given, but unless you’re aware of the things listed in other comments the resulting codebase might need an entire rewrite to support the actual features which customers expect. Maybe you built an entire UX which fundamentally doesn’t work when using a screen reader or a software keyboard. You might you have no way to support optimistic updates or undo. Maybe your choice of routing framework won’t allow you to block a route update until some data is loaded or an animation is finished. Sometimes these things are easy to bolt on, sometimes they result in weeks of lost progress. All that might be acceptable for an internal site, but the vast majority of frontend developers spend most of their time on client-facing ones.

I guess my main point is that I frequently hear stuff like this from backend developers, and I also frequently have to fix the frontend code they wrote because they just didn’t know how much goes into making the slightest bit of a non-trivial workflow for customers. As an aside, I think the worst offenders in this regard are actually people who describe themselves as full stack. I have done a fair bit of backend work. I’m not full stack. My backend work rarely has to worry about load balancing or database consistency, but that’s because actual backend devs are catching those things for me. I know those things exist though, and that many more that I’m not aware of do too.
by mhast | 2025-06-08 13:51:58+00:00
I suspect that Waymo car's could operate in a lot more areas than they do. The issue is that Waymo are trying to sell the service of safe travel and not a car with an addon you can pay for which doesn't actually work.

In other words, since they accept liability for their cars it's not in their interest to roll out the service too fast. It makes more sense to do it slow and steady.

It's not really a strong argument that their technology is incapable of working in general areas.
by the__alchemist | 2025-06-08 13:52:35+00:00
Like unclad, I disagree that not having private fields is a problem. I think this comes down to programming style. For an OOP style (Just one example), I can see how that would be irritating. Here's my anecdote:

I write a lot of rust. By default, fields are private. It's rare to see a field in my code that omits the `pub` prefix. I sometimes start with private because I forget `pub`, but inevitably I need to make it public!

I like in principle they're there, but in practice, `pub` feels like syntactic clutter, because it's on all my fields! I think this is because I use structs as abstract bags of data, vice patterns with getters/setters.

When using libraries that rely on private fields, I sometimes have to fork them so I can get at the data. If they do provide a way, it makes the (auto-generated) docs less usable than if the fields were public.

I suspect this might come down to the perspective of application/firmware development vice lib development. The few times I do use private fields have been in libs. E.g. if you have matrix you generate from pub fields and similar.
by soulofmischief | 2025-06-08 13:52:55+00:00
We must separate the act of training from the act of distribution (which could include filtering). Training and personal use seems well within the scope of fair use.

I do however understand why you would be upset if Meta or OpenAI hosts/distributes a model that could fully reproduce your books (assuming that is really the case) and make money providing that information.

That said, and I'm not trying to move goalposts here, I just don't personally find Meta in particular to be morally at fault, as I already have particular views on the freedom for myself and others to share information with each other that may be incompatible with your views (and to be clear, as an artist and open source engineer I do have an informed personal opinion on this matter, I have deeply considered and continue to reconsider the balance of freedoms required for artists to make a living off their craft without infringing upon what I see as inalienable personal freedoms).

Meta released their models publicly and freely after investing a lot of time and money into them, and I see it as a net good for humanity to have access to these incredible neural networks that were relegated to science fiction just a few years ago.

I also think LLMs are going to force us to rethink our entire approach to copyright. Whether that means abandoning our current notions of copyright entirely, or creating residuals for hosted commercial LLMs, or something else, I don't know.
by skeeter2020 | 2025-06-08 13:53:07+00:00
>> Well it turns out you can manage just fine.

You missed the full context: you would never be able to trust a bunch of amateur randos self-policing their content. Turns out it's not perfect but better than a very small set of professionals; usually there's enough expertise out there, it's just widely distributed. The challenge this time is 1. the scale, 2. the rate of growth, 3. the decline in expertise.

>> Using LLMs effectively is a skill too, and that does involve deciding when and how to verify information.

How do you verify when ALL the sources are share the same AI-generated root, and ALL of the independent (i.e. human) experts have aged-out and no longer exist?
by adrian17 | 2025-06-08 13:53:37+00:00
> This was one of the most successful product launches of all time. They signed up 100 million new user accounts in a week! They had a single hour where they signed up a million new accounts, as this thing kept on going viral again and again and again.

Awkwardly, I never heard of it until now. I was aware that at some point they added ability to generate images to the app, but I never realized it was a major thing (plus I already had an offline stable diffusion app on my phone, so it felt less of an upgrade to me personally). With so much AI news each week, feels like unless you're really invested in the space, it's almost impossible to not accidentally miss or dismiss some big release.
by vidarh | 2025-06-08 13:54:15+00:00
Others have largely dealt with your arguments, but to this:

> > And you can not increase the bus interval to compensate for it because it makes off-rush-hour bus commutes impractical.

Most transit systems DO operate different intervals during rush hour. Most places I've lived there's been anywhere from 3-5 different intervals at different times of day: At a minimum a night schedule which might be once an hour or not at all, a rush hour schedule, and 1+ day-time non rush-hour schedule.

I do agree that mini-buses would be an advantage though, once you don't need drivers, and that'd further reduce the advantage of small self-driving cars by allowing for far more routes.
by threeseed | 2025-06-08 13:54:22+00:00
Learning from LLMs is akin to learning from Joe Rogan.

You are getting a stylised view of a topic from an entity who lacks the deep understanding needed to be able to fully distill the information. But it is enough to gain enough knowledge for you to feel confident which is still valuable but also dangerous.

And I assure you that many, many people are delegating to LLMs blindly e.g. it's a huge problem in the UK legal system right now because of all the invented case law references.
by rainsford | 2025-06-08 13:54:54+00:00
That's not a bad setup, but now your DNS requests to the root servers aren't encrypted, which means anyone between you and the root servers can see the requests. I guess it depends on whether it's more likely that someone is snooping the requests off the wire or that the server you're sending the requests directly to is snooping on them in addition to just resolving them.

I think the ideal solution would be if the root servers adopted encryption of some sort. But I can see why they're somewhat reluctant to do that, especially with relatively heavy protocols (compared to DNS) like DoH or DoT.

Edit: With the existence of QNAME minimization, I guess I should say that the requests to the root servers or authoritative DNS servers are unencrypted. This does at least spread out the risk a little, since other than your ISP there's probably some variation in who is actually between you and the various servers you're making requests to.