4 ms·
Uh hang on. Cappucino or ExtJS vs XAML/C#? Are you trying to compare Apple vs Orange or JS vs Flash/SilverLight? One of the previous companies I worked for bet
by hello_moto 15y ago
Uh hang on. Cappucino or ExtJS vs XAML/C#? Are you trying to compare Apple vs Orange or JS vs Flash/SilverLight?
One of the previous companies I worked for bet on WPF and it didn't go well. Memory hog, crashes, boilerplate code (sometime hidden by VS.NET), and the consensus was that WPF pretty much sucks out of the box (have to work very hard to make it look good).
By the way, another company I used to work for used GWT + Ext-GWT (GWT port of Ext-JS). It was pretty good as long as you don't have to modify the Look-n-Feel to be something it is not.
- moonchrome 15y ago>Uh hang on. Cappucino or ExtJS vs XAML/C#? Are you trying to compare Apple vs Orange or JS vs Flash/SilverLight? Silverlight vs Cappuccino and ExtJS. We tried both before silverlight and eventually gave up as the code became a complete mess (javascript and that monstrosity objective-j), debugging was hell (especially with objective-j) and documentation substandard (cappuccino had the assumption that you were keeping the apple cocoa reference handy I guess). OTOH Silverlight and MVVM Prism worked like a charm, we were able to redo the months front-end work in few days (everyone needed to pick up Prism). Things were super easy to mock and provide concepts with the Blend tool. If they only had TPL it would have been ideal. >One of the previous companies I worked for bet on WPF and it didn't go well. Memory hog, crashes, boilerplate code (sometime hidden by VS.NET), and the consensus was that WPF pretty much sucks out of the box (have to work very hard to make it look good). So you agree then - tools and platforms do matter ? If there was no time to "work very hard" would the project succeed ?
- hello_moto 15y agoThey rewrote from delphi, that was usable and efficient, to wpf. Bad call.