MurphyA/hacker-news huggingface dataset:
by basch | 2025-09-03 03:05:30+00:00
Ill maintain that family management of access control is one of the most broken things on the internet. Not only does 2fa make granting access on other devices a nightmare, but then each developer has its own version of parental controls.

ALL of account permissions, relations to other accounts, and authentication should be an exposed api that rolls up into a single dashboard. I should be able to go into one single control panel to control exactly what accounts are allowed to do what on what devices for all services for all family members. That includes lockouts, auth resets, push of auth to a device I dont have physical access to (kid is on a trip, I need to sign him into something).

I could go on and on and on about all the different ways this paradigm is so broken, it actually breaks our imagination of what it should look like in a functioning world. We are so used to doing it completely wrong, its hard to see right.
by Mars008 | 2025-09-03 03:06:17+00:00
> What I really want is something like a front-end framework but for LLM prompting

It's not simple to even imagine ideal solution. The more you think about it the more complicated your solution becomes. Simple solution will be restricted to your use cases. Generic is either visual or a programming language. I's like to have visual constructor, graph of actions, but it's complicated. The language is more powerful.
by mdaniel | 2025-09-03 03:06:50+00:00
but, hey, at least they get to be ultimately dynamic, leading to horeshit like this https://github.com/aws/aws-cli/blob/2.28.22/awscli/botocore/...

What does `create_client` return?! don't you worry your pretty head about it, it'll be whatever you want it to be! flexability!!11
by a-dub | 2025-09-03 03:07:11+00:00
also most python usecases that are in the realm of things like high performance concurrent request servicing push it down into libraries that i think are often tied to a native network request processing core. (gunicorn, grpc, etc)

python is kind of a slow choice for that sort of thing regardless and i don't think the complexity of async is all that justified for most usecases.

i still maintain my position that a good computer system should let you write logic synchronously and the system will figure out how to do things concurrently with high performance. (although getting this right would be very hard!)
by rtpg | 2025-09-03 03:07:25+00:00
I’ve also lived in NA Europe and Japan and disagree with this sentiment.

“Don’t waste stuff” is taught by plenty of parents, people talk about using every bit of the buffalo in America. Everyone in my generation has the grandparent who threw nothing away.

There’s maybe more modern examples of cultural thrift in Japan due to the postwar experience compared to the US… but even then.

I feel like I’m talking to aliens when these discussions of “unique Japan” things come up that are, in my experience, plenty present abroad.

I don’t even think Japan is particularly that good about reuse and waste beyond its recycling programs!
by ath3nd | 2025-09-03 03:08:15+00:00
> GPT-7 will need its own sovereign wealth fund

If the diminishing returns that we see now continue to prove true, ChatGPT6 will already be financially not viable so I doubt there will be GPT7 that can live up to the big version bump.

Many folks already consider GPT5 to be more like GTP4.1. I personally am very bearish on Anthropic and OpenAI.
by Jcampuzano2 | 2025-09-03 03:08:52+00:00
There are many companies that regularly spend much more than that on other software related licenses that devs need to do their job productively.

If the average US salaried developer is 10-15% more productive for just 1k more a month it is literally a no-brainer for companies to invest in that.

Of course on the other side of the coin there are many companies that are very stingy with paying for literally anything for their employees that could measurably improve productivity, and hamper their ability to be productive by intentionally paying for cheap shitty tools. They will just lose out.
by inetknght | 2025-09-03 03:09:11+00:00
Indeed, and there's a thing called "race to sleep". That is, you want to light up as much of the core as possible as fast as possible so you can get the CPU back to idle as soon as possible to save on battery power, because having the CPU active for more time (but not using as many circuits as it "could") draws a lot more power.
by BLKNSLVR | 2025-09-03 03:10:12+00:00
Since moving the GrapheneOS and basically re-setting up the phone from scratch, I've been choosing No to the inevitable "allow Notifications" permission request upon successful install (or first run).

