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

141–150 of 337 posts

Re: Cal.com is going closed source

#141

Post by bensyverson »

esafak wrote: post #40
gouthamve wrote: post #3

This is a weird knee-jerk reaction. I feel like this is more a business decision than a security decision. I feel like with AI, self-hosting software reliably is becoming easier so the incentives to pay for a hosted service of an OSS project are going down.

Their product is getting commoditized: https://workspace.google.com/resources/appointment-schedulin...

The real downside to Google's solution is that you have to use Google Meet. Depending on your opinion of Meet, this is either no big deal or a total deal breaker.

Re: Cal.com is going closed source

#145

Post by jemiluv8 »

I have fond memories of this project. Contributing to it really helped me ramp up my dev skills and was effectively my introduction to monorepo’s in JavaScript. It was the kind of codebase I couldn’t get my hands on while working in my part of the world. Good luck going closed source.

Re: Cal.com is going closed source

#146

Post by philipov »

notnullorvoid wrote: post #116
OsrsNeedsf2P wrote: post #96

Earlier quoted context omitted.

An app like Cal.com can be vibe coded in a few evenings with a Chrome MCP server pointed to their website to figure out all the nooks and crannys. The moat of Cal.com is not the code, it's the users who don't want to migrate. The real answer is they are likely having a hard time converting people to paid plans

> The moat of Cal.com is not the code, it's the users who don't want to migrate. That's a very weak moat unless you have something else like the friction of network dependence similar to a social network.

Sunk cost is sufficient friction for most people even without network dependence.

Re: Cal.com is going closed source

#148

Post by ezekg »

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"

Re: Cal.com is going closed source

#149

Post by pianopatrick »

sandeepkd wrote: post #125
ButlerianJihad wrote: post #6

This seems kind of crazy. If LLMs are so stunningly good at finding vulnerabilities in code, then shouldn't the solution be to run an LLM against your code after you commit, and before you release it? Then you basically have pentesting harnesses all to yourself before going public. If an LLM can't find any flaws, then you are good to release that code. A few years ago, I invoked Linus's Law in a classroom, and I was…

Every change would introduce the possibility of a vulnerability being added to the system and one would need to run the LLM scan across the entire code base. It gets very costly in a environment where you are doing regular commits. Companies like Github already provide scanning tools for static analysis and the cost is already high for them.

Might lead to a move away from continuous delivery back towards batched releases.

Re: Cal.com is going closed source

#150

Post by CamperBob2 »

Today, AI can be pointed at an open source codebase and systematically scan it for vulnerabilities.

AI also goes a long way towards erasing the distinction between source code and executable code. The disassembly skill of a good LLM is nothing short of jaw-dropping.

So going closed-source may be safer for SaaS, but closing the source won't save a codebase from being exploited if the binaries are still accessible to the public. In that sense, instead of dooming SaaS as many people have suggested AI will do, it may instead be a boon.

Post reply on HN