Hacker Newsnew | past | comments | ask | show | jobs | submit | opem's commentslogin

played around with it a little, works great for - basic conversational tasks - basic reasoning - creating little UI snippets and not good for one shot coding tasks. once it starts hallucinating about something you can't make it rectify that. during a coding task it wrote some madeup library function, despite of pointing it out, giving docs, it kept producing the same code with the madeup function all while acknowledging the problem. btw, thanks for putting it together!

It's hard to imagine how a single person managed to accomplish so much. RIP to the great soul :|

Seriously. After reading, I scrolled through his Known For section and thought, “Alright already, leave something for everybody else to work on.”

There is also lemonade-server from AMD. Although I am not sure if that is any better.

For real, one of the reasons I use cal.com is because it's open source. Time to migrate.

Same. I expect in a misguided effort to save customers, they are going to lose a lot more. My two companies will be canceling over this.

> When we started Cal.com, we believed deeply in open source.

No you certainly didn't, otherwise you shouldn't have come up with such a meaningless excuse!


I see that is an issue with many people, but now with github adding support for stacked PRs, I guess that would change

I think one major difference between git and jj is how immutable their DAG is, due to the difference in how they refer to their unit of change (i.e. stable change ID with changing commit IDs vs. immutable commit ID). One implication of that is change history in a git repo feels much more immutable to the one in a jj repo. Consequently operations that involves changing the history like, undo/rebase feels much easier/flexible. Is my understanding correct?

Sorta! I think it can feel that way at times, but also the opposite. jj’s changes are immutable in the same way commits are, when you modify a change, it makes a new immutable commit and associates that with the change. So on the literal level, they’re the same.

But it’s true that mutating history is easy and sometimes even automatic with jj, whereas it’s not with git. So that could make it feel more mutable. On the other hand, jj has the concept of mutable vs immutable commits; jj will present you from modifying certain changes unless you pass in a flag to override it. So in some ways, it’s more immutable than git.

Just really depends on your perspective.


At least they aren't hiding and transparent about it unlike the big tech corps with so called SLAs


There are no outages in Azure sing se.


GitHub's Ops team would approve this message, I assume.


i see you, brother! <3

why this AI slop is on the front page?


But that doesn't always pay the bill, as OP mentioned, he has "adult responsibilities".


That’s fair, but the likelihood you’ll have a better time monetizing something you love is much higher, both in willingness and ability imo.


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: