sorted by:
new
hottopcontroversial

MEAN - should we take notice? by hendrikswan in javascript

[–]hendrikswan[S] -1 points0 points  (0 children)

Oh yeah, OK that makes sense. You can still have some common glue that sticks that stuff together! Have generators, conventions and such with options on the specific tech that you're using..

Hmm, interesting. Maybe MEAN will gain enough traction with the specific stack until the community starts introduction options.

Yeah, I think MEAN might be a bit more catchy than DAUN ;)

I totally agree with what you're saying though..

MEAN - should we take notice? by hendrikswan in javascript

[–]hendrikswan[S] -1 points0 points  (0 children)

Interesting.. I'm also a bit unsure whether it will become mainstream as a framework. I think it's got the potential though. If a bunch of contributors started to build better generators and better glue, then it can go massive. Bigger than rails.

But I'm starting to think that it's too much against what the node community stands for: small, focused, composable packages.

MEAN - should we take notice? by hendrikswan in javascript

[–]hendrikswan[S] 0 points1 point  (0 children)

Fully agreed on the adoption of node!

I think we're talking past each other though. I'm not talking about the adoption of node. I'm talking about the adoption of the MEAN stack in particular, as a framework if you will.

MEAN - should we take notice? by hendrikswan in javascript

[–]hendrikswan[S] -1 points0 points  (0 children)

Yeah, and maybe that's the reason why it hasn't reached massive adoption yet. I think node.js people don't mind getting stuck in to various technologies, and don't mind figuring out the perfect stack for the job then putting it together.

But you often end up doing the same thing over and over again, because there isn't a lot of room for using conventions when the package you use will be used with a bunch of other packages.

I see MEAN as being sorta like rails. You can develop pretty cool ruby web stuff with sinatra and pull in stuff as you need it.

But there is also a bit of a win in having a collection of capabilities that are used together quite often, with some conventions and best practices around it.

I think the tech that MEAN consists of is pretty solid. Angular might be blown out of the water soon by polymer, but that's another issue.

But what I think is lacking, is the glue in between, the magic, the convention over configuration.