[wp-hackers] Redactor WYSIWYG Editor for WP

[Kevinjohn Gallagher]

> Kevinjohn I'm curious if your NS4/6 fans appreciated that their desire to support outdated systems should also increase their costs over update of browsers, possibly up to 3x and maybe even 10x?
Some do, some don't.I am always upfront about our costs: supporting IE6 or IE7 will add 1 year of my mortgage to your cost - flat rate, regardless of size of project.
The specific company that asked the NS4/6 question had over 50,000 employees ; and was for an intranet CMS RFI.They weighed up the cost of supporting the development in older browsers browsers; versus the cost of upgrading over 50,000 computers (in over 100 languages and 200 countries) and all the support questions it would raise. For every year they supported the older browsers, they saved more money than I'll make in my lifetime.
We geeks sometime forget that upgrading, heck CHANGE, has a cost associated with it (time / money / support / training ). Sometimes the cost of doing nothing, is less than the cost of change.

(hopefully didn't de-rail this thread)

Kev

Kevinjohn Gallagher    
+44 (0) 7788 718382 
KevinjohnGallagher at hotmail.com 
http://www.kevinjohngallagher.com 
http://www.linkedin.com/in/kevinjohngallagher 




> From: mike at newclarity.net
> Date: Sun, 12 Aug 2012 14:59:07 -0400
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] Redactor WYSIWYG Editor for WP
> 
> On Aug 12, 2012, at 11:10 AM, Kevinjohn Gallagher wrote:
> > Doesn't support IE7.Regardless of whether you or I like the browser; a large number of companies/organisations/educational-institutes still use this browser.
> > Last year we answered an RFI where we were asked to support Netscape4/6.
> > Apparently the client didn't actually care about NS4/6, but wanted to weed out the companies who would complain about Enterprise's not upgrading everyone to the latest version of every bit of software they use.23 companies didn't make it through to the RFP process on their answer to that question alone.
> > 
> > On top of that any CMS that changed its layout / workflow significantly within a year of a previous release was deemed to be ruled out.
> > I understand the desire to change these things; but honestly, there needs to be some benefit to the people using and choosing the software - otherwise we're just re-painting!
> 
> I love this post; real-world pragmatic concerns, something I feel too many people dismiss or outright ignore.
> 
> That said, Kevinjohn I'm curious if your NS4/6 fans appreciated that their desire to support outdated systems should also increase their costs over update of browsers, possibly up to 3x and maybe even 10x?  I completely agree that technologists should be more willing to embrace real-world considerations, but I often find that clients want this but also want the same prices they would get if sites were simply coded for modern browsers, and I find that hypocritical.  
> 
> Supporting legacy browsers is not that different from writing mobile apps on multiple mobile platforms; it's a lot more complex and a lot more costly to make it all work. Have you found these companies who expect legacy support to be willing to pay significantly more to get it?
> 
> -Mike
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers