So, either don’t use Github web ui or don’t use Chrome. However it‘s probably pretty safe to say all browsers behave equally power-hungry.

We need to learn to be more conscious about the impact our way of doing things has.

Elon having Cursor in his claws now doesn’t exactly instill a sense of security in me to actually store IP on their servers. Forgejo works nicely enough my homelab. Thank you!

I'm also not confident this is something that will stick (and survive the acquisition), which further weakens the idea that companies would set up expensive migration projects to it.

That's not entirely true, and skews the actual facts, that while Microsoft Bing Ads network is used to generate revenue for Qwant it does NOT provide BING with the full user details of their users, but only with limited anonymous (pseudonymous) data.

Suffice to say they need to get their own search index fully filled and stop using Bing (or whatever US-based) data. It's a process...

This is genuinely cool! I have it bookmarked now and will definitely get back to it after my todo list lost its fight against me. ;)

Kudos! The site rocks as well! I also have an api-first SaaS (see https://thelawin.dev), but it unfortunately needs a bit more explanation.

Best, Steviee

Thanks Steviee! Checked it out interesting concept, legal APIs are definitely harder to explain than visual ones. In my case i added small playground on the app dashboard for better understanding. Good luck with the todo list Best, Aldin

Hey, good question. The cli tool itself is more or less just modifying files within the repo so you should be good to go with Mercurial or any other vcs. To smooth things out for AI agents the skill files and descriptions would need to be migrated for the respective vcs of course.

Fair enough. Any plans to have a "serve" mode to serve up a web issues board?

Actually yes and no. The current implementation is more like a monitor of things going on. I used it to visualize the current state of a project that I let AI agents work on. So the board is read-only, and I think that's mostly fine for now. Porting this read-only view to HTML and put a little http/websocket service in there would be easy on the one hand, but break the TUI setting somewhat. Feel free to create an issue for it, though.

This makes total sense to me. Everything that makes up the state of your project should either be part of the versioned repo (git) or not be part of the project.

I created a little Github Issues replacement for myself that puts the issues within the repo so that the work and the todos stay in sync. https://github.com/steviee/git-issues

And I bet there's numerous other projects like that.

Hope you get your submarine, man! ;)

Wearing my Ruby T-Shirt (ok, Rubyconf.TH, but you get the gist) while reading this makes me fully approving and appreciating your post! It totally resonates with my current project setups and my trying to get them as simple as possible.

Especially when building new and unproven applications I'm always looking for things that trade the time I need to set tings up properly with he time I need to BUILD THE ACTUAL PRODUCT. Therefore I really like the recent changes to the Ruby on Rails ecosystem very much.

What we need is a larger user base setting everything up and discovering edge-cases and (!) writing about it (AND notifying the people around Rails). The more experience and knowledge there is, the better the tooling becomes. The happy path needs to become as broad as a road!

Like Kamal, at first only used by 36signals and now used by them and me. :D At least, of course.

Kudos!

Best, Steviee

Marketing is wrong, selling LLMs as AI is like someone giving you a clutch and telling you "now go drive somewhere in your new car!".