nawitus

The parent made the claim that it's hard to buy a car and expect it to last more than 5 years, which is clearly wrong.

> This includes cars

Plenty of manufacturers give a 7 year warranty for new cars. In addition, there's no sign that new cars depreciate faster than older cars (when comparing current depreciation for historic depreciation). In markets where cars are driven for many, many years and kilometers (e.g. Finland), there's no evidence that new cars shouldn't be expected to last more than 5 years.

You should compare the monthly price to leasing, which is around $250/month for a decent new car. Using your "other costs" the total goes up to $330/month. (However, I think the other costs would be higher).

They can go up to $130k, but that's due to supply and demand, not construction costs.

The space of possibility within the confines of law is very large.

Renault Zoe has a 400 km range model for €23,600 (in France). They compare to Model 3 in some aspects and not in others. I can of course claim that Tesla doesn't have any experience in producing affordable electric cars.

>All this demand could be met by other car manufacturers if they too produced long range EVs of similar or better quality than combustion engine cars. But no-one does and no-one will for an other year. Don't say Nissan Leaf; it's not long range

For comparison, the Renault Zoe and Chevrolet Bolt EV have a higher range than the standard Model 3. Both of them have also sold more than the Model 3 so far and have a lower price. These cars are in a different class than the Model 3, but it seems that traditional manufacturers won't have any trouble producing long range electric cars.

There's the problem with the sample size, but Twitter for example outsourced some early development to Eastern Europe.

You can sell gradually.

What evidence exactly are you looking for? If you compare two different cities with different housing densities, you're not only changing the housing density but (likely) also the value of the housing (since it increases availability of services and so on). It's not possible to magically adjust one variable while not touching the others.

However, if the prices in silicon valley were, say, 30% lower than they are now due to zoning which allowed more housing, would that constitute as evidence? You could still say that the "prices are high, higher density housing doesn't work!" - even if the higher density housing would've decreased prices by non-trivial amounts.

In any case, it's weird to see people objecting to basic supply and demand when it comes to housing.

A land value tax is not even needed if land-use planning and related regulation would be relaxed.

It seems that almost everywhere supply of housing is being artifically restricted leading to rising prices. This is also unsurprising. Housing is the biggest investment most people have, so people prefer policies that keep housing prices to be ever increasing.

Sometimes it sort of reminds me of "bitcoin for old people". Why invent new things when you can get decent returns on housing? Of course until the bubble bursts. But if that happens the government tends to intervene to a degree, not so for crypto bubbles.

The types will make reading the code multiple times easier when someone else reads the code. Or when you go back to the code six months later.

>They should be comparing the Model 3 to high end luxury combustion vehicles because from my vantage point you're getting that kind of driving experience, better even, for half the price.

The Model 3 can't compare to high end luxury combustion vehicles.

There's still communities for niches. Subreddits, Facebook groups, forums, Slack instances etc.

"The emerging knowledge economy, Mr. Moretti argues, depends on constant innovation, which turns out to be a social process."

Why can't this happen online?

Well, that's why I work with full-stack developers who can do both changes at the same time.

Why is returning say the three top comments not RESTful?

>I suppose you could hack something like that with REST but it would be difficult.

Not really. You can design specific REST endpoints to return the data in the format you want.

How is it cumbersome and heavyweight? If the app is already using AWS, it's trivial to start using the parameter store.

However, GDPR is a regulation, not a directive. I haven't seen that countries pass their own implementation of it.

Well, I personally don't like laws to be vague.

GDPR was announced years ago, but this pratical guide was authored a few months ago. EU should have released an official guide two years ago.

a) The problem with this is that this practical guide was released in November 29, 2017. And this is unofficial. EU should have released a practical guide two years ago in my opinion.

If the process is gradual the law should reflect that.

c) Good to hear :). Apparently it's this: https://ico.org.uk/for-organisations/guide-to-the-general-da... - I hope it's not written from the perspective of the UK legislation.

d) The law should clearly define what is required for smaller companies and what is not. There's some disagreement if this is the case in GDPR articles too.

GDPR will go into effect this month.

EDIT: My mistake, in May

There's plenty of alternatives. The main problem with GDPR is not the goal of advocating privacy but the details. I would have done it like this:

a) bring out regulation gradually instead of in a single big change like GDPR to have companies time to comply

b) don't write vague laws

c) give specific examples of what GDPR means in practice

d) be more lenient on smaller companies

This is the biggest problem with GDPR, there's no agreement what it means, but it will go into effect in a few weeks.

> I think all of the above features can be implemented in a few weeks by a small team.

That's.. optimistic in the enterprise world.

You need power for acceleration, not torque. (But I agree that modern diesel cars accelerate fast enough).

Not true in Finland.