Organiser of the Edinburgh Language Exchange and The Edinburgh Open Tech Scene |
Full Snack Developer 🥪, Ramen guzzler 🍜, quiche murderer 🥧. A friendly cat.
Indeed. Frameworks, libraries, and many other applications and tools, are designed to make a task easier.
My point is, if the framework in question and its own ecosystem have a tendency to force you into doing things One Holy Way, at the exclusion of the rest of the ecosystem, it's definitely worth stepping back and thinking, "Why?"
Because of the reason I mentioned in the first point - writing everything from scratch would take too much time and it will lead to unnecessary repetition.
If someone already wrote a library for making HTTP requests, it's properly tested and it's stable, why would you write your own library? Just to be able to say that you're not forced to do things in a certain way?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Indeed. Frameworks, libraries, and many other applications and tools, are designed to make a task easier.
My point is, if the framework in question and its own ecosystem have a tendency to force you into doing things One Holy Way, at the exclusion of the rest of the ecosystem, it's definitely worth stepping back and thinking, "Why?"
Because of the reason I mentioned in the first point - writing everything from scratch would take too much time and it will lead to unnecessary repetition.
If someone already wrote a library for making HTTP requests, it's properly tested and it's stable, why would you write your own library? Just to be able to say that you're not forced to do things in a certain way?