The biggest thing people seem to be up in arms over is the disk space. I don’t see any of the suggestions on that page freeing the disk space back up, please correct me if I’m wrong.
Space is really, really big. I think it's hard for us to comprehend just how much space is in space, especially in 3-dimensional terms. It would take a lot of sand to mine all of the useful orbital space, and that's just LEO. There's tons of room in higher orbits. It would measurably increase the risk of passing through LEO on the way to other destinations and make some orbital planes unusable for e.g. Starlink or human habitation, but when you're just passing through, the odds of getting punctured are probably still reasonable, at least for unmanned spacecraft. Keep in mind that the ISS maneuvers out of the way when there are several miles to a potential impactor, just in case. We have all our eggs in one basket right now, so everybody is really careful with that one basket.
LEO is relatively simple to destroy simply because it's already so populated with mass, and that population is growing rapidly, and because they all come pretty close to crossing each other's orbits. Collisions with even very small pieces of debris typically generate secondary debris, growing the population.
A half-hour boost phase through LEO to get to higher orbit is dramatically less risky than spending 87600 hours there over a 10-year orbital lifespan. In the event that it all goes asymptotic, what sort of timescales would be afflicted by collision risks 10^6 or 10^9 or 10^12 greater than what exist now, I am uncertain.
Low earth orbit isn't that much space though right ? It is effectively a stack of practical orbital shells. A rogue nation state can make satellite launches financially unfeasible.
It would take a lot of sand to mine all of the useful orbital space, and that's just LEO.
Nope. You just need to make it a high enough probability of your spaceship being damaged that people won't take the risk. For humans that's very low. For anything moderately expensive it's quite low.
There's tons of room in higher orbits.
You have to go through the lower orbits to get there.
> You have to go through the lower orbits to get there
Math doesn't math.
The closest solution I've seen is putting 10^6 to 10^9 kg fragmented debris in the 700 to 1,000 km band to create a 5% failure rate at fastest transit, which is economically devastating. But that assumes away grain-grain collisions.
I think when I last ran the math, you'd need to sustain 5 to 10 Starship loads of fragmented debris to that orbit a week to create a proper barrier–near 100% hazard. At which point the solution becomes shooting down those launch vehicles. In a couple years (3 to 10, depending on the solar cycle), the skies would clear to about 1% hazard. That hazard, however, would persist for some time–how long is anybody's guess.
Unfortunately probably not available in Australia, but as I've mentioned in other comments, GM for all its faults has managed to check all these boxes with the Bolt EV. It feels pretty much like a normal, boring car, which is a great thing. The only thing that violates the author's must-haves is that they put the A/C, heat, and heated seat controls on the touchscreen, although the "auto" climate control works well and is operated with a physical knob. Also I believe we have the higher trim model and it does not have motorized seats or seat memory, thankfully my wife and I are similarly proportioned enough that I only have to move the seat forward when I drive. It is by far my favorite of all the vehicles we've owned in recent years, and it's very affordable in the US.
I am the author of the blog post and yep, the Chevy Bolt is basically the perfect car (for me at least). Ticks all the boxes. Apparently the 2027 Bolt RS has driver's seat memory.
But the Bolt isn't available in Australia! GM abandoned us when they shut down Holden. Ironically, it was designed for production based on a South Korean prototype in Port Melbourne, 40km from where I live! https://www.carsguide.com.au/car-news/chevrolet-bolt-reveale...
Anecdotally, to me it's just more fun. It increases range by relying entirely on the regenerative braking and relegating the disc brakes to an "emergency" role. For freeway driving in traffic it's also more intuitive, since you don't have to balance coasting/braking and can just ease off the pedal more to slow down quickly. Muscle memory can definitely be hard to break though, when I'm in a hurry I sometimes forget to enable single-pedal and drive for a bit before I realize it. The car we have (Chevy Bolt) has a separate regenerative brake control as a paddle on the back of the steering wheel for use in "regular" mode, but it's awkwardly placed.
It increases range by relying entirely on the regenerative braking and relegating the disc brakes to an "emergency" role.
I'm not sure about the Bolt, but most EVs work that way, one-pedal or not. Even a hybrid Prius doesn't seem to use the friction brakes unless it has to (emergency, coming to a low speed stop).
I don't like one-pedal on the Hyundai Ioniq if for no other reason than it uses both front/rear motors regardless. In contrast to Eco/Normal mode that uses the front motor only if it feels the need for moar power!!
Not only that, but why buy diamonds when Moissanite exists? Not as hard as diamond (by a tiny amount) but much less brittle and much more sparkle. Also even more “rare” than diamond since the only natural occurring ones are microscopic. Plus they come in colors! It took a while to talk my wife down off of the diamond industry’s hype, but she loves lab grown stones now.
I've been daily-driving a Planck with a custom layout for years now. I developed my own layout (QWERTY based but with punctuation and function keys on thumb-driven layers) and it took me a few weeks to get speed parity with my old 104 key, which was rough. But now I can't go back to a standard layout, it's just so much less hand movement that it feels so much better to type on. For gaming it's still a tossup, as most games expect you to have all the same keys in the same places. I've experimented with a "gaming" layer, but lacking a 5th row on the Planck still causes issues with some games.
It still baffles me that the standard layout isn't ortholinear after all these years. There's no reason for staggered rows other than path dependence. But when you have billions of people relying on years of muscle memory on the same layout, it's just not a tradeoff most people are willing to make.
Touch screens don't have to be modal, that's a UI choice. The 2020 Bolt we just got leaves the climate controls on screen at all times, even when CarPlay is open. I was also pleasantly surprised by the number of buttons it has, including both a volume knob and a temperature knob.
That being said, the touchscreen software is abysmal and laggy. CarPlay works great, but any time I have to navigate the car's built-in software is a headache.
Actually it's an odd split. The temperature and fan adjustment are physical buttons, but the A/C, recirculation, and heated seat controls are on the screen. I'm thinking this is for two reasons: If a lower trim level lacks heated seats then they just exclude them from the firmware, and the AC and recirc controls require lighted indicators, which is probably a lot more expensive than just a button, so those were much cheaper to integrate into the display. That being said, I've heard digitizer failures can be an issue on this model so I dread that happening.
It also irritates me that there are 3 of those blank button placeholders on the dash and I wish they were actual buttons that were just mapped to A/C and recirc...
What I’ve always wished is that I could take pictures with a nice DLSR or bridge camera and have a way to quickly load the RAWs into my phone for culling and processing. You could get the best of both worlds, better sensors and lenses, and simple developing within seconds. I know there are cameras with built-in WiFi that do this but camera manufacturers seem to let their software become outdated quickly.
What I’ve always wished is that I could take pictures with a nice DLSR or bridge camera and have a way to quickly load the RAWs into my phone for culling and processing.
Apple makes (made?) an SD Card to lightning dongle. It's a wonderful thing on vacations.
I can take the SD Card from my Hasselblad and plug it into my iPhone. I then delete photos and videos I don't want, upload the keepers to iCloud as a backup, and AirDrop pictures to my wife so she can send them to her friends.
iOS has no problem with most current raw formats, and you can even convert them to JPEGs right in the phone.
You can also import the raw images and do basic editing of the photos with the Photos app.
The only problem I've run into is with long videos sometimes being laggy. But that might be an issue with a slow card, or moving data over a Lightning interface.
The WiFi in cameras is definitively in the "do not use" category. It's usually some kind of flaky, broken, and/or slow.
I wish camera manufacturers just used Android on their devices, with possibly 5G for geotagging and time sync. It would immediately solve all the connectivity issues.
When is the last time you purchased a camera and how much did you spend? I am happy with the wireless performance of my Sony A7 SIII. I kind of splurged on it as my once in every 2 decades camera so I don't have anything to compare to besides connectivity first cameras (Drone).
It’s exploiting the natural tendency of trees to create “waterspouts” through a technique called pollarding. When a tree suffers an injury it creates a bunch of new twigs that tend to grow straight upwards if the injury is on the upper branches. The waterspouts grow more slowly and so in this species of cedar they develop those desirable properties.
I started writing a more fleshed out vi compatibility mode for TextAdept earlier this year. As someone who understood the basics after going through :vimtutor multiple times but always struggled with the more "advanced" commands, there's no better way to actually grok vi than to just try to recreate it. It's pretty amazing how much Bill Joy managed to pack in. Of course, if you're implementing POSIX vi, there are quite a few features that have aged poorly, like roff/troff macros and line-editing, but there are also quite a few commands that I had never paid attention to (like _) that have subtle behaviors that sped up my editing even more. The hardest part about becoming proficient in vi is committing commands to muscle memory so you don't habitually fall back on hjkl.
> Of course, if you're implementing POSIX vi, there are quite a few features that have aged poorly, like roff/troff macros and line-editing
What do you mean by "roff/troff macros"?
EDIT: Ah, you're probably talking about the "section-wise" movements, defined in POSIX with language like "A line whose first character is a <period> and whose second and third characters match a two-character pair in the 'sections' edit option (see ex)" - that's the first time I've stumbled upon the 'sections' and 'paragraphs' options in the Vim manual ... Very quaint!
Yep, those are the ones! There's also the oddity of the [[ and ]] motions. In the POSIX standard, those are the only two-character motions. I was using a state-machine to implement motion commands, and that single command threw a wrench in the works. Of course, vim took two character commands and ran with it, so in vim [ can be followed by a whole host of characters that all do different things. Since g was not mapped in vi they also did the same thing there.
reply