Show HN: Imba – I have spent 7 years creating a programming language for the web
121–130 of 354 posts
Re: Show HN: Imba – I have spent 7 years creating a programming language for the web
#122Re: Show HN: Imba – I have spent 7 years creating a programming language for the web
#1231. The live demos that you can easily click to open and edit the examples (but doesn't load in a slow, clunky, ad-infested live code editor like some sites do)
2. Those arrows pointing out language features, so compact, succinct and useful
3. A short list of very well thought-out demos showing off different aspects of the language. (I almost laughed with pleasure at the "autorender=1fps" part).
Great work.
Re: Show HN: Imba – I have spent 7 years creating a programming language for the web
#124With no benchmarks to back up that statement?
Re: Show HN: Imba – I have spent 7 years creating a programming language for the web
#125I'm all for new programming languages but you need to justify it with actual new ideas and new ways of thinking not some opinion about syntax. Guess what? everybody has one, they're all different.
Re: Show HN: Imba – I have spent 7 years creating a programming language for the web
#126Earlier quoted context omitted.
It's fine if you have a few colors, but with 50+ lines of SASS/component I'd rather have them separately. > I have a hard time finding related things when they're separate. Store them in the same directory? I agree on the events/business logic that they make sense to couple with the template code.
And have to switch between three files back and forth?
Re: Show HN: Imba – I have spent 7 years creating a programming language for the web
#127One thing that irks me about Javascript is "const". I think it should have been called "con". "var", "let", "con". So the first thing I did here is look up the docs and see how variables are declared. Aaarghh.. "let" and "const" again :)
I've never used a language with a 'cons' keyword, but nevertheless that's what I'd assume your 'con' was, if you didn't tell me otherwise. I'm no particular JS fan, but 'const' is much clearer, it's a complete syllable, just like 'var' or 'func'. Yes 'fun' is used, but I think that's awkward for the same reason.
Re: Show HN: Imba – I have spent 7 years creating a programming language for the web
#128I have to say, I don't know if I'll use this language as I'm not a fan of Ruby syntax really, but the landing page presenting Imba is just phenomenally well done. 1. The live demos that you can easily click to open and edit the examples (but doesn't load in a slow, clunky, ad-infested live code editor like some sites do) 2. Those arrows pointing out language features, so compact, succinct and useful 3. A short list o…
Re: Show HN: Imba – I have spent 7 years creating a programming language for the web
#129 name
Why are we moving away from elegant legible HTML/JS/CSS stack to no nightmares like this and React where everything is smooshed together?> bringing the elegance and concision of Ruby into the browser
As a big fan of Ruby how does this tap into the elegance of Ruby? Ruby is readable, this is not. In Ruby it's very difficult to write code that makes people suffer greatly to understand, this seems to be the opposite.
> It is very opinionated, so some of you might not like it
As if that's the reason people won't like this. Give me a non-opinionated language and I'll show you as many people not liking it. Create a good language and people will flock.
Re: Show HN: Imba – I have spent 7 years creating a programming language for the web
#130Earlier quoted context omitted.
> ... [W]hy [are] a lot of new web languages/frameworks are mixing logic and content in the same file again...? In olden days, the DOM was treated like something shared. This could lead to a single DOM elements receiving changes from all over the place: Multiple CSS selectors would include it and apply style rules, and multiple JavaScript scripts might select and manipulate it. Spitting the CSS/HTML/JavaScript into m…
If you isolate the DOM elements from each other, then how do they share common styles? You certainly do not want to define the font type for each DOM element individually, do you?
It handles CSS by letting you define it in within an individual component (file) but also import a style from another file. That way, your shared styles are in one place and only the overrides or extra styles needed for a special component are in its file.
I think it's wonderful!
Not to denigrate this project in any way, but most or all of its goals are already met by Lit[0]. Instead of a new language, it uses regular TS and regular CSS.
[0] http://lit.dev