3 ms·

I guess the reason why your client chose ExtJS of Sencha instead of Backbone/Ember/Angular is due to the level of support they can get from Sencha, not because

I guess the reason why your client chose ExtJS of Sencha instead of Backbone/Ember/Angular is due to the level of support they can get from Sencha, not because of any advantages or what not. Decisions like that don't come from developers, they come from the typical 'business guy'. Generally speaking bleeding-edge frameworks don't bode that well for any business guy. If a problem arises and a developer gets stuck, a developer just googles it and looks for ways to tinker with it - in the eyes of the 'business guy' they'd opt to throw money at the problem for it to go away, no time should spent troubleshooting or googling. To sum it up: your client can't rely on a community of people that supports things only in their spare time. Thus by gaining comfort and trust from buying ExtJS contracts (https://www.sencha.com/store/extjs/ https://www.sencha.com/store/extjs/) - whenever something goes wrong, your client's dev team gets stuck or needs training they can choke the hell out of Sencha for it. Just let them go through with ExtJS. If the decision maker has consulted his devs long enough, it's a better decision. Being in one page and getting their things done quickly is far better than taking too much time learning things and contemplating on what framework to use.

eduardordm 14y ago
"The reason why they chose ExtJS of Sencha instead of Backbone/Ember/Angular is due to the level of support they can get from Sencha, not because of any X number of features." I would pay 10x more for consulting instead of support. The constant need for support means your team is incompetent. If you need external support to keep things moving, chances are you won't get very far. "in the eyes of the 'business guy' they'd opt to throw money at the problem for it to go away, no time should spent troubleshooting or googling." I'm also a co-founder and technical guy, I assure you spending money is always the last thing any company wants to do. "Decisions like that don't come from developers, they come from the typical 'business guy'." Lead engineers are usually who de-facto make those choices together with a CTO. "To sum it up: your client can't rely on a community of people that supports things only in their spare time." I've been running an 'enterprise' company with Rails, for almost 7 years now. Both the applications and the company are large. I don't really understand what 'rely on a community' means here. Who does not depend on open source software?
- acesubido 14y ago
  > I would pay 10x more for consulting instead support. The constant need for support means your team is incompetent. If you need external support to keep things moving, chances are you won't get very far. Totally, agree > I don't really understand what 'rely on a community' means here. Who does not depend on open source software? I'm sure you know this - that's how a huge chunk of non-tech people view anything labelled with "open-source", they all view it as "unreliable" or "geeky". By how I constructed my sentence it seems I'm saying this from my perspective, but we're like minded in that aspect: everyone depends on open source software one way or another. I'm just assuming that's how his client thinks. I'm assuming the decision maker for his client is one of those 'guys' who's outside the tech bubble, and probably worse: they don't listen to engineers. I mean, if OP has already built a nice prototype on Backbone and it's all good why would they go towards ExtJS? Backbone is widely used and constantly worked upon, if his client is well aware of the software development industry they wouldn't just dismiss the prototype and go towards something with 5-digit contracts. Again I'm just assuming the worst case scenario about OP's client by trying to understand the situation from what he said about their decisions. > I'm also a co-founder and technical guy, I assure you spending money is always the last thing any company wants to do. I'm also sure you know this: any hard-headed, non-tech decision maker outside the software industry who is very desperate would throw a lot of money for a problem to go away.

eduardordm 14y ago

"The reason why they chose ExtJS of Sencha instead of Backbone/Ember/Angular is due to the level of support they can get from Sencha, not because of any X number of features." I would pay 10x more for consulting instead of support. The constant need for support means your team is incompetent. If you need external support to keep things moving, chances are you won't get very far. "in the eyes of the 'business guy' they'd opt to throw money at the problem for it to go away, no time should spent troubleshooting or googling." I'm also a co-founder and technical guy, I assure you spending money is always the last thing any company wants to do. "Decisions like that don't come from developers, they come from the typical 'business guy'." Lead engineers are usually who de-facto make those choices together with a CTO. "To sum it up: your client can't rely on a community of people that supports things only in their spare time." I've been running an 'enterprise' company with Rails, for almost 7 years now. Both the applications and the company are large. I don't really understand what 'rely on a community' means here. Who does not depend on open source software?

acesubido 14y ago
> I would pay 10x more for consulting instead support. The constant need for support means your team is incompetent. If you need external support to keep things moving, chances are you won't get very far. Totally, agree > I don't really understand what 'rely on a community' means here. Who does not depend on open source software? I'm sure you know this - that's how a huge chunk of non-tech people view anything labelled with "open-source", they all view it as "unreliable" or "geeky". By how I constructed my sentence it seems I'm saying this from my perspective, but we're like minded in that aspect: everyone depends on open source software one way or another. I'm just assuming that's how his client thinks. I'm assuming the decision maker for his client is one of those 'guys' who's outside the tech bubble, and probably worse: they don't listen to engineers. I mean, if OP has already built a nice prototype on Backbone and it's all good why would they go towards ExtJS? Backbone is widely used and constantly worked upon, if his client is well aware of the software development industry they wouldn't just dismiss the prototype and go towards something with 5-digit contracts. Again I'm just assuming the worst case scenario about OP's client by trying to understand the situation from what he said about their decisions. > I'm also a co-founder and technical guy, I assure you spending money is always the last thing any company wants to do. I'm also sure you know this: any hard-headed, non-tech decision maker outside the software industry who is very desperate would throw a lot of money for a problem to go away.