|
|
|
|
|
by lolinder
1237 days ago
|
|
I disagree that this is a bad thing. If the frameworks start developing lock-in they can and will be forked. In the meantime, we have multiple competing full-stack JavaScript frameworks that are being actively funded. Also, I think Netlify and company know that a framework that is locked in won't be adopted. The history of mainstream developer tooling over the last thirty years is a migration away from proprietary languages and frameworks, and it's going to take more than a few rogue JS fullstack frameworks to change that. |
|