There are just so many fewer distraction events coming from the damn device. It's almost peaceful. I can forget that it's there and get on with the things I want to, or should be, doing. I've also had mini-rants before about the unimportance of email communication; having notifications about the receipt of an email is as useful as a reminder to breathe (with some edge cases that if you set things up correctly, can be managed). Email, SMS, chat apps aren't real-time communications. If it's important I'll get a phone call - and only my chosen contacts cause the device to make a sound.

(This isn't about GrapheneOS, it's about choosing sanity at the time the initial choice is requested after having the experience to know what I want and what I don't. But GrapheneOS is great, for separate reasons).
by crazygringo | 2025-09-03 03:10:22+00:00
This is the answer. The food is perfectly fine. It's fresh, there's catering on set, and it can be replaced as needed, unless it's something super unusual.

BUT if you eat the food in one shot you need to eat it in all the shots for continuity, so you can edit it together. Get ready to start barfing after 40 big bites of the same damn thing.

If you look closely, you'll also see the coffee/tea cups actors sip from are usually empty. Can't afford the risk of accidentally spilling liquid on the costume and delaying the shoot.
by mantra2 | 2025-09-03 03:11:26+00:00
I am, yes. It worked as I described up until I think October of last year.

I’m logging in and out of client accounts - often for services that don’t do delegate access - so private windows work nice for me to make sure that I’m always cleared out of what I was working on before changing to a different project. Often I copy things in private windows that aren’t secrets, it just happens to be how I used the feature.

Containers and Profile are great - but - I’m not trying to have 50+ of them at work, much easier to flip open a private window.

I acknowledge my usecase is unusual and for most I think the feature makes sense - I just want to be able to turn it off, an about:config would be fine.
by mindwok | 2025-09-03 03:12:06+00:00
IMO “junior developer who doesn't learn“ is not quite right. Claude is more like an senior, highly academic engineer who has read all the literature but hasn't ever written any code. Amazing encyclopaedic knowledge, zero taste.

I've been building commercial codebases with Claude for the last few months and almost all of my input is on taste and what defines success. The code itself is basically disposable.
by eklitzke | 2025-09-03 03:12:44+00:00
I agree. If you actually know what you're doing you can use perf and/or ftrace to get highly detailed processor metrics over short periods of time, and you can see the effects of things like CPU stalls from cache misses, CPU stalls from memory accesses, scheduler effects, and many other things. But most of these metrics are not very actionable anyway (the vast majority of people are not going to know what to do with their IPC or cache hit or branch hit numbers).

What most people care about is some combination of latency and utilization. As a very rough rule of thumb, for many workloads you can get up to about 80% CPU utilization before you start seeing serious impacts on workload latency. Beyond that you can increase utilization but you start seeing your workload latency suffer from all of the effects you mentioned.

To know how much latency is impacted by utilization you need to measure your specific workload. Also, how much you care about latency depends on what you're doing. In many cases people care much more about throughput than latency, so if that's the top metric then optimize for that. If you care about application latency as well as throughput then you need to measure both of those and decide what tradeoffs are acceptable.
by zbentley | 2025-09-03 03:12:45+00:00
I don't love Python's async API either, but I think a lot of its complained-about complexity arises from two things: making "when does the coroutine start running" a very explicit point in code (hence the Task/awaitable-function dichotomy), and how it chooses to handle async cancellation: via exceptions.

And Python's async cancellation model is pretty nice! You can reason about interruptions, timeouts, and the like pretty well. It's not all roses: things can ignore/defer cancellations, and the various wrappers people layer on make it hard to tell where, exactly, Tasks get cancelled--awaitable functions are simple here, at least. But even given that, Python's approach is a decent happy medium between Node's dangling coroutines and Rust's no-cleanup-ever disappearing ones (glib descriptor: "it's pre-emptive parallelism, but without the parallelism").

More than a little, I think, of the "nobody does it this way" weirdness and frustration in Python asyncio arises from that. That doesn't excuse the annoyances imposed by the resulting APIs, but it is good to know.
by apetresc | 2025-09-03 03:13:16+00:00
Can someone ELI5 what Statsig actually is? Their landing page is full of gems like "Turn action into insights and insights into action" and "Scale your experimentation culture with the world's leading experimentation platform" so I have no clue. It appears to be another analytics + A/B testing platform, but surely that can't be worth $1.1B to OpenAI?
Is government OHS spending directly tied to workplace fatality outcomes?
by safety-space | 2025-09-03 03:13:41+00:00
I was curious about whether higher government spend on occupational health and safety correlates with lower workplace fatality rates. So I lined up the data to 2023 where possible, and compared per-worker spend against fatality outcomes.

Some quick observations:

More OHS spend per worker often sits next to lower fatality rates, but not always.

Germany and the UK look strong on both spend and outcomes.

Japan has a low fatality rate despite very low direct spend, which suggests other levers at play.

Takeaway: spending helps, but money alone isn’t the silver bullet.

Is it a suprise that Japan wins again?

* Australia 2023: spend \~\$23 per worker, fatality rate \~1.4 per 100k

* Canada 2023: spend \~\$8–9 per worker, fatality rate \~1.6 per 100k

* France 2023: spend \~\$3 per worker, fatality rate \~2.5 per 100k

* Japan 2023: spend < \$1 per worker, fatality rate \~1.4 per 100k

* United States 2023: spend \~\$5 per worker, fatality rate \~3.0 per 100k

* United Kingdom 2023: spend \~\$7 per worker, fatality rate \~0.4 per 100k

* Germany 2023: spend \~\$33 per worker, fatality rate \~0.8 per 100k

* New Zealand 2023: spend \~\$18 per worker, fatality rate \~2.5 per 100k

* South Korea 2023: spend \~\$9 per worker, fatality rate \~5.0 per 100k
by yoyohello13 | 2025-09-03 03:13:49+00:00
Same for me. I’ve got a Voyager as my main keyboard and I use Colemak. I didn’t have any fatigue or anything, I was just curious what all the hype with alternative layouts was about.

I’m about the same speed as I was on qwerty, but my back and shoulders feel a lot better with the split keyboard. It feels really good to type with an alternative layout, but I wouldn’t necessarily recommend it, the learning process was pretty arduous for me, and I’ve kind of lost my ability to use qwerty.

I would definitely recommend a split keyboard though. The ergonomics are much better.
by rtpg | 2025-09-03 03:13:53+00:00
This bugged me for a while but two things came to play for me:

- humidity and the generally mold-friendly conditions of Japan means that not doing wrapping of certain food in small packs means you’re risking food waste. And generally speaking food hygiene issues can be avoided

- if you look up how much plastic is actually needed to wrap something in plastic, it’s not that much material. A single Lego brick is more plastic than a loooooot of Saran wrap.

It’s good to reduce waste when possible, but I do get the health/food waste concerns. And to Japans credit, I’ve found that plastic packaging for like… products tends to be way less than equivalent plastic packaged products abroad in many cases IME. My Sony earbuds came entirely in cardboard packaging! No fancy thick printed box either, just some thin simple paper material.
by AlexanderTheGr8 | 2025-09-03 03:15:19+00:00
Apple stock is up 3%, strongly implying that this ruling is good for Apple as well. That is in contradiction to a lot of folks saying that this ruling means Google won't have to pay Apple. While the terms of the deal with Apple will likely change, based on the stock price increase, Apple will likely end up with a different deal (if not better).

Another thing to note, contrary to some comments, is that Google is still allowed to make a deal with Apple to be the default search engine, but with extra rules.

``` Google also would be permitted to pay Browser Developers, including Apple, to set Search as the default GSE, so long as the Browser Developer (1) can promote other GSEs and (2) is permitted to set a different GSE on different operating system versions or in a privacy mode and makes changes, if desired, on an annual basis. ```
by Jcampuzano2 | 2025-09-03 03:15:35+00:00
If devs salaries are so crazy its quite the opposite. NOT investing 1-1.5k/mo to improve their productivity by a measurable amount would quite literally be just plain stupid and I would question your boss ability to think critically.

Not to mention - while I know many don't like it, they may be able to achieve enough of a productivity boost to not require hiring as many of those crazy salaried devs.

Its literally a no-brainer. Thinking about it from just the individual cost factor is too simplified a view.
by nine_k | 2025-09-03 03:16:31+00:00
Threads are more expensive and slow to create. Submitting a task to a thread pool and waiting for a result, or a bunch of results, to show up, is much more ergonomic. So `async` automatically submits a task, and `await` awaits until it completes. Ideally `await` just discovers that a task (promise) has completed at that point, while the main thread was doing other things.

Once you have this in place, you can notice that you can "submit the task to the same thread", and just switch between tasks at every `await` point; you get coroutines. This is how generators work: `yield` is the `await` point.

If all the task is doing is waiting for I/O, and your runtime is smart enough to yield to another coroutine while the I/O is underway, you can do something useful, or at least issue another I/O task, not waiting for the first one to complete. This allows typical server code that does a lot of different I/O requests to run faster.

Older things like `gevent` just automatically added yield / await points at certain I/O calls, with an event loop running implicitly.
by mdaniel | 2025-09-03 03:16:31+00:00
I've always heard the theory that if you're not ashamed of your launch announcement then you've launched too late, but a page with just "Book a Call" is stretching the plausibility for who could possibly be in the target demographic

I know dang is going to shake his finger at me for this, but come on.

Also:

> AWS emulator

isn't doing you any favors. I, too, have tried localstack and I can tell you first hand it is not an AWS emulator. That doesn't even get into the fact that AWS is not DevOps so what's up: is it AWS only or does it have GCP Emulation, too?

That's my whole point about the leading observation: without proper expectation management, how could anyone who spots this Launch HN possibly know if they should spend the time to book a call with you?
by bee_rider | 2025-09-03 03:18:44+00:00
I think it was a brilliant and evil trick by the linear algebra folks.

Start the path at calculus. Naturally, this will lead to differential equations. Trick the engineers into defining everything in terms of differential equations.

The engineers will get really annoyed, because solving differential equations is impossible.

Then, the mathematicians swoop in with the idea of discretizing everything and using linear algebra to step through it instead. Suddenly they can justify all the million-by-millions matrices they wanted and everybody thinks they are heroes. Engineers will build the giant vector processing machines that they want.
by rich_sasha | 2025-09-03 03:18:59+00:00
Cancellations probably caused more bugs in my async code than anything else.

If any code in your coroutine, including library code, has a broad try/except, there's good chances that eventually the cancellation exception will be swallowed up and ignored.

Catch-all try/except of course isn't the pinnacle of good software engineering, but it happens a lot, in particular in server-tyoe applications. You may have some kind of handler loop that handles events periodically, and if one such handling fails, with an unknowabl exception, you want to log it and continue. So then you have to remember to explicitly reraise cancellation errors.

Maybe it's the least bad Pythonic option, but it's quite clunky for sure.
by yoyohello13 | 2025-09-03 03:19:02+00:00
I use colemak so a lot of keybinds in programs are similar enough to not be too bad. Vim was surprisingly easy to adjust to, although hjkl are in terrible positions in colemak. It’s kind of nice though because it forces you not to rely on hjkl too much. For games, I usually just switch back to qwerty.
by AlexanderTheGr8 | 2025-09-03 03:20:39+00:00
To add on: a 3% stock shift means that the search-engine deal was worth >=3% of the stock. That is massive free cashflow. In 2022, Google paid Apple $20B (full profit bec negligible costs) while Apple's total profit was around $100B. 20% of Apple's total profit came from Google's search deal. Based on this, I am sure the stock price worth would be much higher than 3% (actual numbers are complicated because stock price accounts for future growth of things).
by nothrabannosir | 2025-09-03 03:20:50+00:00
Your position would be eminently reasonable if this comment thread were kicked off by a blog post called "Evil Corpos are Bad Guys, They Should Accept AGPL! A Treatise Out Of Nowhere."

Corporations are free to do as they choose. They can choose not to use AGPL software. That's ok, they don't owe anyone anything (arguable but let's go with it), and I'd have no leg to stand on.

But that's not what happened here. Look at the quote that kicked off this thread:

> Shame on the people who recommend the AGPL to effectively be an OSI-approved source-available license.

> This is a grievance against the spirit of open source.

Note "Shame" and "the spirit of open source." Someone kicked off this thread painting authors of AGPL software as going against the spirit of open source for promoting a license which they know big corporations shun.

At that point it's a very different context. Remember how corporations don't owe anyone anything? Neither do free software devs. That entire comment is completely wrong, and the entire thread which followed only exists in its context. Not outside. And inside that context, it is absolutely valid to talk about the spirit of open source, to talk about what "should", etc, because that's the context introduced by the comment itself.

"Software freedom" doesn't just "enter" the discussion--it is the discussion.
by mikepurvis | 2025-09-03 03:21:50+00:00
I had my residential waste pipe lined with a fibreglass/resin sheath about a year ago. Inserting it was a process involving a lot of work on endoscopes and then the liner itself was adhered to the old pipe using a bladder filled with hot water. See: https://en.m.wikipedia.org/wiki/Cured-in-place_pipe

It was over CA$10k to get it done, but the cost of trenching that line could have been 3-4x the amount + an unacceptable risk to the foundation of the house from destabilizing the dirt around it.
by conartist6 | 2025-09-03 03:22:36+00:00
I read that part. The court mandates a search engine choice screen initially for each device, then once a year afterwards. Google is allowed to pay for advertising on this screen.

It seems to me that at very least Mozilla will have to renegotiate a contract and it's not clear what they might make off selling ads in that space. Google will presumably not value the lesser advantage as highly, but if the other provisions create more search engine competition there could be growing value to Mozilla in that ad real estate in theory
by vivzkestrel | 2025-09-03 03:24:53+00:00
i have never seen a messenger app made by anyone that was capable of migrating all the existing users and their chats from another platform instantly. the day someone makes this, its gonna get traction by a mile compared to anything else out there. imagine clicking "import from messenger" and boom all users and chats from messenger added and clicking "import from whatsapp", "import from wechat" you get the idea
by mdaniel | 2025-09-03 03:25:21+00:00
If you haven't seen it, there's also https://addons.mozilla.org/en-US/firefox/addon/temporary-con... (https://github.com/stoically/temporary-containers MIT) when you don't care about the containers but do care that their browsing context is isolated. The screenshot even shows the handy "delete temporary container 15 minutes after the last tab closes")

Actually, sorry, it seems to be https://addons.mozilla.org/en-US/firefox/addon/temporary-con... and https://github.com/GodKratos/temporary-containers) based solely on the language present in the add-on and commit history
by justsomehnguy | 2025-09-03 03:25:48+00:00
> As I recall it, Intel brought about Hyperthreading on Northwood and later Pentium 4s as a way to help with issues in it's long pipeline.

Well, Intel brought Hyperthreading to Xeon first and they were quite slow, so the additional thread performance were quite welcome there.

But the GHz race was lead to the monstruosity of 3.06GHz CPUs where the improvement in speed didn't quite translated to the improvement in performance. And while the Northwood fared well (especially considering the disaster of Willamette) GHz/performance wise, the Prescott wasn't and mostly showed the same performance in non-SSE/cache bound tasks[1], so Intel needed to push the GHz further which required a longer pipeline and brought even more penalty on a prediction miss.

Well, at least this is how I remember it.

[0] https://en.wikipedia.org/wiki/List_of_Intel_Xeon_processors_...

[1] but excelled in the room heating, people joked what they even didn't bother with an apartment heating in winter, just leaving a computer running
by eduFreedom | 2025-09-03 03:26:16+00:00
Yes, I do, and I'd say the opposite. I started using incremental reading after using Anki for 11 years, and now, five years later, there is no way I would go back to the Anki style.

You can check my YouTube channel, 'Pleasurable Learning', for a course and many videos on how to get started with incremental reading.
by SAI_Peregrinus | 2025-09-03 03:26:28+00:00
I think the heuristics are stupid, but happen to work with the current round of LLMs. The next round of training will work to stop the heuristics working, since if they work it means the LLM isn't correctly guessing the next token a human would produce. I don't think LLMs will become indistinguishable from humans any time soon, but I think it'll be a very long back & forth of training & finding new heuristics.