HN user
Get off my lawn
As a member, the gas savings pay the annual fee, and I get my staples from Costco every few months. Peanut butter, paper towels, TP, tissues, and sometimes mushrooms and washed greens.
Everything else I'd rather get from my local grocery stores.
Can you elaborate on SELinux? It affected me too but I just had to add :Z to my mount argument. Curious about whether there's further impact I'm unaware of.
I presume he's exhilarated that the government is taking the threat seriously and banning foreign nationals from accessing these super dangerous tools.
Congratulations, Dario!
Thank you for sharing these wonderful stories!
You're also not paying to search on Google.
Did you read what you shared?
It’s talking about security cameras, low-bitrate video.
FTA: "Myth Busted: At security camera bitrates (400-800 Kbps), H.265 provides negligible compression benefits. The marketing claims of "50% savings" apply only to high-bitrate content like 4K movies at 25+ Mbps, not security cameras."
Still they are not notes, which means GP continues to be valid.
This is exactly what I meant. It's not the ability to build things; of course you can.
The progress has been in agreeing on a coherent interface everyone uses and which handles 99% of what most projects need with minimal friction.
That's a fair question. It's part ecosystem, part tooling. The ghcup, stack, cabal mishmash is closer to maven than a tool with a modern streamlined UI like cargo.
And yes, Haskell is significantly more expressive than Rust--at the cost of performance.
As someone who loves Haskell more than any other language, some challenges are
- the tooling is decades behind, say, Rust or Go
- finding the right library in looks very different in Haskell--you frequently start with the signature on Hoogle. Agents can learn this but it's not the same as "web search"
- creating the right solution also looks different. It's usually borne out of thinking about the types and coming up with the correct algebra. Again models can probably learn to create the right types and orient the solution around that, but it's not automatic
- same today as yesterday, laziness is a blessing and a curse. The runtime can do unpredictable things when you suddenly evaluate a deep thunk
- GHC directives effectively mean there are multiple "Haskells"
Some of those are a result of the "avoid success at all costs" mantra. You can't shake that off in a day. It will take a concerted effort to make it more amenable for seamless adoption.
Haskell continues to be my favorite language to write and read, but Rust is the more practical language with a rich type system. If you're looking for something approaching Haskell's expressiveness but with fewer of these issues, check out PureScript.
Every time I see a post about the TI calculators, I think about how much I dislike their interface, and it's all because I started out on a Casio.
It's usually a small amount of waste, and handling gas is very different from distillate.
You'd need to either liquify that gas or collect it to a pipeline in order to make it useful. I remember reading that modern refineries make use of the gases instead of flaring them though I'm not sure how.
If your mind goes to TLS when you read crypto, you surely do live under a rock ... in bliss.
That is understandable, but the issue is the sudden drop in quality and the silent surge in token usage.
It also seems like the warning should be in channel and not on X. If I wanted to find out how broken things are on X, I'd be a Grok user.
That's what I've done for years.
Long pressing is much more pleasant.
I wish Apple would give us a hint rather than requiring us to chance upon this recommendation on HN.
Well it's good to be honest, and so I commend you on that.
So the hierarchy is
- our kids
- "third-world orphans"
- other species
For what it's worth, I'm not denying the benefit we obtain by testing on animals, nor am I suggesting that we live surrounded by rodents that we know to be vectors for multiple diseases that would affect us.
The comment above was merely an observation on the value of life and how little attention we pay to it.
We subject sentient beings to untold amounts of horror every day, and we are completely destroying the balance of life on earth with a system that is entirely devoted to serving humans--individual humans, not humanity.
The statue is not the point. The point is what this little creature did and how we might learn to show mercy and respect to our fellow sentient beings.
These are the creatures we kill with poison and carry experiments on.
Rick Roderick on Habermas.
The series "Self Under Siege" is one of my favorite things on YouTube. Highly recommend watching all 8 in order.
Stealing this brilliant idea. Thank you for sharing!
That's the first thing that came to mind when I saw this website. The Bay Area is famous for its numerous superfund sites (among many other things, thankfully).
It's good to see just how far we can push the mods here until we finally face consequences!
Thank you for keeping this place healthy day after day after day.
Isn't that literally every modern OS, always, unless you tell it to act differently?
Same reaction. I can't even say the author is correct/wrong because I couldn't get through it.
With the AI. I read the whole thing and correct the model where it makes mistakes, fill the gaps where I find them.
I also always check that it explicitly states my rules (some from the global rules, some from the session up until that moment) so they're followed at implementation time.
In my experience opus is great at understanding what you want and putting it in a plan, and it's also great at sticking to the plan. So just read through the entire thing and make sure it's a plan that you feel confident about.
There will be some trial and error before you notice the kind of things the model gets wrong, and that will guide what you look for in the plan that it spits out.
I tried it when it first came out and it was lacking then. Perhaps it's better now--will give it a shot when I sign up for cursor again.
Thank you for sharing that!
My suggestions:
- like the sister comment says, use the best model available. For me that has been opus but YMMV. Some of my colleagues prefer the OAI models.
- iterate on the plan until it looks solid. This is where you should invest your time.
- Watch the model closely and make sure it writes tests first, checks that they fail, and only then proceeds to implementation
- the model should add pieces one by one, ensuring each step works before proceeding. Commit each step so you can easily retry if you need to. Each addition will involve a new plan that you go back and forth on until you're happy with it. The planning usually gets easier as the project moves along.
- this is sometimes controversial, but use the best language you can target. That can be Rust, Haskell, Erlang depending on the context. Strong types will make a big difference. They catch silly mistakes models are liable to make.
Cursor is great for trying out the different models. If opus is what you like, I have found Claude code to be better value, and personally I prefer the CLI to the vscode UI cursor builds on. It's not a panacea though. The CLI has its own issues like occasionally slowing to a crawl. It still gets the work done.
I feel so weird not being the grumpy one for once.
Can't relate to GP's experience of one-shotting. I need to try a couple of times and really hone in on the right plan and constraints.
But I am getting so much done. My todo list used to grow every year. Now it shrinks every month.
And this is not mindless "vibe coding". I insist on what I deploy being quality, and I use every tool I can that can help me achieve that (languages with strong types, TDD with tests that specify system behaviour, E2E tests where possible).
What has worked for me is having multiple agents do different tasks (usually in different projects) and doing something myself that I haven't automated yet.
e.g. managing systems, initiating backups, thinking about how I'll automate my backups, etc.
The list of things I haven't automated is getting shorter, and having LLMs generate something I'm happy to hand the work to has been a big part of it.
Fair enough, though I feel so entirely differently that your position baffles me.
Gleam is still new to me, but my experience writing parsers in Haskell and handling error cases succinctly through functors was such a pleasant departure from my experiences in languages that lack typeclasses, higher-kinded types, and the abstractions they allow.
The program flowed happily through my Eithers until it encountered an error, at which point that was raised with a nice summary.
Part of that was GHC extensions though they could easily be translated into boilerplate, and that only had to be done once per class.
Gleam will likely never live to that level of programmer joy; what excites me is that it’s trying to bring some of it to BEAM.
It’s more than likely your knowledge of type systems far exceeds mine—I’m frankly not the theory type. My love for them comes from having written code both ways, in C, Python, Lisp, and Haskell. Haskell’s types were such a boon, and it’s not the HM inference at all.
With all due respect, you can use all of those languages and their type systems without recognizing their value.
For ensuring bits don't get lost, you use protocols like TCP. For ensuring they don't silently flip on you, you use ECC.
Complaining that static types don't guard you against lost packets and bit flips is missing the point.