You make some great points. The arbitrary entitlement is an important and vital step in the growth of an organization. Not every basketball fan should play or work for a NBA team. There has to be some sort of gatekeeping otherwise a bad hire or misplaced promotion could become a cancer that kills from within.
I first came across this in the Marine Corps, which pushes you to ideally no more than 4 direct reports, with the idea that you could have up to 8 directly reporting temporarily, but that would lead to your own personal performance degrading in anything that's not directly managing those 8. Hence the structure would be 4 to a "fire team" with a team leader, 3 teams to a squad with a squad leader, three squads to a platoon with a platoon leader.
There's similar numbers found in the book An Elegant Puzzle: Systems of Engineering Management, and I want to say that similar numbers are espoused by Jocko Willink in his leadership books.
Does remarkable use a fork of ChromiumOS? ChromiumOS uses the BOOT-A and BOOT-B partitions for upgrades and it reverts to the previously used boot partition if the OS fails to successfully boot[0].
Thank you for the fast response and, also, for putting this onto my radar. For anyone else who is curious, Yocto/OpenEmbedded is used to create custom linux distributions for embedded devices:
using two partitions in this way on embedded devices has been a trope for a very long time. service/warranty calls are expensive!
usually there are three. system a and system b which are updated and flipped and some sort of emergency recovery that either has a factory image or a very light rom that phones home for a new image.
sorta. but i think that blue/green deployments are typically monitored by some central control that will halt and reverse a whole fleet deployment, where typically embedded devices run that state machine locally. (after flashing the unused partition, if it fails to boot, fail back to the old one and disable the update).
Great explanation...
For anyone interested, the following jupyter notebook explains three different ways to process HTTP requests: serial requests (the baseline), pipelined requests and parallel requests with multiple connections (and without threads).
Introducing javascript into the mix will not make the botnet more difficult to detect. Headless browsers have their own fingerprints which allow defenders to identify them from legitimate traffic. You can spoof the features that headless browsers don't have but that will always be a cat and mouse game.
Yes, good point. Gopher is internet browsing too but is Firefox the best way to experience FTP and Gopher? How many different protocols should Firefox support? Firefox does not have the same resources as Google so focusing on what Firefox is known to do best such as HTTP and its supporting protocols, like WebSocket, really well looks like a good strategy.
I just checked my Windows 10 machine and it still has the FTP command-line program built in. What proportion of machines have Firefox but no FTP command-line program (or a "finder"/"explorer" that doesn't support FTP)? I cannot imagine this number is large.
