You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I enjoyed reading the KyuWeb Specification. Thanks! I have been thinking something along the same path with MarkWeb, but you have come way further.
My main issue with the KyuWeb Specification is that the keywords (such as <!-- KyuWeb Doc Start /--><pre id="kyuweb-doc">) are too "branded" to become a standard. It's like Netscape proposing its own <Netscape> tag in html. I think it would be better to use something more neutral along the lines of <!-- markdown start /-->. Is there any reason this is a bad idea?
The text was updated successfully, but these errors were encountered:
What you are trying to define is a new standard. To my thought standards need to be very careful not to connect themselves too closely to just one actor in order to get traction and succeed. I have no other evidence here than successfull standards with "generic" names and my own hessitant reaction to the KyuWeb name. As I mentioned I'd much rather have a more "generic" standard. KyuWeb could be a good name for a browser or server implementing this standard, but as the name for the standard itself I think it will be hard to get it adoped. Just an honest reaction on my part! Hopefully I'm wrong!
I enjoyed reading the KyuWeb Specification. Thanks! I have been thinking something along the same path with MarkWeb, but you have come way further.
My main issue with the KyuWeb Specification is that the keywords (such as
<!-- KyuWeb Doc Start /--><pre id="kyuweb-doc">
) are too "branded" to become a standard. It's like Netscape proposing its own<Netscape>
tag in html. I think it would be better to use something more neutral along the lines of<!-- markdown start /-->
. Is there any reason this is a bad idea?The text was updated successfully, but these errors were encountered: