clivedup
A "real performance bottleneck that I observed during testing" is a little bit unclear whether it occurred outside of test conditions, or whether speeding up that particular bit improves anything anyone cares about.
Can I do that with Jason's reference implementation?
Let people build. They might have reasons you haven't foreseen.
I didn't mention determinism or predictability.
I said "It feels like playing factorio: whatever is manual needs to be automated away.".
I'm sure you can find many differences between Factorio and what I'm doing.
> If you gave an engineer a non-deterministic solution and a deterministic solution to the exact same problem, which do you think they would prefer? Would they willingly remove determinism from a system?
We choose non-determinism in our systems a lot, because we get better outcomes in other aspects.
* Non-deterministic network latency: Packet switching rather than circuit switching.
* Multi-tasking operating contending for the same resources.
* Multi process programs whose interleaving/execution is non-deterministic.
* Profile guided optimisation, depends on the profile.
* The entire field of randomised algorithms.
I prefer deterministic processes, but if the benefits of non-deterministic processes are significant enough, I pick non-deterministic.
Comedy gold.
Yes, reviewing an LLM code is at times infuriating, but at least I can be brief and direct, rather than spend 2x the effort trying to make sure it won't be interpreted as harsh.
I spend about 90% of at-computer time in a herdr-like tool.
It feels like playing factorio: whatever is manual needs to be automated away.
LLM writes the test. The test is crap. Update the skill. Ask an LLM to review your feedback on the last 5 PRs and write a skill for a review bot to look for similar problems and post. Now you only see PRs after they've gone through a few rounds of review.
The LLM has stopped picking up new issues. Ask an LLM to diagnose why. Ask an LLM to write a cron to regularly check if the LLM PR pipeline has halted and ping you. Get an LLM to try to diagnose it first.
I'm using a lot of LLMs! Ask an LLM to diagnose why. Write a tool to audit your usage, and produce a weekly report. Have it raise issue to reduce spending.
And like a base building game there are many competing facets, coming all at once.
DNSSEC is not widely deployed, and so we cannot rely on the authenticity of DNS.
Maybe if we had DNSSEC, then we could rely on it for publicsuffix. Maybe lots of others things could be more easily solved if we had that too.
DNSSEC automation is coming, e.g. https://www.rfc-editor.org/info/rfc10026/. It might never become mainstream, but don't let anyone tell you that we couldn't benefit from having DNS authenticity!
Even as an appreciator of multiple Git forges... Github seems good?
> > The NHS approach: close source everything.
> Yeah good luck. I've seen how these systems work at decompiling and I expect they're probably going to be really good at fuzzing too.
Me too. The agents are much faster if it has access to source. NHS would have been easy hunting grounds. Now at least they don't stand out.
"a system should be secure, even if everything about the system—except the key—is public knowledge"
Should indeed, but we've all been caught with our pants down.
> but maybe it has some nuance?
> eh, I think I still don't care enough to click
> but maybe I could post a funny comment
> it doesn't sound that funny, and besides, HN doesn't usually like these sorts of comments
> okay, let's just read the next story
> unless
Worse, I claimed the moral high ground. Lesson learned!
When Amazon's policies unfairly push up prices across the Internet, it deprives us from competition pushing prices down, and having a better idea of what online overheads are.
"Just see a physio" misses that:
* I want the physio's advice during workouts
* I want the physio's advice during moments of pain
* I want the physio to explain things in more detail, but my 30-60 minute appt is not enough, and it's difficult/expensive to book them for longer.
Sometimes I don't know a topic well enough to even know the right terms, or sources. But an LLM can help me become familiar with relevant concepts, and then I can more easily find the authoritative sources.
Sometimes I don't know a topic well enough to know how far it is from my understanding. An LLM helps me quickly learn how closely I have the relevant foundational knowledge: if it's absolutely gobbledygook, then I realise I've probably bitten off more than I can chew; if I half sounds familiar, then I can more confidently begin independent exploring of authoritative sources.
Flake stabilisation probably hasn't gotten any easier/more likely by LLMs, but it does make it quicker for people to pickup technology.
Technology sometimes has that odd effect. (And it will apply to different technologies in different contexts at different rates.)
Client isolation would help, but it also breaks some devices.
Are there decent daemons that allow me to allowlist which broadcast traffic to permit?
Ideally it'd be compatible with IPv6-only clients on my LAN.
Single binary. Sqlite. Minimal UI. Perfect!
Mozilla have more momentum, experience, and funding, but still struggle.
Bad call, because it's genuinely too hard for someone the size of Kagi, as they've discovered.
There's room for a Chromium fork that has a better reputation than Brave. (I use Brave, and it's great, but I realise many people don't want to use it.)
I think this is part of it. Growth is treated with skepticism in Europe.
Growth isn't "jobs, high salaries, innovation, cheap good/utilities, well funded military" there it's "pollution, inequality, big corporations".
It's no surprise that they aren't growing as fast as other regions: it's not their priority.
As the saying goes, if you aren't growing...
But there's a few things that make this trickier in Sydney, than, say, much of European cities:
* Sydney is too hot/UV to comfortably cycle between 9AM-5PM for at least 4 months of the year. Maybe tree-lined corridors could help that.
* Sydney is very hilly. It didn't have centuries of being flattened. This makes it challenging, even for experienced commuters. Ebikes could help.
* Sydney has low density: houses are big, detached, and thus spread apart. This makes relevant cycling distances further.
EVs are much more aligned with Sydney, at least for tackling the polluting issues with cars.
Australia is more than cities.
Cities can make public transport free and congestion charges if they want to reduce usage of cars.
I didn't really know the rules, but enjoyed protecting the frog.
I played a few games, and each time was protecting the frog. I wished I had a turn trying to kill the frog!
There's a spectrum of fidelity/purity in all retro computing.
This sits a bit purer than "emulate it all on RP2040", far from "physically the same chips", but practically cheap enough for many.