4 ms·

I read the entire README and have absolutely zero idea what Hypen does (and I am a relatively experienced javascript/react programmer). Perhaps a 1-2 sentence

I read the entire README and have absolutely zero idea what Hypen does (and I am a relatively experienced javascript/react programmer). Perhaps a 1-2 sentence explanation, plus some code examples, would help.

dmix 3y ago
I didn't understand it until I looked at the index.html source code example (code > words sometimes) and I think it's a thin wrapper around Web components https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements https://developer.mozilla.org/en-US/docs/Web/API/Web_compone... But don't quote me on that, I just use Vue for a living
- deanebarker 3y ago
  This is correct. It's a wrapper around web components, kind of like Lit (which they credit in the acknowledgements). Web components are cool, but the spec is bare. This means, a lot of rote work gets custom implemented. There are a lot of frameworks popping up, trying to "standardize" this. Hyphen appears to one of these.
  - dhimes 3y ago
    Thank you. That would be a great leading paragraph on their web page if anyone from the project is reading this.
andybak 3y ago
Me neither. "An elegant custom element base class" could relate to any programming language. I skim the page and see angle brackets - so it's browser-related. Great - but for what? Is this client-side, server-side? Does it relate to a specific framework or approach? I don't blame the project. They know their audience. It's the HN policy where extra context in the post title is forbidden that hurts stuff like this.
- keepamovin 3y ago
  Thanks, its good feedback! :)
keepamovin 3y ago
Point taken, good idea on the summary and code to all who provided that feedback. Indeed code > words sometimes! That was silly of me! I’m sorry, I’ll correct that. Thank y’all for pointing that out! :)
croes 3y ago
>Hyphen simplifies the creation of custom Web Components, which are a standard for reusable user interface elements for web pages. Was that part added later?
- rco8786 3y ago
  Yes
deleted 3y ago
[deleted]
verisimilidude 3y ago
It's really clear to me. (And I did account for the subsequent README commits since your comment). But that's probably because I already know Web Components well. I'm in the market. In the following line... > Hyphen - A custom element base class for great developer ergonomics. ...I would recommend adding a link on "custom element" that points to a definition somewhere. This might make it easier for skimmers to parse the meaning of this opening line.
- keepamovin 3y ago
  Thank you, sir! I'll consider adding that link. What do you think of this? I'd love to hear your thoughts on how it could be improved in the issues or discussions, or just here! :)

dmix 3y ago

I didn't understand it until I looked at the index.html source code example (code > words sometimes) and I think it's a thin wrapper around Web components https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements https://developer.mozilla.org/en-US/docs/Web/API/Web_compone... But don't quote me on that, I just use Vue for a living

deanebarker 3y ago
This is correct. It's a wrapper around web components, kind of like Lit (which they credit in the acknowledgements). Web components are cool, but the spec is bare. This means, a lot of rote work gets custom implemented. There are a lot of frameworks popping up, trying to "standardize" this. Hyphen appears to one of these.
- dhimes 3y ago
  Thank you. That would be a great leading paragraph on their web page if anyone from the project is reading this.

andybak 3y ago

Me neither. "An elegant custom element base class" could relate to any programming language. I skim the page and see angle brackets - so it's browser-related. Great - but for what? Is this client-side, server-side? Does it relate to a specific framework or approach? I don't blame the project. They know their audience. It's the HN policy where extra context in the post title is forbidden that hurts stuff like this.

keepamovin 3y ago
Thanks, its good feedback! :)

keepamovin 3y ago

Point taken, good idea on the summary and code to all who provided that feedback. Indeed code > words sometimes! That was silly of me! I’m sorry, I’ll correct that. Thank y’all for pointing that out! :)

croes 3y ago

>Hyphen simplifies the creation of custom Web Components, which are a standard for reusable user interface elements for web pages. Was that part added later?

rco8786 3y ago
Yes

deleted 3y ago

[deleted]

verisimilidude 3y ago

It's really clear to me. (And I did account for the subsequent README commits since your comment). But that's probably because I already know Web Components well. I'm in the market. In the following line... > Hyphen - A custom element base class for great developer ergonomics. ...I would recommend adding a link on "custom element" that points to a definition somewhere. This might make it easier for skimmers to parse the meaning of this opening line.

keepamovin 3y ago
Thank you, sir! I'll consider adding that link. What do you think of this? I'd love to hear your thoughts on how it could be improved in the issues or discussions, or just here! :)