I think the menu in your toolbar that allows you to open a new tab in a particular container (you then have to do it via a long press or right-click on the new tab button), to re-open a current tab in a different container, and this new container-specific VPN functionality.
Without the extension, you can't set a domain to always open in a particular container, at least I couldn't find a UI to do so. To me, that is a very important part of using containers.
You extension also lets you sort open tabs by container but that doesn't sound very useful.
I experienced the same thing. Without the extension but with these flags enabled, there's no way to bind certain hostnames to certain containers.
This is sort of documented in https://support.mozilla.org/en-US/kb/containers#w_what-you-c... #5. That page covers it but doesn't clearly spell out that the itemized features are only possible with the extension. As far as I can tell, the extension is called "Multi-Account Containers" while the feature is called "containers" and readers are expected to know the difference when reading that doc. (Suggestion to Firefox docs maintainers: if that's correct, change all occurrences of "Multi-Account Containers" to "Multi-Account Containers Extension")
Oh, I had never discovered that feature... So I won't miss it yet. Need to think whether that makes it worth to use the extension again. For now I just enabled the manual configuration and have not noted any differences yet.
Yes. The shell in BusyBox is derived from ash via dash. They have diverged over the years but there is some flow of patches between the two. While dash aims to be POSIX-compatible the BusyBox shell includes selected bash features.
The shell in the busybox-w32 port has much of the POSIX and bash goodness of upstream BusyBox. It's a native WIN32 application so there are some concepts that don't translate well. For example, job control isn't supported and signal handling is limited. On the whole, though, I think it provides a reasonably comfortable shell experience.
Hanging above my desk is a sheet of thirty two dollar bills which I purchased from the Bureau of Engraving and Printing in Washington DC and had framed. It's a conscious nod towards Boggs and his art.
This won't be to everyone's taste but if you value 'lightweight' over 'feature-complete' busybox-w32 [1] may be worth a look. It's a port of BusyBox to WIN32, with random code borrowed from GNUlib for stuff that Microsoft omitted.
I maintain the most active fork and got into using it when I ported my last employer's software to Windows. This was originally developed in the early 1990s to run on Unix workstations. For portability it used Bourne shell (not bash) and nawk (not gawk). BusyBox allowed them to bundle a single executable with the Windows version that was adequate to run those scripts.
Some projects use busybox-w32 to allow a Unix-centric build system to work on Windows. Julia, for example, seems to use it just to get echo and printf.
