Live data from Hacker News

The Earl Grey programming language

breuleux.github.io

41–50 of 137 posts

Re: The Earl Grey programming language

#41
post #17

Earlier quoted context omitted.

I think a lot of lisps use hyphens in variable names

There's plenty of precedent. It's just rare for a reason. I'm not sure allowing slightly easier access to CSS syntax justifies it.

I'd love to hear why people prefer underscores over hyphens. I think I grew out of syntax fanboy-ism, but C and python __private__, _special_variable are everything but readable to me. They break the visual line too much. Even historically it was a weird symbol, originally a line break that made it into non-space separator in PL/1, then almost everywhere. Before that it was pure formatting, a typewriter glyph to be overtyped/composed on words to underline them.

Re: The Earl Grey programming language

#42

Hyphens in variable names. It's a bold strategy for a scripting language, Cotton.

Imagine being able to type style.border-width in JS instead of style.borderWidth

You just reminded me of http://en.wikipedia.org/wiki/JavaScript_Style_Sheets

Re: The Earl Grey programming language

#44
I really like how the tooling to create a full application is already there, it isn't like "here's my new language, but there are no libraries, good luck!".

> Global variables need to be declared to be accessible: > globals: > document, google, React

If I'm getting this correctly, what a brilliant idea! Contain the shittiness by having one single location where all globals are declared. So very helpful.

Re: The Earl Grey programming language

#45
post #38
post #7

"Oh god, do we need another language that compiles to javascript?!" —Everyone, probably

I think it's unfortunate that this is currently the top comment on this post. Someone puts hundreds of commits of work into a nifty language with a nice feature set (including compile-to-js) and awesome integrations, and this is what they get on HN... I think this looks like a great project, we can never have too many programming languages to play around with.

>we can never have too many programming languages to play around with.

Wait until we start having legacy code in all those languages.

>we use 30 different compile-to-js languages used in our projects(that are no longer being developed) and you have to maintain it.

Re: The Earl Grey programming language

#46

Earlier quoted context omitted.

There's plenty of precedent. It's just rare for a reason. I'm not sure allowing slightly easier access to CSS syntax justifies it.

I'd love to hear why people prefer underscores over hyphens. I think I grew out of syntax fanboy-ism, but C and python __private__, _special_variable are everything but readable to me. They break the visual line too much. Even historically it was a weird symbol, originally a line break that made it into non-space separator in PL/1, then almost everywhere. Before that it was pure formatting, a typewriter glyph to be o…

Because fanboy-ism could be parsed as fanboy - ism = fanboy minus ism.

Re: The Earl Grey programming language

#50
post #46

Earlier quoted context omitted.

I'd love to hear why people prefer underscores over hyphens. I think I grew out of syntax fanboy-ism, but C and python __private__, _special_variable are everything but readable to me. They break the visual line too much. Even historically it was a weird symbol, originally a line break that made it into non-space separator in PL/1, then almost everywhere. Before that it was pure formatting, a typewriter glyph to be o…

Because fanboy-ism could be parsed as fanboy - ism = fanboy minus ism.

You mean like this :

let some-var = a-number-another-number

instead of

let some-var = a-number - another-number

Post reply on HN