3 ms·
Exactly... I worked on a project a couple years ago, and decided to use a beta version of bootstrap as the baseline for the project... I cloned the repo, merged
by tracker1 12y ago
Exactly... I worked on a project a couple years ago, and decided to use a beta version of bootstrap as the baseline for the project... I cloned the repo, merged the pieces into my project, and kept a copy of the docs at-that-time for reference.
The site still works great... the codebase is fine. It was before some later changes to bootstrap 3, so it isn't current with the released version, but it still works, and did better so than v2. The same goes for most things involving open-source tools. You can go through migration cycles, or accept and limit the scope of how you use it.
I always applied the same arguments for using Mono in places as a practical reasoning. So what if new development stopped/dropped or rolled.. as long as what I'm doing can keep running.
Your best bet is to keep your codebase modular so much as possible, and it makes it easier to replace certain pieces.
Today, I really like react + yahoo's flux implementation. There are some weird corner cases I've had to deal with, it's still nice. It really just depends on your needs.