HackerTrans
TopNewTrendsCommentsPastAskShowJobs

throwaway284962

no profile record

comments

throwaway284962
·4 lata temu·discuss
throwaway284962
·4 lata temu·discuss
Yeah Spring is obviously deliberately obfuscated, which makes perfect sense considering the business model.
throwaway284962
·4 lata temu·discuss
> If you find a bug with the adhoc framework you need to convince a busy person in another team to spend time to unblock you.

Which is not so difficult, because that busy person is in the same organisation as you, and therefor working towards the same goal.

Fixing that bug is much more difficult if that person is in an outside organisation, serving many other customers on the same code base (with possible conflicting needs), and/or is not actually in any way accountable for it (open source).
throwaway284962
·4 lata temu·discuss
I started using a framework for a task at work, was immediately tripped up by an obvious stupid bug in the config files, reported it and it was closed because "too many people already depend on this behaviour". So now I've in-sourced other companies legacy and taken on a huge liability in depending on the evolution of undefined number of other organisations and their code bases.

And even worse when these frameworks are open source and don't even have any accountable people at all, and god knows how many people working professionally are suddenly held hostage by some dude who just felt like going backpacking in south america for 6 months without giving any notice to anyone.
throwaway284962
·4 lata temu·discuss
> 1. Every sufficiently complex framework-free application contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of a framework.

Of which you are the creator and expert, and have complete control and insight, and can change it in any way you want any time. It is in 100% alignment with your goals at all time.

If you use a framework your organisation becomes incredibly complex, because you are now actually competing against the needs of other companies, your competitors, which are also influencing the framework.

Your software is custom made for your organisation, it's not mass producing identical systems on an assembly line, so it doesn't make sense to share a common platform like you do with cars. And even if you did, this platform would be a joint venture, and absolutely not made by a subcontractor, and no way in hell some random unpredictable volunteering hobby organisation.