davej

Presumably because most of the commands are just shortcuts for other shell commands. Probably the right tool for the job in this case.

I suspect there's a perf bug in React 15 that causes the 'clear rows' test to be an order of magnitude slower than react 0.14. Otherwise, React is getting faster.

edit: My hunch was correct, see here https://github.com/facebook/react/issues/7227

It's required because Elon Musk is already a significant stockholder in SolarCity.

Tesla tried this and it didn't seem very popular (albeit low sample size): http://fortune.com/2015/06/10/teslas-battery-swap-is-dead/

I'm confused by this comment. This app does not seem to be built using Electron. Nobody has contradicted you so maybe I'm missing something here.

This isn't correct, `users` would be undefined.

> Not enabling pipelining was used as a political tool to prevent HTTP 1.1 from being on par performance-wise with the new protocol people wanted for other reasons

I'm curious, what are the politics behind this? What are the 'other reasons'?

To get an idea of the kind of stuff Palantir do then it's worth taking a look at the presentation that was leaked during the HBGary leaks: http://www.businessinsider.com/palantir-wikileaks-2011-2?IR=...

Nitpick, Electron is Node + Chromium (not webkit).

> Any idea how V8 releases relate to Node (especially now post-io.js)? When could we see these improvements on the server?

April and October are the planned release months for a new major node version AFAIK. The April releases then become LTS releases in October. October releases don't become LTS.

Presumably new major node versions will be cut from the latest stable (or perhaps stable - 1, depending on timing) V8 release.

Might be wrong about this, so I'm open to correction.

This! Especially with the web being increasingly consumed on low-powered mobile devices.

It's also not just about being faster than the network because the browser is probably simultaneously doing page layout, javascript parsing, image decompression and a ton of other things. Also more time spent decoding images is a drain on the battery.

Focusing solely on compression stats can be misleading, it's a balancing act. For example, I'm not sure being 0.7x smaller than PNG is much of a win if FLIF ends up being an order of magnitude slower. Perhaps it is still a win but it needs a bit more nuance in the analysis to reach that conclusion.

This comes up quite often, here are two helpful links:

http://ramiro.org/vis/hn-most-linked-books/

http://www.hnreads.com/

Either is Electron.

Also, the free "Getting Started with Redux" video course: https://egghead.io/series/getting-started-with-redux

The approach taken in the videos is great because it starts off with implementing your own simplified version of Redux and builds on that. There are no "magic" steps, this makes it much easier to develop an understanding of how it works.

Worth considering the es2015-node5 preset instead. It will only transpile the features that are not already in node 5.x. The standard es2015 preset transpiles lots of APIs that are already natively available in node 5.

I'm using this: https://github.com/chentsulin/electron-react-boilerplate

I find it excellent.

I'm sure the reason npm3 is slow(er) is primarily because it's doing important stuff.

However, having played with `ied`, it does flat deps and it's literally an order of magnitude faster (10-20x in my testing). I use npm a lot every day and npm's slowness is becoming a significant UX issue for me. I would like to continue using npm but right now I would switch if either `ied` or `pnpm` had decent feature parity with `npm install`.

The semantics are the same (with a couple of minor exceptions) as Javascript so it's just sugar really. I found it very easy to reason about, it often comes down to whether or not you are comfortable with reading significant whitespace.

I liked CoffeeScript but haven't used it in years. IMO CoffeeScript is probably a bad choice for a modern dev environment.

Not sure it was meant literally. I took it as more of a jibe at the quality of existing space companies (and Blue Origin).

That's a bigger phone than the Xperia Z3 Compact that I currently have.

Yeah, that's cool too. I guess we just have different use cases.

I'm an average sized male (5'11") with average sized hands.

Even if you have large hands it's difficult to use modern phones one-handed. Try reaching the top left/right corner of your phone (one-handed) without having to adjust your hand position.

I feel like phones are slightly larger than optimum at the moment. At least for my preferences. I guess it's tougher to fit high spec hardware into a phone with a smaller footprint.

I bought into Steve Jobs' idea phones should be usable one-handed. I think the sweet-spot for that is 4 inches or less. A premium phone at these dimensions doesn't exist anymore, the last one was probably the iPhone 5S.

I went from iPhone 3GS -> iPhone 5 -> Sony Xperia Z3 Compact and honestly the Z3 Compact is larger than I would like (4.6" screen). I'm honestly considering getting a 5S for my next phone because I don't want a phone as big as the iPhone 6.

I noticed recently that the One Plus 2 Mini is going to have a 5" screen, that seems insane for a "mini" phone.

Yeah, considering switching to Netflix US + VPN. Only decent content here (Ireland) is the Netflix Originals stuff.

Two years is a lifetime in tech. This isn't a mainline consumer product even though they may market it as such. A few hardcore gamers and VR enthusiasts will buy this, slightly more will get to experience this through a friend who has purchased it. It will churn away and people who can't quite justify shelling out the cash will still be excited by the experience. By the time v2 comes around, the price point will be much more acceptable. I would expect that by v3 it will be mainstream.

I wouldn't be surprised if we saw yearly iterations of the Rift for the first few versions. Ultimately I think this tech has to be paired with a console rather than a PC for widespread adoption.

I'm previously a Djangonaut too but recently I've been exclusively JS. I spent a few hours playing with this yesterday and I really like it.

It was pleasing (and a little surprising) that everything was almost exactly how I expected it to be. I watched the video, got started and rarely needed to go back to the API docs. It actually feels very light and natural despite the fact that it's already quite fully featured.

The author is simply highlighting the disconnect between critics ratings and audience ratings for Netflix shows.

Yeah my rMBP uses an embedded Intel graphics card. The performance is horrible, ~2 fps, tried FF and Chrome.

It's very laggy and slow on a quad i7 16GB Macbook Pro. Presumably this is because of the retina display.

Why particularly with Electron?