786 karma · joined December 5, 2012
Somehow ECS does though… tradeoffs everywhere I look have made me dizzy.
I used to use Gitlab at work, and small teams would run into so many footguns with CI that we had to throw up guardrails to prevent mistakes. Far too many links to gitlab issues that were not fixed even after >8+ years of being open ended up biting us. With GHA I haven't had that experience, and same for all of my self hosted Forgejo instances. I used to hate using GHA from about ~2018 to 2021, but they've fixed a lot of things I disliked since then.
Which surprised me because of the many hundreds of services I rely on regularly that also have status pages.
There’s a perception that those who seek knowledge and truth are somehow less happy. Ignorance, and the willingness to take the path of least resistance, can be seen as an advantage for those who would rather not look too closely. Fundamentally, perhaps the difference comes down to red pill versus blue pill, and the illusions we’re willing to accept.
If you have advanced use cases you might be more frustrated, but I’m not aware of any off the top of my head. I think my biggest complaint is that they haven’t exposed action logs over the API, so I can’t build tooling around them at the CLI level, feed them to an LLM, or more quickly diagnose problems that arise without using the website.
For people who want a similar experience today, I’d recommend trying Codeberg (An official instance of Forgejo) though. However, keep in mind they voted in July to ban mostly AI generated repositories. You can read about that here: https://blog.codeberg.org/protecting-our-floss-commons-from-...
Curious if you’ve find yourself enjoying DS or Kimi more than Opus 4?
Are you talking about AWS or Fly here? I seriously cannot tell.
Probably one of the most fun projects I’ve ever worked on, and I largely attribute that to the protocol.
I’m particularly interested in the permissioned data spec, but don’t want it to hold me back, so some functionality is on ice, and I went live without it.
Happen to be a startup that isn’t mission critical to someone’s health and well being? Great, now you can use AI and be as dirty as you would like.
Are you working with dangerous chemicals that are ingested by others, or systems that control hunks of metal flying through the sky with hundreds on board? Maybe we should stay clean in those environments until we make AI itself clean.
Only use GitHub for employers at the moment, but don’t intend to put new code there going forward.
Here is a screencap of the wip mobile UI on old safari: https://files.catbox.moe/bo7pxn.jpeg
One funny thing I see it doing is deleting seemingly random comments lines, for example if a file has a comment that spans multiple lines but doesn’t use a multi line comment syntax. It just chooses one at random transforming the once useful comment into slop.
I don’t see them fixing this any time soon, and thus human in the loop is a requirement to use these tools effectively. That is unless you love your slot machine dopamine rush enough to ignore quality gates and respect for your peers time.
I plan on focusing primarily on these areas:
- mobile experience is first class, even on old/slow devices
- diff viewer is fast even on extremely large pull requests
- stacked pull request support
- user interface is modern, accessible, and theme-able with a light touch of whimsy
- search is accessible from anywhere
- opinionated keyboard shortcuts and commandk palette from day one
Many other longer term goals that I’m not mentioning here for now while the roadmap is forming.
I’m working on an open source Forgejo browser called Joui. It’s coming along nicely, and is so much snappier than GitHub in every single way.