3 ms·

form/validation should be what HTML excels at, it should even one of the few things it does. and we should use another technology to do other things we've been

form/validation should be what HTML excels at, it should even one of the few things it does. and we should use another technology to do other things we've been commandeering it to do.

grzm 10y ago
Client-side validation can be very useful. At this point I think that the inconsistencies between implementations are the primary pain points, similar to what prompted the Web Standards Project.[0] Is there anything similar to the -{webkit,moz} in CSS for HTML? Or abstraction libraries comparable to jQuery? It would also be very useful if the validation is extensible, as different projects require different validation rules. I'd also want validation rules that are portable between the client and the server to reduce code duplication. One combination I've been toying with is using clojure.spec[1] with ClojureScript/Clojure with varying levels of success. I imagine you can do similar things using server-side JavaScript. > we should use another technology to do other things we've been commandeering it to do. What types of things are you thinking of? [0]: https://en.wikipedia.org/wiki/Web_Standards_Project https://en.wikipedia.org/wiki/Web_Standards_Project [1]: http://clojure.org/about/spec http://clojure.org/about/spec
- jlebrech 10y ago
  there should be a form language that works client/server and is just for classic web such as forms, something similar to meteor or volt. i'd even resort to using those in future or write a dsl on top that makes web development a breeze.
- jlebrech 10y ago
  there should be a form language that works client/server and is just for classic web such as forms, something similar to meteor or volt. i'd even resort to using those in future or write a dsl on top that makes web development a breeze.
jacksonsabey 10y ago
client side validation is pointless if you can't validate server side http://www.w3schools.com/html/tryit.asp?filename=tryhtml_input_email http://www.w3schools.com/html/tryit.asp?filename=tryhtml_inp... the firefox implementation will gladly accept the invalid test.@example.com but won't accept the valid "test"@example.com this is just a case of poor validation which we are now stuck with

form/validation should be what HTML excels at, it should even one of the few things it does. and we should use another technology to do other things we've been commandeering it to do.

grzm 10y ago

Client-side validation can be very useful. At this point I think that the inconsistencies between implementations are the primary pain points, similar to what prompted the Web Standards Project.[0] Is there anything similar to the -{webkit,moz} in CSS for HTML? Or abstraction libraries comparable to jQuery? It would also be very useful if the validation is extensible, as different projects require different validation rules. I'd also want validation rules that are portable between the client and the server to reduce code duplication. One combination I've been toying with is using clojure.spec[1] with ClojureScript/Clojure with varying levels of success. I imagine you can do similar things using server-side JavaScript. > we should use another technology to do other things we've been commandeering it to do. What types of things are you thinking of? [0]: https://en.wikipedia.org/wiki/Web_Standards_Project https://en.wikipedia.org/wiki/Web_Standards_Project [1]: http://clojure.org/about/spec http://clojure.org/about/spec

jlebrech 10y ago
there should be a form language that works client/server and is just for classic web such as forms, something similar to meteor or volt. i'd even resort to using those in future or write a dsl on top that makes web development a breeze.
jlebrech 10y ago
there should be a form language that works client/server and is just for classic web such as forms, something similar to meteor or volt. i'd even resort to using those in future or write a dsl on top that makes web development a breeze.

jacksonsabey 10y ago

client side validation is pointless if you can't validate server side http://www.w3schools.com/html/tryit.asp?filename=tryhtml_input_email http://www.w3schools.com/html/tryit.asp?filename=tryhtml_inp... the firefox implementation will gladly accept the invalid test.@example.com but won't accept the valid "test"@example.com this is just a case of poor validation which we are now stuck with