Release Firefox 23.0.1 in repo
- Thread starter hdonk
- Start date
GizmoTheGreen
Active Member
on the other hand you never know what version your chrome is, unless you go check. it's just "chrome" and always up to date, that's why I like it
levi
Still fresh, damnit!
Same with Firefox, on my PCs at least.
ekianjo
Hardcore Member
That's why Chrome is not used in corporate context : because it rolls out changes before you can test them
I prefer Firefox in that regard.
Btw hdonk this firefox 23 does feel a little faster than before on Pandora. Not really at startup, but once you are in, it's clearly doing a better job than before.
ekianjo
Hardcore Member
Well that's probably because you only use like as a browser then, and don't build/run applications on the intranet with it. If not you are bound to run into troubles sooner or later. That's what LTS versions are for.
Kumaki
Well-Known Member
Would need updates, then if these little criminal bastards would get caught and shot for being jerkoffs. Sorry, but I am pissed off cuz I just got hit with the Crypto-Lock virus - which is basically extrotionware.
Fortunately, most of my important stuff was backed up on flashsticks, so it was wipe the computer, start over, re-install everything - took me most of a day, and I'm back to 95 percent of what I had. But it is a cast-iron pain in the ass. They should make that sort of activity a freaking capital offense. I am not kidding.
The idea that some jackass from halfway around the world can just bop along, encrypt a bunch of your files and then hold them ransom...with no chance of ever catching the son of a bitch and making him go to prison for a good long time...after a serious ass0kicking of course...well, it just realy pisses me off.
It's a priciple thingm, ya know? I got most of my important stuff back, because it was backed up on flashsticks that never come into direct contact with the Internet.
Kumaki
Well-Known Member
Chrome just looks weird on my screen. I could never get used to the way it looks - so much different from Firefox that I am used to.on the other hand you never know what version your chrome is, unless you go check. it's just "chrome" and always up to date, that's why I like it
It's just all these Version numbers that bug the snot out of me...it is like they are competing to get the higest version number.
levi
Still fresh, damnit!
That's exactly what they're doing. It's very childish, I agree, but meh...as long as the software still works and maintains its current trajectory of slimming down, they could call it Trixibelle Fifi My Little Pony for all I care.
Thanks for the update! During my quick test yesterday I had no problems, but I didn't do much anyway (mainly browsing the forums, so no flash or anything).
I kept my appdata-folder, because I don't want to loose all my settings, plugins and so on. Are there some specific things that may cause problems or slowdowns? Would be quite helpfull to isolate those, so you don't have to erase everything. But for me it doesn't seem necessary with this update anyway.
I kept my appdata-folder, because I don't want to loose all my settings, plugins and so on. Are there some specific things that may cause problems or slowdowns? Would be quite helpfull to isolate those, so you don't have to erase everything. But for me it doesn't seem necessary with this update anyway.
Kumaki
Well-Known Member
ASnd I gotta go thru almost daily updates and having plugins suddenly not work anymore and etc etc etc because of this childish nonsense.
Let them intro a new version when there's enough of a change to make it worthwhile, that's all I'm saying.
levi
Still fresh, damnit!
It was just the same before this versioning policy, with plugins breaking when you updated from Firefox 1.2 to 1.3. They could do something about it to be honest with you - often the problem is just that the developers haven't tested the plugin against the new version. It's possible to open up the plugin and modify it's metadata to test it against newer versions yourself, but it's a massive pain in the arse and Firefox should just give you the option to try your plugins regardless of what its metadata says.
Edit: Actually, as I recall the change to enable plugins to be versioned only came in after the numbering policy change (though I could be wrong). You still had plugins breaking, but that was because something actually had changed, and it could make your browser unstable until you removed it - but at least most of the time it worked okay.
Edit: Actually, as I recall the change to enable plugins to be versioned only came in after the numbering policy change (though I could be wrong). You still had plugins breaking, but that was because something actually had changed, and it could make your browser unstable until you removed it - but at least most of the time it worked okay.
Last edited by a moderator:
Kumaki
Well-Known Member
But that is why I hate updates. You get plugins breaking all the time.
Again, you make assumptions... Since this has nothing to do with the thread topic. I'm done.
levi
Still fresh, damnit!
I know what you mean, but you have to choose between no progress or things breaking, as in pretty much everything in life. Firefox does have something that might be of interest though: Firefox Extended Support Releases (ESRs)
http://www.mozilla.org/en-US/firefox/organizations/all.html
All you need is for someone to compile and package that up for Pandora. And package up all the subsequent security fix releases, which Firefox apparently guarantee will not break your plugins.
But when you do finally update to the next ESR you might find a number of your plugins have fallen by the wayside and are no longer supported, but I guess that's progress for you.
Kumaki
Well-Known Member
Well, that also becomes a problem, when a plugin you like, that was useful to you, suddenly is no longer supported.
But, yeah, this would be a good idea for Pandora, so that other plugins would not break.
That is my main biatch with updates. I resist them, because I have the old-fashioned attitude of - if it works, it isn't broken...and if it isn't broken - DON'T FIX IT.
That attitude is obsolete, I guess, in the computer world, lol.
I just don't like updates because, like I said...if what I HAVE...works...then why do I want or need an update, see?
This is why, for example, I still have machines running Windows XP, LOL.
The one I'm on now is using Windows 7.
I might try a Linux machine soon, if I can also have WINE on it...AND the Windows programs I need to run on that will still then run.
At least that way I would not have to worry about stupid friggin' viruses!
But, yeah, this would be a good idea for Pandora, so that other plugins would not break.
That is my main biatch with updates. I resist them, because I have the old-fashioned attitude of - if it works, it isn't broken...and if it isn't broken - DON'T FIX IT.
That attitude is obsolete, I guess, in the computer world, lol.
I just don't like updates because, like I said...if what I HAVE...works...then why do I want or need an update, see?
This is why, for example, I still have machines running Windows XP, LOL.
The one I'm on now is using Windows 7.
I might try a Linux machine soon, if I can also have WINE on it...AND the Windows programs I need to run on that will still then run.
At least that way I would not have to worry about stupid friggin' viruses!
levi
Still fresh, damnit!
Firefox 1.0 worked. Hell, early Mozilla Suite worked too. If you want your browser to look the same in ten years (here's a reminder of ten years ago) then feel free to fork the project and only apply security patches from here on in - that's the beauty of open source. But it's also the democratic element of open source - cos you'll need good luck to convince anyone else to do that for you, especially as the codebases diverge and applying the patches becomes a real struggle.
Last edited by a moderator:
levi
Still fresh, damnit!
Yes, but that's not the reason for updates that break your plugins, at least not most of the time, and even then not directly. Plugins break because the interface changed, and it changed often just because the developers decided to do things a different way. That's a little unfair - often developers realise the current way isn't good enough when they discover that trying to patch the holes attackers are making in it is harder than it should be.
These Firefox ESRs show that it's not rocket science to maintain the interfaces for longer than they do though, at least for the limited lengths of times they're supporting.
FWIW, if anyone's interested in building the ESRs from source, the source seems to be available here:
https://hg.mozilla.org/releases/mozilla-esr17/tags
These Firefox ESRs show that it's not rocket science to maintain the interfaces for longer than they do though, at least for the limited lengths of times they're supporting.
FWIW, if anyone's interested in building the ESRs from source, the source seems to be available here:
https://hg.mozilla.org/releases/mozilla-esr17/tags
Similar threads
