211–220 of 354 posts
So, had gone through samples and my conclusion as a seasoned web dev with projects as big as having thousands of files with hundreds business scenarios, imba is not the setup for this scale. When people come and go, requirements change, new tools come along, trading flexibility to some initial development boost is not worth it, imo
Earlier quoted context omitted.
Considering Javascript is the only language supported on the frontend, claiming to be more productive is definitely valid. Coffeescript was a breath of fresh air compared to writing ES5.
I sure am tired of Javascript being the lingua franca of the web. Imagine if we decided C was good enough and now all programming languages from that point on should just be something that cross-compiles to it.
> Getting started > > The best way to get started with Imba is to use npx to get a brand-new project up and running. What is npx?
npx will run the node package from node_modules if it's present, else it will npm install the package and then run it.
Looks cool. I'm honestly curious as to why a lot of new web languages/frameworks are mixing logic and content in the same file again though. The distinction between HTML, JS and CSS always made perfect sense to me. Anyone care to enlighten me?
When all three of these things have to care very directly about eachother, separating them makes less sense.
This read like gibberish to me 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 understa…
fs = font-size
fw = font-width
ta = text-align
c = color
Looks cool. I'm honestly curious as to why a lot of new web languages/frameworks are mixing logic and content in the same file again though. The distinction between HTML, JS and CSS always made perfect sense to me. Anyone care to enlighten me?
A feature usually consists of all three HTML/CSS/JS. So, if you split by technology, you don't have the code belonging to one feature in one place.
Looks cool. I'm honestly curious as to why a lot of new web languages/frameworks are mixing logic and content in the same file again though. The distinction between HTML, JS and CSS always made perfect sense to me. Anyone care to enlighten me?
https://adamwathan.me/css-utility-classes-and-separation-of-...
Looks cool. I'm honestly curious as to why a lot of new web languages/frameworks are mixing logic and content in the same file again though. The distinction between HTML, JS and CSS always made perfect sense to me. Anyone care to enlighten me?
This is exactly why I prefer Angular to React. Our designer wouldn't have been able to deal with HTML markup within the JS files in React. Having the HTML and (S)CSS separated out made life much easier for him in Angular. (edit: Naturally downvoted due to being slightly critical of React on HN. Which happens every time.)
You are being critical of separation choices. To which I am curious why embedding the CSS and HTML inside a Javascript file makes any difference to the designer? In practice, we often see slightly different syntax to accommodate, but I cannot imagine that is a true barrier. The CSS and HTML (or their slightly modified equivalents) are still logically separated from the rest of the logic in the file.
I just want to compliment the OP on a very clear and comprehensive website at https://imba.io/ . It clearly explains (by showing and telling) what Imba is, why I should care, how it works and how to get started. The floating demo applications even work well on mobile. Rare to see this level of polish for these things.
Exact opposite of Elastic.co.