Re:Isobuild: why Meteor created a new package system
by tel on Sunday August 31, 2014 @01:54AM
(#8248545)
Yeah... It's Wadler's Law. I accept it.
I think there's a lot of room for creativity in technical fields (étale morphism comes to mind) but typically once a word has a technical definition it is made off-limits within relevant fields. Terminological blurriness is nice sometimes, but often technical terms are incredibly concrete.
To me "isomorphism" means exactly "a pair of arrows, called witnesses, (f, g) in a category such that fg = id and gf = id" and it confers many properties. If you find a category where {Server Javascript} and {Client Javascript} are two objects and exhibit an isomorphism then I will gladly let you call that object "isomorphic javascript" all day long. Frankly I'm already feeling "isomorphism" fails to capture the nature of this relationship, though.
I think there's a lot of room for creativity in technical fields (étale morphism comes to mind) but typically once a word has a technical definition it is made off-limits within relevant fields. Terminological blurriness is nice sometimes, but often technical terms are incredibly concrete.
To me "isomorphism" means exactly "a pair of arrows, called witnesses, (f, g) in a category such that fg = id and gf = id" and it confers many properties. If you find a category where {Server Javascript} and {Client Javascript} are two objects and exhibit an isomorphism then I will gladly let you call that object "isomorphic javascript" all day long. Frankly I'm already feeling "isomorphism" fails to capture the nature of this relationship, though.