Firefox - nightly builds

Novosti vezane za 64-bitnu podršku.

Ciljevi za 2013 godinu.

Ide se korak po korak.

Više informacija: https://wiki.mozilla.org/Firefox/Features/New_Tab_Page_v2

Meni također, skroz beskorisna stvar.

Nisam se udubio u razlog (mrzelo me čitati) zašto će biti uklonjeno. :)

Što se tiče JavaScript tima, malo novosti: http://javascript-reverse.tumblr.com/post/41949177399/js-team-update

Koristiš sinhronizaciju ili?

Na koji način biraš koji ćeš profil pokrenuti?

Btw. Mozilla ima svoje prezentacije na FOSDEM-u. Raspored prezentacija se nalazi ovde, a možete ih i uživo pratiti ovde.

Još malo informacija o JavaScirpt engine-u u Firefoxu:

A small update for you guys on the different compilers and GGC. I hope it answers some questions you had.

1) What's the deal with GGC and the impact for performance
I'm not involved with GGC and I only hear bits and pieces about it. But from what I've heard the GGC development is going nicely. There is still a lot of work to do, but it is coming. It will probably take another 2-3 months to get it in a functional state. It will decrease the GC pauzes even more and that will be very noticeable in the browser. As for increasing performance, yes it will increase performance, but only by reducing the GC time that happens during benchmarks. That means no increase for SS. For V8 we already identified some places that will definitely benefit from it. BUT the performance atm is not blocked on GGC. For most benchmarks where we are not on par with google chrome, the improvements coming from IonMonkey will be greater than the improvements GGC will bring. (At least that's what I assume from the measurements I did)

2) What's the deal with JaegerMonkey
It will get removed. Yeah I'm really happy with that. There are some reasons for this. Many optimizations in JaegerMonkey are hacked together, because there is no decent way to do. IonMonkey has a much easier/better design in that regard. Also JaegerMonkey needs to recompile whenever types changes ... That's one of the reasons of our bad performance on SS. Also it looses it's information when we compile IonMonkey, resulting in the performance differences of 10% on some V8 benchmarks. ETA is when the replacement baseline compiler is done and at least as fast as JaegerMonkey.

3) What's the deal with Baseline
Shaping up nicely. The basic design is done and the hardest part are in. That is almost all opcodes get compiled to a basic version. Later on we can improve the generated output by seeing which types flow in. Evilpie, a contributor, has already begon with this, Thanks! But the major focus is nowto fix all the failing tests. Last thing I heard it would take another 2-3 months.

4) What's the deal with IonMonkey
Most faults are now gone and we are fully looking at performance issues. Mostly on the V8 benchmark, a benchmark where we were historically bad at. That has given us already nice gains since October. This focus will continue in the next few months.

http://arewefastyet.com/ - za kratko vreme su se poboljšali rezultati na raznim benchmarkovima.

Ono što je dobra stvar je i što idu ka što boljoj optimizaciji korišćenja memorije, što bi značilo da bi Firefox trebao koristiti manje memorije u buduće.

Može jedan off topic?:

Kak da upalim na lisici side bar za bookmarkove?

jes.

kompa puno hvala

tipkam po glupim postavkama 3 sata

Ako je kod sada optimiziran znači li to kako bi se australis uskoro mogao pojaviti i u betama/finalnim verzijama??

icecold koja je tvoja "uloga" u mozilli? pišeš li kod, daješ ideje ili samo testiraš i šalješ feedback?

Može li svaki "smrtnik" dati nekakvu svoju ideju ili to mogu samo mozilla članovi?

Ovo pitam samo informativno, a znam da se nalaziš i na about:credits, pa koga bolje pitat nego tebe

Spremite se na zoom shockove, Firefox za 3 verzije (od 22) počinje istinski poštovati high DPI setting u Windowzima, meni je sve postalo veće, ne znadoh zašto, a sad mi je sve jasno.. Trenutačno mi je ko šaka u oko, valjda ću se navić, jer kad se isključi ne valja, nije kao prije, sve je premalo.

To su sve ovi ekrančići 10'6 i 13'3 sa fullHD rezolucijama krivi.

Pogledat za egzampl:

Bojim se da je, najgore je što koliko god šarafio po layout.css.devPixelsPerPx ne mogu dobiti onaj odnos texta i UI chroma kakav je bio, ono, chrome se smanji, ali UI tekst se previše smanji. Nije mi jasno jednostavno, a nije mi ni jasno zakaj IE10 izgleda dobro ko i IE9 a Chrome Canary i Firefox 22 mi ne pašu više. Ludilo..

Možda ovo pomogne:

The new pref is 'layout.css.devPixelsPerPx'.

-1.0 makes Fx use the OS DPI. This is the default.
1.0 makes Fx use the original method of handling DPI. This will make things look normal again.

If you set the pref to a 2.0 everything will zoom 2x. A 3.0 will zoom things 3x, etc. You can use decimals (1.5). Using something like 0.5 will make things twice as small.

Set the pref to 1.0.

grab this add-on Theme Font & Size Changer and use it to change the font size of chrome text. I use 15 (my OS dpi is 120).

Ipak sam se navikao na ovaj HighDPI-aware Nightly 

Od jučer je u Nightly kanalu i Australis UI.

Zna li netko mogu li se u Australis temi podesiti ove stvari da budu kao na staroj temi