203 karma · joined June 5, 2017
One benefit of this, like you say, is you develop a general disgust for sweets and have no interest in them outside of training.
At any rate when they shout at you, roll coal, swerve to force you off the road their intentions are clearly not good.
It’s obvious in hindsight, but looking back there are plenty of thinkers that i look up to (e.g. Du Bois) that supported the regime far longer than is comfortable (so i’m hesitant to say i would have been any different at the time).
That said, it's not obvious that the underlying data model needs or should map to a theoretical model for how human cognition works. Maybe it should and it's worth considering the theoretical landscape before setting out, but there are other features that come into play.
I know very little about library science, but I assume they take a more practical (for this task) approach to this that's worth looking into.
Which is not to say smashing windows is a good move. Though I would also contest that drivers breaking the law to endanger cyclists also don't make up the 'general public'. If they were not a small minority I would never ride my bike outside.
However, I've been using the above mentioned laminar for my personal frontend project needs and it really is a unique approach to the 'reactive' frontend with no vdom actually using reactive streams to track what needs to be updated. The dsl is easy to read and write and i can actually read the underlying code. For me it's scaled well too large datasets generating svgs. I think it's worth the scala.js barrier to entry.
I looked at a few dozen cbsa metro areas, big cities, small cities, east, west, middle and the only 3 i could find with more people traveling 10-24 miles than <10 miles were Houston (34/36), Dallas (34/37), and Atlanta (34/38) so even in the worst case ~⅓ of commuters are doing less than 10 miles.
I couldn't figure out how to query this data via an api, but I did find a paper that looked at the 96 largest metros, which showed that Houston, Dallas, and Atlanta had the highest median between 12.2 and 12.8 miles. So I think that a 20 mile average is likely not true anywhere, though double digit over 50 miles does occur in all three of the above cities. Most cities have plenty of people commuting across the spectrum, though some are significantly denser than others (up to ~45% for <10).
Now looking at the per mode data, 10 miles is still on the long side for a bike commute. There is a steep drop off in people cycling/motorcycling to work (for some reason combined in the dataset) at the 30 minute mark. 20mph is fast even with a e-bike assist, probably somewhere around <2-6 miles would be the ideal probably.
I do agree with you that most people aren't going to start using bike lanes if that means a worse commute. I used to, but I cycle for sport and would do those hours anyways (now my bike commute is faster than train or car). Most Dutch people don't bike commute for fitness or sport or fun, they do it because it's the most efficient way for them to make their daily trips. Part of this is because of the density of that country and part of that is the infrastructure.
On page 10 in the pdf you can see the vehicles and animals compared.
I also question whether you really bought a horse in this analogy.
All of this to avoid spinning up an SQS queue?
Though if we want to make the clear distinction, like in the Clojure talk below, for the programming domain that’s fine.
You say the same request has a different impact on the system, but what that means is the system converges to the requested state.
Maybe this is overkill if your retry strategy is to have a user in the loop, but I don't see how it's simpler for the client even without any retry behavior (if/else new/reuse uuid vs if/else put/post).
I get that this is early days for this project, but the issues are general for all of these non-browser, non-native UI toolkits. Hopefully we get there though.