Add daily email for 2024-12-31
Why do people still build their own CMSes and frameworks?
This commit is contained in:
parent
c7a091735b
commit
e1c216fa91
26
source/_daily_emails/2024-12-31.md
Normal file
26
source/_daily_emails/2024-12-31.md
Normal file
|
@ -0,0 +1,26 @@
|
||||||
|
---
|
||||||
|
title: Why do people still build their own CMSes and frameworks?
|
||||||
|
date: 2024-12-31
|
||||||
|
permalink: daily/2024/12/31/build
|
||||||
|
tags:
|
||||||
|
- software-development
|
||||||
|
cta: ~
|
||||||
|
snippet: |
|
||||||
|
Why do companies still build and sell their own CMSes and frameworks? I'm surprised this still happens.
|
||||||
|
---
|
||||||
|
|
||||||
|
A few times in the last couple of years, I've come across companies or agencies writing their own CMSes or frameworks.
|
||||||
|
|
||||||
|
Not as a learning exercise, which I think every Developer does at some point as part of their learning, but to host production applications.
|
||||||
|
|
||||||
|
With so many free and open source options - there are Drupal, WordPress, Symfony and Laravel just in the PHP ecosystem - why would people use custom or proprietary CMSes or frameworks?
|
||||||
|
|
||||||
|
One reason is [vendor lock-in][0].
|
||||||
|
|
||||||
|
If someone is locked into your CMS, framework or hosting platform, it's difficult for them to move away.
|
||||||
|
|
||||||
|
That's one of the main benefits of open source software.
|
||||||
|
|
||||||
|
There isn't just one company that provides services for it and customers can choose who they want to work with.
|
||||||
|
|
||||||
|
[0]: {{site.url}}/daily/2024/12/30/domain-names
|
Loading…
Reference in a new issue