gonyea

Google Maps has a show speed limit toggle, behind a setting.

Why couldn’t they? No/little international pressure to do otherwise and a currency printing press to subsidize back room deals.

This is a great strategy for China and it’s utterly insane that we allow this situation to continue.

Yet another company driven out of China by government-industry collusion.

Let them build. My only opposition is stopping at 6-stories. Populations go up and so should our housing.

On the flip side, attempting to evade situations can cause greater catastrophe. I’d rather they wire up the horn and call it done.

2fa would have protected him.

> it's fundamentally anti-user

I don’t get this sentiment at all. The vast majority of users don’t know what root access is, let alone care about it.

It lets me defer the inevitable Chrome Tab Bankruptcy. But seriously, having a heavy build system with lots of dependencies will easily max out a desktop like this.

Are you kidding? Spying to see if they're violating trade embargoes == Systemic, blatant IP theft from westerners--aided at all levels of the Chinese government and industries?

Heh, you're using a throw away account just to go full whataboutism on this comment thread. So brave.

Are Wumao into Hacker News now?

Obviously the FBI and the Chinese Government are equally untrustworthy. Who can truly say that one is worse than the other? /s

Give your data/source to a domestic competitor? Because they would absolutely do that.

Be less naive when it comes to China.

Azure in Hong Kong is quite zippy. Even in the depths of inner-China. I was very impressed... and I'd rather host my stuff with Microsoft.

I doubt Alibaba would ever care about protecting your data.

I'm not sure Rural and Vegan intersect much. Doubtful this Is the source issue.

I'd wager a sedentary lifestyle and stimulants are a major culprit.

The trick isn't to interview well. It helps! But the trick is to have a great referral into the companies.

No, you need to delete the .git folder from your server entirely. Ideally, delete it before you deploy. In fact, don't even put a github deploy key on the server. Deploy binaries.

And don't just stop with .git: Delete any folder/file that's not required to operate the app in production.

Redis is great when used as a persistent cache for short-lived + no value data, or data that can be reproduced from another source. If your data, or queued items, have value then find a better tool.

But if you're foolish enough to use it as a database... lol.

Redis vs. MongoDB, seriously? Up next: choosing to die via hornets or scorpions.

What an awful article. Good to know putting Verilog on your resume is a Most Wanted thing! You can put it to use by becoming an intern /after/ you graduate with a CS degree.

That's just awful marketing. Time to get Bourdain on video eating Chilean Scallops.

What. I've seen issues with Homebrew at every company/team I've worked with since it came out. The solution is always the same: Use vagrant and chef/puppet for your development environment.

Meanwhile, apt packages are incredibly stable, install the same way every time, and are exactly what you'd run on the server anyway. You can use PPAs if you need bleeding edge versions.

Have a MacBook Pro on the side because time is expensive and you need a laptop anyway.

Install a modern Bash and set it as your default shell. When Homebrew updates (which it does automatically now) you might be locked out of your Terminal.

`brew --prefix package` returns the latest installable package, and not the version you actually have installed.

Also things like: https://github.com/Homebrew/brew/issues/2402

It tries to do too much and ends up being a never ending surprise from hell.

(The solution to the Bash issue is to hard code the path for chsh, etc.)

I've been using a Linux workstation for the past year and actually feel like I could go with a Linux laptop too. I was contemplating Hackintosh but no need. I only miss the Magic Trackpad.

Atom + Chrome (with a dozen extensions) makes web development a breeze. I can do a lot of quality front-end work.

You're also not stuck with god awful Homebrew for installing dependencies. OS X is a pretty hostile place for developers who don't live out of XCode.

I can vouch for Spanner: it's a badass piece of Google's infrastructure.

Why I have no money

> I don’t know why I purchased it.

Well, guess my adblocker isn't going to help him make rent either.

That's a great problem to have.

Pro: Can't make hot cakes fast enough.

Con: I wish I could switch ovens; a white one matches my kitchen's decor.

But how will this fit in with their lineup of "things that explode"?

I'm honestly not so sure I'd accept it as the "fastest rendering library" for a variety of reasons:

- micro-benchmarks are really good at telling you the story you want to hear.

- profiling erector revealed that it placed a lot of pressure on the garbage collector. This was back when it too was the "fastest templating library." Micro-benchmarks won't really tell that story.

Other issues:

- blocks are a good abstraction until they aren't. No doubt backtraces are better than with erector. This was seriously traumatic to debug, templates were a gigantic ball of mud.

- "_I_ don't need caching" isn't a counter-argument. The reality of using blocks to nest elements is that the boundary between "cacheable, static content" and "dynamic stuff" is indistinguishable.

It's not like caching is turned off in erector (or fortitude). People were constantly making changes to templates, shipping them, and having changes not show up because memcache isn't running in development.

You COULD try to argue that it's the same problem in erb or slim, except it mostly isn't. When ALL your code is ruby code, seeing the "cache below this line" is a lot harder.

Oh sweet jesus. This is erector all over again.

The code inside the blocks are uncacheable; it's an expensive novelty. Plus these abstractions always break down. Our job is to build products that meet people's needs. Not to contort solutions into our preferred form, at the expense of the product.

Yes, I did. There's a lot of people who will ignore his caveat and try to use these optimizations where they don't belong.

I see it a lot and it's painful. Hence the "throw it out the window" advocacy.