ef4

It's precisely because I have kids that I prioritize a walkable place. Because kids can't drive!

So in car-dependent places, they have no autonomy until they're nearly adults. I think it's much more healthy for them to slowly and steadily expand their autonomy, rather than a sudden discontinuous break when they learn to drive.

The same argument applies in reverse to old people too. In places with good transit and walkability they can stay independent and active longer, with no sudden loss of freedom when they can no longer safely drive vehicles at high speed.

Walking and transit are both overwhelmingly safer than cars (most things are).

When kids are small you just push them in a stroller. Once they're too big for a stroller, they're big enough to walk everywhere that you can walk. It's really not that complicated. Suburban kids who never walk anywhere may whine about needing to walk two miles, but my kids have been doing that since before they could walk unassisted, it's perfectly normal to them.

I do also have a Dutch-style cargo bike which we use a lot around our neighborhood. It's wonderful.

I think as you gain more experience and perspective you will look back and realize that you simply weren't upper middle class yet. It's not about income (which is just a point-in-time metric that can change in an instant), it's about assets.

Programmers have a much better shot at establishing this kind of security than most people, because you should be making 2x to 3x median income for your area, which means you can live on 1x median income and invest the rest.

A lot of the people I've worked with as a programmer over the past 14 years have done effectively that, so by now they have a lot of assets. That is what upper middle class security looks like.

What nobody told this unfortunate person is that working for a tech company is not the same as being a tech worker.

I'm not defending the two-tier system inside many tech companies, just pointing out that it's real and it's maintained by market forces bigger than any one company.

If a big Seattle software company lays off a team of programmers, recruiters are swarming around them by the end of the same day.

It's 100% open source, there's a very nice Docker-based install. You can host it yourself on AWS or Digital Ocean for very little money.

Make a free Mailgun account and put your credentials into the Discourse installer and delivery is free up to 10,000 messages.

Yours is a pretty weird description of the current real estate market here in Somerville.

It's a pretty even mix of owners and renters (about 40%/60% last I checked). Because of all the factors in the article, huge amounts of money are flowing in and they're being spent on upgrading the housing stock. Far from "shitty and falling apart", you see gleaming post-restoration projects everywhere, at astronomical prices.

Maybe I'm biased toward the west end of the city because I live there and the gentrification is furthest along here. But "it's extremely expensive" and "no one likes it" are really not compatible statements. The market remains extremely hot, and it's being fed by people with money who want to buy and live here, not absentee landlords. There are still some of those, but it's a shrinking group because the overwhelming financial incentive is to gut-renovate and sell as condos.

As for increasing the density, I'm all for it, but it's worth pointing out Somerville is already the densest city in New England. Denser than Boston proper, despite all Boston's own high rises. You don't find a denser city until you get to NYC. People underestimate how effectively you can pack a city even at three-to-five stories tall, if you actually stick to that height _everywhere_. We were lucky to be built in the streetcar era, and then ignored through the incredibly-dumb architectural trends of the second half of the 20th century. If the rest of Greater Boston was merely as dense as Somerville there would be no housing shortage.

My favorite strategy for getting higher density here is killing all the parking lots, along with simply getting our transit system back to the scope and quality it had in 1930, with streetcar lines all over the place.

Sure, but I think many programmers underestimate the investment value of that time.

Diving into codebases is a skill that gets stronger with use, such that you can eventually do it radically faster. That makes a much larger set of problems economically practical to fix.

You're basically describing asm.js -- a subset of javascript that is known to be easy for engines to turn directly into native code and execute, that you can use as a compilation target.

The difference between asm.js and WASM is mostly just that WASM is more compact and easier to parse, while asm.js is a more gradually compatible upgrade story.

The problem with this kind of deep dive optimization is the cost of maintaining it in a long-lived project as the underlying javascript engines keep changing. What was optimal for one version of V8 can actually be detrimental in another version, or in another browser.

It's precisely the unpredictability of JIT-driven optimizations that makes WASM so appealing. You can do all your optimizing once at build time and get consistent performance every time it runs.

It's not that plain Javascript can't be as fast -- it's that plain Javascript has high variance, and maintaining engine-internals-aware optimization in a big team with a long-lived app is impractical.

If you are running your own webserver even a static simple site has required maintenance. You need to keep the server and OS patched. So adding a letsencrypt cron job is not any worse than configuring something like Debian's unattended-upgrades.

But I don't think most site owners should be doing even that much. They should just pay for static hosting, which is cheap and ensures somebody else will keep the server, os, and cert all safe.

There is a saving grace here, which is that almost nobody who would ship a new grid-based design today is shipping only one layout. They're shipping a family of layouts for different devices.

And once you have a family of layouts, it's not a big deal to add one more layout that covers non-grid-capable browsers.

The design choice that makes this all tenable is to accept that the site isn't supposed to look identical across every browser. You're accepting that you'll do progressive enhancement of layout. Old browsers still get all the content, they will just get it in a more boring format (like all stacked into a single column).

They save people from serious injury much more frequently than that. Extreme turbulence that can smash you against the ceiling happens not infrequently.

> Getting off GMail is one of the best ways to take back your data in the face of dragnet surveillance.

This just isn't true. You can host your own mail server and GMail will probably still end up hosting a large fraction of the email you read and write, because the people you correspond with are still using GMail.

(In the same vein, you can refuse to have a Facebook account but Facebook probably has a dossier on you anyway. Enough people you know have dumped their contacts into Facebook that they already know your place in the social graph.)

They take HIPAA seriously (because there are fines), but that is definitely not the same thing as taking security seriously.