Data wrangler, software engineer, systems programmer, cyclist. Unix (mostly Solaris) for aeons. I talk C, Python, SQL, Performance, Java, Kafka and Makefiles.
Location
Brisbane, Australia
Education
BA (Mathematics, Modern History), University of Queensland
I don't agree - an IDE is completely different to either a library or a framework; it provides you with an environment in which you can write/debug/test your implementation of either.
A SDK might be a bit of both worlds here - "here's a collection of libraries for you to use while working on $project, and you should use our Framework/API to structure how you do it" - but it's not imnsho a framework per se.
I keep coming back to:
an API or Framework is a (more or less) abstract definition of exposed surfaces between components.
a Library is a concrete implementation of an API.
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.
I don't agree - an IDE is completely different to either a library or a framework; it provides you with an environment in which you can write/debug/test your implementation of either.
A SDK might be a bit of both worlds here - "here's a collection of libraries for you to use while working on $project, and you should use our Framework/API to structure how you do it" - but it's not imnsho a framework per se.
I keep coming back to: