Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cal.com is going closed source

cal.com

Post reply on HN
Print view View original

261–270 of 337 posts

Re: Cal.com is going closed source

#261

Post by OccamsMirror »

eloisant wrote: post #250
OccamsMirror wrote: post #249

Earlier quoted context omitted.

> otherwise your clients are going to vibe code a custom solution instead of paying you. How many things do you want to be responsible for? How many vibe coded projects do you want to maintain? I think this line of reasoning is overblown. Just because you can doesn't mean a significant number of people will . I think the 3D printer comparison is apt.

Individuals and SMB might stick with Saas but those don't pay much. Enterprise customers have the means to develop in house, those are the customers that will leave. And those are the whales of the Saas business.

They already have the means to develop in house. Why aren't they?

Re: Cal.com is going closed source

#262

Post by aswerty »

Surely the argument is just to have an LLM stressing for vulnerabilities during the build pipeline before merging to main? Resulting in better security from LLMs.

One must assume this was a direction they wanted to move towards and this is the justification they thought would be most palatable.

Re: Cal.com is going closed source

#264

Post by eloisant »

OccamsMirror wrote: post #261
eloisant wrote: post #250

Earlier quoted context omitted.

Individuals and SMB might stick with Saas but those don't pay much. Enterprise customers have the means to develop in house, those are the customers that will leave. And those are the whales of the Saas business.

They already have the means to develop in house. Why aren't they?

This is much less work (= cheaper) to develop in-house with AI now than before.

Re: Cal.com is going closed source

#265

Post by ryanleesipes »

jen729w wrote: post #235
ryanleesipes wrote: post #143

Head of Thunderbird project here. Our scheduling tool, Thunderbird Appointment, will always be open source. Repo here: https:// github.com/thunderbird/appointment Come talk to us and build with us. We'll help you replace Cal.com

1. Goes to site. Clicks appointment.tb.pro link in sidebar. 2. Gives email address. 3. Is told to join the waitlist. 4. Blocks email address given at 2. Hardly a terrific experience.

Yeah. We need to create a docker container and make it easy to deploy for folks. We're not ready with the hosted option at the moment.

Re: Cal.com is going closed source

#266

Post by ryanleesipes »

ezekg wrote: post #148
ryanleesipes wrote: post #143

Head of Thunderbird project here. Our scheduling tool, Thunderbird Appointment, will always be open source. Repo here: https:// github.com/thunderbird/appointment Come talk to us and build with us. We'll help you replace Cal.com

"Thunderbird, the open source Cal.com"

Love it!

Re: Cal.com is going closed source

#267

Post by ryanleesipes »

raybb wrote: post #162
ryanleesipes wrote: post #143

Head of Thunderbird project here. Our scheduling tool, Thunderbird Appointment, will always be open source. Repo here: https:// github.com/thunderbird/appointment Come talk to us and build with us. We'll help you replace Cal.com

You should add some screenshots to the readme or somewhere before a sign in screen. Sounds like a great tool though. How much is the hosted version?

Yes, we should. Will do that today

Re: Cal.com is going closed source

#268

Post by Tepix »

The AI companies profit hugely from open source. In fact, without open source, their most significant financial success (coding assistants) wouldn't exist.

They should provide free continued git commit security analysis for open source projects. That would increase the quality of open source projects and would inspire more projects to go open source, which is also a win for the AI companies.

Re: Cal.com is going closed source

#269

Post by chasd00 »

OccamsMirror wrote: post #261
eloisant wrote: post #250

Earlier quoted context omitted.

Individuals and SMB might stick with Saas but those don't pay much. Enterprise customers have the means to develop in house, those are the customers that will leave. And those are the whales of the Saas business.

They already have the means to develop in house. Why aren't they?

Same story as always, writing the code in the easy part. Requirement gathering, analysis, consensus, direction, those are all the hard parts. Enterprises have a business to run and don’t want to run a software shop on top of everything else.

Re: Cal.com is going closed source

#270

Post by ltbarcly3 »

Let me share the press release template for 2026:

Hi {audience},

It is with a heavy heart that I have to announce that {thing we were going to do anyway} is necessary due to AI. AI has changed the industry and we are powerless to do anything other than {unpopular decision we were going to do regardless}.

Post reply on HN