Yes, that's how it is written in Vietnamese. To oversimplify: Vietnamese words are a collection of single syllables that are always separated by a space when writing.
"Viet Nam" is also, actually, the "official" English way to write it. (Check how the UN puts it on all their stuff.) However, most Europeans don't do that in their languages, so it usually gets written as Vietnam even by Vietnamese when they're writing European languages.
kernel_task is due to high temperature on the left thunderbolt ports caused by charging. Plug your charger into the right side instead and it'll go away in about 15 seconds.
As someone running my 2015 MPB into the ground this sounds absolutely insane. I love MacOS, but this is on par with the “you’re holding it wrong” insanity. I really hope Apple gets their newer MBP straightened out before I have to buy a new laptop.
Are you sure it was that good with large files? I used to be a TextWrangler evangelist until I noticed it was mangling large files. You'd change one character but the saved file differed by far more than one character. Medium-sized nowadays, hundreds of MB TSV files. About 10 years ago.
Yup. About 15 years ago, doing search/replace on multi-hundred-MB log files and SQL database dumps.
About 3-4 years ago it stopped being nearly as performant with large files (even a couple MB).
I’ve never had a problem with either BBEdit or Textwrangler mangling files. I can believe there may have been such a bug at one point, but I must have sidestepped it - perhaps it was caught and fixed quickly.
Will L2 congestion become a problem once JWST and a few more missions join this craft? Will we have to manage that orbit like we do with geostationary?
I saw this post on the bus, installed the app. Checked what it says for my transfer. I had about 8 minutes.
Google said my bus comes at 7:29. Transit app says it comes at 7:37. The bus came at 7:29. The app didn't match the posted time table either.
This is in a major tech area next to a major university. Their About screen lists dozens of local transit authorities as data sources, with the one running the bus in question as a licensed source.
Because your $apt_repo_url is useless to a yum user.
The package management community needs to stop balkanizing.
How else do you propose releasing software to all Unix-like OSes without learning a half dozen package manager formats and quirks? Only other choice is a container.
American rail is built for cargo, so there are no sections as fast as a freeway.
Also there are several sections that are particularly slow. The track through the Rockies is the original 1869 route, with original curvy single track and original tunnels. Speed there is around 20mph. Sometimes you come close to I-70, where cars are going 60-80mph. The Sierras also have slow sections. That said, those were my favorite parts of the trip.
This is mostly true, but in fact the route currently used by the California Zephyr through the Rockies (Salt Lake City - Soldier Summit - Moffat Tunnel - Denver) was built by the Denver and Rio Grande Western Railroad or its predecessors [1]; the section in question was completed no earlier than 1883.
The more famous railroad finished in 1869 takes a more northerly route, through Ogden instead of Provo, and through Rawlins, Laramie, and Cheyenne in Wyoming instead of adjacent to I-70 through Grand Junction and Denver.
The mountainous sections of the Zephyr, specifically the crossings of the Rockies and the Sierras, are indeed the least competitive vs. driving. Based off of the official timetable [2], the Zephyr takes:
~9 hours between Chicago and Omaha vs. 7.5 hours driving
~8.5 hours between Omaha and Denver vs. 7.5 hours driving
~15 hours between Denver and Salt Lake City vs. 8 hours driving
9 hours between Salt Lake City and Reno vs. 7.5 hours driving
7.5 hours between Reno and Emeryville vs. hours 3.5 driving
Lengthening the driving time to include breaks, the train is viable between Chicago and Denver, and between Salt Lake and Reno, but is nearly twice as slow as driving on other parts of the route.
Stating the obvious here, I know, but Chicago-Denver has so many flights it's not even funny, United, American, Spirit, Southwest, Frontier, well over twenty flights any day.
The nominal max speed of Amtrak trains is about 79mph [1]. When I was traveling up I-57 in IL (speed limit 70mph), the Amtrak train was going almost identically in speed.
Most of the class I railroad track was built to handle high speed (by early 20th century standards) traffic, so trains can generally reach 70-90mph (although not so much in suburban or mountainous areas) with little modification. The difficulty is that there's no economic reason to push freight trains to high speed, and mixing higher-speed passenger and low-speed freight creates scheduling conflicts, so passenger speed tends not to hit its top speeds.
[1] On freight track, that is. The NEC, which is all passenger traffic and all-electric, has higher nominal speed: even the "slow" NE regionals will hit 100mph on the empty track in MD.
To add to this, the FRA regulates track speed based upon condition of the track and some other requirements. Track condition is typically quite good (rail companies really want to avoid derailments), but one of the biggest impediments is grade crossings. The faster the track, the more extensive protection needed to keep trains and cars separate. Table 42 [1] here gives the requirements. Most of the mainline track is Class 4. You'll notice to hit 125 mph every grade crossing needs a full barrier between the car and train. And faster that that, complete grade separation (ie, bridge). US rail was not designed with this in mind and while they close a grade crossing any chance they get, they're still a major hindrance to high speed operation.
There aren't no sections, but there are certainly very few that beat 70mph...for example, IIRC the Amtrak Downeaster hits 70-80 at at least one point (the speed limit of the train is 79mph throughout the route)...for like a mile or two as it crosses the Scarborough marsh ;)
