Closed metaperl closed 7 years ago
We chose the name Hamlet as an homage to the Haml syntax the templates are based on. We aspire to be a newer generation of templating, solving the problem for dynamic, single-page JavaScript applications the same way Haml did for traditional server-client applications originally.
In addition, @strd6 wrote an adaptation of the play Hamlet set on the moon during college. So, we thought it was a good fit.
We don't have plans to change the name in the immediate future but we're open to the possibility if it becomes a major problem.
Overall I agree, in terms of Google results for just hamlet
will almost never return this library :( What about at least hamlet.js
? My preference would be something more identifiable.
hamllet
ham mullet
LOL :smile:
Back to being serious, that does suggest hamulet
.
omelette
HamletJS as suggested by @alexgorbatchev might be great.
Similar to @JikkuJose and @alexgorbatchev's suggestions I think we can go with Hamlet.coffee as the full name and use Hamlet as shorthand in contexts where it is unambiguous.
Cool, that should make it more discoverable.
On 7 July 2014 03:49, Daniel X Moore notifications@github.com wrote:
Similar to @JikkuJose https://github.com/JikkuJose and @alexgorbatchev https://github.com/alexgorbatchev's suggestions I think we can go with Hamlet.coffee as the full name and use Hamlet as shorthand in contexts where it is unambiguous.
— Reply to this email directly or view it on GitHub https://github.com/inductor-labs/hamlet/issues/8#issuecomment-48128987.
It's Jadelet now :1st_place_medal:
A quick google search shows a number of web things named Hamlet.
What did you like about the name Hamlet? Could you possibly name it something a bit more representative of what it brings to the templating world?