I refuse to take a repo with an AI-generated readme seriously. If you haven't bothered to write a readme, what else have you not bothered to do?<p>(100% AI according to Pangram btw)
Not sure why it matters? I can't tell the difference, personally, but even if I could the AI is much more likely to have given complete and accurate information than any human..
Do we have to
explain in every bloody thread why human-generated Readmes, with their faults and omissions, are preferable to overly verbose and flowery AI slop prose?<p>Conciseness and highlighting relevant points is much more important than word count. Machine generated readmes are anything but. Sorry you can’t tell the difference between that and human prose, you should try reading more human content.
[dead]
> I refuse to take a repo with an AI-generated readme seriously. If you haven't bothered to write a readme, what else have you not bothered to do?<p>I care whether the readme is any good, not who wrote it. If you haven't bothered to critique the readme and instead critique its suspected creator — something entirely in your head — what else have you not bothered to do?<p>> (100% AI according to Pangram btw)<p>So what? Who cares about Pangram? I certainly don't! You cannot detect AI — it's impossible. Perhaps it's just Kenyans?[0]<p>[0]: <a href="https://marcusolang.substack.com/p/im-kenyan-i-dont-write-like-chatgpt" rel="nofollow">https://marcusolang.substack.com/p/im-kenyan-i-dont-write-li...</a>
Why does AI-generated imply "not bothered" to you? If I take all of my design docs/specs, all of the existing repo, and I tell an agent that I'd like to make a readme that contains things X, Y, and Z, what's the problem?<p>Rejecting slop doesn't imply rejecting all AI-generated text wholesale.
> Why does AI-generated imply "not bothered" to you?<p>1. AI generated text is just hard to read and verbose, if you worked so hard on your docs/specs, why would you want your README to be unreadable?<p>2. There's so much garbage written with AI that I'm just going to assume yours also is. Would you sign up to a gym with broken windows? It could be the best gym ever, but I wouldn't count on it.
> <i>what's the problem?</i><p>I can do it. Anyone can do it. Probably better for my/their own needs than someone else’s agent can.<p>The README is meant to communicate substance and intent. Without the latter it’s an overly-verbose landing page.
If it wasn’t important enough for someone to take the time to write, it isn’t important enough for me to take the time to read.
Why does AI-generated imply "not bothered" to you? If I am not bothered to write the content, so I ask the agent to do it for me, what’s the problem?
We all know AI does not write well today.<p>What JetBrains needs is nothing short of a revolutionary product, which they would need to sell with an excellent introduction.<p>Instead they phoned it in and pasted that slop:<p>> Once a GitHub PR is open it shows the CI checks and review decision, and lets you mark it ready, hand failing checks or a diverged branch to the agent, merge it with the repository's last-used method, reopen it, or delete the remote branch.
The problem is that it’s market or care and respect. If you can’t even be bothered to while a simple readme communication your intentions, what else can’t you be bothered doing properly?<p>It’s a marker that the project is likely to be low-effort slop, which may or may not just be abandoned at the deep of a hat.
Because AI-generated README means that the person doesn't care about the audience. It means that the author never read the README themselves to see that the "load-bearing ground truths" actually reflect what the project is about, and not some hallucinated bullshit.<p>There's a famous Jobs story in which he insisted that even the insides of the computers be made beautiful. Because that shows care. Now people are arguing that even the outsides can be as ugly as they want, who cares.
> Why does AI-generated imply "not bothered" to you?<p>If it is blatant unfixed llmese, then it means that no effort whatsoever was put into making this text.
[dead]
there's no need to announce this. might as well announce you don't eat meat, or you don't like electricity.
> I refuse to take a repo with an AI-generated readme seriously.<p>Well, good luck in professional development then. Love it or hate it, this is the way everything is moving.
But why read it? Just point your agent at it and use your personalized project exploration skill.
I’ve been using JetBrains IDEs for over a decade but rarely open them anymore because working on several worktrees concurrently is extremely frustrating and wasteful. Their AI strategy is all over the place and they always wanted to sell their opaque and overpriced tokens, which made no sense. I hope they get their act together.
I canceled my subscription after like 12 years because I realized all the things that made it great aren’t really needed anymore. The “it just works” tooling, refactoring, jumping around code, etc.<p>Now my agents mainly write code under my direction and I review it either in the harness or on GitHub.<p>I hadn’t opened it in ages and when I did need an IDE something like Zed was more than sufficient.
Part of what I've loved about JetBrians tools has been the navigation and deep semantics for large code bases. Zed is pretty basic in that regard. My agents usually get what I need, but when they go off the rails, cleanup gets interesting.<p>But I'll admit to keep my skills from atrophying, there are some projects of mine I don't touch with AI.
Code review is the problem I'm currently trying to figure out for myself. I've never liked GitHub PRs but I'm not 100% sure what I want instead (which is possibly just: it feels like it should be a VS Code plugin... But maybe I don't like VS Codes interface that much either?)
Yeah, their worktree implementation was very recently hacked in, and it really doesn't work well. The IDE project list duplicate entries for every worktree, IDE project settings don't transfer across worktrees, and every time I switch to another worktree it asks me again what project I want to open, instead of just opening the same solution I have opened.<p>It's wild that a set of IDEs that are generally fairly good just completely fail in this basic workflow. I really wonder what went through the minds of the product owners and developers that implemented this.
I also have to work in multiple workspaces simultaneously, and it drives me up the wall every time one of my IDE windows freezes (sometimes even just from inserting a Tab), because now ALL of them are frozen.
I thought so too until I learned that there is a dedicated worktree switcher hidden away as a tab in the GitHub pain. Now I can open each worktree in a separate window as if it were its own project. Maybe that's not everyone's ideal work though, but it's exactly what I want 99% of the time.<p>But I don't use it for AI assistant development, it's definitely meant for humans and not AI agents.
Same. I like their products but they have a problem with feature creep and design debt, and their AI tools are extremely in your face while also being underwhelming. I don't know if I'm going to renew my subscriptions.
I disabled all the AI tools in my JetBrains IDEs. They suddenly feel so much better. Less intrusive completions, suggestions and better performance.<p>An IDE still has it's uses, and it's perfectly fine without AI. Agents and IDEs have never felt like something that should be combined in my opinion.
Been a paid user for a very long time but now Claude Code and Codex do the job, dont need Jetbrains anymore.<p>I just could not understand their AI strategy.
[dead]
Didn't JetBrains release JetBrains Air recently? This looks like it's basically the same basic premise, except implemented differently. What's their strategy here, are they just launching competing products?<p><a href="https://www.jetbrains.com/air/" rel="nofollow">https://www.jetbrains.com/air/</a>
They also started developing Fleet several years back and made a few alpha releases, only to shutter it before it ever was ever fully released for reasons that essentially seemed to boil down to "we want to focus on our core IDEs instead, which didn't really explain what changed. I was interested in Fleet, so at this point I can't help but be skeptical of anything new they've done since then because it's not clear to me why the same logic for discontinuing Fleet couldn't apply to pretty much anything else.
Fleet was tragic. I was so excited for it but it was a perpetual WIP.<p>I suppose they were in a tough spot regardless though. They started developing it before the AI age, so they would have to pivot either way.
Many of the improvements and refreshed design were "backported" into the traditional IDEs.<p>And fleet was made to attract the VSCode generation, who they were starting to lose new user momentum to. But VSCode is no longer the biggest threat.
[dead]
At a guess, they are uncertain about the long term financial viability of selling their full IDEs, and development is cheap, so they are throwing up what they can to see what sticks, and will kill what doesn’t.
It seems that Air is a strategic product, and Thinkrail is more of an experiment.<p>While they are both "agentic development tools", it seems that Air is mostly concerned with managing multiple agents, whereas Thinkrail is about spec-first development.
Who is naming this stuff…
My take: I don't see the point of those new-IDEs. They are mostly just worktrees+sandbox+tabs+prompts, which is just git+docker+tmux+thinking, but if you actually learn to use those tools instead of handcuffing your agents to whatever take the IDE has, you're going to be much happier and effective.<p>(That's also why there are so many of them: It just isn't that hard, everyone feels like a genius when they figure it out, and it's a great way to resume-build in the AI era).
It feels like the day after I got comfortable with jj everybody become obsessed with git worktrees
It feels like JetBrains is dying, and they're trying very hard to survive.<p>I liked their products. Also, personally I am not seeing next level devexp yet, other than just using my agents for everything
It's nice to see JetBrains finally wake up and realize they can't sell a Cursor competitor from 2024 anymore. Something about JetBrains writing a new IDE seems bold... not sure if it feels correct.
The problem with all the AI IDE's is you can't use them with most enterprise/teams accounts, you have to use API which can cost upto to 10x more over an enterprise plan. I really like JetBrains, used them for a LONG time, but just find myself doing 99% of my day to day with iterm and sublime now.
Running agents outside containers seems crazy to me... It should at least launch a sperate microVM or container for each agent / task.
I've been subscribed to Jetbrains full product pack for years now, but nowadays the thing I want more than anything is either a convergence of all their IDEs via plugins or a lighter universal editor like Fleet was getting close to. Agents let me work with languages I had no business with before, but now it isn't unusual to have RustRover, Rider, Webstorm, and Intellij open at the same time. Alternatively, I'm curious as to whether their code intelligence over MCP helps coding agents. If they did, I'd still pay for good code intelligence even if it was a headless MCP server. Thought they were going that way with Air, until they killed it yet again. Air is a plugin now, but that's back to the specific IDE thing.
Still rooting for these guys
Hmm, most of this seems like it would be cutting edge in 2025. And why do I want to use Monaco? If I’m in the JetBrains ecosystem isn’t it because I prefer their IDEs over VSCode?<p>The versioned and linked spec feature sounds somewhat interesting though.
So is this DOA? I use IntelliJ for work every day and I have a project that will work for agentic coding but that I want to experiment with...
Jetbrains using vs code is really sad.
Interested in the SPEC.md format and workflow. Where can I learn more?<p>EDIT: found it at <a href="https://thinkrail.ai/blog/thinkrail-sdd/" rel="nofollow">https://thinkrail.ai/blog/thinkrail-sdd/</a><p>---<p>Also... why bun?! I just finished purging it from all my systems, ha! It'd be cool to have plain pnpm support.
NGL Jetbrains has massively helped my developer journey and be a great tool for many many years. I don’t open it that often anymore, but I see that they’re trying hard to stay relevant, which is probably not easy as probably the whole market moved against you.<p>So I’m willing to give it a try.
Where is local model support and just any openai compatible api support?
Pi agent is compatible with more stuff
Boy people in here are super negative.
I'd have to be _strongly_ convinced to leave oh-my-pi and Paseo.
Yeah, now that agents are doing most of the work, and we want to give them as much freedom as possible to run code, take screenshots, click on things, etc, it really doesn't make much sense to have a setup where all of this happens on your local computer. IMO it makes more sense to have this hosted somewhere, and then have UIs that make this visible to you on your devices.
This sounds like a short-term strategy at best
You only need an agent to click things long enough to build an API on top of the thing it's clicking on. And running a full windowed virtual machine is expensive!<p>I'd also caution against saying things like llms are doing most of the work I don't think that's true. And where it is true it shouldn't be. These things are still new tech and they need a lot of hand holding and oversight still.
Exactly. They sit in their little world in my homelab and I control everything through networking and virtualization restrictions. They run on a beefy VM, can spawn their own VMs (Ubuntu, Debian, Fedora, Arch, Windows, even macOS on an old mac mini), run their own browsers, access their own secrets, etc. There's no way I would go back to agentic development on my local machine anymore.
I am curious about Pi, but my experience with a seemingly more fully-featured Hermes has been endless tinkering and fixing minor issues. Have your experience been at all similar?
I've been using it without thinking much about it for 3 months now. Have yet to run into any bugs or strange behaviors. But bear in mind I'm using oh-my-pi, not Pi. I found the latter to be mostly useless in terms of what I needed for my day to day work. I'm sure I could tinker with it to get it right, but that's literally what oh-my-pi is doing for you. And like I said, zero problems thus far.
Do you use Paseo as a layer <i>over</i> oh-my-pi or alongside?
Paseo!! :goat:
yesterday: <a href="https://news.ycombinator.com/item?id=50219186">https://news.ycombinator.com/item?id=50219186</a>
My reaction to AI generated websites and READMEs: I ain’t reading all of that - but happy for you, or sorry it happened
It’s an absolute shame that they’re using Monaco as their editor for this. Shocking, even. I wish they would have used the editor they built for Fleet. Monaco just feels like the lowest common denominator editor UI and isn’t nearly as polished as what you get from say Zed or a full fat Jetbrains IDE.<p>I’ve been using Orca as my agent orchestrator du jour - but its editor experience is just pathetic. Really what I want is Zed integrated into a similar all-in-one platform like Orca (but more minimal - Orca is a total slopshow with way too many features)
I've been working on a similar concept, around claude code, for my own productivity <a href="https://github.com/bits4breakfast/albedo" rel="nofollow">https://github.com/bits4breakfast/albedo</a>
I cannot express how happy I am that it uses a Pi core. Look forward to complementing herdr with this
Ah this reminds me I need to cancel my jetbrains subscription. I started with CLion and used RustRover, PyCharm, WebStorm, DataGrip over the years but now they all feel outdated and unnecessary.<p>Edit: oh shit I am on the cancel screen and reminded I also used ReSharper. Best of luck jetbrains I have given you a lot of money figure your shit out and I would happily return.
It's interesting to see that the README is much less CLAUDE-y than the abomination that currently runs at <a href="https://thinkrail.ai/" rel="nofollow">https://thinkrail.ai/</a><p>Also, reading through their "SPECS".... <a href="https://github.com/JetBrains/thinkrail/blob/d299f20d2ba014f382ddbcc9b49f2aa63fada132/apps/website/SPEC.md" rel="nofollow">https://github.com/JetBrains/thinkrail/blob/d299f20d2ba014f3...</a> or <a href="https://github.com/JetBrains/thinkrail/blob/d299f20d2ba014f382ddbcc9b49f2aa63fada132/apps/web/SPEC.md" rel="nofollow">https://github.com/JetBrains/thinkrail/blob/d299f20d2ba014f3...</a><p>How is this llm-vomit "specs that are ground truth" etc.?
> We built a rich interface around the pi coding agent<p>This is exactly what I was missing
[dupe] <a href="https://news.ycombinator.com/item?id=50219186">https://news.ycombinator.com/item?id=50219186</a>
As a Pi user, this may be very interesting. Especially after they add full support for Pi extensions.<p>I tried Air before and found it underwhelming. I tried using it around Pi through ADB, but it didn't any benefit around using Pi purely.
Looks interesting, but they need to clean up the claudese in those bullet points holy crap. It's like they purposely want the "what you get" section to be as obtuse as possible.
This is moving in the direction towards a final interface, very good.<p>There aren't enough digital french cleat systems.<p>The true benefit of a French cleat isn't storage or organizing the way a fiddly pegboard and hanger approach uses, it's the ability to move all tools for a specific project onto a single rail without having to fiddle around, reducing friction for engaging and re-engaging with a project.
> TypeScript followed by a myriad other (objectively) slow languages<p>JetBrains, explain concisely why this isn't written in C/C++/Rust?
Very likely because Pi is written in TypeScript and Pi plugins are expected to be TS. TS is becoming the one true language. Best get used to it.
Because it's just slapping web-based Monaco editor on top of pi which is written in Typescript.
This is a great step. JetBrains integration of AI agents inside their ides is horrendously clunky.
[flagged]
I do not get the appeal of web-based GUIs now that we have LLMs.<p>Migrating my screenwriting software[0] from OpenTUI to Roc thought me what were once rough edges that take a lot of time are now just a prompt away from a solution.<p>It now uses 10x less RAM, bundle is half the size, and my initial implementation is 700-800 fps for scrolling and 200 fps for writing.<p>Granted, a TUI is less complex than a full-blown GUI, but I built a Roc Iced platform just as easily that abstracted Iced flux away<p>[0]: <a href="https://blisswriter.app/" rel="nofollow">https://blisswriter.app/</a>
JetBrains UIs aren't web-based, unless this is an exception.<p>JetBrains tools are heavier and can take a few seconds to launch, but they also have some of the most responsive typing out there. They did some good work on zero-latency typing modes when that was a big topic and they were very good at typing latency relative to most editors.<p>They will never be the right tool for the personality type that gets angry when their IDE takes a few seconds to launch at the beginning of the day or when an application takes more than 1GB of RAM, but I am not that type of person so I enjoy them.<p>I think the TUI people are well served by vim or emacs and should just stay there and be happy.<p>The rest of your post feels like an injected ad for your project underneath a topic where it's not relevant
This post is about a TypeScript repo, which is what I commented on. It may as well be a necessity since Pi is using a JS runtime as well. It has nothing to do with JetBrains and everything to do with the codebase in the link.<p>It also has nothing to do with TUI vs. GUI, since my comment addressed both (anecdotally).<p>If anything, your mentioning of their performance work is exactly my point.
for people who still code. why do you need them not to?
I do code -- the app logic. I also am well aware of what the infrastructure code does, I just don't type any of it myself.<p>Even if I wanted not to code it I couldn't. LLMs are still incapable of creating code up to any decent standard.<p>Also, while I do the get the joy of programming, we sometimes forget to focus on the user. You being happy to have typed the whole thing once, and have it run everywhere via the magic of browsers may not be the best strategy if this means your user's lap will be overheating.<p>In the end as much as I like coding I would prefer my users' experience to be the best it can be. LLM assisted code delivers this better and faster than hand-typing it all (which in turn is better than completely vibecoding it)
Jetbrains software is not web-based.