jeffhykin

The more reliable/reproducible the container is the more pain/effort it is to setup. If you don't need reliability, then you don't need containers.

• If you want unbeatable reliability, use nix.
• If you want better-than-nothing use venv/anaconda envs (one or the other, not both)
• If you want the most reliability-per-effort and don't care about performance, use distrobox

Fights breaking out? Idk man. When my friends go on a long ride they just toss a wall charger in their backpack. No need to wait in line for an hour when there's plenty of shops that'll let you charge.

Personally I can't see anyone paying $9,000 for normal looking ebike with 200 miles of range. Especially with options like the Eahora Juliet being 1/4 the price and available now. Buy an extra battery and charger for the Juliet, save $5K, and skip the 2.5hr wait at the charging station, charge both batteries at home overnight.

Not only in order but also

1. very human-obvious (international 1-1-2020 is not obvious if day-mo-year or mo-day-year)
2. Allows for arbitrary additional levels of precision to be appended. (E.g. year-mo-day-hour-min-sec-etc)

Fair, I did miss that requirement

It is a sad story. Keeping it in legendary meme status is the best way to remember it IMO.

Temple OS

A mattress with per-side heat controls. Unplug it, set your side to super hot, then use a timer socket to make it turn on when you want to wake up.

👍 when you get one definitely post it!

6.2 hours (150km at 24kph) is one hell of a commute.

TLDR: Because of rain and snow, I'd recommend prebuilt (water sealed electronics are difficult to do right). You can get both the bus and 150km range by getting one that's well-under 50lbs with a quick release battery. Use the bus for 99% of commutes, and when you want to go for a 6 hour trip, get saddle bags and load them up with ~5 extra batteries and a charger. I say well-under 50lbs because putting any bike on a bus mount is a bit awkward; putting a 50lbs bike on a mount in the rain/snow many weeks out of the year is asking for a back injury.

In terms 150km off a single charge, Eahora Romeo seems hard to beat to me. Being over the 24kph limit probably doesn't matter so long as it doesnt look like it very obviously goes over the 24kph limit. For context, the Onyx RCR with an extended 55ah battery, should get you right around 150km at 32kph, but the battery alone weighs 37lbs and costs $2,200. It also definitely looks like an "above 24kph" bike cause it does +90kph. The Eahora Romeo battery seems more efficient at 27lbs and 60ah. If you want actually under/at 24kph I don't know of any prebuilt with 150km of range on a single charge that doesn't have top speed of like +40kph, so it would probably have to be custom. Even custom though, getting that down to 50lbs with 150km of range on a single charge, with a ~300lbs payload (person+backpack+saddlebags,etc), and tires capable of rain/snow, is near limits of technology. With the right design you could get away with taking the battery off the bike before putting it on the rack. But really, frames that support a +55ah battery, even if they're pure carbon fiber, still are probably are probably not a good form factor for a bus rack. Using a smaller battery and bringing two or three

1. Gets bikes closer to the 24kph limit
2. Lets it go on a bus or up stairs
3. Will be a ton cheaper (less expensive frame)

Even with multiple batteries, unless you find a great deal, I don't think there's a real way to get that kind of range without spending upwards of $2,000 after taxes. Batteries are getting cheaper, but 150km is a long drive, even for a car.

For standard notes, its got an auto-export plaintext file option on desktop. Were you wanting two-way editing of plaintext? (e.g. Auto export and import)

When you're editing yaml, why not just always write JSON?

Almost all nix attr keys are unquoted strings. Maybe I'm missing the point list, but I kinda wouldn't expect it to be on the list.

Despite my love of yaml. I actually think he has a small point with unquoted strings. I teach students and see their struggles. Bash also does unquoted strings and basically all students go years and years without realizing

cat --help
cat "--help"
# ^ same thing

cat *
cat "*"
# ^ not same thing

cat $thing
cat "$thing"
# ^ similar but not the same 

To know the difference between special and normal-but-no-quotes you have to know literally every special symbol. And, for example, its rare to realize the -- in --help, isn't special at a language level, its only special at a convention level.

Same thing can happen in yaml files, but actually a little worse I'd say. In bash all the "special" things are at least symbols. But in yaml there are more special cases. Imagine editing this kind of a list:

js_keywords:
- if
- else
- while
- break
- continue
- import
- from
- default
- class
- const
- var
- let
- new
- async
- function
- undefined
- null
- true
- false
- Nan
- Infinity

Three of those are not strings. Syntax highlighting can help (which is why I don't think its a real issue). But still "why are three not strings? Well ... just because". AKA there isn't a syntax pattern, there's just a hardcoded list of names that need to be memorized. What is actually challeging is, unless students start with a proper yaml tutorial, or see examples of quotes in the config, its not obvious that quotes will solve the problem (students think "true" behaves like "\"true\""). So even when they see true is highlighted funny, they don't really know what to do about it. I've seem some try stuff like \true.

Still doesn't mean yaml is bad, every language has edge cases.