@giansegato so this only worked because you trained your muscle-memory to spam CMD+C every now and then? that's very impressive. happy that your valuable work wasn't lost and you found a way to get it back.
@schickling C4 is fun: https://t.co/2zyHB3gEhV
Especially good at zooming in and out to different levels (overall architecture up to the code unit eg. function/module level)
There is good tooling for drag-and-drop layouting C4, saved as metadata. still feels a bit clunky though.
@schickling feeling the same.
it's been strange, observing more and more conversations with others where I am naturally talking on the diagram level abstractly, while others think about it in very concrete "concepts" in the code.
high-level systems behavior vs. low level implementation
@andreasklinger@phil_rechberg@paulg no, it's not just zoning. read some of the examples on that page:
> Garagennutzung als Abstellraum, zum Beispiel für eine Skiausrüstung oder andere sperrige Gegenstände, die eigentlich in den Keller gehören
> Garagennutzung als Partykeller, Büro oder Schlafplatz
@andreasklinger@phil_rechberg@paulg oh it does, if the city or your friendly neighbour hears that you are not using your garage as a storage for cars, there's going to be problems
https://t.co/l4Jm7jx12V
> Eine Garagennutzung als Werkstatt ist ... verboten.
> In Hessen ... Geldbuße von bis zu 10.000 Euro ...
i have never been able to persuade myself to be interested in the snail thought experiment
here's one that bothers me instead:
there's some set of words in your subconscious that, if you said them out loud in the right way, would rearrange your entire reality. what are they?
@GergelyOrosz yes AND others like Cloudflare and AWS have really suffered in reliability "recently" (it's not only recently anymore, it's been consistent for a while now)
@DavidKPiano@kenwheeler on 3., sadly my agents have shown great skill at either ignoring berating or being passive-aggressive about it, so I started skipping that step 😞
Open source is dead.
That’s not a statement we ever thought we’d make.
@calcom was built on open source. It shaped our product, our community, and our growth. But the world has changed faster than our principles could keep up.
AI has fundamentally altered the security landscape. What once required time, expertise, and intent can now be automated at scale. Code is no longer just read. It is scanned, mapped, and exploited. Near zero cost.
In that world, transparency becomes exposure. Especially at scale.
After a lot of deliberation, we’ve made the decision to close the core @calcom codebase.
This is not a rejection of what open source gave us. It’s a response to what risks AI is making possible.
We’re still supporting builders, releasing the core code under a new MIT-licensed open source project called cal. diy for hobbyists and tinkerers, but our priority now is simple:
Protecting our customers and community at all costs.
This may not be the most popular call.
But we believe many companies will come to the same conclusion.
My full explanation below ↓