In order for the Management Engine to really do much, you need to have a network card that the management engine knows how to talk to. If you don't have such a network interface, the ME can't do all that much, and any adverse security risks are near zero. Add to that things like the firmware write line being controlled by a completely separate microcontroller, and the big things that are discussed are completely infeasible. I'd be much more worried about the lack of microcode updates that libreboot users shun in the name of "freedom".
If you had a basic syslog setup, it stored as text files. However, a more interesting syslog setup would take those entries and send them to a remote database, filter them to match certain contents, run scripts based on those matches, etc. Systemd only seems magical because most distros don't use even a sliver of the abilities that modern syslogs provide.
Systemd is a Jenga tower. Yes, there are lots of little pieces, and yes, removing a few won't hurt anything, but it's still fragile, and rather inconsistent. "Parts" like the journal, are a separate executable, but are not managed like other services. It uses a poorly documented ipc interface to talk to the various parts, and the configuration files are a nasty tangle of symlinks and control files stretching across the filesystem. It's just not a very well engineered piece of software.
Manpages can have a rather large amount of interactivity. Documents can be formatted as text, as HTML, with links, etc. The problem is that manpages are an afterthought in too much of the Linux ecosystem, so people have low expectations and low beliefs in what they can actually do. They can have tables, they can have equations, they can have graphics.
They missed a format that's ubiquitous, has a lot of formatting options, and has search facilities. Manpages. When someone's looking for a piece of documentation, they are usually working on a system as they do it, and man -k <thing> is a lot easier to remember than some other search tool that requires its own set of packages, etc.
One of the first questions I would ask is what is an indirect assertion of a patent in this situation? If you get shaken down by a patent troll for a patent related to React stuff, would that be considered an indirect assertion? After all, you're making a statement there that React is violating some patent. While I can agree with patent severance clauses, this one just feels full of real ugliness that would drive a lawyer crazy.
Is there any plan to have docker for windows containers and docker for windows use a different socket? At the moment, both trample on each other, and there are times when I'd like to use them together.
This is a working draft of a findings document that's being actively edited. Google Docs allows for realtime cooperative collaboration, with nice features like chat and annotation of documents. There are a few other collaborative editing systems out there, but they tend to have more hitches than google docs'
I've found the dev process to be a lot easier if the development environment mirrors the production environment. So I'll spawn jails and/or vms for the database server, for the various bits and pieces of the apps/environment. It means less things that can be forgotten about as an app gets pushed to staging/production, and that documentation becomes easier. Also, names are usually more memorable than numbers, so it helps keep things moving while you're working on things.
For doing what Haiku and BeOS excel at, you need a huge pile of patches to the Linux kernel, to rewrite even more subsystems than Android did -- for one, the audio subsystem in Linux is an absolute disaster, and have the impedance mismatch of your kernel not being written with neither the same philosophy nor language as the rest of the OS. Haiku wants to be backward compatible with programs written for BeOS, so you'd have to write a mish-mash of compatibility drivers for that to work. At a point, it becomes easier to just write your own kernel.
Both gcc and clang have flags to emit raw object files. At which point, your porting work really centers around making sure you have a good standard library in place, and that your kernel has a reasonable implementation of parsing a binary format like ELF or PE, etc.
MS doesn't write a lot of drivers for hardware. Even the stuff they provide on disk has a lot of drivers written by a third party. Intel's RAID mode is something that's not supported by default on Windows 10 even, which means you have to have the special RAID driver for even Windows to work on it. Intel has the driver info and isn't even releasing it to any OS makers as far as I can tell.
One of the parts of the MS Signature Series agreement is that there is no crapware, that what you get is pretty much the same if you installed a direct from microsoft copy of Windows. The signature series is probably the only line I would get from lenovo, because it's guaranteed not to need hours of futzing to get it working decently.
It isn't hard to figure out what's happening if you read everything that went on. Windows itself doesn't install on these computers unless you have special drivers in the boot medium that aren't included with Windows 10. Why would Microsoft sabotage their own OS like that if this were something done to stymie other OSes?
Caltrans has a long-term plan to get I-40 extended to Bakersfield. It's probably not going to ever quite hit the ocean because the Coast Range west of there is pretty rugged, and the traffic continuing through is pretty minimal.
There's a simpler explanation. It's a pre-existing route that was adopted by the federal highway system. US 50 is well known enough that resigning it would be more trouble than it was worth.
They were skipped for unknown reasons. US Highway 50 and 60 exist though. Could possibly be why. An Interstate 50 and a US 50 in close proximity would be...confusing.
Another glaring exception is Interstate 238 in California. It's an important, if short, route in the Bay Area, but at the time it was redesignated an Interstate, every x80 number had been taken, either by other local freeways, or by unrelated highways. So, when it was updated to interstate standards, they just decided to let it keep its old number, even though interstate 38 doesn't even exist.
Since then, Highway 480 (it was never formally adopted as an Interstate) has been removed, but renumbering would be more trouble than it's worth, so it's remained I-238.
Spur and belt routes, the ones with three digits, are reused across states. They tend to be ones that branch off to serve particular cities and not cross state lines.
US routes are mirrored -- US 1/2 in the Northeast and US101/(Defunct)80 in California, with US 90 ending in Texas. The 3 digit routes -- except 101, because the Federal Highway System had a lot more exceptions -- tended to be more tenuously associated with their "parent" route.
There's another rule this one doesn't touch. Route numbers that are divisible by 5 are considered major routes, and with a few exceptions go from one geographical extreme to the other -- Interstate 5 goes from Canada to Mexico, Interstate 80 goes from San Francisco to New York.
Yes, pitchers sometimes intentionally throw those kind of balls, in order to do what happened in the video. The one in the video is an extreme example, with most balls of this type crossing the plate very low, but not hitting the ground. It's also sometimes done with no intention of it being playable, but rather to throw off a batter for the next pitch or two.
There are also situations where a pitcher will intentionally walk a batter, such as if the batter is very good, so that they can pitch to the next player, who may not be as good of a hitter. There are a whole other set of rules though on how to intentionally walk someone. An at-bat can get complicated with the various ways a batter and pitcher can go about trying to get into the headspace of the other in order to achieve their successive goals.
Razor/razor blade is a marketing strategy. Sell/give the base at a low or free cost, and make the money on selling the consumables at a significant markup. The razor itself also has to be engineered for durability, with springs, latches, etc. While it's a comparatively simple part, it needs to be rugged to last a few years in a moisture filled environment where it's liable to be dropped and otherwise abused.
Similarly, the print heads are the precision part in a printer. Drive components in the printer itself -- motor, the belts, rollers, etc, are all pretty cheap and easy at this point; the same print engine will be used over several series of printers. The print heads on the other hand, have piezoelectric parts and/or heat elements that have to be very quick and accurate to do a good job. Both cases, while there is definitely some engineering in them, it doesn't rise to the cost levels we see them being sold at.
I wouldn't doubt it for a second. Printer makers use the razor/razorblade model for consumables, where the printer's dirt cheap, but the ink costs an arm and a leg. This is just the latest tactic for getting people to go OEM only.
At this point, I long for the good old days, when Canon embraced 3rd party ink vendors. Canon's cartridges were cheap because the print heads were a separate, replaceable, item, and the third parties were more than free to put out really interesting inks, like sets of greyscale for making really nice black and white prints.