141 karma · joined August 20, 2011
In a way many iOS and macOS applications are front-end software. It much more makes sense to make Swift available for other kinds of front-end development that for server-side coding.
It is unintuitive that you need to parse logs or pay $10 month to find out how much you are paying for each bucket.
Was actually flying on regular commercial flight from Kiev to Odessa on AN-24 yesterday.
2. I assume that iPhone is not discharging when it is plugged in this charger while being actively used (probably true even for less powerful chargers)
3. Wolfram: "12W for a year in kWh" ( http://www.wolframalpha.com/input/?i=12W+for+a+year+in+kWh ) = 105.1 kWh
4. Article says that iPhone consumes 361kWh which is more than a fridge(322kWh).
Either I don't understand something, or this is bullshit.
However this time we've got a difference: new dominant browser engine is open-source with a very liberal license (BSD, LGPL). So anyone who is not satisfied with the development of WebKit is welcome to fork. In fact, Google has replaced JavaScriptCore (part of WebKit) with V8.
So is there actually any reasons for having competitive open-source full browser stacks? I believe licensing reasons (the one behind FreeBSD and Linux) is not very important for browser world (Gecko and WebKit have very similar licensing terms). And I don't see much ideological reasons that can't be fixed by forking.
What else? Usually developers hate abandoning their work and switching to improve competitor's solutions — especially in the open source world. Developers like the feeling of doing important stuff and money. Market share of Firefox is still quite high (~25%) and Mozilla still receives money (company is non-profit, but developers are being paid I believe). Probably for this reasons the struggle will continue for some time.
However it is difficult to assume that there is something useful for web platform in this struggle. Every new web standard feature requires independent implementation from two different open-source projects and the whole platform adoption process goes as fast as the slowest team goes.