I don't use it for my primary workflow, but I use the Android app all the time for "grab a couple of interesting shots to send to friends, from the parking lot right after a hike/nature shoot", and it's fine for that (and for firmware updates.)
I don't really see this with modern graphics programming, but I was highly amused that my 1980s-1990s graphics skills (in particular, coordinate transform math) were very useful when I started working in robotics in the 2010s-2020s (because forward and inverse kinematics are exactly the same thing as 2d/3d projections.)
The trick there is that they both have related physical analogs, and machine learning math doesn't really (in that while you can visualize them spatially, it doesn't seem to help solve any problems in that space.)
At least in the US (and this probably is different from Europe) it matters a huge amount how the asbestos is exposed to the environment. Asbestos that's sealed up generally gets (a) labelled so noone cuts into it (b) sealed up even further - but if it's exposed, the evaluation is more about "can it get into the air" (sealing is again the preferred step, epoxy over tile, that sort of thing) - actually removing it is a last resort. So "mere detection" is a really small part of the problem.
(Of course, the place I've dealt with this the most was a former post office building from the late 1930s - we didn't really need tests, a historian would probably have just said "of course you have asbestos" :-) It does expose an interesting problem with the labeling part, though: USPS as an ancient federal agency has its own rules for things and had a distinct asbestos markers - an A in a point-down triangle - which we fortunately found documentation for, it isn't public record.)
Well, the .meow kickstarter raised €121,896 with just an assertion and a voucher system, so there's at least some community support for this kind of thing, without it needing to be a good idea :-)
Higher cabin pressure, but it is marketed in pressure-corresponding-to-altitude; Norwegian Airlines for example keeps their cabins at 6000ft, ie. equivalent atmospheric pressure to being at 6000ft. (Looks like "equivalent effective cabin altitude" or just "cabin altitude" is the more accurate term.) So yeah, I worded that backwards, higher pressure, lower altitude, is more comfortable for passengers (me) especially on longer flights.
Concorde is exotic, absolutely, but having seen the one at Udvar-Hazy I'm not sure I'd call it beautiful... not being an aircraft designer, my sense for this is of course biased by the way the average commercial jet looks like, well, a commercial jet, and the Concorde looks like someone who was really good at paper airplanes got ahold of the CAD system for the weekend :-)
I had a round trip BOS↔LHR that was 747 eastbound, 777 westbound; I ended up on the upper deck of the 747, which was fascinating as an otherwise casual flyer. One especially memorable bit was landing - you're basically three stories up and suddenly the wheels are on the ground, and you're still three stories up :-)
(I'm still happy to have traded that for planes with a much higher cabin pressure-altitude - and would trade even further for business-class transatlantic non-cruise ships. But it was definitely fun to have had the experience.)
"valves" being british for vacuum tubes (though there's an entire generation of scifi where future computers are built around miniaturized valves even among american authors for some reason, Asimov in particular)
In emacs, c-x 8 RET prompts you for unicode character names (or hex) so for rare use you can just spell it out. There's also C-x 8 _ m for em dash and C-x 8 _ n for en dash. (Hit c-x 8 c-h to get a full list of those bindings, like any normal secondary map - they're about as idiosyncratic as the XCompose bindings, but you might find some of them "stick" in your head better (I personally like "C-x 8 1 / 2" better than "Compose 1 2" even if it's a lot more typing...)
(having it right there mostly serves as a physical token/reminder that I don't want to get sucked in to my social media and other phone apps as much, so if I'm just using it to fill "politely waiting" time I can just grab the x4 instead. I also have a trivial pandoc-generated epub todo list as the first document, though that would work better as a crosspoint fork/feature really...)
It's way smaller than modern phones, though - I clip mine to the back of my Samsung (magsafe case) and it only blocks one of the five cameras. (phone: 288g xtelink x4: 75g.)
(also: hasn't the x4-v2 already been announced that is supposed to have a frontlight?)
I think that might be just imagination - android autocorrect in particular got sufficiently worse that I finally turned it off (I still use it as a "typing assist" - it only displays choices that I can tap to replace, or (more often) ignore.)
I saw https://www.youtube.com/watch?v=tohImHa4f5U (Hoarder Sam, "I'm building a drone for the DARPA lift challenge") the other day and it was a pretty good discussion of the "shape of the envelope" of the problem (and what kind of lift ratios actually exist in modern air vehicles), and particularly how they've set up the constraints to eliminate a bunch of "easy" approaches.
It also reminded me that for the first round of the self-driving grand challenge, none of the vehicles even completed the course :-) They really are trying to encourage "out of the box", or at least "not in the obvious box", designs...
wasn't some of that smoothness because it ran at a 100hz tick without any way of adapting it (and still running existing code)? That was the complaint I kept hearing from people attempting to make flash on phones viable (this led to ludicrous battery consumption)
A long time ago I was doing some on-site programming at a swiss bank, and the only available editors were vi on a Sun, or EDIT on a VMS machine (the project involved both.) I learned rudimentary vi on the fly while waiting for ftp-by-mail-over-uucp to deliver GNU emacs sources :-)
Arguably they (we :-) were right at the time. Around Ubuntu 16.04, the journal was Hot Garbage - to keep a production system working (as in, "didn't randomly stop logging, didn't regularly corrupt logs, didn't uncontrollably fill the disk because none of the limit options actually worked") we eventually backported about 30 fixes from newer versions - by 22.04 or so it was "fit for purpose" out of the box, but earlier than that it earned every bit of hatred it got.
hmm, when did that get added? Last time I checked, the only timezone you could specify was UTC (which was one more than cron supported, but still insufficient.)