pythonaut_16

Presumably the site owner with Cloudflare providing enforcement.

Generally isn't a good bot one that respects robots.txt and is respectful of the site's resources by not being spammy?

These are valid push-backs on the "postgres everywhere" argument.

The two critical questions IMO are:

1. At what scale do these issues arise? 2. Does Postgres make it harder to solve them when you reach that scale than another solution would have?

Some of that probably depends on the libraries or tools you use on top of Postgres but being able to easily swap to Redis or a proper queue at scale should mitigate the risk of starting with Postgres if you don't already have the scale.

Is this a bot or LLM reply? Because you've given this exact comment word for word at least twice in this thread...

The problem is that argument is indistinguishable from the argument "the lack of proof is the proof!"

It literally does though? GP said they'd never seen anyone achieve anything interesting.

The person you're replying to said they know someone who closed a few deals as a result of their OpenClaw. How is that not interesting?

It doesn't prove that it's globally useful, well implemented, or even worth the cost/effort. But it is something interesting.

Within the first second it's recognizable as a Suno song. And not even the best example from Suno. (They rhyme structure and rhythm is weird)

Seems like a bunch of noise. What does this even mean?

It sounds like you're saying "Actually you, as a human, are simply not smart enough to evaluate Opus 4.8"

It has seemed to me that with each step from Opus 4.6, to 4.7 to 4.8 Claude has gotten worse at building good solutions. Like perhaps it is more "capable" in the small scale than 4.5 was but it's much worse at knowing what to do.

Dojjjo, pronounced do-jj-jo

Seems like a strong signal the money burning party is coming to a close.

One provider who was undercutting the market with non-standard billing model moving to a more standard billing and prices doesn't seem like that strong of a signal, other than that Copilot was underpriced.

I don't disagree with your other points though.

At this point RAM prices dwarf everything else in a system, at least for me

Why are you mad that they're trying to build brand recognition?

I get there's been plenty of vaporware cars in the past but by all signs Slate is making real progress towards delivering actual vehicles.

Arguably more accurate is that it pivoted from colonising Mars to Elon's personal piggy bank to bail out his other failing bets.

SpaceX was surely more profitable before it was used to bail out Elon's xAI which was used to bailout his purchase of Twitter.

strictly speaking, it was working before and now it isn't

I've been seeing more things like this lately. It's doing the weird kind of passive deflection that's very funny when in the abstract and very frustrating when it happens to you.

Imagine you have 3 branches: local-dev-tuneup, bugfix-a, feature-b

Remember in JJ you're always "in a commit", so the equivalent of the git working tree (i.e. unstaged changes in git) is just a new commit, often with no description set yet. (Because in JJ a commit also doesn't need a description/commit message immediately).

So in a mega-merge you can have a working tree that pulls from local-dev-tuneup, bugfix-a, and feature-b, and you can then squash or split changes out of it onto any of those source branches. Like you can avoid serializing those branches before you're ready to.

I've definitely faced the scenario in Git where I have a unmerged changes that I want to use while continuing work on a feature branch. I end up creating a PR for the branch of the first smaller features (e.g. local-dev-tuneup->master), then a second PR pointing at the first (feature-a -> local-dev-tuneup). It works but it's all a bit cumbersome, even more so if feature-a ends up needing to land before local-dev-tuneup. JJ has better tools for handling this.

Or potentially a team member has critical changes with a PR open and you want to start building on top of their changes now. Manageable in Git but you're locked in on a branch of their branch. Now add a second set of critical changes. Can be done in git but you'll be jumping through hoops to make it happen.

Of course you might say that all indicates a workflow/process problem, but my experience is this situations are common enough but not frequent.

