I've just found-out about this project and it looks very nice especially to guy coming from Laravel/Symfony background.
A question for the JS experts: Between this and Trails(Sails) how does one make a choice?
Adonis.js v2 released – Laravel for Node.js
21–28 of 28 posts
Re: Adonis.js v2 released – Laravel for Node.js
#22Earlier quoted context omitted.
I'm not sure what you're looking at... but it does resemble laravel quite a bit to me.. the way relations are setup is almost identical laravel: public function resources(){ return $this->belongsToMany('App\Resource'); } Adonis: posts () { return this.hasMany('App/Model/Post') } The routes/middleware page seems even closer to laravel 5's, that's all I've looked through so far, but it does look interesting at least as…
i mean, these features resemble basically every MVC ever
So what exactly were you expecting? What that defines "Laravel" to you is missing?
Re: Adonis.js v2 released – Laravel for Node.js
#23Laravel is a fantastic PHP framework, so if this is even close to as good for JavaScript it is worth checking out.
Yes. Laravel is very coherent php framework. But it seems there is no need php in future since ES6
I was going to answer to that post, then I realized I would be making a choice between PHP and Javascript on the server in the future.
And really, I want neither of them.
Re: Adonis.js v2 released – Laravel for Node.js
#24nope. I'm done. There are enough JS frameworks, client and server side. I don't need to look at another one. I'd really like 2016 to be the year that everyone who thought of making another new JS framework decided to not do that and instead go fix bugs in one of the existing ones that people are already using.
What do you like to use?
Re: Adonis.js v2 released – Laravel for Node.js
#25This is sorta tangentially related... I used to think DI was a good idea, but as I've gotten more experience... I'm no longer convinced using a DI framework nets you huge wins relative to the added complexity. My hypothesis is that good design can remove the need for a DI framework in many cases, or at least that's been my experience so far. Maybe I just haven't worked in an application that's big and complicated eno…
What is DI?
Re: Adonis.js v2 released – Laravel for Node.js
#26nope. I'm done. There are enough JS frameworks, client and server side. I don't need to look at another one. I'd really like 2016 to be the year that everyone who thought of making another new JS framework decided to not do that and instead go fix bugs in one of the existing ones that people are already using.
What do you like to use?
React+Redux and Express at the moment, but that's at the end of a long, long trail of trying out JS frameworks.
I got fed up of constantly learning new frameworks searching for that One True Framework that would be expressive and powerful but without too much boilerplate and... well, you know the quest.
I gave up looking for the Holy Grail and settled on what seemed to be working for me at that point (like quite a few other devs I know). It just got too much, the constantly learning new apis in order to keep up.
hence "I'm done"... I'm going to go deep instead and really learn how to use a single environment properly, as in 10,000 hours properly.
Re: Adonis.js v2 released – Laravel for Node.js
#27This is sorta tangentially related... I used to think DI was a good idea, but as I've gotten more experience... I'm no longer convinced using a DI framework nets you huge wins relative to the added complexity. My hypothesis is that good design can remove the need for a DI framework in many cases, or at least that's been my experience so far. Maybe I just haven't worked in an application that's big and complicated eno…
What is DI?
Dependency Injection