max_streese

To me this goes in the same direction as people not feeling sorry for software developers because our job is supposedly automating the job of other people (which I don't think describes the profession accurately as a whole at all).

Neither sits right with me. Can't we just all collectively acknowledge that we have to grapple with this new piece of technology that either is already or at least seems to be going to be hurtful to a lot of individuals?

Instead of looking at the in comparison limited group of people currently pushing this technology and asking ourselves whether we should be on board with their doing, we look to one another and are happy that someone else is now suffering just the same as we are. What a sad state of affairs.

Assuming writing code by hand is slower (which I agree with), why can't it still have merit compared to code written via llm harness?

To people stating these high commit numbers: What is your average changeset size? I have found that having agent do large changes (few hundred lines or more) results in a lot of friction for me and it feels like at some point I leave a happy path where instead of moving quickly I get dragged down.

One thing I am wondering: How much logic (in the programming sense) is there in this product and how much of it is „just“ a lean wrapper around the LLM?

Hi HN, I am wondering if with the recent push for CLIs rather than MCPs people have heard of or are using Restish for creating their own CLIs for APIs?

The thing lets you create a single CLI for any number of APIs following OpenAPI v3 or JSON Schema. I've tested if with our self-hosted Grafana and it does work, though I am not sure if it is as good as the Grafana MCP.

Anyway, it seems perfectly positioned for the CLI over MCP push, while sitting at 1.2k GitHub stars which is tiny by AI standards. So I am wondering if there is more nuance in CLI over MCP here or if other solutions exist?

(Note: I am not in any way affiliated with the project, I just think its neat and interesting)

And if we do adapt we might still get replaced because less of us will be able to do more. Or we wont because of Jevons Paradox. Linux maintainers on the other hand can code (with and without AI) what I could not (with or without AI). So in a way becoming a more knowledgeable, more skilled programmer is the way? In any case, too much speculation about the future.

Two questions:

(1) Are there any plans to make this compatible with the ducklake specification? Meaning: Instead of using Iceberg in the background, you would use ducklake with its SQL tables? My knowledge is very limited but to me, besides leveraging duckdb, another big point of ducklake is that it's using SQL for the catalog stuff instead of a confusing mixture of files, thereby offering a bunch of advantages like not having to care about number of snapshots and better concurrent writes.

(2) Might it be possible that pg_duckdb will achieve the same thing in some time or do things not work like that?

GDP?

How are you folks related to Anguilla? Couldn’t really find anything AI specific about OpenObserve so I am guessing the domain is for other reasons?

The article itself states this too (though without the undertone). To me this does not undermine the research though. Why would it?

Is it just me or do others find the Electron bashing a little over the top as well?

I mean VS Code, Discord, Slack and Obsidian are all in very widespread use and work perfectly fine for me.

Are there alternatives to Electron that require less resources? Tauri seems to be proof that there are.

But I think there is real value in large communities and backing. Electron seems to work perfectly fine to me for everyday use as is evident by the applications mentioned above. I would personally choose Electron over Tauri even for greenfield projects, simply because Electron seems to power applications that are in much more widespread use.

Is it just me or do prices for a lot of UI/design resources seem high compared to prices of resources on other parts of IT? 100 $ for a 218 page PDF seem quite steep to me.

Awesome, thanks so much!