I’m pretty sure this thread doesn’t have any special “top billing”.
As to why I don’t think this should be locked, see Comment 106
2 Likes
I feel like focused topics would be more beneficial. There’s tons of great thoughts in here, and I wouldn’t want them to go away, (I guess I didn’t really mean to use the word delete) however ~ if each line of thought had it’s own thread I bet we’d be able to drill down to more meaningful ideas that could benefit the community. Either way, if it’s a venting thread - I put my steam in it already. : )
Maybe it’s how I have my filter… I’ll set it to “new.”
@eccegordo @workmanw @Panman8201 @bailey86 I’ll be cross posting this to the responsive framework thread, but you might really like what I’m about to release here: https://github.com/runspired/flexi/pull/1
I might have just met this bootstrap menu issue you mentioned. It didn’t collapse on mobile automatically when menu links are clicked. I found a way to deal with by the help from this post. Bootstrap navbar collapse - #14 by Hao To what I don’t like bootstrap about on mobile is the slow responsiveness of the click but that’s not their problem. Click is always slower than touch. (300ms seems). There is Ember addon which is even trying to solve that: https://github.com/runspired/ember-hammertime
What do you mean by React’s “imperative” approach? I thought the whole point of React was to be purely functional and not imperative at all. I must be missing your point.
You can use this ember-cli addon and it manages the collapse on mobile properly: GitHub - zoltan-nz/ember-bootstrap-nav-link: Ember CLI component - Bootstrap 3 navigation link with proper active state management
I hate ember!!! I don’t see any advantage to use it…
The time for develop an application increases indefinitely with the complexity. .Ember is big so you have to study many and many and so if you want to hire a new person you have to hire a person only for ember… not all company can hire one person for develop a front end when this is also simple… Complexity for the configuration, you have double configuration for backend and front end, two https certificate ecc… Adapter configuration… Duplicate the model data in backend but also in front end… The official documentation show how work the single piece but not how these piece work together…and is the only guide…and miss important thing like the use of the form ecc…
How you can use ember with another framework? I search for Rails and I find only two amateur guide of one page…And for the other framework i can’t imagine
But if I think that I can use JQuery and give good name to the file and use the include sistyem that every framework have…
The only advantage is the speed that with the new language Java9, rails5 and good server not justifies the increase of many hours of development…another advantage is that the data update automatically and this is helpfull but depend of the site…but is important to comunicate in “real-time” the insert or update of an element…in “real-time”…and not after 10 sec when the user change or refresh the page…I think this is helpfull only if you have a specific site but i see helpfull only for 1 on 10000…so not justifies the increase of many hours, the big effort and the bill…
Is helpfull if you work with big data but big data sure
The big problem is that for me is not natural
1 Like
Alessio,
We still 
you.
Ember has trade-offs.
You’ve learned (the hard way) what some of them are. However, I’m confident that you will continue to run into these kinds of things no matter which javascript tech stack you choose.
Honestly, though… if you were the guy/gal that solved all these problems and blogged about it then you would be one of the Ember elites. The kind of folks that work from anywhere they want and are paid handsomely for the privilege 
You see problems, I see opportunities!
Take Care, I hope that you find what you are looking for!
– Benjamin
2 Likes
If you’re doing something relatively simple then the time/effort to learn Ember might not be justifiable. On the other hand, once you have learnt it, you can be much more productive going forward and it will feel natural. Nothing new will feel natural to begin with because you’re forced to learn/think differently, Ember is definitely not unique there.
Whether it’s worth it and/or whether you like Ember’s approach is a personal choice but don’t be too afraid of new ideas because they’re part of why JS has evolved so rapidly. There was a time when jQuery would have been viewed as “unnatural” but now everyone struggles to remember a world before it existed!
I’m pretty sure Ember is great but you’re right, documentation is hard to understand, (At least for a begginer)
1 Like
While there is value in discussing negative experiences, that value is diluted by lumping together unrelated experiences in a thread that spans many years, many projects, and many very different versions of Ember. With that in mind, we’re going to lock this thread. Please feel free to open new threads about your unique experiences, good and bad, which can be discussed separately and with more focus.
5 Likes