201–210 of 257 posts
> Well, one problem is declarative programming has never been as expressive as imperative programming. In React you'd use JavaScript for this iteration. This is why I like React over say Angular, with ng-each, ng-if, etc. Flow control does not belong in markup. I cringed the first time I saw an XML schema with an IF element.
The other-side of the argument is that JavaScript is much harder to tool than HTML.
Earlier quoted context omitted.
Not at all! Honestly there are some WONDERFUL things about angular. There are some bad ones too. - Polling for changes vs. event driven - two way data bindings causing infinite redraw loops. - "feels like O(n^2)" performance on ng-repeats / large pages but things like the templating, directives, data-binding... they are all really good things. And dependency injection! They have really moved the needle forward on cli…
The overarching problem here is herd mentality. Using Angular is a bad idea, but lots of companies are using it anyway because The Herd stampeded towards the new shiny thing, mostly because of how cool two-way binding looked in Angular's demo toy app. Now all those companies are bogged down by Angular, but feel like ejecting it would be too costly. Elsewhere, lots of new developers are introduced to Angular and inves…
The most ironic thing in all this is that your comment is still full of Herd mentality, except that it goes the other way.
Angular is a framework, period. Using it is neither a good or a bad idea, it all depends on the people who actually use it.
Earlier quoted context omitted.
> I constantly feel that I'm behind on my homework having to evaluate new libraries and frameworks showing up. Every two weeks, another one shows up with another paradigm shifting approach. Every two weeks ? Try every day. I hate to be that guy, but this sounds like whining. You're a developer, it's an incredible privilege (we're part of one of the fastest-growing, most-successful businesses ever, and we basically ge…
Come on, I'm a full-stack guy and worked on lots of teams/projects/companies. I have yet to see a need to stay on top of every new development constantly, especially JS frameworks that still need to be proven. None of the productive developers I know care about all the daily/weekly noise, if something is truly new and good it'll become known on a monthly or quarterly scale. And about job description - developers are…
I imagine most here have day jobs with projects that last more than a few months so I doubt the need to learn things faster than your cycles of your job.
I'd be more interested to see a performance comparison with Mithril[1] rather than React, their core functionality is similar but Mitril strives to be lean and fast. [1] https://lhorie.github.io/mithril/
Agreed. Mithril's performance is incredible, and it's also closer to React in philosophy. That's the alternative I'd be looking at (perhaps along with Vue, which also goes unmentioned). EDIT: though, one difference is this supports server-side rendering out of the box, while Mithril requires a (tiny) third-party module: https://www.npmjs.com/package/mithril-node-render
I think it's great that there is such an amount of active development in the JS sphere, and I'm sure your framework is fantastic - so don't take this as directed at your framework specifically. That being said... I am however feeling so overexposed to new libraries and frameworks that I can hardly muster the energy to even look at it. I constantly feel that I'm behind on my homework having to evaluate new libraries a…
Take a look at Mithril. People are frequently surprised by its small learning curve (and for many, the majority of the learning is for knowledge that you can go and apply outside of Mithril)
I seriously think this is some sort of parody of JS. Really? A new framework every week?
As someone who mostly codes in Python, I don't understand, why JS gets new framework so often. What is the reason behind? Is Javascript makes thing easy to develop a new framework? Why doesn't Python get new framework so often?
It definitely did with django, pylons, flask, turbogears, web2py, . . . I didn't know which way to turn.
PHP had the same thing with cakePHP, symphony, drupal, and so forth. I remember rolling my own using smarty long ago, because I couldn't decide.
> Isomorphic JavaScript Framework No. Just no.
Is this just criticism of the "isomorphic" term? I'm not a fan of it either ("isomorphic" already has a different well-defined meaning in CS), but it does seem to have some traction now. Perhaps you have an alternative term you'd prefer these frameworks used?
Earlier quoted context omitted.
Totally fair question. I think the reason I want to try react is to compare and contrast the various approaches. I've written both angular & mithril for production. So far I haven't enjoyed anything as much as mithril. It is so clean & pure. It stays almost completely out of your way. In fact there are places where I'm actually running angular INSIDE mithril pages (long story, part of migrating a project from angular…
FYI, Mithril is largely a scratch-my-own-itch kind of project project and I use it heavily at work, so I'm definitely not going to walk away from it :)
But what if you're in a Starbucks, and the person behind you is the head of BMA Model's hands and feet division? (http://www.bmamodels.com/hands_legs_feet). As you reach for your frappachino you're "discovered" as the next-big-thing. About to explode into the glamorous, yet high stakes world of hand-modelling. It's a multi million dollar deal... but with the stipulation... no more coding effective immediately.
What happens to mithril then Leo? What then?
If it happened at facebook they'd give the job to Jimmy "Stubby Fingers" Malone and move on.
Obviously I'm teasing (hopefully at least).
I think there are actually a lot of advantages to your running mithril lean & (mostly) solo.
I've been impressed by seeing the contributors in github https://github.com/lhorie/mithril.js/issues and the quality of the discussions in the google group https://groups.google.com/forum/#!forum/mithriljs ... to say nothing of how great your blog posts are.
You contribute and participate in all those places and even turn up on HN.
It does make it a consideration when selecting a direction for a project though. It's a bit of a risk awareness/tolerance thing. I still think C# is way better than node.js for some things too :)
I think it's great that there is such an amount of active development in the JS sphere, and I'm sure your framework is fantastic - so don't take this as directed at your framework specifically. That being said... I am however feeling so overexposed to new libraries and frameworks that I can hardly muster the energy to even look at it. I constantly feel that I'm behind on my homework having to evaluate new libraries a…
To me this
-) is a sign of an area or areas of still not recognized core problems leading to tackling it from different angles
-) it could be connected to the average age of developers in the field responsible for the choice of their tools. They will settle for something with time ... eventually ;)
-) bears resemblance with an earlier me, eager to find the latest, newest and most importantly most different way to ... well, what actually? Most probably traverse the unknown landscapes of new, landscapes of "my way"
-) is worst than it used to be, as the _really_ old ppl say ;) ... or I changed the sides, moved on on this spectrum of professional attention deficit hyperactivity disorder.