Even though i don't like your attitude i will try to give a little info that may assist other people.
The reference i have is a couple of enterprise level projects (information systems for the public sector) built with c#, iis6 for the server side parts, sql server 2005 and win2003 R2 servers. Also sharepoint which was quickly replaced due to slowness and high resource consumption.
- Win2003 servers had a limit on the amount of RAM so that was a bit of a problem along with the sluggish performance compared to linux based servers that we are used to work on. Did we have a choice to switch operating system? hm.. not really
- sql server was pretty good it did much better than i expected and i really enjoyed all the functionality out of the box, but that was until we reached more than 10 millions of records in some tables, then it was no more fun but that could obviously happen with any database. Did we have a choice to switch database? hm.. not really
- iis6 whether you like it or not you have no other choice. Having a background with jee application servers of different vendors where i could configure and customize them in any level, switch them with other vendor solutions and do plenty of architectural tricks.... i did find iis situation a bit weak
- programming with c# was great, but if we needed any good libraries/APIs did not exist or we had to pay, not many choices here either and as with all other parts targeted only to ms platforms
Stackoverflow is really great, and i was sure that in the past i had stumbled upon a post about stackoverlfow architecture i.e. http://highscalability.com/blog/2009/8/5/stack-overflow-arch...
to be honest i was a bit suprised that they were using ms technologies.
To me the bottom line is that for large scale projects based on ms technologies you will eventually need to invest money and time to proprietary solutions without many architectural choices, at least not as many as other platforms provide. Of course that is certainly not a problem if one works only on ms platforms.
At the server side it simply gives no choice but proprietary and unreliable ms systems and a weak app/web server (iis). The desktop client side is only good for ms clients. For the devices realm there is nothing to talk about really and regarding windows phone it's a bit early.
I've worked with .net in the past but now i usually avoid it as much as i can.
Downloaded win version for a 32bit xp system and noticed two bugs,
1. along with the app another window started which was like the menu with a menu item "File" represented by a horizontal line at the very top of my screen, i just right clicked from task bar and closed it, main app still worked.
2. tried to open saved html file with browser (assigned to chrome) but the url was wrong, it was missing the drive letter so nothing showed.
3. after closing page and then choosing another template the app vanishes.
At first glance it is ok, maybe better suited for users without much experience with browser tools and code. However it provides viewing in different screen sizes, code snippets and drag and drop which are helpful.
Same approach here. No ember-data just creating Ember objects within a type of DAO ember class/object using ajax calls to the server side. Caching is enabled both in client at that Ember controller and on the server side before hitting the data source, however this depends on the data requested.
If offline capability is required on the browser or mobile device, local storage also comes into play.
I agree that all this is really clear and simple.
From personal experience in order to get started just checking out the documentation(i had started with the old documentation now called guides) should be fine. Some googling around might be needed but should not take much time. Generally i agree that it is a bit hard to get used to the framework, but if one has the ability to look in the console and figure out errors, should not really have any problems getting started with emberjs. Also just grabbing code from the first page, i don't think is a really good idea. Does this technique work with other popular frameworks like http://nodejs.org/http://jquery.com/ .... ?
i've been using ember for the past three months in a fairly complex project and i'm very happy with it ; a platform that builds business web apps dynamically for devices (20+ pages,250+ fields per app with validations, calculated fields, conditional flows etc , rendering/theming in jqm -> packaged with phonegap) and client web browsers (render/theme in bootstrap),the backend is in java. So, i certainly don't feel the same way for emberjs as the writer.
I had decided to build the frontend in a js mvc framework and the candidates were backbone, emberjs (pre version), angularjs. Read about them and gave backbone a try, however from the documentation only emberjs approach felt better maybe because of a similar in-house development java framework that we work on. So i tried to give emberjs a try at the same time, due to the tight deadlines. I dropped backbone, and spent more time on emberjs because everything simply worked and fitted together nicely. All these binding mechanisms are great and actually work :) . Haven't tried angularjs.
The system now works with emberjs (pre and rc) with a nice layered architecture and separate independent business logic modules.
My advice is to read the documentation carefully and choose what fits better to your needs and coding styles.
Thanks for posting this article.
Dr. Joshua A. Miele is an incredible person and very inspiring. Thank you for your great work and contribution to people.
i've been using ember for some time now for a complex application and everything seems to be clearly separated. Easily integrated with jqm and generally its model and controllers can be used effortlessly by other frameworks as well. Actually the complexity depends on the context and kind of integration.
Thank you Paul for sharing!
no_more_death i share your beliefs and i think you answer to yourself. Christianity does not encourage coercion at all, after all as you mention only states the consequences of actions that people might take.
umm.... i think he focuses on the merits of the new product and the fact that the company eventually paid attention on the details, otherwise he would probably go for something else
I agree with other commenters, that sometimes you try other revenue streams in order to see how the market or potential customers might respond. If you see any good signs then one may choose to focus and strengthen these options.
In addition to the 3 minimal actions I would also add, to use relevant keywords in each page's content. Often I notice clients creating content without actually using the keywords, by which they want the specific pages to be found. Also check the grammar, especially when creating multi-language content.
It's true that some people are genetically more intelligent than others. What matters is what you do with your intelligence, which only makes the work easier or harder, and the amount of improvement. People can get much better or worse, regardless of their genetic characteristics. After all anything genetic has been simply given for free..
- Win2003 servers had a limit on the amount of RAM so that was a bit of a problem along with the sluggish performance compared to linux based servers that we are used to work on. Did we have a choice to switch operating system? hm.. not really
- sql server was pretty good it did much better than i expected and i really enjoyed all the functionality out of the box, but that was until we reached more than 10 millions of records in some tables, then it was no more fun but that could obviously happen with any database. Did we have a choice to switch database? hm.. not really
- iis6 whether you like it or not you have no other choice. Having a background with jee application servers of different vendors where i could configure and customize them in any level, switch them with other vendor solutions and do plenty of architectural tricks.... i did find iis situation a bit weak
- programming with c# was great, but if we needed any good libraries/APIs did not exist or we had to pay, not many choices here either and as with all other parts targeted only to ms platforms
Stackoverflow is really great, and i was sure that in the past i had stumbled upon a post about stackoverlfow architecture i.e. http://highscalability.com/blog/2009/8/5/stack-overflow-arch... to be honest i was a bit suprised that they were using ms technologies. To me the bottom line is that for large scale projects based on ms technologies you will eventually need to invest money and time to proprietary solutions without many architectural choices, at least not as many as other platforms provide. Of course that is certainly not a problem if one works only on ms platforms.