HNHacker News
TopNewBestAskShowJobs

zbraniecki

1,111 karma · joined October 18, 2013

Zibi Braniecki, engineer at Mozilla. Working on l10n/i18n stack, ECMA402 and performance.
submissionscomments
zbraniecki··on A uBlock Origin update was rejected from the Chrome Web Store
Try Beta/Nightly! Firefox got much better for MacOS in 70/71 but that version is not yet in stable.
zbraniecki··on A uBlock Origin update was rejected from the Chrome Web Store
Thank you.
zbraniecki··on Chrome 77 Breaking Drag and Drop Events
"should be prioritized" is a very subjective statement. Out of every 100 tickets, there is 50 people who believe theirs is the most important one. And we have over 200k tickets total (not all are bugs, many are resolved, but the scale is massive).

If you think a bug is easy to fix, pleasez consider providing a patch.

zbraniecki··on Firefox moving to 4 week releases
> Firefox itself was created by a couple programmers chatting late at night in a Denny's.

You're presenting a very naive and romanticized version of the story.

source: I've been involved in Phoenix since 0.2.

zbraniecki··on Firefox moving to 4 week releases
Another thing that I observed in our culture since we switched is that it is easier to coordinate cross-team efforts - if I know X will be done in Fx70, I can plan my work on top of it for 71.

Such logic is commonly performed without releases until you start depending on multiple features in multiple places. Then it saves you.

The same "alignment" works also much better between engineering and non-engineering teams. Once we collect the focus areas and major features planned for release X, security, performance, accessibility, localization, platform integration, UI, UX, design, legal and marketing teams can prioritize their work to aid them.

Having no release cycle, or long release cycle, dilutes this effort and reduces visibility.

There is, in my opinion, somewhere, a threshold beyond which the release cycle burden outweighs the benefits and/or where the cycle is to short for teams to usefully react, but I don't think we hit it so far.

zbraniecki··on Why Go and Not Rust?
I'm not discounting your experience, nor am I trying to devaluate the problem, but I think there are more than one reason why someone may ask "Why not Rust?".

In my case, I sometimes ask it to learn about particular real or perceived shortcomings of Rust, which may be fixable.

If I believe that Rust should address the problem, and someone chose not to use Rust (which is different from choosing to use Go!) I am curious as to what obstacle the person hit.

We should tame the zealous members of our community, but don't cluster everyone into the same bucket :) Some of us are just trying to build a great ecosystem and that requires us to find blindspots and notice hard-to-observe-from-inside problems.

zbraniecki··on USB4 Specification
thank you for the explanation! Do you happen to know if there's any work on bumping the power bus to 130W?

I see that USB PD rev 3.0 allows up to 100W - https://en.wikipedia.org/wiki/USB#Power-related_specificatio...

Is there any work on rev 4?

zbraniecki··on USB4 Specification
Will this bring higher PD? A lot of laptops require 100W-130W of power (see, Lenovo X1E or Dell 7590), while the highest PD I've seen from usb is the Apple charger for 86W. I know Dell produces proprietary 130W usb-c charger, but I'm wondering if usb4 will help make it a standard.
zbraniecki··on Contributing to the Mozilla code base
That's not true. Majority of the front end is in html+js+css these days. Most of it is /browser and /toolkit directories. The rest is Gecko engine and it's written in a mix of Rust, C++ and JS. We're moving more to Rust with the back end but staying with JS on the front end.

You can develop almost any feature of Firefox without ever leaving JS.

zbraniecki··on Firefox 68.0
Mozilla is not "going to kill extensions in Android FF".
zbraniecki··on When it comes to privacy, default settings matter
My personal problem with the model is not how much they make, but rather the intentionally hidden relationship they develop with the user. If the relationship is - you get the article, we get to show you an ad that gives us a chance to sell you something and make money on it, which is ~$0.00008 - that would be clear.

Even if the relationship was - you get the article, we get the above plus we'll collect some bits of information about you that we explicitly list. The ad itself will give us ~$0.00008, and the collected data another ~$0.000007 - that would be ethical imho.

