ale55andro

If you want to be BIG then this is how you do it. You stop being a fucking joker :D

FIND A WAY. OR MAKE ONE! great stuff on there. This is an excellent motivational post.

This is a nice compilation. Thanks!

I guess I cannot argue that. all summed, at the end of the day, C# is quite nice indeed :P

I'm in agreement with wes-exp, even though I still have to make the "long walk home", mono currently offers a workaround or perhaps a false reassurance that when the requirement comes up, you can still run your apps on Linux. Truth is it's lagging behind, it does not enjoy good community support (everybody in the *nix community is against it) and to top it Novell was acquired recently and the new management put a lid on mono. Miguel has started a new company but it seems their priority is standing on their feet first ( making money and being profitable). So, no. Mono is not a good alternative for .net at this point.

the reason to rewrite depends on the project your involved in and what features you want to make use of moving forwad. A simple example when .net 2.0 came out, simply upgrading to the latest version of the framework didn't give your older apps all the benefits of latest features included in 2.0 (new controls, master pages, provider model support out of the box etc) ; A rewrite was inevitable. When MVC was introduced everybody in the .net community felt it was their sacred mission to promote it over webforms. If you wanted to stay current skillwise and evovle with the community you either rewrote if this was even feasible or used MVC for the next project ( for most this really meant a new investment in learning and also not being able to reuse a vast array of controls and component that were already written for webforms and available, instead we were reinvesting our efforts in rewriting in such a way that this was consumable from an MVC paradigm). I agree with you that a lot of this is just hot air, but not if you are seriously invested as in someone writing tooling for webforms for instance and your business depended on it, your customer base dimishes quickly and you have to quickly adapt and rewrite. This is the same for winforms/wpf/silverlight. People seriously invest in these technologies after going through a lot convincing top management and what not because MS promised at some point that they are committed to seeing this through.

Consider having a product developed in silverlight. Now MS is saying they are backing html5 but fear not, you can still rewrite it for metro because sadly IE10 on metro will not support plugins. This is their own plugin on their own operating system. Not supported! Which is not the same thing because SL atleast worked on the mac cross platform. Your metro app wont. So, html5? even still your developing a metro app so forget cross platform or perhaps you can reuse a lot of the code base but some effort is still required and we're really hoping for the best. In the end we are rewriting again.

Not very suspicious if you look at how .NET evolved and continues to evolve. They have had massive changes in their offerings which is a good thing but frustrating if your a dev strongly invested in what they offer. Often you have to rewrite your code with each new offering they push. Then ASP.NET Webforms slow death in favor of MVC, another major rewrite again. Along with the rewrites you are giving up a huge investment you've made in webforms ( their previous offering).

From asp.net 1.0 to 2.0 required a rewrite to take advantage of 2.0 featureset. From linq2sql to EF where linq2sql was dropped in favor of EF and we still have no proper assurance. winforms 1.0 to 2.0 then wpf. Moving to wpf as you may guess requires a major rewrite. Then the rumors that wpf is dead. SL is the next best thing. Now they say SL is dead but your skillset will carry over to building metro style apps.

Perhaps he can avoid all this frustration now!

Dead is a rather harsh statement. It's true that the mobile market is flourishing and is more important now than ever, but what I see clearly is that adobe wants that market too and they seem to be investing in html5 tooling whilst maintaining their flash offering.

So in the end it will come down to using the right tool/tech for the right job. More choice to you, more power to you and works out for adobe as well. Don't forget that flash still enjoys an excellent penetration rate on the desktop and there will always be a market for it.

Perhaps one day when the pc is dead too and the indefinite, perfectly working apps written in flash are rewritten in html5 because we've now replaced the pc with tablets and mobile devices.

I got a crash ( using chrome on windows 7). I did get to see a slow scrolling rectangular 3d cube before the tab crashed. The crash is probably due to the specific video card I have in use. Nice demo still.

Regardless, it's still good information.

I thought the website looked neat. It's not going to win any competitions but it's well done and a good start. The idea is interesting too. If this person wasn't passionate about what they were doing, I'm sure they wouldn't be writing a post to improve their visibility and exposure. I wish them good luck and so should you :P