Rygu

Very cool. It does remind me of the incredibly useful Peek functionality on iPhone 6S when you 3D Touch an item on screen. Have you considered rebranding as GitHub Peek? :)

What do you rnean?

Slightly off-topic, but I wouldn't worry. Nowadays hypervisors can boot up complete OSes in ~800ms.

https://insights.ubuntu.com/2015/05/18/lxd-crushes-kvm-in-de...

It would be a really philanthropic thing to do. I like your way of thinking.

And now Arment has killed the messenger but still spreads the message.

Seems that screen/window resolution is an important factor.

Love how the video starts with "Meeting? OK give me 5 minutes" and then shows how quick it is to create a prototype that even runs on hardware.

Most of the time that's true. Though I've seen some open source software projects being put on Kickstarter, and every one of them ends in disappointment. Either too low pace, or half of the promised features are cut. (Some joke about software estimates.) It's impossible to complimentary increase or rightfully decrease your contribution depending on performance it's one-off funding.

Patreon is an incredible crowdfunding platform. "Continuous Funding" is how I'd like to call it.

Continuous Funding solves the problem many high-value funded Kickstarter/Indiegogo projects have: not being able to deliver at a constant pace. It's one thing to write a business proposal to raise funding with excitement. Another to settle down and budgetize the money to prevent burning through it too fast or investing it too slow, meanwhile not being able to focus on the product.

Some programmers may not immediately see the benefits of having such a UI builder and would never touch the generated code with a ten foot pole.

However I don't think that it's about the code it generates or boilerplate it proposedly saves you from writing. It's way more about the instant feedback and feel you get when dragging UI elements into the canvas, re-arranging them, finding creative ways to (re)structure your app BEFORE you even start coding. This playground will strengthen the concept of the UI in your head, and believe it or not, that greatly enhances your productivity when you do start to code (from scratch or with the generated code).

And if you like Dan's talk, check out his blog post My Inspiration to get some more background on the topic. https://medium.com/@dan_abramov/my-inspiration-ce454ab65f33

BTW vjeux, great job at React Europe!

If you're using webpack (who isn't?) then you can add .jsx to the known and attempted extensions. Although I prefer .js as well because there's eventually there's no reason to structure your JS codebase on extension-level. Better do it at the directory-level.

To illustrate this point, React min+gzip is about 40 KB: https://cdnjs.cloudflare.com/ajax/libs/react/0.13.3/react.mi... not 121 KB.

It doesn't seem to compare the minified + gzipped library sizes. That's the most important metric to me. Who still serves comments in JS?

I see an iframe on the page. Right now.

Ugh, what people will do for job security.

Seriously, they don't have to. That kind of timeout makes the DOM element irrelevant.

Lack of types != lack of validation. No Python rule says you may leave out the latter. Same goes for any typeless language.

Agree, they aren't the same type to begin with.

> in_array(.., .., $strict)

I think you're aware of the third parameter but for anyone who reads this post, it disables the type coercion of the in_array call.

> The Graph panel now supports 3 logarithmic scales, log base 10, log base 32, log base 1024. Logarithmic y-axis scales are very useful when rendering many series of different order of magnitude on the same scale (eg. latency, network traffic, and storage)

Have been waiting eagerly for logarithmic scale support.

Version control for everyone.

"Change Epicenter for Mac. Never lose a file, ever again."

Depends on the backend platform actually. Apache CGI processes (PHP) are fire-and-forget per request. But for example Ruby and Node.js servers persist through request cycles. It's important that any state is unique to the request, sometimes even the caches should be per request.

Node.js has a package called piping that hot-reloads require()ed files. It makes interactive development possible. Checkout my backend and frontend interactive isomorphic starterkit: https://github.com/RickWong/react-isomorphic-starterkit It hot-reloads Node server code and client code your browser.

For people who want to find out how their components can be hooked up to Relay, checkout React Transmit: https://github.com/RickWong/react-transmit

It's basically Relay but using more powerful and generic Promises instead of GraphQL.

Yeah, that's the reason why they tried React I guess. But as far as I can tell they kept the should-update-or-not procedures they implemented specifically FOR React. So what they removed wasn't the concept of React, just the library as their DOM rendering implementation.

Want to use out Relay ahead of the official release? See React Transmit: https://github.com/RickWong/react-transmit

It's basically Relay but using Promises instead of GraphQL to write queries. Transmit is coincidentally also a very efficient way to create isomorphic apps that can render on the server.

Someone wrote a GraphQL query parser. https://github.com/madjam002/graphqlite There aren't any GraphQL servers yet though. Pretty hard to write too in a generic useful-for-all manner.

They never really needed React in the first place, because React doesn't solve THEIR problem. Their problem is so specific to text editors: how do you get hundreds of lines of hundreds of rich-text characters to render as fast as possible?

In terms of game engines: React is comparable to the occlusion culling capabilities of a 3D game engine (render less), where Atom was in search of the fastest way for the graphics engine to push triangles to the GPU (render fast). Ultimately I believe a mix of both is the best.

Fact: he is already convinced that he's better off, because he is. Read his post again.

IMHO these aren't "mental tricks" but valid suggestions for him to find closure to something from the past that he really shouldn't consider important anymore. Finding peace is good.

Thanks. Went for `undefined` because it's for query string building, where `null` still is a valid key-value combination.