jankassens

For a long time, console.error had a stack trace in the Chrome devtools while console.warn didn't. I believe this was the main motivation to use console.error.

We've moved from runtime generation of queries to 100% of queries generated at compile time to remove a large chunk of computation out of runtime. Some APIs got more complicated to use than I'd like to. For example, pagination currently requires developers to write an explicit query to fetch more entries. Now with performance in good shape, I want to focus on improving the developer experience again in a way that doesn't sacrifice runtime speed. For example for pagination, we should in most cases be able to synthesize a query at compile time instead of asking for an explicit query.

Hey, Jan here together with Lee from the Relay team. Happy to answer your questions.

Hey, Jan here from the Relay team, happy to answer questions.

You can use `flow check`, but the server has the benefit of giving almost instant responses even on large code bases by only revalidating a subset of the project.

How would Uber find files on some employees personal device?

Crossing a red light is a pretty strong traffic violation in Germany. If the light was red for longer then 1 second apparently 200€, a 1 month driving suspension, and 2 out of 8 points to lose your license.

https://www.bussgeldkatalog.org/rote-ampel/

- Flow understands the semantics of it.

- The path can only be given as a static function literal and there is no function call overhead at runtime because of the bundled babel transform that transforms the code to a bunch of ternary operators.

I wouldn't be surprised if it's more accessible. I would think it has voice over like the iPhone which is supposedly one of the smart phones for visually impaired people.

Take an input that shows you the number of characters you typed or a form where the submit button is disabled until all required fields are filled in. These kinds of states might change on every keystroke and are not offered directly by a plain text input.

There are definitely Individual Contributors who are on the same compensation level as directors. These are the engineers who revolutionize how the company operates, such as inventing HHVM and saving tons of resources.

That's how I understand it. "fill my bag with juices" is not the same as taking a snack for later.

They're definitely doing research for efficient JS on low end devices:

- AOT compilation for a subset of JS: http://www.eecs.berkeley.edu/Pubs/TechRpts/2015/EECS-2015-13...

- "A JavaScript engine for Internet of Things": http://samsung.github.io/jerryscript/

They used to type in short (3 or 4 digits) codes for the products at Aldi in Germany maybe 10 years ago. I assume they did this because the scanner technology was not as fast. The cashiers memorized the codes and were crazy fast.

While I don't know the internals of different regex engines, anything that sounds so simple will probably be done by a good regex compiler/engine anyway. The simple | separated list of keywords seems a lot less error prone.

An 2009 article on the V8 blog about a regex optimization they did: http://blog.chromium.org/2009/02/irregexp-google-chromes-new...

There is a tag on some Github issues "good first bug" that should be a good start.

https://github.com/facebook/react/issues?q=is%3Aissue+is%3Ao...

I think a lot of the core folks also hang out on IRC at #reactjs on freenode.

Thanks for the report. spicyj created an issue to track this: https://github.com/facebook/react-devtools/issues/172

everkitten.com was a similar fake service. Subscription to have a jung kitten. https://web.archive.org/web/20140218072828/http://everkitten...

In this case it's enough to set the algorithm to "bi-directional". If one side is enclosed it will stop. This only breaks if both disjoint parts are infinite (for example, an infinite wall between start and end.

You could test for a single file (possible with a timeout) and see if it's "fast enough" to check all files.

You could also check in the background and update the display if the heuristic turned out wrong.

Store memberships for points and rebates on products are really common here in the US. When you sign up for them, they ask for your email, phone number, address, etc.

Safeway, a big supermarket chain, does this to an extreme. Many of their products are "50% off" when you enter your phone number of your membership on checkout. (It really just brings it down to a normal price).

Nothing prevents you from using a fake number, but as far as I can tell, most people give a real number.

It's certainly a different culture in Germany. Media and people are a lot more concerned collection of data.

They're already planning it: "Involve the user: Obtain user consent to trust service provider to decrypt select HTTPS"

Quote from someone working for a satellite internet provider for airlines.

Source: http://www.atis.org/openweballiance/docs/OWAKickoffSlides051... page 27

Advancements can be made in many different ways. If it's an advancement in polish, organization, and easy of use it looks like you'd agree it's the most advanced. It's probably not an advancement in customizability.

Press 'f' to hide the controls.

On a mac I use the `say` command.

    make && say "I'm done."

I also thought about mis-clicking. This could be solved with a small timeout (say 1 second) before the home button has the new behavior and brings you to the first screen.

You are actually kind of forced to think about it. If you want to 'follow' someone you can only do so by adding him to one or more of your circles. Of course, you can throw all people in the "Friends" circle, but I think given this visible choice not many will do that.

Different size (and color) make it way easier to distinguish the different bills – especially for blind people.

A related patent: sun-lit screens: http://www.crunchgear.com/2010/03/25/apple-patent-watch-sun-...

It's also in (and probably a copy of) the Jargon File: http://www.catb.org/jargon/html/A/ASCII.html