|
|
|
|
|
by lelanthran
597 days ago
|
|
> And then 5 years down the line it has grown into a worse version of the popular alternatives, the original developers are gone and the ones who currently maintain the mess have to pay the price. Isn't that true for using the popular alternative too? At some point the original devs have moved on from $FRAMEWORK v1 to $FRAMEWORK v2 and now you're going to have to do a migration project and hope it doesn't break. > When you’re working on something others won’t have to maintain years down the line, thankfully your hands aren’t tied then and you can have a bit more fun. I think the implication is, with the in-house library, that the in-house library would be a lot easier to replace or update than a deprecated external alternative. IMO, it's all very contextual. |
|