91–100 of 131 posts
Non-closing html tags? Looking at the doc it seems it is using the same structure as hiccup or hyperscript except. What was the reasoning?
Doesn't solve any of the big problems with large scale javascript apps: 1) Lack of type checking leading to exploding runtime exceptions 2) Object inheritance/prototype is weird and counter intuitive to other OO languages 3) Lack of proper encapsulation leading to spaghetti code when combined with #1 I suspect we are in for a new era of languages targeting web assembly to be used as webapp frontends and backends but…
Doesn't solve any of the big problems with large scale javascript apps: 1) Lack of type checking leading to exploding runtime exceptions 2) Object inheritance/prototype is weird and counter intuitive to other OO languages 3) Lack of proper encapsulation leading to spaghetti code when combined with #1 I suspect we are in for a new era of languages targeting web assembly to be used as webapp frontends and backends but…
Doesn't solve any of the big problems with large scale javascript apps: 1) Lack of type checking leading to exploding runtime exceptions 2) Object inheritance/prototype is weird and counter intuitive to other OO languages 3) Lack of proper encapsulation leading to spaghetti code when combined with #1 I suspect we are in for a new era of languages targeting web assembly to be used as webapp frontends and backends but…
JavaScript is syntax sugar for Scheme (Lisp variant). Lisp is proven to support large scale apps, but you need to cook it using another cookbook.
I've been following Imba for the past several months since the initial announcement on HN. I like the clean syntax, tags, and high performance, so I hope you guys attract interest despite all the library/framework fatigue we're experiencing in frontend JS land. It's rather refreshing to be able to write code and view all together, like .css(appropriate_styling) It would be great if you had some walked-through example…
Doesn't solve any of the big problems with large scale javascript apps: 1) Lack of type checking leading to exploding runtime exceptions 2) Object inheritance/prototype is weird and counter intuitive to other OO languages 3) Lack of proper encapsulation leading to spaghetti code when combined with #1 I suspect we are in for a new era of languages targeting web assembly to be used as webapp frontends and backends but…
Yes, exactly: http://www.elevatesoft.com/blog?action=view&id=why_limit_web...
I've been following Imba for the past several months since the initial announcement on HN. I like the clean syntax, tags, and high performance, so I hope you guys attract interest despite all the library/framework fatigue we're experiencing in frontend JS land. It's rather refreshing to be able to write code and view all together, like .css(appropriate_styling) It would be great if you had some walked-through example…
I think the HTML standard prohibits you from using non-standard tags like or , unless they have a dash in them.
Earlier quoted context omitted.
Javascript is disguised to look like Java because people keep trying to "fix" it.
It was designed from the very beginning by Eich to look like Java and not because subsequent people tried to "fix" it. Where are you getting this stuff?
Where are you getting this stuff?
Why not use the more familiar C-syntax of JavaScript?
I'm a Python guy so that's probably half the reason - but the syntax looks nice and clean to me.
Earlier quoted context omitted.
JavaScript is syntax sugar for Scheme (Lisp variant). Lisp is proven to support large scale apps, but you need to cook it using another cookbook.
I have a lot of respect for Lisp/Scheme, but I wouldn't regard Emacs as the most maintainable of large scale apps. Besides, the ability level of the average Lisp/Scheme developer and the average Javascript developer is likely not commensurate.