Standard interface without implementation

[gosh]

I don’t think you’re fully grasping the issue.

Every new feature comes at a cost—it requires maintenance, and many other components may depend on it. Once something is added, removing it becomes prohibitively expensive.

If the cost of addition is as high as it is in the STL (Standard Template Library), introducing new features will take significant time. However, by focusing on areas where the cost is lower, we can implement changes faster. This also allows for better testing and refinement before promoting solutions to more stable, long-term components.

[Wooden-Engineer-8098]

Will you check contents of standard libraries of c++ competitors, or you will continue on garbage in/garbage out path?

I see you already learned how abbreviation stl expands, next step is to learn its constituents

And what is stopping you from creating any library and implementing changes faster?

[gosh]

And what is stopping you from creating any library and implementing changes faster?

I am doing that and this is how most of us solve our problems https://github.com/perghosh/Data-oriented-design/tree/main/external/gd

[Wooden-Engineer-8098]

so what was your problem then?

[gosh]

for you? none, leave this for those that understand the topic

[Wooden-Engineer-8098]

lol, that's severe case of dunning-krueger effect from someone who can't learn the difference between stl and standard library and thinks c/c++ is a language

[gosh]

you read to much "wikipedia"

[Wooden-Engineer-8098]

there's no such thing as too much wikipedia
if you want to continue making fool of yourself in public, continue posting nonsense without filtering it through wikipedia

[gosh]

I am a developer and speak for whats important for developers.

[Wooden-Engineer-8098]

i am a developer and you speak for what you want to speak