MurphyA/hacker-news huggingface dataset:
by emptysongglass | 2025-07-03 10:40:49+00:00
Please don't make personal attacks on HN.

The only difference between an imagined smooth solution is the sync mechanism and a unified client application ecosystem, neither of which is really possible without a large company behind it.

I said you don't understand how KeePass works because you refer to 3 applications for 3 different OSes (2 mobile) as if they were a confusing mix of different applications, when really they're just client implementations around a single, formalized spec. And most folks don't use both iOS and Android so really there's just your choice of KeePass desktop app and one for Android or iOS.

No one says the plethora of email client choices is confusing. This is exactly the same.
by Sammi | 2025-07-03 10:41:04+00:00
I'm expecting to see so much more poor quality software being made. We're going to be swimming in an ocean of bad software.

Good experienced devs will be able to make better software, but so many inexperienced devs will be regurgitating so much more lousy software at a pace never seen before, it's going to be overwhelming. Or as the original commenter described, they're already being overwhelmed.
by ifwinterco | 2025-07-03 10:41:36+00:00
This is my read as well.

Hard to say for sure because chatGPT came out at almost exactly the same time the post-covid wheels where starting to fall off anyway, but I think it's fair to say that as of right now you can't really replace all (or even many) of your engineers with AI.

What you definitely can do though, is fire 20+% of your engineers and get the same amount done simply because more is not necessarily better
by herbst | 2025-07-03 10:41:43+00:00
Working in a team and peer reviewing each others code was definitely what teached me most. It did help a lot that one of my team members was also a dev of that specific tool.

Refactoring, taking my time to do so and learn new things to optimize while doing so is what helps me most today.

AI for some reason is totally not helpful for my vision of clean code.
by nothrabannosir | 2025-07-03 10:42:14+00:00
That article covers a bug in implementations of blurring in browsers. It shows how when a 200px red circle is fully covered by a blur with radius 16px, today you will see a 232px sized blurred circle. But when the circle is shifted down from under the blur, so there is one pixel of space separating the two, you would still expect to see 15 px of blurred red circle. Instead it goes 18, 17, 16, 0, 0, for every successive frame. That’s a bug.
by lproven | 2025-07-03 10:42:23+00:00
Yup.

As many American readers don't know: 3 years after Acorn's Archimedes, with an 8MHz ARM2.

https://chrisacorns.computinghistory.org.uk/Computers/A300.h...

It was £799.

In 1987 USD, $1450.
by TacticalCoder | 2025-07-03 10:42:42+00:00
> "You are given an array A of n - 1 integers"

It's an array of integers so it fits in memory (otherwise it wouldn't be called an array). As it fits in memory, n cannot be that big. I'd still ask for more requirements, TopCoder problem style: I want to know how big n can be that the array fits in memory.

I didn't know that XOR trick. My solution would be a bit arrays with n bits and two for loops: one to light each bit corresponding to a number and one for loop to find the missing number.

And if my bit array doesn't fit in memory, then neither does the array from the problem (and certainly not the HashSet etc.).
by dodomodo | 2025-07-03 10:43:14+00:00
1. True, but in practice it's not always the case, for example older versions of resharper sometimes slowed down typing speed. It's much harder to fuck it up when there is a network request in the middle.

2. What about languages like Java and Go?

3. a. The experience of lsp server crashing is much better than an editor crashing, the editor usually automatically restart it. I had lsp servers crash without me noticing at all.

b. Memory problems in both lsp servers and traditional IDE analysis are extremely common in my experience. It seem to me that the problem is that there are a lot of pathological cases where the analysis enters a loop and keeps allocating memory.

4. When mixing runtimes I actually find it easier to have multiple processes because I can attach a specialized debugger to each process but this is definitely an important point.

5. good counter argument, I retract my point

6. what I meant is that for very large code bases it can be beneficial to run a central lsp server that many people can connect to because most of the index is shared between all of them and the parsing+indexing itself is very costly. I heard Google were doing something like that but I don't have more information.
by worldsayshi | 2025-07-03 10:43:42+00:00
I think the bottleneck can be summarized as verification and understanding. While that was the bottleneck before as well now it makes even more sense to find comprehensive ways to work with that. If you can quickly verify that the code is doing the right thing and that it is understandable, then you might achieve productivity increase.

And there's no good reason why LLM's can't at least partially help with that.
by lionkor | 2025-07-03 10:43:54+00:00
The difference between AI as autocomplete and vibe coding couldn't be bigger. It's like the difference between having your phone with you on a trip somewhere to take pictures with, and just watching a video of the place on your phone at home.

Autocomplete speeds up code generation by an order of magnitude, easily, with no real downside when used by experienced devs. Vibe coding on the other hand completely replaces the programmer and causes lots of new issues.
by creatonez | 2025-07-03 10:44:46+00:00
Yes, Microsoft is the worst company ever.