But the real model is - we give you an article, and in return you sign a blank document that allows us to collect all the possible data and try to maximize the amount of money we can make on it. You step into it today, but we are not comfortable putting any price point on this agreement because we bank on the idea that in the future we'll make more as we increase our grip over understanding of user behavior and improve our ability to monetize it in any, potentially unethical way. The reason companies hide the nature of the relationship is because their business models are built around the assumption that the data collection will generate increasing amount of revenue in the future. And since there's no way for you to understand the relationship, or step out of it, you're entering it with information disadvantage, and there's no turning back. I hope you can see how this approach is by design hostile to users and the Internet as a public plane.

zbraniecki··on Fluent 1.0: a localization system for natural-sounding translations
I started https://github.com/projectfluent/fluent.vim but my vimscript is terrible and I will take all help I can get :)
zbraniecki··on Fluent 1.0: a localization system for natural-sounding translations
> but you lose some credibility right from the start

Thank you for the feedback! I updated the article to include the mention about `msgctxt`.

Personally, in my experience, many project environments end up with partial support for this feature (for example many react/angular extractors don't support it) which leads to limited use and requires the localizer to request adding a context by the developer.

I did not include that since it's just my personal experience and I assume more mature projects tend to recognize the feature and use it, hopefully, extensively :)

> Message interpolation in gettext works and can be absolutely readable. E.g. "You have {count} items".

As far as I understand this is not part of the system (gettext), but its bindings and in result is underspecified and differs between implementations. For example [0] uses `%{ count }` while [1] uses `{{ count }}`. If I'm mistaken here, please, point me to the spec :)

Since it is a higher level replacement, this approach likely suffers from multiple limitations. First of all, I highly doubt that there is any BiDi isolation between interpolated arguments and the string leading to a common bug when RTL text (say, arabic) contains an LTR variable (say, a latin based name of a person). Fluent resolves it by wrapping all interpolated placeables in BiDi isolation marks.

Secondly, I must assume that any internationalization, such as number formatting, date formatting, etc. is also not done from within of the resolver in gettext. That, in turn, means that it may be tricky to verify that a number is formatted using eastern arabic numerals when used in arabic translation, while formatted to western arabic when used in english translation. Fluent formats all placeables using Unicode backed intl formatters (for example in JS we use ECMA402), allowing for consistency and high quality translations where placeables get formatted together with the message.

For example, in your example, will the `You have { count } items` be translated to `لديك 5 عناصر` or `لديك ٥ عناصر`? And what will happen if instead of `count`, you'd have `name: "John"`? Will it be RTL or LTR?

[0] https://hexdocs.pm/gettext/Gettext.html#content [1] https://angular-gettext.rocketeer.be/dev-guide/api/angular-g...

zbraniecki··on Fluent 1.0: a localization system for natural-sounding translations
Hi! This is also a problem in Welsh [0]. In the Fluent world we solve that on the level of design principles (do not reuse the string `yes` because it can be translated to a different `yes` in different buttons) and bindings (compound messages allow us to localize a whole widget with a main message and its yes/no options).

[0] http://psychopixi.com/languages/yes-and-no/

zbraniecki··on Fluent 1.0: a localization system for natural-sounding translations
Hahaha, thank you! I still feel ashamed of making a strong claim based on informal conversations, but I feel a bit vindicated by your agreement! :)
zbraniecki··on Fluent 1.0: a localization system for natural-sounding translations
I don't know if there's any public statement about this. I base my position on experience at Unicode Conference and work on CLDR and ICU. I understand that it diminishes the value of my claim.

I can also point out to ICU MessageFormat - which has been designed much after Gettext and, I'd dare to say on purpose, bares no resemblance to it.

zbraniecki··on Fluent 1.0: a localization system for natural-sounding translations
Hi! FormatJS is very similar to some of our bindings, and is powered by MessageFormat on the lower level.

Here's our take on the differences between MessageFormat and Fluent - https://github.com/projectfluent/fluent/wiki/Fluent-and-ICU-...

zbraniecki··on Fluent 1.0: a localization system for natural-sounding translations
For ya'll dabbing into the list of rules - feel free to use the Unicode Plural Rules list as a reference point - http://www.unicode.org/cldr/charts/33/supplemental/language_...

