Timeline for What strategies are you using to migrate your web site from Silverlight to HTML5 + JavaScript?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2012 at 0:23 | comment | added | Erik Reppen | It's critical in JS because you start with a blank slate and the mother of all paint cannons. | |
| May 29, 2012 at 23:07 | comment | added | NoChance | I like your point "it's also easy to set a paradigm with it and stick with it", it is a good idea in any language not just JS. | |
| May 29, 2012 at 23:03 | comment | added | Erik Reppen | In JS, architecture is your problem to solve but there are now many libraries out there that help with that and many years of vociferous client-side developers getting serious about architecture and best practices to guide people. JS's success isn't an accident, IMO. It's easy to make a mess with but it's also easy to set a paradigm with it and stick with it. Ultimately, it's an exceedingly powerful and flexible language when you know what you're doing with it. | |
| May 29, 2012 at 22:31 | comment | added | NoChance | @ErikReppen, thanks for your comment. The state of Silverlight today. In a short time it moved from a zero to a hero then the unexpected happened. Not many people could have guessed this. You point about HTML and JavaScript is valid but they have their pains too. You can get much cleaner code in SL and C# that what you'd get in JS and HTML. At least I think so :) | |
| May 29, 2012 at 21:36 | comment | added | Erik Reppen | Correction: "starting to support." Most of the old bells and whistles were supported but we've been waiting about 10 years for them to get on board for a lot of the newer stuff, which is in fact mostly quite mature in web-years. | |
| May 29, 2012 at 21:10 | comment | added | Erik Reppen | Except nobody owns JavaScript and HTML5. They are standards built off the old standards that everybody has agreed to try to work with. You don't always have equal access to the latest features on all platforms but code from 2002+ is still likely to be of some utility today. You can't say the same of Flash or Silverlight. The real question, is why would you go with proprietary technology in the first place when HTML5 is nothing more than what HTML, CSS and JS have been for years now with a handful of new bells and whistles that IE is finally supporting. | |
| May 27, 2012 at 22:20 | history | answered | NoChance | CC BY-SA 3.0 |