...But this article headline is insanely misleading by not mentioning it's being migrated to Edge. To the point where I'd call it a smear crafted for maximum clickbait shock value. Nothing is being wiped, it's just being moved to a different app. Sure, there's good reasons to not like that app (it's the Internet Explorer sequel after all), but the story here is not as extreme as implied.
by moritzwarhier | 2025-07-03 10:45:16+00:00
The website you link (disgusting people) has apparently changed.

> For Content Thieves (Warning)

> If you are currently using Body Cam Declassified content without [...]

> You are in violation of copyright law and will be subject to legal action

[...]

> We aggressively pursue legal remedies against content theft, including statutory damages of up to $150,000 per infringement under U.S. [...]

> An additional administrative fee of $2,500 per infringing video will be assessed

> We demand all revenue generated from the unauthorized use of our content

> We maintain relationships with copyright attorneys who specialize in digital media infringement

> We recommend removing the infringing content immediately and contacting us regarding settlement options

A paragraph about the videos being fake is still there.

> While actual government-produced bodycam footage may have different copyright considerations and may be subject to broader fair use provisions in some contexts, our content is NOT actual bodycam footage.

> Our videos represent original creative works that we script, film, edit, and produce ourselves.

> As privately created content (not government-produced public records), our videos are fully protected by copyright law and are NOT subject to the same fair use allowances that might apply to actual police bodycam

> The distinction means our content receives full copyright protection as creative works, similar to any other professionally produced video content.

This reminds me of a non-AI content mill business strategy that has been metastasizing for years. People who film homeless people and drug addicts and make whole Insta and Youtube channels monetizing it, either framed at "REAL rough footage from city XY" or even openly mocking helpless people. The latter seems to be more common on TikTok and I'm not watching "original" videos of such shite.

There is a special place in hell for people who do such things and in my opinion, there should be laws with very harsh punishments for the people that "create" this trash and make money from it. When it's about the filming of real people without their consent, we really need some laws that effectively allow to punish people who do this, because the victims are not likely to defend themselves.

And in total, the whole strategy is to worsen societal division and tensions, and feed bad human instincts (voyeurism, superiority complex) in order to funnel money into the pockets of parasites without ethics.
by amluto | 2025-07-03 10:46:16+00:00
I can’t help but read Apple’s guidelines and think they read something from the 90s or early 2000s and completely misinterpreted it. Quoting (and this theme is repeated over and over):

> Ensure that you clearly separate your content from navigation elements, like tab bars and sidebars, to establish a distinct functional layer above the content layer.

This makes perfect sense. Separate content and controls. In this variant, controls go on top, like a toolbar, and then there’s a horizontal division (maybe an actual line, maybe just blank space), then content.

Then I looked at the pictures again and did a double take. Apple doesn’t have a clear separation at all. And the controls are at the bottom, not the top.

The punchline, of course, is that Apple transposed the Y and Z axes! The functional layer isn’t toward the top of the screen — it’s toward the user! You are supposed to separate content and controls along X or Y so that content is next to controls but separated a bit but, for some reason, Apple is floating controls over content, in the Z axis. The separation is a plane, parallel to the screen, that you can’t see because the controls are in the way.

Apple, turn off your fancy shaders and go back to the drawing board. You have so many more pixels than any 90s designer, and yet you can fit almost no unobscured content on the screen. And your poor users can’t see the divisions between content and everything else because you built the technology to rotate the whole UI 90 degrees about the X axis!
by dgellow | 2025-07-03 10:47:48+00:00
To answer the “where”, the response is in a workplace environment. Some people seem to be able to develop that set of skills by joining serious open source projects. But really, you have to learn that on the spot.

Great teams do take that in account and will train newcomers in what it means to be a “professional” developer. But then the question becomes, how do you find such a team? And I don’t think there is a trick here. You have to look around, follow people who seem great, try to join teams and see how it goes
by eadmund | 2025-07-03 10:47:48+00:00
This JSON (taken from https://www.w3schools.com/js/js_json_intro.asp):

{"name":"John", "age":30, "car":null}

could be this S-expression:

((name John) (age 30) (car ()))

The canonical representation (suitable for cryptographic hashing) would be ((4:name4:John)(3:age2:30)(3:car())).
Show HN: GitSlice – Extract folders or files from GitHub using CLI
by sanjaykumar584 | 2025-07-03 10:48:00+00:00
Hi HN

I built GitSlice, a fast CLI tool that lets you extract just a folder or file from a GitHub repo — without cloning the whole thing.

It uses sparse-checkout under the hood and resolves GitHub URLs automatically. Useful for grabbing only what you need from giant monorepos.

Example: gitslice https://github.com/05sanjaykumar/Flappy-Bird-OpenCV/blob/mai...

Supports folders and files Auto-detects branches CLI only, no GUI fluff Fully open-source

Repo: https://github.com/05sanjaykumar/gitslice Let me know what you think or where it could be better.
by mreid | 2025-07-03 10:48:26+00:00
A lot of those skills come from thinking about development in a team as a system and ask where do things frequently go wrong or take too long?

Practice clearly and concisely expressing what you understand the problem to be. This could be a problem with some code, some missing knowledge, or a bad process.

Check to see whether everyone understands and agrees. If not, try to target the root of the misunderstanding and try again. Sometimes you’ll need to write a short document to make things clear. Once there is a shared understanding then people can start taking about solutions. Once everyone agrees on a solution, someone can go implement it.

Like any skill, if you practice this loop often enough and take time to reflect on what worked and what didn’t, you slowly find that you develop a facility for it.
by z3t4 | 2025-07-03 10:48:56+00:00
When I learned coding it took a lot of effort just to get something to work at all, it took many years until I could take an idea and write code that works right away after the spelling errors have been fixed. Now I have colleges that have no idea what they're doing but AI gives them code that works... Meanwhile the coding standards, languages and frameworks changes faster then I have time to keep up. I always liked code that was simple, easy to understand, and easy to change, remove and rewrite. Writing and working with such code is very satisfying. But noone cares about code anyway. It's more of an brutalist abstract artform that very few people appreciate.
by throw0101b | 2025-07-03 10:49:28+00:00
See also "DOJ announces plans to prioritize cases to revoke citizenship":

* https://www.npr.org/2025/06/30/nx-s1-5445398/denaturalizatio...

"DOJ memo pushes for broader effort to revoke naturalized US citizenship":

* https://thehill.com/policy/national-security/5379452-doj-mem...

"DOJ directs US attorneys to seek to revoke citizenship of naturalized Americans over crime"

* https://www.foxnews.com/us/doj-directs-us-attorneys-seek-rev...
by wraptile | 2025-07-03 10:49:44+00:00
China does have their own Github as gitee.com¹ which runs a fork of Gitea but it's basically dead because it's impossible to have anything like Github with the current censorship aparatus. Here's the excerpt from wiki:

> On 18 May 2022, Gitee announced all code will be manually reviewed before public availability.[4][5] Gitee did not specify a reason for the change, though there was widespread speculation it was ordered by the Chinese government amid increasing online censorship in China.[4][6]

1 - https://en.wikipedia.org/wiki/Gitee
by ffsm8 | 2025-07-03 10:50:06+00:00
There is also the situation in which the developer knows the tools by heart and has ownership of the codebase, hence intuitively knows exactly what has to be changed and only needs to take action.

These devs don't get any value whatsoever from LLM, because explaining it to the LLM takes longer then doing it themselves.

Personally, I feel like everything besides actually vibe coding + maybe sanity checking via a quick glance is a bad LLM application at this point in time.

Youre just inviting tech dept if you actually expect this code to be manually adjusted at a later phase. Normally, code tells a story. You should be able to understand the thought process of the developer while reading it - and if you can't, there is an issue. This pattern doesn't hold up for generated code, even if it works. If an issue pops up later, you'll just be scratching your head what this was meant to do.

And just to be clear: I don't think vibe coding is ready for current enterprise environments either - though I strongly suspect it's going to decimate our industry once tooling and development practices for this have been pioneered. The current models are already insanely good at coding if provided the correct context and prompt.

E.g. countless docs on each method defining use cases, force the LLM to backtrack through the code paths before changes to automatically determine regressions etc. Current vibe coding is basically like the original definition of a hacker: a person creating furniture with an Axe. It basically works, kinda.
by signal11 | 2025-07-03 10:50:25+00:00
This so many times. The cryptography around passkeys is great. An operational consequence that a lot of people seem to miss is lock-in.

I know passkey vendors will say they’re working to make interoperability easier in 2025, and that’s true. Equally the number of users who’ll take advantage of this interop will be a rounding error. The net effect will be even more platform entrenchment.
by simondotau | 2025-07-03 10:50:50+00:00
It's critical to note that Autopilot is not FSD, and has nothing in common with FSD, other than running on the same physical hardware. Autopilot is a brand name for lane centering / adaptive cruise control, similar to Nissan ProPilot and Ford Co-Pilot. Deaths attributed to the misuse of lane centering / adaptive cruise control features are commonplace among all makes of car, but deaths in Fords and Toyotas rarely make media reports, because the media is in the business of generating clicks.

A lot of people have died because their self driving Teslas

Two is not "a lot".

In the USA in 2023, the fatality rate of human drivers was 1.26 fatalities per 100 million vehicle miles in the USA.

Over the 60 million miles driven by Waymo vehicles, the number of fatalities involving a Waymo is one. This is a fatality rate of 1.67 deaths per 100 million miles. (It should be noted that this isn't a statistically meaningful number because Waymo vehicles have driven so few miles.)

Over the 3.8 billion miles driven by Tesla FSD, the number of fatalities involving a Tesla running the FSD software stack is two. This a fatality rate of 0.05 deaths per 100 million miles. If those 3.8 billion miles were driven by humans, you would expect 46 more deaths to have occurred.
by Sammi | 2025-07-03 10:50:55+00:00
Software is going to be of two types:

1. Mostly written by LLMs, and only superficially reviewed by humans.

2. Written 50-50% by devs and LLMs. Reviewed to the same degree as now.

Software of type 2 will be more expensive and probably of higher quality. Type 1 software will be much much more common, as it will be cheaper. Quality will be lower, but the open question is whether it will be good enough for the use cases of cheap mass produced software. This is the question that is still unanswered by practical experience, and it's the question that all the venture capitalists a salivating about.
by lproven | 2025-07-03 10:50:58+00:00
Indeed so.

I had fun with a series of what-if ideas last year:

https://www.theregister.com/2024/08/28/where_computing_went_...

https://www.theregister.com/2024/08/29/where_computing_went_...

https://www.theregister.com/2024/09/04/where_computing_went_...

Commodore bought Amiga. What if Sun bought Commodore?

Come up with some kind of early virtualisation to run AmigaOS stuff on SunOS/68k.

Actually make and ship the Amiga Hombre, but with SPARC instead of PA-RISC.

The other line of thought is where Commodore could have gone...

It didn't realise that the C64 was such a cash cow, and wasted effort on the C16 and Plus 4. It only did the C128 with a Z80 because otherwise the C128 wouldn't have worked with the CP/<M cartridge.

Can the whole C16 family, the C64C, C64SX, the C128.

Instead, incrementally improve the C64 rather than leaving a decade, coming up with the C65 and then cancelling it.

Incremental improvements that were on offer and affordable:

* better BASIC

* more RAM

* faster CPU

* 16-bit CPU

* Stereo sound

* More colours, higher resolutions

Lots of fun what-ifs to be had with the 1980s and early 1990s industry giants, before x86 caught up and swept everything else away.
by mykehunt | 2025-07-03 10:51:05+00:00
Bump for the Miniatur Wunderland - reason enough for anyone into to trains to visit Germany/Hamburg. You can easily spend two half days there. Their behind the scenes tour will give anyone with or thinking of building a layout enough ideas to keep them busy for years.

Their attention to detail, not only on the front end but also the backend is incredible. My wow moment was their staging. Since the trains run for the duration of the hours they are open - they get hot so they switch between two trains for each line so the motors don't burn out. Underneath each 12-18 inch riser section in the staging area is a separate smoke detector. (~20 smoke detectors in each staging area.)

https://www.miniatur-wunderland.com/ https://www.youtube.com/@MiniaturWunderlandOfficial
by andrelaszlo | 2025-07-03 10:51:19+00:00
I agree, normally the process (especially of manual testing) is a cultural thing and something you instill into new devs when you get broken PRs - "please run the tests before submitting for review", or "please run the script in staging, here's the error I got: ...".

Catching this is my job, but it becomes harder if the PR actually has passing tests and just "looks" good. I'm sure we'll develop the culture around LLMs to make sure to teach new developers how to think, but since I learned coding in a pre-LLM world, perhaps I take a lot of things for granted. I always want to understand what my code does, for example - that never seemed optional before - but now it seems to get you much further than just copy-pasting stuff from Stack Overflow ever did.
by Wilsoniumite | 2025-07-03 10:51:38+00:00
I think it's the case that both these systems can, should, and do coexist. When doing research or development, precision is more important than immediate grasp-ability. With people in general conversation, we operate on rules of thumb and appearances really do sometimes matter more than rigor. Colloquial speech then takes precedence, even if it is imprecise.

This article is nice because it is both interesting in the purely rigorous sense (phylogenetically), and it highlights this divide between precise definitions and the words we find useful (most of all in that catchy title!).
by joshstrange | 2025-07-03 10:51:41+00:00
I am skeptical of passkeys. Not of the technology itself exactly, but people’s implementation of it.

Username/password is much easier to grok (for developers and users) and while it absolutely has downsides, as a user, I can fully protect myself with username/password (unique password per site).

Passkeys might allow for fewer _user_ footguns but I worry there more _developer_ footguns. Also as a “power user”, I don’t want to deal with passkeys when I’m trying to automate something or scape my own data out of a website. It’s just another complication and I worry that anything edge-case-y (even approved methods) will break or have complications if you use passkeys (think app-specific-passwords when 2FA rolled out for gmail access).

Because of this I consistently decline passkey usage until such a time that I feel it’s better understood by the people implementing it.