Self-taught software engineer and entrepreneur in high school, specializing in full-stack development and UI design. Blogger on software engineering, internships, and high schoolers.
In my opinion, I think that everything should stay the way it is. Not that your argument is not valid, but that it doesn't post enough incentive for REST API's to change their HTTP methods.
I'm just saying, "If it ain't broke, don't fix it."
No hate though, love this post! It was a really good topic to question.
I agree, there really isn't an incentive to change -- plenty of people have plenty of code that uses the most popular system. But I think we both know that sometimes "if it ain't broke..." usually just delays the big bugs in the programming world. Not that I know what would possibly break from current implementations, just that I've seen that happen so often (I mean... hasn't every developer?) that I'm assuming something is going to happen eventually. It's just something I felt like I needed to get off my chest.
Self-taught software engineer and entrepreneur in high school, specializing in full-stack development and UI design. Blogger on software engineering, internships, and high schoolers.
Oh yeah of course! Some things get to the point where it's not really broken, but so inefficient that it's practically broken. Even though HTTP requests are at that point, definitely a valid point.
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.
In my opinion, I think that everything should stay the way it is. Not that your argument is not valid, but that it doesn't post enough incentive for REST API's to change their HTTP methods.
I'm just saying, "If it ain't broke, don't fix it."
No hate though, love this post! It was a really good topic to question.
Thanks for the reply, I generally don't get any!
I agree, there really isn't an incentive to change -- plenty of people have plenty of code that uses the most popular system. But I think we both know that sometimes "if it ain't broke..." usually just delays the big bugs in the programming world. Not that I know what would possibly break from current implementations, just that I've seen that happen so often (I mean... hasn't every developer?) that I'm assuming something is going to happen eventually. It's just something I felt like I needed to get off my chest.
Oh yeah of course! Some things get to the point where it's not really broken, but so inefficient that it's practically broken. Even though HTTP requests are at that point, definitely a valid point.