The Eric Wroolie Blog

Overpass Experiences

I love coding for WP7

by Leave a Comment

So, I’ve spent ages trying to learn to code on an Android.  I’ve read a few books.  I’ve got my dev environment all set up.  I’ve coded a few test apps and put them on my phone.  But the going is slow.  If I were a Java developer, I’d probably be all over it.

A friend asked me to do a quick Windows Phone 7 app and I could not believe how easy it was.  Since I’ve been working heavily with Silverlight for the past few years, I know most of the code already.  I had to do minimal reading to get a full app up and running.  It was was nice to work in Visual Studio again.  Using Resharper, I was flying through the code.

I only wish more people had Windows Phone 7. 

I would get a phone myself, but 3 things are holding me back currently:

  1. I don’t want to be one of 5 people in the UK with a Windows Phone 7.
  2. It’s not open, like Android is.  I would be at the mercy of the phone manufacturers for upgrades (like with an iPhone).
  3. It doesn’t have expandable memory (to my knowledge).
  4. My current contract isn’t up until April.

But it’s nice to be able to write apps so quickly (since I spent so much time learning the trivial details of Silverlight).  Maybe.

The “View Source” belongs to me too.

by Leave a Comment

For me, the sign of a good web developer (or web application developer) is someone who can right-click a web page to view the source and tell you why he did things the way he did.  “I used this div to position this element over here, and used the unordered list for a sub-menu, . . . “

A bad web developer is someone who says “It looks fine in my browser” and “Well, I’m not a designer . . . “

One of the biggest crimes of ASP.net Web Forms was to strip HTML skills from new web developers.  They view the source of their code (in the browser—not Visual Studio) as gobbledy-gook.  And ASP.net ensures that it is.  It’s full of ViewState and control names like ctl_100_className_ctrlName which the developer didn’t put there.  It tried to remove the whole stateless-http challenges and make web development accessible to desktop developers.

I’m so very pleased every time I see a new site created with the Microsoft MVC Framework.  MVC is making up for the ASP.Net webform crimes.  Just like Ruby  on Rails or PHP (or classic ASP), it allows the developer to think about what gets sent from the web server to the browser.  When I do a site in MVC framework, I can view the source and recognize my own handy-work.  I can make full use of CSS3 and jQuery.  I know that everything in my user’s browser is something I put there intentionally.

CSS, Javascript, and HTML (along with images, flash movies, Silverlight, or other plugins) are the ingredients of any web application.  Server languages like ASP, PHP, and Ruby are only tools to deliver these ingredients to the browser in unique and creative ways.  A good web application developer (like a good chef) can look at his source and tell you exactly what everything does.  ASP.Net webforms are like ready-meals.  Everything is done for you, but you don’t really know everything that’s in it.

Now, don’t get me wrong, I’ve known some fantastic ASP.Net devs who build apps free of ViewState and server controls.  But I’ve worked with too many who could drag a control onto a web canvas, set a few properties, and call themselves web developers.

I recently worked on a DotNetNuke project where we customised a third-party component.  The page was not rendering as it should.  ViewSource gave me a bunch of ViewState and nested tables.   I knew of a 100 ways to get css to make the site look the way I wanted, but this wasn’t my source.  It wasn’t even the developer’s source—it was the clientIds of the server control.  Since I was struggling, a web guy (proper Mac-using, firebug-toting, standards-compliant, web guy) asked to see the source so he could suggest something.  When he saw the source, he was mortified.  I was embarrassed –“It’s not mine!  I didn’t write it.”  In the end, I hacked it with jQuery.  I didn’t have the sourcecode to modify it properly. 

The legacy of Web Forms lives on.  Sharepoint 2010 is full of it.  Young Microsoft developers (in the last 5 years or so) know nothing but how to use WebForms.  (An ASP.net dev told me a few years ago “But I don’t know html.”).  But, hopefully, one day we will get around this idea of creating tools that “do everything for you” for developers who should know to do it themselves.  Just like I wouldn’t create ready meals for people who call themselves chefs.

DNN, Orchard, and Joomla–some thoughts

by 3 Comments

I’ve been looking at CMS systems a lot recently.  Here are some of my thoughts:

DotNetNuke

I’m using DotNetNuke for a contract right now.  Although it’s written in Asp.Net and I can code in that easily, it’s a pig to run.  Even version 6, which was released last week, seems sluggish when run in the browser (even on my local machine with 8gb ram). 

DNN is advanced—don’t get me wrong.  There is no lazy-ness there.  In fact, there is so much available in DNN, that it pains me that it runs so slowly.

It’s an okay platform.  But compared to MVC or PHP counterparts, the ASP.Net webforms are still far too slow and lack elegance.  DNN will always have that Asp.Net webform dependency hanging around its neck.

Orchard

Orchard is a new CMS which was started by Microsoft.  I fell in love with it last month.  It’s based on MVC3 with the razor engine.  It supports multiple sites, just like DNN.  There aren’t many extensions or themes, but it’s written in C# so I can easily create what I need.

But, then . . .

But then I looked at the page source after it has been rendered in the browser.  Although it doesn’t have a lot of ugly ViewState like DNN (and all other webform pages have), it does include a lot of stuff that I didn’t put there.  There is huge amount of javascript added which would at least triple the size of my source.  The beauty of MVC is that I have more control of the html—but Orchard adds a stunning amount of code.  Most of it is serialised model information—but I’m not sure why it is on the client.

This really bothers me because I spent a lot of time working with Orchard.  It is not easy to use as an Admin.  While DNN is simple and I could give it to any client to customise, you have to really study Orchard just to add a few things onto a page.  You can’t just add something to a sidebar, for example, you have to create a layer and add a shape, and add some code so it only shows when a page uses that layer or shape.  Really, it was ridiculously difficult.

So, Orchard adds too much to the source and is too difficult to use.  But, in terms of speed, it is very fast.

Joomla

Okay, Joomla is PHP.  I’ve done PHP projects for clients before, so I’m fine with that—but I prefer C#.  I looked at Joomla and Drupal just to see how they compare.

Joomla puts the .net CMS alternatives to shame.  It is easy to set up, the code is very current, and it delivers pages super-fast.  The admin interface is not as easy to use as DNN (in my opinion), but much easier than Orchard.  There are loads of themes and extensions available.  When I did a viewSource, all the html was what I expected it to be.

Why can’t the .net projects be this good?

 

One thing I hear a lot in my contracts are developers comparing .Net, PHP, and Java (and sometimes Rails).  DotNet developers always say .Net is better.  PHP and Java developers talk about how sluggish .Net is and how it is inferior because it requires being hosted on Windows (except for Mono—but who really uses that?).  The truth is, all these languages pretty much do the same thing—they deliver HTML to the browser.  You can write a site in any language and it wouldn’t matter.  I’ve seen .Net sites outperform PHP sites (but unfortunately, it is the other way around). 

I’ve looked at other .net CMS systems lately too (Umbraco, Sitefinity, etc) and didn’t like the look of those enough to even install.

I might start using Joomla.  Page speed is far more important than how easy it is to code.  Hopefully, someone will write a decent .Net CMS system one of these days.