Originally posted by curaga
View Post
Announcement
Collapse
No announcement yet.
Opera 15 Is Here, But Not Yet For Linux Users
Collapse
X
-
Originally posted by curaga View PostIn three points:
1. CPU use, incl. startup speed
2. RAM use
3. Native code included in the release doesn't break between releases, addons often do. This point could be solved by designating some addons as official and not releasing until they work, but I don't see Mozilla doing that.
Originally posted by curaga View PostThanks for the correction, I got the name wrong. The issue with all those combined bars is that what I type as an URL should never be sent anywhere, only what I explicitly intend as a search should be sent. This is only possible with separate fields.
FF's awesome bar still defaults to doing searches, and leaking data in the name of suggestions, no?
Originally posted by curaga View PostI wouldn't be surprised if the option to disable that entirely is only available in the registry.
Originally posted by curaga View PostContent blocking is one thing that absolutely should be native code. I don't want the string matching of my huge blocklist be in JS.
Originally posted by curaga View PostThat's only the most recent example: look back to see all other removed options.
Comment
-
Originally posted by Ferdinand View PostFx does a feeling lucky search by default. Otherwise no information is sent to google. The suggestions come from your browsing history not from google.
Comment
-
That's a positive surprise with the suggestions indeed.
Javascript means it doesn't break between releases and doesn't even break between cpu architectures.
I guess you call about:config the registry? I love that feature and wish each piece of software would add that including Windows.
Comment
-
Originally posted by curaga View PostThere are a ton of reports of addons breaking between FF releases. JS is clearly not immune to breakage.
Comment
-
Originally posted by Osik View PostThat's because FF broke API - srsly, you can't have backwards compatibility if someone decides to break API or ABI. JS is immune to latter (beacuse there isn't any in first place), nothing to former.
Comment
-
Originally posted by curaga View PostThere are a ton of reports of addons breaking between FF releases. JS is clearly not immune to breakage.
I think it's mostly been a solved problem since around FF15? Or at least it's a solved problem for most popular extensions. Probably the random ones out there doing crazy stuff are the ones that get broken more often.
Comment
-
Originally posted by smitty3268 View PostWhile i'm sure that's true, I can't even remember the last time i had an addon break. And I'm running on the betas.
I think it's mostly been a solved problem since around FF15? Or at least it's a solved problem for most popular extensions. Probably the random ones out there doing crazy stuff are the ones that get broken more often.
Comment
Comment