Top Reasons to Firefox even better than Chrome for web development

Some time ago, some of us, web developers, we changed the Firefox Google Chrome because of the important features such as speed.

With the release of Firefox 4, it solved some of the problems we had in past versions, leaving it better, at least when it comes to web development.

This article, divided into two parts, explains some of the reasons why the Firefox browser is still a better than Google Chrome for your web development work.

Evolution of the market share of browsers

About a year ago, I talked about something most of us already knew, that PHP developers are switching to Google Chrome as its web browser access.

As you can see in the table below, this trend continues to be true this year. These numbers were taken from statistics developers PHP Classes logged in to the site .

Browser	May 2009	May 2010	May 2011	Change
Mozilla Firefox	68.0%	63.5%	57.3%	-6.2%
Microsoft IE	18.5%	13.6%	8.9%	-4.7%
Google Chrome	6.0%	15.7%	28.1%	+12.4%

As you can see, Chrome almost doubled its share in a year, while Internet Explorer has lost a little more than half. Firefox also fell slightly.

The gain of Chrome is greater than the loss of the Firefox and Internet Explorer. This means that Chrome also gained share lost to other browsers.

Reasons to Firefox even better than Chrome for web development

Given the fact that the participation of Google Chrome continues to grow enough, you may wonder why on this article. The fact that Chrome will continue to become increasingly popular for web browsing does not mean that web developers are also working with him in his projects. For me, this is not the case. Often when I'm doing development work, I feel I need to switch to Firefox, for reasons which I will list below.

I wish they had in mind that this article is not a rant against Google, which gave us web developers a lot to be grateful to him, but when we speak of Chrome, there is still much to be improved.

I decided to write this article now in the hope that maybe someone at Google to read, and do something to resolve these issues, most of the time, really bother most of us, since we do not keep changing all the time browsers .

1. View HTML

When the code of our sites have bugs, it usually generates an HTML code that is incorrect or invalid. So we need to analyze the HTML code to understand what's wrong. Firefox has an amazing feature that allows you to select a portion of the page and it shows the exact HTML that corresponds to that portion of the selected page. This feature does not exist in Chrome.

The best you have is the Inspect Element feature, which allows you to find the HTML code for the page element below the cursor of your mouse. Not the same thing. If I select a region of the page, I want to see the full HTML of that region, not a single element.

Another annoying thing is that Chrome tries to make the HTML pretty. This means that if you have a malformed HTML, you will not see where he is malformed because Chrome will show an embellished version of the HTML code after it has been repaired. I wish they had an option to disable.

2. Validation of HTML

Another great feature of Firefox is the ability to display any validation errors of HTML that you may have. In fact, this feature is provided by the extension HTML Validator .

I tested several extensions with the same goal in Chrome, but nothing that was really good. Some just used the W3C validation service through the page's URL, which is not good, because when you are developing a page that is not public service W3C can not access it, and any user logged into the site you is developing can not access it.

Other extensions have tried to copy the currently loaded page and pass it to the validation service, but none showed any invalid HTML code that the Firefox extension HTML Validator shows.

It also does not rely on an external validation service. That means you can validate pages even if you do not have internet access. So for all these reasons, an equivalent version of the HTML Validator extension is sorely needed for Chrome.

3. Disable JavaScript

Sometimes you need to test your site with JavaScript disabled. The only way to disable it in Chrome is going to preferences and disable. This is truly annoying. In Firefox, you can use the extension Web Developer by Chris Pederick to add a button to the browser to quickly disable and re-enable JavaScript when you want.

In Chrome, there is also the extension Web Developer the same developer, but it provides no means to disable JavaScript. The problem is due to the limitation of the API exposed to Chrome extensions. It does not allow a way to disable JavaScript from extensions.

There is a request for funding for the project Chromium to implement the necessary support to disable JavaScript. Implementing this feature was actually given a year ago, but it never happened. Oddly, users have been banned from posting future comments on the application of this feature.

4. Empty the browser cache

Sometimes you need to force the cleanup of the browser cache, so that new content can be recovered from the site server you are developing.

It is the same limitation to disable JavaScript. You can not do this through an extension. You need to go in the preferences of Chrome.

There is also a feature request to enable support for clearing the cache from an extension. It was made more than two years, but only a few months ago was released for implementation.

