In a front-end project, being "headless" means that all functions can work without dependence on any user interface elements/components. With Refine, you can use features such as data management, authentication, real-time functionality, audit-logging, internationalization, and access control with any user interface element/component of your choice. This means that Refine does not restrict you in terms of styling and customization.
In this context, "server side" and "headless" refer to different things. "Server side rendering" (SSR) or "client side rendering" (CSR) refer to a method of rendering a website or application, while "headless" refers to the architecture of the application's business logic.
I feel like they are using open source as a marketing and growth channel. Even if you self-host it, there's no way to self-host the API. You have to pay to use it. So you're just self-hosting the UI. They can change the API at any time or kick you off it. Also the AGPL is a very restrictive license.
The pricing tiers on the website are also misleading/incorrect (edit: may be outdated info). For example, the free tier has unlimited event type only for the duration of a trial period. After that it downgrades you to 1 active event type at a time. I've run into a few "bugs" like that, but it still works well enough that I haven't bothered with the difficult self-host for my recruiter booking calendar.
> The pricing tiers on the website are also misleading/incorrect. For example, the free tier has unlimited event type only for the duration of a trial period. After that it downgrades you to 1 active event type at a time.
hey hey, that pricing is long gone. there are no trials anymore, everything is that is PRO on calendly is free on cal.com
Good to know if true. I ran into that particular issue only about 6 months ago, so I'm not sure about long gone. I'll definitely double check when I have the chance and I've updated the prior comment to reflect that it may be outdated.
Absolutely. All these new open source companies are a bit shady. Supabase was also another one of these although I hear now their stuff is easier to self host.
It's the VC-funded OSS playbook (restrictive open source, monetize support and advanced deployments until the open source loses potency, relicense). Cal.com took money from https://oss.capital/portfolio and others
I don’t see the point in making this open source to begin with, it’s not like their target audience even cares. When you’re selling to developers etc it could make sense. But when you’re selling to doctors, HR, teachers? Eh. I guess maybe they could score a few free bug fixes, but I don’t see much added value beyond that.
It is just you. Those jobs that you deem "pointless" make the economy work. To find great jobs:
1. Be clear about what "great" means to you. What do you value?
2. Research the company to determine if what you value is the same as what they value. Every company goes after profit. This is a good thing. Profit = you're providing value to someone. If you don't believe that, work for a non-profit. That's cool too.
3. Realize that everything meaningful was built by teams. No one can build something that stands the test of time by themselves. When you zoom in, things may seem pointless, but when you zoom out to look at the timeframe of decades, you'll see meaningful change derived from many of today's companies.
JIRA offers an almost limitless amount of customization to fit any workflow. I think the custom attributes/fields/reporting part of it adds a lot of complexity.
Yeah... and once it comes down to a company's pm level, they all lock it down to what they think is the best, leaving teams using something that is guided towards PM and reporting, instead of getting job done.
You can use server-rendered React. You get the benefit of having components without the cost of downloading React on the frontend (unless you have something interactive). This is what NextJS does.
Mostly by writing a blog posts and driving SEO traffic. But this takes a long time and may not succeed unless your blog posts are discoverable. You solve this problem by writing guests on other people's blogs (usually blogs that are in your product's niche).
I've done a bit of blogging. Have you experimented with driving traffic through newer forms of social media? I'm played around with FB groups and Instagram. It doesn't feel familiar, but I've seen some results, after experimenting with content; though, I'm still experimenting.