There is no solution here. Who decides what I can and cannot declare with the select? If it's not me, then how will this other body of control make sure to include all possibilities in their API, which satisfy my requirements that even I don't know yet? And of course, how will these features work together? and then also be efficient?
By that reasoning any library is not a solution. Somehow people keep writing useful ones.
The article is saying the form is useful but needs to be extensible. Doesn't seem pointless to me.
Using Javascript has pros and cons, but the idea that it's fundamentally flawed is amusing. It certainly has had its warts, but the community has figured out how to use it efficiently and reliably. You're views on JS would have been much more relevant 10 - 15 years ago.
Comments
By that reasoning any library is not a solution. Somehow people keep writing useful ones.
The article is saying the form is useful but needs to be extensible. Doesn't seem pointless to me.
I think you meant people keep writing JS libraries, constantly. Why? Because they are flawed at their core - they use JS.
Using Javascript has pros and cons, but the idea that it's fundamentally flawed is amusing. It certainly has had its warts, but the community has figured out how to use it efficiently and reliably. You're views on JS would have been much more relevant 10 - 15 years ago.