dblohm7

77 ms·

841.
by dblohm7 10y ago
It ran its course. It was only supposed to be a three month project. See the original announcement: https://medium.com/project-tofino/browsers-innovators-dilemm...
842.
by dblohm7 10y ago
Dismissing a company because one engineer there is bad at interviewing seems potentially short-sighted. One could swap "a company" and "one engineer there" and still have a perfectly valid argument.
843.
by dblohm7 10y ago
1) Tofino (which has now ended) was just an experimental testbed for trying some new browser concepts. It was easier for them to use Electron than to contend with Gecko's ossified embedding APIs. Hopefully positron ( https://
844.
by dblohm7 10y ago
A direct Firefox to Firefox OS comparison is not reasonable. For one, FxOS was a greenfield ecosystem, so it was built with multiprocess from the start, whereas the e10s project moves relatively glacially toward a multiprocess world so that
845.
by dblohm7 10y ago
The leadership from the Firefox OS era is all gone, FWIW.
846.
by dblohm7 10y ago
It shouldn't: experimental web features are now hidden behind browser preferences instead of prefixes that anybody can (ab)use.
847.
by dblohm7 10y ago
Addons are not supported by default in e10s mode on the release channel yet.
848.
by dblohm7 10y ago
Chrome didn't have extensions when it came out. Neither did Edge.
849.
by dblohm7 10y ago
This. Greenfield development makes it far easier to implement multiprocess and sandboxing. Try contending with a decade-old extension ecosystem and a legacy extension API that provides direct access to browser internals.
850.
by dblohm7 10y ago
We also didn't used to have nice things like JITs and hardware accelerated graphics.
851.
Mozilla could walk away from Yahoo deal and get more than $1B(recode.net)
421 points by dblohm7 10y ago|197 comments
852.
by dblohm7 10y ago
Last decade I wrote a server based on the old API and BindIoCompletionCallback. I can't comment on the performance differences, but the newer threadpool API is much better to work with. IMO one of the biggest problems with the old API
853.
by dblohm7 11y ago
Perhaps if we were to restrict this discussion to the physical aspects of the job, then yes. That is a very narrow view, however.
854.
by dblohm7 11y ago
We'd love it if you submitted some profiling data: https://developer.mozilla.org/en-US/docs/Mozilla/Performance...
855.
by dblohm7 11y ago
You can change the API without removing functionality. WebExtensions are going to be based upon the Chrome extension API, but will be expanding on that so that many of the "uniquely Firefox" addons can still exist.
856.
by dblohm7 11y ago
There is also about:performance, though I'm not sure whether that has made its way to release yet.
857.
by dblohm7 11y ago
It must have been: Brave co-founder Brian Bondy blogged about that purchase several months ago. http://www.brianbondy.com/blog/171/the-link-bubble-android-w...
858.
by dblohm7 11y ago
I'm amazed that in all of these discussions nobody ever references the RFC, so here you go: http://www.ietf.org/rfc/rfc4122.txt
859.
Bugs from Hell: Injected Third-Party Code and Detours Equals a Bad Time(dblohm7.ca)
36 points by dblohm7 11y ago|2 comments
860.
by dblohm7 11y ago
One caveat with coroutines and fibers is that all the code that runs on them must be fully aware that they are running on said coroutines and fibers.
861.
Bugs from Hell: Injected Third-Party Code and Detours Equals a Bad Time(dblohm7.ca)
2 points by dblohm7 11y ago|0 comments
862.
by dblohm7 11y ago
Good lord... M4?! Sounds painful.
863.
by dblohm7 11y ago
Yes the plan is to replace XUL with HTML. I have no idea where you heard otherwise.
864.
by dblohm7 11y ago
Remote Mozillian here: can confirm!
865.
by dblohm7 11y ago
As of version 42, 64-bit Firefox is available on all tier-1 desktop platforms (Linux+GTK, Mac, Windows).
866.
by dblohm7 11y ago
Yes.
867.
by dblohm7 11y ago
I'm a Mozilla dev who has spent way too much time working on NPAPI over the past few years. The major problem with NPAPI IMHO is that everything is reentrant. Calls to plugins can call back into the browser, which then can call back in
868.
by dblohm7 11y ago
There's nothing stopping you from bundling native code with your addon and having the addon launch the native process and communicate via a pipe.
869.
by dblohm7 11y ago
CLOSED for being off-topic!
870.
by dblohm7 11y ago
Here's the bug for jemalloc3 by default: https://bugzilla.mozilla.org/show_bug.cgi?id=762449

More ›