| ▲ | exe34 2 hours ago | ||||||||||||||||
my problem with frameworks has always been that the moment I want to do something the framework writers aren't interested in, I now have three problems: my problem, how to implement it in the underlying platform and how to work around the framework to not break my feature. | |||||||||||||||||
| ▲ | SoftTalker 2 hours ago | parent | next [-] | ||||||||||||||||
Yes this happens in every framework I've ever used. My approach used to be to try to work around it, but now I've got these local exceptions to what the framework does and that is inevitably where problems/bugs pop up. Now I simply say "we can't implement the feature that way in this framework, we need to rework the specification." I no longer try to work against the framework, it's just a massive time sink and creates problems down the road. It's like designing a kitchen and you don't make all the spaces some multiple of three inches. Now, standard cabinets and appliances will not fit. You will be using filler panels or need custom cabinetry. And anyone who later wants countertops or different cabinets will be working around this design too. Just follow the established standard practices. | |||||||||||||||||
| |||||||||||||||||
| ▲ | devin an hour ago | parent | prev [-] | ||||||||||||||||
In Clojure land, the mantra has long been "libraries over frameworks" for this reason. | |||||||||||||||||