Re: google to pull support for firefox 3,5
On Thu, Jun 2, 2011 at 2:27 PM, William Hopkins <we.hopkins@gmail.com> wrote:
> On 06/02/11 at 08:15pm, tadziu wrote:
>> i'm just curious, is there any chance to bring iceweasel 4.0 to
>> stable before google ends support for 3,5? i got 4.0 on my
>> second computer with squeeze, but i had to mess a bit to get
>> it working, and it's not performing as well as i've expected.
>>
>>
>> http://techcrunch.com/2011/06/01/google-apps-to-pull-support-for-firefox-3-5-internet-explorer-7-and-safari-3/
>
> How awful! Google has brought browsers to the PC hardware game: upgrade or get left behind.
> I only upgrade browsers for security reasons, as I use noscript and requestpolicy and my browsing experience is essentially similar to my browsing experience in 1999. I am willing to bet gmail et al will continue to work for as long as you can use them without the fancy features (google does try their hand at requiring javascript now and then, such as the recent google images fiasco).
>
> OK rambling aside, you can use iceweasel 4.0 from experimental. Also given that it exists there, I'm sure there are plans to bring it forward to unstable and testing (and probably backports).
It's freeware, with a metric caboose load of add-ons and streaming
API's and security dongles and all sorts of bits. Doing backwards
compatibility and multiple platrform spupport for any project,
especially a bulky one, is painful and expensive in skilled
engineering time and QA. I've *been* the author, or support engineer,
for components that had major new releases and people weren't willing
to upgrade their old components for simple supportability and
maintainability. Backporting fixes may rely on completely
re-engineering components, which means significantly forking old
components.
This happens with kernels, databases, and GUI's all the time. It's
hardly unique to Firefox.
Reply to: