submain

NVidia seems to want them. They have a lot of lobbying power.

Not op, but I use it for seeing the joystick + throttle and the "real" instruments in flight simulator.

The investors will get their money back on the IPO. They'll dump all their stocks in the market and run away, leaving retail with the bill.

I think that's a fair take. We could also frame it as society in the past has carried a lot of the burden of raising kids.

Tribes and communities helped raise kids. That's no longer true in an individualistic and institutionalized society.

Is that enough though? Women change their entire bodies, sacrifice years of their lives, and go through considerable stress to have a baby. And at the end, the benefits of that ordeal are not clear.

Society would need to offer something to offset all those costs.

I agree. It comes down to the opportunity cost for women to have babies.

On pre-industrialized societies, women have barely a choice. On industrialized ones they do. And it turns out that, when given the choice, they choose not to have babies.

It seems to me China is chasing widespread adoption, while the US is chasing the AGI dream.

I have been doing this and the results have been fairly good.

I use claude to build requirements.md -> implementation.md -> todo.md. Then I tell opencode + openrouter to read those files and follow the todo using a cheap (many times free) model.

It works 90% of the time. The other 10% it will get stuck, in which case I revert to claude.

That has allowed me to stay on the $20/month claude subscription as opposed to the $100.

Great work :). Go doesn't have TCO. That means functional languages (no for loops) could blow up the stack. How did you solve that?

And don't even let me get started on how bad Claude client has become

The latest versions of claude code have been freezing and then crashing while waiting on long running commands. It's pretty frustrating.

bots perhaps? Anyways, mods should remove this post.

If you search for problems on linux, you will get much higher quality answers.

Not only that, but in the past I've cooked hacky bash scripts to work around issues while waiting for upstream fixes. I'd imagine that'd be harder with other OSs.

I usually define functional programming as "how far away a language is from untyped lambda calculus". By that definition, different languages would fall in different parts of that spectrum.

The real secret to agent productivity is letting go of your understanding of the code and trusting the AI to generate the proper thing

The few times I've done that, the agent eventually faced a problem/bug it couldn't solve and I had to go and read the entire codebase myself.

Then, found several subtle bugs (like writing private keys to disk even when that was an explicit instruction not to). Eventually ended up refactoring most of it.

It does have value on coming up with boilerplate code that I then tweak.

"Magic Leap raises $827M in Series C". Aged like wine.

This is great! Coincidentally, I just started replacing my collection of bespoke security bash scripts with an app like yours. WIP here: https://github.com/leolimasa/age-vault

We all keep reinventing the same thing :)

Yeah, I run macos for the same reason.

However, I went back to linux on my personal laptop (nixos on my case) and I am pleasantly surprised how many things now just work.

The only thing that still annoys me is the laptop not sleeping properly and therefore using too much battery power when idle.

It has made great strides on the last two or so years.

This echoes my sentiment that LLMs are higher level programming languages. And, as every layer of abstraction, they add assumptions that may or may not fit the use case. The same way we optimize SQL queries by knowing how the database makes a query plan, we need to optimize LLM outputs, specially when the assumptions given are not ideal.

Type checking is indeed an advantage of ORMs. You pay for it with object relational impedance mismatch. That impedance grows as your schema grows.

In my experience, the way to get the best of both worlds is to use a query builder as opposed to a full ORM.

ORMs are one of those things that make sense for really tiny projects but fail to scale once complexity settles in.

I love doing research. I published a minor unimportant paper in undergrad and had a blast doing it.

Then at graduation I was offered a well paid job in the industry. Decided to pursue it as opposed to spending 5-6 more years in academia looking for grants.

Would love to go back and get a PhD, but the economics just don't make sense for me. For now, it's a retirement plan.

What does windows 7 do that windows 10 doesn't? Why does the same web page need 60MBs to load when it only need 1-3MB 10 years ago.

Ads. And tracking code to serve you ads. And AI - that collects your prompts to serve you more ads.

\s

This is great! How does it compare to silverbullet (https://silverbullet.md/)?

As a manager, if upstream changes priorities on me but what we’re working on is almost done, I just go ahead and finish it anyways.

When they eventually switch back to the original thing they are always surprised to know it’s been completed.

I am not familiar with LiveView, so I'm curious. Looks like it processes UI actions server side.

So, are all client interactions sent through the websocket? I remember years/decades ago we used to do that with ASP.NET, where every single component interaction was handled by the server. How is this different / better?

just like you don't roll your own crypto, you don't roll your own date libraries.

His book "A new kind of science" is quite fascinating and has some interesting ideas about cellular automata. But I couldn't finish it because of how every few pages there is something about how great the author/his ideas are.

Quite the opposite actually. My developers barely touch their tickets. Most of the updates are done rather informally. They mostly interact with git and I make sure things are tracked.

You’ve used quite strong words there.

I share the sentiment and frustration of having to fill useless boxes.

However, as a manager, things go south very quick if you're not tracking what's being changed and by whom. You won't know what's included in your release, nor if it was tested properly. You won't know who to reach for fixes after testing or even what to tell clients when they ask if a feature/fix was shipped.

I hate overly complicated processes, but tracking things is essential.

As someone who worked at a fortune 500 company making such EMR software:

There's no incentive to make the UI or workflows better. They don't pay the bills. Software is sold to the suits during dinners and baseball games, not doctors or nurses.

Besides, a great portion of the development is outsourced chasing lower costs. The code reviews were so bad that a coworker used to joke that "we'd get more stuff done if we just fired the overseas team".

The biggest and most well funded dev team was the one that worked on Revenue Cycle.

I quit a few years ago and haven't looked back.