skysight-inc/HackerNews huggingface dataset:
Uber is great, but the biggest cost is that you need to pay for the services of someone driving for you. I live in Montreal and regularly use http://communauto.com/ They have two services, 1) for ~$2,50/hour + $0,10/km, where you need to make a reservation, you get the car from one specific parking lot and have to return it there. It's useful only if you plan in advance, if you haven't reserved a car for the weekend by Wednesday forget about it.

The 2) service though you just swipe your metro card on the panel for an auto-mobile car parked somewhere, drive for $0,30/minute and leave the car anywhere (in some very big zones in the cities). It's exactly like https://www.car2go.com/ except their auto-mobile vehicles (hybrids and electrics) have backseat, so we can go around with kids (whereas you can't with a Smart).

I commute by bicycle to work, so we use this only on the weekends. It takes around $7 to go from our place to the center, while public transport would be $5, so it's really great for the convenience and speed.

By far it really beats owning a car in Montreal in cost and convenience. Parking space is limited and very expensive ($8 for 2 hours in city center). If you have a car you have also to keep changing parking even if you don't use it because there are very few buildings with garage and they clean the streets at least once or twice a week for the entire year. I've been car-free for over 20 years, it's a huge relief to not have to worry about taxes, maintenance, robbery, etc etc that comes with the responsibility of owning a car.

Come self-driving cars, we might have only some very few people that will keep owning their own vehicles due to some nostalgia feeling.
While I agree in principle, in practice this idea sounds like a security and authentication nightmare.
Any site that uses Persona could be used anonymously through a trusted identity provider that generates on-demand, expiring email addresses.

(sans traffic monitoring ofc)
They do a particularly weird instrument called a "charge card." It's not a debit card because it's not pulling straight from a checking account, but there's no long-term line of credit either. It's like a credit card that you're actually required to pay in full every month. So no different from responsible credit card use, but still not credit.
neo-luddites perhaps, when I was an active cyclist a bit more than a decade ago the fixie was an unknown thing. There were single speed bikes then - the well known beach cruiser - it was a single speed, yes, but it also could idle along without peddling and had a rear drum brake - I can see a place for that kind of thing - no one has been able to explain to me how a direct drive fixed gear bicycle is better than even that option.
> A person smart enough to be a doctor could be many things and earn a lot more money doing one of those things.

Is that really true? Doctors are most of the best-paying jobs in the US [0] It seems to me that if you're bright, and care about making a lot of money, medicine is absolutely the way to go. Yes, there are some people who strike it rich with startups or high finance, but that's essentially buying a lotto ticket.

[0]: http://www.bls.gov/oes/current/oes_nat.htm#00-0000 (sort by annual mean wage, Anesthesiologists, Surgeons, Oral and Maxillofacial Surgeons, etc.)
Regarding applications to modern software engineering, this parable is basically about operations surrounding architectures that promote long-lived processes and rare reboots (VAX) vs. ones that promote quickly-spawned, ephemeral processes and which rely on reboots for cleanup (Unix).

The modern comparison I would make is between the design of scale-neutral twelve-factor apps in language-platforms made for quickly spawning ephemeral processes ("scripting" languages like PHP, Ruby, Node, Lua, or even—in practice—Go)† and the design of "living system" VMs—and languages thereupon—that load and unload modules over time without shutting down (JVM app servers, Erlang, etc.)

It's okay to effectively "reboot" your Heroku instances to get them into a sane state. Not so with your databases, stateful load balancers, or VoIP servers. They come from two different worlds: one eschews state, while the other owns and manages it.

† Notice how all these languages are effectively wrappers around the same paradigm. There's a strong sense in which a "scripting" language is just a language that models the world in the Unixine fashion, such that it can be used to glue other Unixine programs together.
Smaller: Not really. You just avoid some K of helper code already build (by the React team). Your code will end up being more than the one you'd have written on top of React -- because it will also have to reimplement and handle all common cases (either poorly, or time-consumingly).

Faster: could be, could be not. Without profiling this is an empty statement. Besides, "premature optimization is the root of all evil".

Simpler: Noope. You have to manually track all the interactions, and you strongly couple things together with your "OO and functions" idea. It might be simpler to just churn out code initially (instead of understanding an architecture), but it becomes an ad-hoc mess soon.

Let me put it this way: it's not like you have discovered a novel way of building stuff compared to these coders that overcomplicate things. What you propose is what these engineers have already tried, used for a decade or so, and found unscalable and wanting.

It can work for small and not complicated pages, but it's not a solution to modern single page web apps.

You might think that you are proposing a clear and simple way of coding as opposed to something like overengineered J2EE patterns mess.

But what you describe is more like the "Why use procedural code etc, GOTOs for flow are simpler and faster", or "why use functional programming, imperative is simpler and faster".
Fellowship income (for example from the STEM fellowships) is not reported as earned income for sure. It's less clear for other positions. Consider this from IRS publication 970:

“Scholarship and fellowship payments are compensation for IRA purposes only if shown in box 1 of Form W-2.”
LA is also a very bipolar town, car-wise. If you have a 5+ mile commute, it's going to be way worse than the same distance in most US cities, because of the traffic. But the flip side is that there is far more density to the LA suburbs than most anywhere else in the country—it's hard to even use the same word to describe suburban LA (7K/sqmile average for the whole urbanized area per Wikipedia, with parts significantly higher) as, say, suburban DFW, where the population density is half that for Dallas proper alone, let alone all the suburbs.

So if you live near where you work, you can bike or walk or bus and there's a decent chance you'll be in walking or biking distance of some shops and restaurants as well. And then the occasional Uber or cab for longer trips (or just bumming off of friends who have cars) is extremely practical.

But if you don't telecommute, being able to live near where you work is something that's a lot easier for those without a family. And then those Ubers would add up fast!

(The other thing I've anecdotally noticed since moving to LA, is that the willingness to sit in traffic for an hour each way to commute seems way higher in LA natives than in transplants—and the reverse is true of the willingness to pay the premium to live close to work and avoid that.)
Rescuing Science from the Military  with Comics?
Although there are some really impressive innovators on that list, I have hard time taking serious a list of young innovators that includes no representative of perhaps the most disruptive and innovative technology of the past several years: the blockchain.

Indeed, there were not even any P2P innovators present at all in that group, despite many, many worthy candidates.

Guess those innovators are just politically too hot.