(I haven't actually used megamerges myself yet but the article has me ready to try them out!)

not hype

Proceeds to write the hypiest comment possible. No substantial claims of why the model is not hype, just how dangerous it would be if the weights leaked and how cheap it would be for anyone to just start using it for EVIL if it ever did.

I don't think you've nailed it either. He SHOULD be saying "54 days ago, I powered on my computer and opened a terminal. From my editor I reviewed my code files and realized I had quite a mess on my hands. Realizing it was the year A.D. 2026, I decided to fire up a modern tool. I typed "claude" into my terminal. As it launched I told it I wanted helping taking my running programs and moving them from the virtual private servers I was running in Linode (inc) and Digital Ocean (co) to Hetzner (LLC). As Claude used it's tool use abilities it read the files and made suggestions on how to do the migrations, it indicated that it could go ahead and copy the files and run the needed commands but I would need to give it permission first. I granted it permission. Once it said the services were running, I instructed it to test that they were accessible and reliable while I reviewed the glowing new code it had written. In summary, with the help of Claude Code I was able to redeploy 37 services in Hetzner."

That basically means nothing. The article is very light on details.

Go into Claude right now. What does it have? Internet access after you prompt it.

Ok now pull out your phone, a credit card, a security camera. You can say "Claude these are yours, run a business", but nothing's going to happen until you build an actual harness.

Like the idea presented by the article is interesting, but it's basically just a fluff piece. The actual interesting article would have way more detail.

Heuristically they'd be right to say that though.

If you start a new job and on your first day they go "Yeah the last guy said we don't need a database, so he rolled his own." are you gonna be excited, or sweating?

Exception being perhaps "The last team chose to build their own data layer, and here's the decision log and architecture docs proving why it was needed."

we just wrote proprietary files to disk

That alone is a terrible thing. Open formats are so much more user friendly

If your language supports it, what is the overhead of working with SQLite?

What's special about SQLite is that it already solves most of the things you need for data persistence without adding the same kind of overhead or trade offs as Postgres or other persistence layers, and that it saves you from solving those problems yourself in your json text files...

Like by all means don't use SQLite in every project. I have projects where I just use files on the disk too. But it's kinda inane to pretend it's some kind of burdensome tool that adds so much overhead it's not worth it.

I use a local garagefs on my NAS for small/new side projects, and it’s on my Tailscale for easy access

- Lets me deploy stateless containers easily

- Let’s me leverage the NAS for local redundancy and a more centralized place to do backups

- When a project grows it’s easy to promote it to use a hosted S3

- Local S3 becomes a target for Litestream and Restic

- Developing against the local fs and then handling file storage is a huge friction, unless I’m using something like Rails that already has a good abstraction

I also like `jj commit [paths]` to commit just a subset of files when I don't need hunk based splitting.

Like `jj commit -m 'Feature A' file1 file2` then `jj commit -m 'Feature B' file3 file 4`

Very cool! I've been spiking out something similar using Rust+Lua rather than Go, and pulling from Django for inspiration in addition to Pocketbase.

This question is a deflection and I suspect is intentionally disingenuous since it literally ignores the main point of the parent's comment.

That seems like a contextual problem, not a Lua problem.

If you're in Love and/or control the environment you're free to bring in whatever libraries you want. Or to build your wrapper to support multiple files from the user.

Like you could suffer from a bad embedded scripting setup with any language. Granted if it was embedded Python or Javascript you would get a bit more for builtin if they embed a full implementation. But also embedding Lua with support for user supplied libraries is less effort than embedding a whole Python/JS runtime

I don't see how you can say Bluesky/ATProto is essentially a Twitter clone and turn around and just assume that Mastondon/ActivityPub is not essentailly just a Twitter clone.

I don't think the GPs point is about personal safety of workers, but rather critical safety systems that rely on one person with no backups. Like an ATC tower for a busy airport staffed by a single person on an overnight shift.

A painter who does a bad job setting up a ladder is going to have a bad time, a lone ATC operator having a heart attack potentially puts multiple large aircraft full of people in danger...

Makes me want to name a project or company Sauron in response.