HN user

sscotth

93 karma

[ my public key: https://keybase.io/sscotth; my proof: https://keybase.io/sscotth/sigs/fJ4RYSQIytxTVFg6yKE24R4fDvfeevUf8thZU4jsbeQ ]

Posts1
Comments41
View on HN

That's $70/month for 2014 hardware (dual core no ssd), or $120 if you need a quad core or ssd. Prices for the new hardware haven't yet been announced.

Either way, if they keep their same pricing, there's a 12 month break even of buying your own hardware if you don't need to be on a data center backbone.

I agree. It won't become mainstream until the next gen of consoles are able to take advantage, because developers will still be required handle the current generation. However, the demand from from developers themselves could be enough for console manufacturers to make sure it is available in their next iteration.

Where have you seen that next gen consoles are confirmed for AMD?

Also, if there is Nvidia tech here that AMD can't replicate, it doesn't mean that AMD can't license it.

Being able to fold your laptop into a tablet does not classify it as a "small Personal Electronic Device" according to the FAA. It is determined by weight/size. Anything under 2 lbs is considered a PED and is allowed for use during all phases of flight. The Surface Book is too heavy and would not qualify.

Although, flight attendants aren't walking around with scales checking and it certainly looks less conspicuous in folded mode. But, I've successfully used my 4 lb 15" Retina MBP during take off/landing many times without issue. YMMV

http://www.cnn.com/2013/11/07/travel/faa-airplane-electronic...

https://www.faa.gov/other_visit/aviation_industry/airline_op...

Larger PEDs are those the operator has determined weigh more than 2 pounds or are of a size that would impede egress

Its also important to consider the environment as well since JSX is potentially much bigger than the web.

JSX is much like other generic user interface markup languages[0] and like many other is simply a dialect of XML. Any interface that can be represented with XML/HTML or any other markup language can use JSX and optionally react. We are already seeing this boom with in native mobile environments with React Native, NativeScript, Titanium...

Here are several examples where JSX is used that is not a browser:

- Native desktop apps for Linux, Mac, and Windows (Not including Electron/NW.js)[1][2][3][4]

- TVs with AppleTV apps or Netflix's Gibbon[5][6]

- Command line apps as stdin/stdout with react-blessed[7]/mylittledom[8]

- Direct to Canvas[9]/pixi.js[10]

- Latex documents[11]

- Web Audio[12]

- Conole.logs[13]

- Truly custom direct to hardware[14] as some C code like: `digitalWrite(led, HIGH)`

I definitely believe JSX could use standardization separate from any implementation, JavaScript or otherwise.

[0] https://en.wikipedia.org/wiki/User_interface_markup_language

[1] https://github.com/sidorares/react-x11

[2] https://github.com/grassator/react-qml

[3] https://github.com/ptmt/react-native-macos

[4] https://github.com/Microsoft/react-native-windows

[5] https://github.com/ramitos/react-tvml

[6] https://www.youtube.com/watch?v=eNC0mRYGWgc

[7] https://github.com/Yomguithereal/react-blessed

[8] https://github.com/manaflair/mylittledom

[9] https://github.com/Flipboard/react-canvas

[10] https://github.com/Izzimach/react-pixi

[11] https://github.com/vzaccaria/jsx-latex

[12] https://github.com/FormidableLabs/react-music

[13] https://github.com/mohebifar/konsul

[14] https://github.com/iamdustan/react-hardware

Not yet particularly, but the goal will only make Node better and less coupled to V8.

With a runtime agnostic Node, different vms would certainly have differing esnext features but may also be optimized for specific platforms or use cases.

He did say to "try" it, you can use a flag. You should assume that any feature behind a flag should never be used in production.

Also, Node v7 will likely get a semver-minor update with V8 55. So, simply waiting for v7.3 or v7.4 should be sufficient and it will be enabled by default.

https://github.com/nodejs/node/pull/9618#issuecomment-264641...

Those who are sticking with the LTS release for production will need to wait until April/May 2017. March is overly optimistic by the OP as the currently scheduled date is 2017-04-30.

https://github.com/nodejs/LTS

Node.js v7.0.0 10 years ago

Correct. async/await was first introduced V8 v5.2 but put behind an testing flag. Node.js v7 includes the latest stable version of V8 (v5.4) which was promoted two weeks ago but still has it behind a flag. The current beta version of V8 (v5.5) now has async/await enabled by default. Shortly after V8 v5.5 goes stable, in about 4 weeks, Node.js will update to include it. However, it will most likely be only updated on the v7 branch and not the v6 LTS branch.

Also of note, chakra still has async/await behind a flag as well.