5. Changing the agent identifier of the browser

Sometimes you need to access your site pretending to be developing using another browser, so you can see if it fits to that browser the way you expect.

For example, if you are serving an RSS feed to be handled by Feedburner, all you need to redirect browsers to the URL of the Feedburner feed, unless the current agent is checking if your Feedburner feed has been updated. Therefore, it would be helpful if you could cause the browser to pretend to be the Feedburner, so you could check if he was working as it should.

In Firefox, you can use the extension User Agent Switcher also Chris Pederick. In Chrome, there is also an extension called User Agent Switcher . The problem is that it does not work. Good works, but not the way you want. The extension can only change the browser identification exposed to JavaScript. This means that HTTP requests sent to the server will not use the string identifying the agent that you need to be sent.

I suspect that an application for resource to be implemented in Chromium, but not found. Until this feature is implemented, we will always have to go back to Firefox, which works well with the User Agent Switcher extension.

10 Reasons Why BlackBerry PlayBook is a Winner

Gadget Mobile Technology: 10 Reasons Why BlackBerry PlayBook is a Winner - The reviews of the new BlackBerry PlayBook are in and they are terrible. David Pogue in the New York Times dismissed it with, “It must be skating season in hell.” In the Wall Street Journal, Walt Mossberg was a tiny bit more charitable but he, too, ultimately shrugged it off as a non-event. Laptop Magazine just sneered at it: “Somewhere along the way, BlackBerry lost its cool.”

Here are 10 reasons to put PlayBook on the review list:

1. “PlayBook is targeted at mobile professionals,” said John Jackson, an analyst with CCS Insight. And that is key. It is not designed as a consumer product like iPad is. RIM instead created its tablet to serve the business user.

2. PlayBook, with a 7” screen, is ultra-portable and it's also zippy with a 1GHz dual core processor and 1GB of RAM. For employees who have been demanding a tablet because it is the latest new thing, PlayBook should scratch that itch.

3. You probably already support PlayBook because it piggybacks on BlackBerry’s enterprise products. CIO’s “already have the infrastructure to handle the devices. Most of our enterprise customers have had RIM devices and Blackberry Enterprise Server for a long time. There is a lot of work that goes into getting the same level of command and control for other platforms,” said Charles Edge, director of Technology at IT consulting firm 318. Getting PlayBook up and running in many enterprises will not be much more complicated than charging the battery.

4. Secure email and calendar -- as delivered via PlayBook -- are big enterprise advantages. Right now, accessing native email and calendar on PlayBook involves “bridging” it to a BlackBerry; essentially putting the mobile device’s mail and calendar on the PlayBook via BlueTooth. That has prompted some reviewers to pan the tablet as a glorified BlackBerry accessory. The upside? Those tools on the mobile phone are secure and so they will be on PlayBook.

5. PlayBook already runs Flash. This means that whole segment of the Web that is unavailable to iPad users is easily accessed by PlayBook. Overall the PlayBook Web browsing experience is hands down faster and better than going online with pokey Safari on an iPad.

6. The PlayBook touch screen provides the best multi-tasking tools of any tablet. iPad still struggles with multi-tasking, but PlayBook, using RIM’s proprietary QNX operating system, offers easy multi-tasking -- just what mobile professionals need.

7. Secure access to Android apps. RIM stared the comparative lack of BlackBerry apps in the face (there are around 3000 compared to hundreds of thousands that run on iPad) and it’s come up with a clever solution. PlayBook will run at least some Android apps (there are over 100,00) but to get on PlayBook they have to be downloaded via the BlackBerry App World, where they have been vetted by RIM staff in a system closer to Apple’s Apps store than the wild west of the Android Marketplace.

8. Plug in an HDMI cable and the PlayBook can be used to deliver PowerPoint shows to a projector. iPad cannot do this.

9. No cellular connection, which, if you think about it, is a kind of plus because it produces cost savings. Right now, PlayBook is Wi-Fi only; no cellular carrier support except it has a built-in tethering tool that lets it power up using a BlackBerry phone’s 3G network for no added cost.

10. Cost: 9 buys the 16GB model. The 32GB model is 9. The 64 GB is 9. Those price points exactly match iPad 2’s.

