Skip to main content

No to new browser unless it keeps the rendering close enough

Dam browser wars.... As a developer I am tired of running virtual machines to test a single site in ever growning list of browsers. I really agree with this articles point.

Current the browsers I test and have on my machine

Win Vista Business (SP2)
  1. IE8
  2. Chrome 2.0
  3. Firefox 3.5
  4. Safari 4.0
  5. Opera 9.64
  6. Firefox 3.0
  7. Firefox 2.x
  8. Virtual Machine (Win XP)
    • IE6
  9. Virtual Machine (Win XP)
    • IE7

Why is that a developer has to suffer at the expense of these big shots, what a average developer has to do to make a living out of a limitted bid amount or time, how can I test so many browsers and still make a profit out of a project or deliver the project on time by testing the website on each and every browser.

The sad part is when a new browser like chrome came just a year ago, the client felt the site has to support it.... no one till that point cared about how the site looked in mac or in safari...

May be I wasn't a mac fan but still its dramatically different and it's always pain to test every single page on multiple browsers.

I really support the notion of killing IE6 browser and forcing clients to upgrade because it's becoming a nuacense, when you provide people a content management system to add/edit/update they thing everything will work as magic, but it doesn't.

Take for instance copy/paste from word processor, I cannot support so many flavors of word processors and I get nightmares about copy paste of microsoft word... if only the whole online web site is online and not mix and match of desktop and online... or a better solution make everything xml complient so all we have to worry about is xsl the rendering and not about copy paste, right click left click, hot keys, F5... geezzzzzzzz....


Popular posts from this blog

Completed UiPath - RPA Developer Advance Training

After a month of training, with late nights and weekends I have completed the UiPath RPA Developer Advance Training.

The Level 1 Foundation Training pretty much covered all the basics of Desktop studio and workflows, only draw back was I started with the default foundation course which was for 2016, and all document reference links where pointing to 2016 version. I didn't understand it during the foundation training and kept switching to 2018 version document/page.

Only after completing the Foundation course that I realized, I was suppose to have started with the 2018 version of Level 1 Foundation Training, but as it was optional I didn't have to retake the 2018 version, the 2016 was good enough for moving to level 2.

The Level 2 Orchestrator 2018.3 Training as good. It gave good understanding of Queue's, Jobs, and schedules and I was able to complete the level two much faster then the level 1.

The Level 3 UiPath Advanced Training was bit tough as it involved the assignme…

Working hours in six months to a year

I usually try to look for how many hours I have worked on a given project and what hours that I  spend on learning or network management tasks.

Below I have added some hours calculation, after finding the breakdown by months from Berkeley website.


2017Working hours six months (Jan 1st - Jun 30th): 
130 days x 8 hours =  1040 hours

Working hours six months (Jul 1st - Dec 31th): 
130 days x 8 hours =  1040 hours

Working hours for the year:
1040 hours + 1040 hours = 2080 hours
MonthWorking Days in the monthMonthly Working Hrs1/2 of working hrsMidpoint of working days in the monthDates of HolidaysJanuary22176888 a.m. 1/172,16February20160808 a.m. 2/1520March2318492Noon 3/1631April20160808 a.m. 4/17May2318492Noon 5/1629June22176888 a.m. 6/16July2116884Noon 7/174August2318492Noon 8/16September2116884Noon 9/154October22176888 a.m. 10/17November22176888 a.m. 11/1610,23,24December21168…