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 Over 80 Percent of Dark-Web Visits Relate to Pedophilia, Study Finds
The problem of guns is a bit deeper than iterated prisoners dillema (or actually, more literate).

If you have a gun and I have a gun I have to take into account that you may use it. Which motivates me to preemtivly use it to prevent you from killing me. Of course you can think the same way and I can think that you can think the same way.

Either way, if we both have a gun and I want to maximize my chance of staying alive (thus, fulfilling my survivial instinct), I should shoot.

The difference between that and Nash's equilibrium is quite drastic in that: a) large scale is in play triggering empathic/humanistic thinking b) the person that is in position to use it is usually less desperate and or in personal danger, so it's more "you kill my people" than "you kill me".

So, while I understand your logic, I would argue that the purpose of developing a weapon is to enable killing someone. The purpose of developing TOR is to enable privacy and anonimity.

zbraniecki··on Mozilla and KDDI Launch First Firefox OS Smartphone in Japan
Basic functionality is getting added and you can help. UX wise, you definitely can change UX. File bugs, join dev.gaia and lets talk about it.
zbraniecki··on Mozilla and KDDI Launch First Firefox OS Smartphone in Japan
Which version are you describing? As I said, I use "nightly" 2.2 and it is drastically different experienxe (altough still fairly raw) than 1.3/1.4.

I used android G1 (same as your dream). Do you claim it was smoother? Faster? More polished?

zbraniecki··on Mozilla and KDDI Launch First Firefox OS Smartphone in Japan
disclaimer: I work on FxOS

Care to elaborate why hopeless? I Use Flame as my second device and while I totally agree that there's a lot of work needed before FxOS "feels" as polished as Android or iOS, I don't feel like it is hopeless.

Remember Android 2.0? What a piece of.. ehm.. unpolished mobile OS it was? FxOS 2.2 is significantly more useful than any 1.x.

p.s. If you also have any basic webdev skills, you can fix UX yourself. I miss charging time notification on lockscreen and I started working on it yesterday [1] - fairly easy to add. We just need webdevs to help us hack :)

[1] https://github.com/zbraniecki/gaia/commit/a7829b7f4750e294b3...

zbraniecki··on Firefox OS Is Coming to Raspberry Pi
it's definitely in the not yet written category. Background services is something hard to design right and we don't think any of the other mobile operating systems got it right (think: battery, data plan drain, privacy, security, user control).

There are multiple ideas on how to approach that as more and more systems in FxOS would benefit from it (background music player, IM, various synchronization services), and I expect us to come with first approach relatively soon.

zbraniecki··on Poll: Did you “drop Dropbox”?
I dropped Dropbox for slightly related reason(s) (pricing policy, terms of service, privacy etc.)

Switched to owncloud. Happy.

zbraniecki··on Mozilla Unveils $33 Intex Cloud FX Smartphone
(disclosure: I'm an employee of Mozilla working on localization technologies for Firefox OS)

> That's no different than making a suggestion to Google about Android, or to Apple about iOS.

I believe you are wrong. There is a substantial difference between being able to send a suggestion to Google or Apple, or even being able to write a patch against an open source subset of Android codebase released months after the phone release, and being able to fork Gaia repo, patch it, and submit a pull request.

I've been helping volunteers go through their first patches for weeks now and it works great! They have helped me clean up the code base for Firefox 2.1 in many ways.

They now submitted their first patches and are skilled to start working on more complex problems and suggest features.

You are right, that that doesn't mean that anyone can submit any random feature and get his/her PR merged. That would result in chaos. But they can suggest features, work with module/app owners, and write the new features for the platform. They can participate in decision making process, weekly calls, daily meetings and day-to-day IRC conversations because it's all open and in public.

In the end, if things go wrong, they can fork the platform and start working on a fork. You may respond - hey, Android has it with CyanogenMod! If that was your first thought, please read about struggles CM has with Google or read arstechnica article of how someone tried to use Android without Google services.

Android sources are only partially open and are released many months after product release. Firefox OS sources are available for hacking from day 0 of work, many months before the product is ready. (for example: if you fork github gaia repo, you'll have the code that will land as Firefox OS 2.1. Current stable version is 1.3).

> The recent tendency of Mozilla to force totally unwanted changes (like Australis) upon Firefox users

Did you read the studies and feedback analysis or are you extrapolating your own sentiment onto majority of users?

> "Openness" means that non-Mozilla parties can actively influence the development and future of Firefox OS.

That's exactly what is going on with the project right now. Many external contributors, both individual volunteers, and companies, are involved in the development process of Firefox OS.

> Likewise, the claim that Firefox OS "doesn't limit your freedom" is suspect, too. How can that claim be made when developers are pretty much forced into using HTML5, CSS and JavaScript to build apps?

That's a fallacy. Freedom in question is referring to the freedom of the user to choose how he wants to use his device, not to programming languages that are supported on the platform. It's like saying "roads does not give me freedom if I have to drive my car on them and can't use them with my submarine of choice".

> A standard that exists but isn't widely implemented probably shouldn't be considered a standard.

You are right. I believe that it's just an oversimplification.

But the sole fact that all API's created in the process are on the standardization path is a major push toward empowering web technologies to be fully capable of handling more advanced applications and systems and does set a precedence. We will soon live in the world where HTML+DOM+JS will be enough to write operating systems and apps that will work on multiple platforms. That's the opposite of vendor lock in that major platforms are leveraging.

zbraniecki··on Warsaw, August 1947
last time I visited Warsaw it was in much worse shape than on google maps photo. Hope it'll get into [2] soon :)

p.s. I grew up really close to it - like a block away. Seeing photos of the streets around my block at the time when you could see horizon and ruins... frisson.

← PreviousPage 6 of 6