A last reality: numbers matter. There’s no counting BlackBerry out, despite the faltering launch of PlayBook, because, at day’s end, it still has a huge installed base: BlackBerry remains the phone of choice in many enterprises.

Source

Mo reasons to love Momo

Arnold's Conan did a few impressive things.  He lifted a giant bowl of green soul.  He pushed a giant wheel.  He... *sigh* knocked out a camel with a punch.

He didn't, however, rip a man's tongue out through his own throat.

I will not have your body burned. I will not give you that honour. The beetles will feed on your eyes. The worms will crawl through your lungs. The rain will fall on your rotting skin... until nothing is left of you but bones.

You'll notice Drogo doesn't even seem to register the flesh wound on his chest from the khopesh (and we seriously need a moratorium on those, they're getting like the katana for the 21st Century), treating it with no more concern than a nettle sting.  Also, that he drops his two tiny knives during the fight: he is Khal Drogo, he doesn't need weapons to kill a man. And to top it all off, he goes all Ken-"Fist of the North Star"-shiro with a final quip.



As with the last showcase of Momo's talent, I really hope Nispel and the gang gave Conan a scene remotely as badass as this one.  Literary Conan certainly had his share of highlights, and it would be nice to have one that doesn't involve animal abuse or lifting heavy things, and hopefully not just rip off one of those moments from the stories.  If there's one thing we can probably depend on, though, it's ingenuity in gory fight scenes.

* I will note that the scene isn't perfect, for the same reason the last one wasn't: Dothraki extras in Game of Thrones suck.  They really suck.  Suuuuuuuck.  In the last video, they didn't seem nearly as fired up as Momoa, reducing the impact of the scene entirely.  I've already talked about how I hate their visual design.  In this case, it's Drogo's "opponent" - more like Drogo's victim.  That guy who challenged Drogo looks like no threat whatsoever to Drogo: surely if you want to show how badass Drogo is, you give him an opponent that looks like he could pose a challenge?  Then, when Drogo defeats him he looks even more dominant? I wasn't remotely worried about Drogo here, and arguably we probably got that point - but that doesn't make it a fight, that makes it butchery.

When Conan fought someone, they were usually treated as dangerous threats.  Howard wrote about their victories, size, deadliness, prowess.  Sergius of Khrosha, Zaporavo, Baal-Pteor, Shah Amurath, the Adventurer, Olgerd.  Conan defeated them all, and while the difficulty of those victories varied, Conan either came out more imperssive because he made them look like nobodies, or because he just barely managed to survive against a truly formidable opponent.  This guy fighting Drogo's a nobody, Drogo defeated him like a nobody, and all I thought during the fight was "how's Drogo going to defeat this nobody?" I'm not going to recall this fight scene as "do you remember when Khal Drogo defeated that challenger to his rule," but "do you remember when Khal Drogo owned that cocky little punk?" Considering we'll (probably) never see Khal truly fight in the series, it's a shame this one fight scene wasn't what I was hoping for.  Ah well. 

Top Reasons to Firefox even better than Chrome for web development

Some time ago, some of us, web developers, we changed the Firefox Google Chrome because of the important features such as speed.

With the release of Firefox 4, it solved some of the problems we had in past versions, leaving it better, at least when it comes to web development.

This article, divided into two parts, explains some of the reasons why the Firefox browser is still a better than Google Chrome for your web development work.

Evolution of the market share of browsers

About a year ago, I talked about something most of us already knew, that PHP developers are switching to Google Chrome as its web browser access.

As you can see in the table below, this trend continues to be true this year. These numbers were taken from statistics developers PHP Classes logged in to the site .

Browser	May 2009	May 2010	May 2011	Change
Mozilla Firefox	68.0%	63.5%	57.3%	-6.2%
Microsoft IE	18.5%	13.6%	8.9%	-4.7%
Google Chrome	6.0%	15.7%	28.1%	+12.4%

As you can see, Chrome almost doubled its share in a year, while Internet Explorer has lost a little more than half. Firefox also fell slightly.

The gain of Chrome is greater than the loss of the Firefox and Internet Explorer. This means that Chrome also gained share lost to other browsers.

Reasons to Firefox even better than Chrome for web development

Given the fact that the participation of Google Chrome continues to grow enough, you may wonder why on this article. The fact that Chrome will continue to become increasingly popular for web browsing does not mean that web developers are also working with him in his projects. For me, this is not the case. Often when I'm doing development work, I feel I need to switch to Firefox, for reasons which I will list below.

I wish they had in mind that this article is not a rant against Google, which gave us web developers a lot to be grateful to him, but when we speak of Chrome, there is still much to be improved.

I decided to write this article now in the hope that maybe someone at Google to read, and do something to resolve these issues, most of the time, really bother most of us, since we do not keep changing all the time browsers .

1. View HTML

When the code of our sites have bugs, it usually generates an HTML code that is incorrect or invalid. So we need to analyze the HTML code to understand what's wrong. Firefox has an amazing feature that allows you to select a portion of the page and it shows the exact HTML that corresponds to that portion of the selected page. This feature does not exist in Chrome.

The best you have is the Inspect Element feature, which allows you to find the HTML code for the page element below the cursor of your mouse. Not the same thing. If I select a region of the page, I want to see the full HTML of that region, not a single element.

Another annoying thing is that Chrome tries to make the HTML pretty. This means that if you have a malformed HTML, you will not see where he is malformed because Chrome will show an embellished version of the HTML code after it has been repaired. I wish they had an option to disable.

2. Validation of HTML

Another great feature of Firefox is the ability to display any validation errors of HTML that you may have. In fact, this feature is provided by the extension HTML Validator .

I tested several extensions with the same goal in Chrome, but nothing that was really good. Some just used the W3C validation service through the page's URL, which is not good, because when you are developing a page that is not public service W3C can not access it, and any user logged into the site you is developing can not access it.

Other extensions have tried to copy the currently loaded page and pass it to the validation service, but none showed any invalid HTML code that the Firefox extension HTML Validator shows.

It also does not rely on an external validation service. That means you can validate pages even if you do not have internet access. So for all these reasons, an equivalent version of the HTML Validator extension is sorely needed for Chrome.

3. Disable JavaScript

Sometimes you need to test your site with JavaScript disabled. The only way to disable it in Chrome is going to preferences and disable. This is truly annoying. In Firefox, you can use the extension Web Developer by Chris Pederick to add a button to the browser to quickly disable and re-enable JavaScript when you want.

In Chrome, there is also the extension Web Developer the same developer, but it provides no means to disable JavaScript. The problem is due to the limitation of the API exposed to Chrome extensions. It does not allow a way to disable JavaScript from extensions.

There is a request for funding for the project Chromium to implement the necessary support to disable JavaScript. Implementing this feature was actually given a year ago, but it never happened. Oddly, users have been banned from posting future comments on the application of this feature.

4. Empty the browser cache

Sometimes you need to force the cleanup of the browser cache, so that new content can be recovered from the site server you are developing.

It is the same limitation to disable JavaScript. You can not do this through an extension. You need to go in the preferences of Chrome.

There is also a feature request to enable support for clearing the cache from an extension. It was made more than two years, but only a few months ago was released for implementation.

5. Changing the agent identifier of the browser

Sometimes you need to access your site pretending to be developing using another browser, so you can see if it fits to that browser the way you expect.

For example, if you are serving an RSS feed to be handled by Feedburner, all you need to redirect browsers to the URL of the Feedburner feed, unless the current agent is checking if your Feedburner feed has been updated. Therefore, it would be helpful if you could cause the browser to pretend to be the Feedburner, so you could check if he was working as it should.

In Firefox, you can use the extension User Agent Switcher also Chris Pederick. In Chrome, there is also an extension called User Agent Switcher . The problem is that it does not work. Good works, but not the way you want. The extension can only change the browser identification exposed to JavaScript. This means that HTTP requests sent to the server will not use the string identifying the agent that you need to be sent.

I suspect that an application for resource to be implemented in Chromium, but not found. Until this feature is implemented, we will always have to go back to Firefox, which works well with the User Agent Switcher extension.

6 Reasons I Choose Chitika

I think Chitika is an advertising media is pretty good. Although I only get in one week, it was when I still have a Metal Archives blog http://metal-arch.blogspot.com. After all this time I had not put Chitika ads, but in the last month until now, I try to put Chitika ads to my blog. The result is not optimal, because my impression that this blog is still low. In contrast to the impression Metal Archives blogs that have a high enough impression.

I ever think to choose other advertising media, such as Google Adsense. I've made ​​adsense account up to four times, because my first account getting banned and another account is disabled by the google. Indeed, the income I get from Google Adsense is very large, in one week I could earn more than 0. But I cheated, so my account got banned. And the money collected is only a imagined lol.

But I never give up to get revenue from ads that I put on this blog. I was thinking to switch to other advertising, but advertising is quite difficult for the other requirements are met. Therefore, I returned to Chitika, then what made me choose Chitika, the following 6 reasons I chose this advertising.

1. Chitika ads have a high prices, not different with Google Adsense. I know Google Adsense ads, have more high prices, so you can get paid more as well. But the Google Adsense publisher is too fierce to face them. because three of my account is disabled because impression of my blog is not enough and this blog will be detrimental to the advertiser. But, why Google Adsense accept me if my blog does not meet the requirements of Google Adsense. Whereas before accepting publisher, Google Adsense definitely do a review on a blog that has been registered. So I better switch to Chitika.

2. Chitika ads including contextual ads (like Google Adsense), so the ads that appear will be in accordance with what you are looking for. Chitika ads are sold mostly in the form of products, so most likely people will click on ads that appear on your blog or website. Because visitors will continue to look for what they are looking for and inadvertently may click on the Chitika ads on your blog.

3. Just as Google Adsense, Chitika has many ad sizes. Ad size is very important, because your ad to be put in place relevant and appropriate to the size of the ad.

4. Chitika not so cruel as Google Adsense. Google Adsense is very cruel and sensitif, but sometimes the cruelty of Google Adsense make many publishers are confused, because no contact can be contacted, to be held account disable reasons.

5. Can earn extra income from referrals who join Chitika using our ID. In addition, payment easier, because the payments can be made ​​via PayPal.

6. To get a click from the ads more easily, so my income is quite satisfy. Although in one week only has $ 4 lol. You need to know that it is easy to Chitika ads? Please try a hidden application IP ---> please read his article here.

Ok I think it is clear why I switched to Chitika. But I think, someday I will switch to Google Adsense, but I am waiting for my impressions soared back then I try to enjoy the Google Adsense. Ok Good Luck!

Five Reasons Why You Should Write for Residuals

 There's a good deal of how-to information when it comes to building a passive residual income online and in the real world, but not much about the benefits, about the why of residual income efforts. Until you've achieved your passive income goals, the efforts to get there can seem enormous compared to the returns: you might write 50 website articles in a month and only see a few dollars in revenue during those few weeks.

That's when a reminder as to what you're aiming for, and why, is important.

Having built up to a full-time residual writing income in the past, and earning one this year as well, I've experienced firsthand the peace and freedom that comes from passive income. A residual income allows you to:

Diversify your income sources: In an unstable employment market, adding to and diversifying the places from which you receive income is especially important. The more income sources you have, the better better you can weather most financial storms in any economy.

Increase earnings potential: By building a residual income stream that doesn't need constant attention, you can can earn more money over time. The more residuals you build through websites and digital media, the higher your overall earnings will be, even if your boss never gives you a raise at your 9-to-5 (assuming you have and keep a regular job). As a work at home mom, I am able to earn far more through residual sources than if I only wrote as a freelancer for hire.


Retire early or on time: Build income source for retirement through your own niche sites, blogs, revenue-share articles, ebooks, apps and the like. While many Americans are facing the threat of less less money in retirement, delaying retirement or even no retirement at all due to lack of savings and investments, savvy online writers can build an income stream to last throughout their retirement years with basic upkeep and maintenance.


Work less hours: If you want to quit your day job and work only as much as you like, building a full-time passive income is the way to go to achieve this without living on peanuts or handouts. Since passive income allows you to reap the benefit of years' worth of efforts, you can work much fewer hours -- even take off for weeks at a time -- if you aren't trying to build up to a higher level.
 
Enjoy life more: Whether it's a long commute, stressful deadlines, or plain old burnout in your current job, many people find their work stressful and their family and personal time too limited. With a strong passive residual income from writing, you can plan your days, have more time with children, a spouse, friends and the adventures and activities you enjoy.


What your motivation for working for a long-term passive income?