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.
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.
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.
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.
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...
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.
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.
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.
No, because the criteria here is state transition from not-in-use/power saving to in-use/"on". The Pi Zero has no meaningful sleep state, as I lamented above, thus the only valid "off-on" state transition for the Optocam Zero is a full boot. Sure, if you were to leave it on in your bag then there's no boot time, but then you're limited to 70-80 minutes of runtime. Then you get "instant-on", but you're limited to the photos you can take within an hour off the charger, which also renders it useless as a camera, and compares unfavorably to the iPhone . If it had a sleep state then we could compare apples to apples. Since the iPhone's default "off" state is sleep, that's what counts for "turning it on".
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.
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.
It's a shame that, being based on a full-blown Linux SBPC, it has an absolutely unacceptable boot time for a camera. 22 seconds. I can have my iPhone camera out and ready to capture an ephemeral moment of child's play in under 3 seconds, most commercial cameras boot in seconds as well. A film camera can be ready to go the second the lens cap is off. 22 seconds is an eternity in the world of photography. It's a shame that the SoC the Raspberry Pi line is based on has no kernel support (or IIRC hardware support) for S3 or anything similar.
The point they were trying to make was that if you take appreciation of assets into account, if your billion is appreciating by a relatively modest 5% per year, you are passively earning 50 million/year. Whereas someone with one million passively earns 50 thousand/year. One is enough to live in luxury anywhere in the world for several lifetimes, the other is enough to live comfortably in some parts of the US (or like a king in many parts of the world) but not enough to throw 6 figures at a programming language foundation for fun.
We just bought our first (used) EV, and charging stations are the Wild West right now. Any random station you pull up to might charge close to the local cost of electricity, or some wild sky-high amount. And hopefully they’ll tell you what that is before you have to swipe your card. There the economics can swing towards gas cars depending on how absurd your local charging station prices are. For people filling their tank every couple days because of a 2 hour commute or something an EV may still not make sense financially. But if you’re putting in under 40 miles and have even a modest 120v 12 amp circuit you can plug into at home (e.g. a dedicated washing machine circuit) you’ll likely only need a charging station on rare occasions such as a road trip. As a matter of fact I am writing this from our first EV road trip. The inconvenience has been comparatively minor and our “fuel” costs should end up being about half of what they would have been in our hybrid SUV.
G-code is like assembly language for CNC. It’s human readable, you can write it by hand if necessary, most machines will compile it internally to machine instructions, and there are a million different flavors with incompatible macros, etc. The flavor I’m most familiar with is Klipper’s interpreter, which will let you write macros, but that would technically be cheating since you could just stuff an entire program into a macro.
I'm sure the idea here was a physical quine, although since it only contains 2.5% of its own G-code it's not really a quine, any more than a "Hello World" program is a quine since the string "Hello World" is in the program text. It would be trivial to generate something like this depending on which part of the G-code you pick.
I think ultimately the conclusion the author reaches is an interesting one, that the real "disease" of tourism is like sepsis. It comes not from without, the tourists themselves, but from within, the changes made by locals to try to capture the opportunities for wealth that the tourists create.
The paradox of the tourist is fascinating. All at the same time, a locality experiencing a flood of tourism will welcome the sudden wellspring of foreign currency pouring forth from the rock, and loathe the disruption the flood causes to the steady pace of life. Anyone who has been a tourist knows what the tourist wants, a break from the monotony of their own culture, a desire to know the other and tread in their footsteps, in some cases a wholesome longing to break down cultural barriers and prejudice. And yet anyone who has been on the other side of the interaction with a tourist feels the heady mix of emotions that comes with the experience of being the toured. The discomfort that comes from the wall being torn down unexpectedly. The inconvenience of disruption in routine. No tourist wants to do harm, but even the most sensitive and well-meaning tourist creates a breach in routine that is disruptive. Nobody likes change.
Houses are big, the air mass inside is big, convection and recirculation maintain a fairly consistent temperature throughout the house, and the thermostat is centrally located so it averages the temperature of the air. The air coming out of the vents is still often colder or hotter than the set temperature, so sitting next to a vent can be less comfortable. Cars have a much smaller air mass, much poorer insulation, a thermostat that is usually installed in the ventilation rather than in the cabin where the people are, so the perceived temperature inside of a car can vary wildly if you don't live in an extremely mild climate, even as a sibling commenter mentioned, between the back seat and front seat, or between the passenger seat and driver seat.
It also prevents all kinds of clients who (for various reasons) can't implement SSL from visiting your website. I'm sure this is a "small web" blog, whose author wants to be visited by e.g. a Commodore 64, an OS 9 iMac, or somebody who just wants to telnet in. If the sensitivity of the information on this page was critical or you were going to be submitting information then by all means yes, SSL is important, but if you're going to be reading a personal blog about calendars then http is probably fine. Of course the ideal solution is offering both and letting the client choose.
For anyone who was also curious what Justin Frankel got up to after the speculation at the end of the article, he founded Cockos Software and is the lead developer on the excellent REAPER DAW.
It's a shame, he's a genuinely cool guy! If I wasn't convinced that my kids would find a way to break it when I wasn't looking I'd definitely have an Acme Klein Bottle by now.
It's not just that, Notepad++ is built around Win32 APIs and is designed for Windows. He's got some non-portable optimizations baked in. At its core, Notepad++ is just another Scintilla wrapper (like SciTE or Textadept) but it's targeted at and optimized for Windows. There will not be a Mac or Linux port.
If you want an editor with the same core as Notepad++, but fewer batteries included and more extensibility, Textadept is worth a look.
Touch and mouse are two very distinct forms of input that need to be kept separate. Every convertible Windows laptop I have ever used has convinced me of that.
Mouse interfaces can be incredibly information dense because mice are both incredibly economic from a space and motion standpoint, and also somehow incredibly precise. You can flick your wrist to select any target the size of a grain of rice on a 32" screen. Touch interfaces require larger targets because fingertips are larger than a cursor point, and also require smaller screens because your arm now has to move the entire length of the screen, which is slow and tiring.
Where touchscreens excel is tactile experiences, things that mice cannot replicate. Multi-touch, pressure sensitivity, pen angle. Sweeping motions are difficult to control with a mouse. Manipulating multiple analog controls is nigh-impossible with a mouse.
When an app tries to accommodate both input styles, it inevitably ends up catering to one style or the other, unless two separate interfaces are built. And because a touchscreen laptop can be touched or have the mouse moved at any given time, it's not really possible to switch between the two input styles seamlessly.
I would really enjoy having a device that is capable of both, since the iPad has a gorgeous screen, a great form factor, and a lot of killer uses. But it can't cannibalize mouse interfaces or we wind up with the direction that MacOS is going.
There is nothing wrong with having a keyboard connected to a touch device per se, but the gross arm motion required to move between the touchscreen and the keyboard, and the awkward angle the keyboard puts the touchscreen at sort of nukes the usefulness of the touchscreen. And again, jumping in text is the sort of small target action that mice excel at.
Not wanting to install an OS package to do something as simple as sending some bytes a couple years back, I wrote a shell script to send WoL packets. Its only dependencies are netcat and bash so if you have busybox it should run almost anywhere. It just takes the mac address and interface as an argument and sends a WoL packet on that interface
#!/bin/bash
hex="\xFF\xFF\xFF\xFF\xFF\xFF"
mac_hex="\\x`printf "$1" | sed 's/:/\\\\x/g'`"
wol_string="$hex"
for i in {1..16}
do
wol_string+="$mac_hex"
done
printf "$wol_string" | nc -u -b -w 1 "$2" 9
It took me a while to find an explanation of something so simple, I can't figure out why everyone relies on huge binary packages and libraries to do it. I just needed something on my router so that I could wake my machines from outside the house. I ended up just writing a couple shell scripts that called it and triggering them with nginx via FastCGI so I could click on a link to wake up my machines.
To me the buns still look far too perfect and fluffy. I don't know if I've ever received a wrapped McDonald's hamburger that hasn't been smashed flat to some extent, with cracks in the bun. The ones that come in boxes fare a little better but they still look as if they've weathered some turbulence.