It's a great abstraction that makes a lot of Fluent easier :)

zbraniecki··on Fluent 1.0: a localization system for natural-sounding translations
Hi! Thank you for your feedback. I'm one of the authors of Fluent, and this wiki article.

I have, in fact, been using Gettext for quite a few years, but of course, as you pointed out, I am also biased.

If you have suggestions on how to improve the article to better represent the reality, please, file an issue and provide a PR! Our goal is to express our design differences, but we don't want to mislead anyone!

zbraniecki··on Fluent 1.0: a localization system for natural-sounding translations
Yes, naming is hard, but, to quote the previous commenter "this can be worked around" - you can `slug` any string if you want to. We prefer to think of the ID as the base of the social contract between the dev and the localizer. This enables a lot of fine tuned control over string invalidation.
zbraniecki··on Fluent 1.0: a localization system for natural-sounding translations
Thank you! That's a good feedback. In our experience of working with the gettext based localizations we noticed that developers almost always omit the context and in result localizers are stripped of the ability to distinguish the message variant which makes them have to ask the developer to introduce it.

This, in turn, breaks the design principle #1 of Fluent - https://github.com/projectfluent/fluent/wiki/Design-Principl...

I'll update the Wiki to reflect that!

zbraniecki··on Fluent 1.0: a localization system for natural-sounding translations
Hi! We've been working with and evaluating Gettext when we started Fluent.

Our opinion is similar to Unicode's - Gettext is fundamentally flawed design for internationalization purposes.

Here's you can find more detailed explanation of our position - https://github.com/projectfluent/fluent/wiki/Fluent-vs-gette...

Please, don't take it as a criticism of using it. We just don't think it scales and we don't think it's possible to produce high quality sophisticated multilingual UI's with it, but if it works for you, don't touch it :)

zbraniecki··on Fluent 1.0: a localization system for natural-sounding translations
That's a great question!

Fluent relies on Unicode Plural Rules [0] which allow us to handle all (as far as Unicode knows) pluralization rules for cardinal and ordinal (and range) categories :)

[0] http://cldr.unicode.org/index/cldr-spec/plural-rules

zbraniecki··on Firefox 65.0 released
Initially, we'll only enable it for users on Windows+Nvidia, to minimize the risk of regressing stability (GPU drivers is a fun minefield). Then we'll gradually extend the scope and focus on other drivers and platforms.
zbraniecki··on Rust Analyzer in 2018 and 2019
I really want Kakoune to succeed. I love the UX behind it and it feels like a vim-done-right.
zbraniecki··on Microsoft Edge and open source collaboration
Firefox (by that I hope you mean Mozilla Project) cares about diversity and choice. Our Mozilla Manifesto [0] describes our vision of the balance between corporate and civic value of the Internet.

I speak for myself - I believe that decrease in diversity of implementations of the Web standard and drift toward a monopoly is harmful to our vision of the Internet and ultimately will hurt the Open Web.

[0] https://www.mozilla.org/en-US/about/manifesto/

zbraniecki··on State of web browsers in 2018
Our power to influence standards is linked to our marketshare.

At Mozilla we say that we have a different reason to strive for marketshare than most companies in the world. We need it to have a seat at the table.

zbraniecki··on The Intl.RelativeTimeFormat API
Hi, I'm the author of the API proposal (together with Rafael and Daniel).

Thanks for feedback!

I understand where your suggestion is coming from, but please, take into account that we are designing the API to fit into the whole ECMA402 Intl API model.

The API we ended up with seems to be more consistent with it than what you suggested. It also allows us to, in the future extend it to compound units more easily.

Saying that, if you have a motivational o help us, come to ecma402 and review our active proposals! We have a bunch such as Intl.Locale, Number first revision, ListFormat etc :) That's a great time to work on the design of them!

Hope that helps!

zbraniecki··on Ten years of V8
Source?
zbraniecki··on Firefox 62.0 Released
Hi, dev here. :)

Can you capture a profile using steps from [0] and send them to us/me?

[0] https://www.reddit.com/r/firefox/comments/7knnn4/firefox_qua...

← PreviousPage 2 of 6Next →