-
The article appears to mostly hinge upon the assumption that Docker is being used primarily as a sandbox, which to me seems like a weird assumption to make. I found it odd that this caveat wasn’t immediately made clear in the article’s headline, since I suppose this is at odds with what most folks would want to use container technology for.
The kernel namespacing and isolation features are convenient when implementing a technology aimed to deliver and host services, but I doubt the overall design of Docker would have been much different if those facilities had never existed. We’d still want to provision and distribute images just the same.
-
This makes me remember an online Curta simulator (unfortunately, implemented in Flash; but hey it was 2003).
-
Interesting. This appears to take a similar approach as the AdNW project (German language site only). They defined quantitative metrics inspired by Dvoraks methods and then ran a genetic algorithm over a 50/50 English-German corpus.
-
I am not surprised, since Firefox’ current mission seems to copy Chrome, throwing away all advantages that they had (like extensibility) to become a worse Chrome. Might as well switch to Chrome then.
-
-
XUL was an incredible piece of technology. Ten years ago I developed a cross-platform application with native look-and-feel and embedded data-visualizations in a couple of weeks. I don’t think there was anything else that would have allowed me to do that back then… and even now, that would be a challenge. I wish XUL had been blessed by W3C standardization.
-
-
Is electrolysis worth losing a ton of extensions and developers over?
Is electrolysis even a good thing? If I open facebook, twitter and youtube at the same time I can expect firefox to grind to a halt. With electrolysis, my whole PC will grind to a halt? I don’t buy better the security argument either - firefox is a reverse shell with or without electrolysis.
-
E10S is required for shipping a sandbox for Firefox. I’m a bit biased, since I work on Firefox sandboxing, but I believe this is probably the single most important security project we have.
I’m not sure what you mean by “firefox is a reverse shell with or without electrolysis” - enabling the sandbox makes it so that any random memory corruption in the content process isn’t game over for security, which is a huge win.
-
You don’t buy the “security argument” of process isolation and sandboxing? It’s fairly easy not to see the benefits of something if you deny the reality of the benefits it does provide.
-
-
That’s my concern though - I don’t think they recognize how much people depend on their favorite extensions to make using Firefox a pleasant expeiernce. The impression I get is they’re basically gonna draw a line in the sand and switch whether or not the extension ecosystem comes with them.
I agree that it needs to happen, but were I them I’d be looking at the most popular extensions and ensuring that a transition plan exists. Their market share depends on it.
-
I agree that it needs to happen, but were I them I’d be looking at the most popular extensions and ensuring that a transition plan exists. Their market share depends on it.
They are doing exactly that… they have many bugs filed that are “enable to be written as webext”. The core webext team is extremely smart and capable.
-
-
-
-
-
Agreed. Throwing away XUIL extensions is going to totally cripple them. I don’t know what I’ll do at that point. IMO they’re what make Firefox a usable alternative, and there are a bunch of things you simply can’t do with the proposed Javascript extension standard (can’t think of the name).
It’s All Text comes to mind.
-
-
-
Yeah, I guess it has to get a lot worse before it gets better. As long as they are (so) dependent on income from advertisers (Yahoo?), they will not put the user first regarding privacy and security. For example why are the Tor Browser’s Firefox settings not the default in Firefox? Why is Privacy Badger or something similar not a default extension? Why are third party cookies still enabled by default?
I guess over time more and more stuff will break again with Firefox as also mentioned in the article, that making it a bit worse now by enabling the Tor settings and Privacy Badger won’t make much of a difference. At least you’d know Mozilla has your back, and Firefox may even gain some users by being privacy friendly by default. That is, for as long as it is relevant and “the web” is used by the average user.
-
Mozilla is actively working with the Tor project to upstream their Tor Browser patches and improve privacy defaults.
-
-
-
-
-
Share your favorite git tips/aliases if you’ve got some good ones!
-
This is a Mercurial trick, but I use it on Git repos via hg-git, so it sorta counts? Maybe? ;-)
# hgrc: # [revsetalias] # feature($1) = _firstancestors($1) and not _firstancestors(master)This shows all commits that were made on a feature branch (branch in the Git sense), whethere they’ve been merged into master or not; and it ignores all commits that were made on the master branch, whether they’ve been merged into feature or not. Like this: only the commits marked ‘F’ for feature get shown.
hg log -r 'feature(myfeature)' v master o--o--o--o-----o \ \ / \ \ / F--F--F ^ myfeatureI prefer rebase-based merging; but git-flow uses explicit merges, and this is really useful for examining that sort of history. It is possible because for each merge commit, Mercurial records which parent was the recipient (
HEAD) and which parent was merged in (MERGE_HEAD). I have a strong suspicion that Git, too, stores merge parents in an ordered manner, but I have yet to verify this. -
Show unpushed commits:
unpushed = log --branches --not --remotesHandy for pipelines:
touched = show --name-only --pretty=format: --relative conflicts = !git ls-files -u | cut -f2 | sort -u staged = diff --cached --name-only --relative untracked = ls-files --others --exclude-standard modified = ls-files --modified --exclude-standardOverview of the repo’s branch structure:
overview = log --date=relative --simplify-by-decoration --all --graph
-
-
[Comment from banned user removed]
-
XMPP used to be the future of IRC and saw significant use by serving as the back-end for now walled-off, proprietary services. I would still love to see it succeed in the long run, but given the great amount of fragmentation I find it hard to imagine any sort of re-unification of the messaging-sphere based on either XMPP or matrix. Do you see reason to expect matrix should fare differently?
-
XMPP was a pain in the ass last time I looked into it. I ended up liking PSYC and IRC more esp after looking at comparisons:
Worse is Better effect kicks in, though, to have XMPP and its extensions dominate. :)
-
-
-
It should be noted that some of these steps are optional. E.g., an initrd is not needed if your kernel has built-in capabilities to access and mount the root file-system. With EFI systems you can also skip the bootloader if the kernel is built with EFISTUB support.