Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

React v15.5.0

facebook.github.io

Post reply on HN
Print view View original

161–170 of 209 posts

Re: React v15.5.0

#161

Post by [deleted] »

DenisM wrote: post #160
bpicolo wrote: post #156

Earlier quoted context omitted.

https://code.facebook.com/pages/850928938376556 It's purely defensive, they'll only revoke your license if you sue them for patent infringement. And they only revoke the patent-grant of React as far as I can tell, not your license to use it (and there aren't any patents related to React as far as the internet claims).

Which in turn means they can infringe on any of your patents with no consequences. If they do, your only choice is to rewrite your entire application in a hurry, and only then you can sue them.

[deleted]

Re: React v15.5.0

#162

Post by markc »

STRML wrote: post #26
acemarke wrote: post #11

For those who are interested in some of the details of the work that's going on, Lin Clark's recent talk on "A Cartoon Intro to Fiber" at ReactConf 2017 is excellent [0]. There's a number of other existing writeups and resources on how Fiber works [1] as well. The roadmap for 15.5 and 16.0 migration is at [2], and the follow-up issue discussing the plan for the "addons" packages is at [3]. I'll also toss out my usual…

I was in awe the entire time Lin was speaking. Not a single "um" or other verbal tic; she's an incredible speaker and was admirably lucid throughout that entire talk. That's so difficult to do. And style aside, she made understanding Fiber incredibly simple. Just wanted to express my admiration for her work and gratitude for making this information public, available, and free.

Terrific presentation and speaker style - I couldn't come close - but she has at least one very common verbal tic that was pointed out in my own speaking style, and now it galls constantly. That's starting a sentence or phrase with a gratuitous "so".

I don't mind if "so" starts a sentence as long as it really means "therefore" but most of Lin's instances don't qualify.

Her "so" affliction is really pretty low compared to most public speakers, but it is there.

Re: React v15.5.0

#163

Post by enraged_camel »

ng12 wrote: post #67
TheAceOfHearts wrote: post #29

React team is doing an amazing job. I remember when it was first announced, I thought Facebook was crazy. "JSX? That sounds like a bad joke!" I don't think I've ever been so wrong. After hearing so much about React, I eventually tried it out and I realized that JSX wasn't a big deal at all, and in fact it was actually pretty awesome. Their migration strategy is great for larger actively developed applications. Since…

Agreed 100% about JSX. Especially since the only alternative anyone uses is opaque stringly-typed template nonsense (Angular, Vue, Ember, etc).

I use single-page components in Vue and write templates like this:

  
      
          {{ title }}
      
  

  
    export default {
        data() {
            return {
                title: "Hello world"
            }
        }
    }
Works well in my opinion. Separates the template into its own section but keeps it inside the same file.

Re: React v15.5.0

#164

Post by spankalee »

untog wrote: post #61
STRML wrote: post #42

Earlier quoted context omitted.

I agree that this is the future. But that will mean telling everyone that they should now run their node_modules through Babel - no inconsequential feat, given the size of the code that must now be transpiled.

It's not just that - is JSX part of ES6? It isn't, but a lot of pre-Babel transpiled code uses it. So people would need to transpile to ES6 for distribution, then to ES5 when someone uses the library. Messy.

Don't distribute JSX, it's not JavaScript. Distribute what engines actually support.

Re: React v15.5.0

#165

Post by spankalee »

Silhouette wrote: post #55
spankalee wrote: post #39

Earlier quoted context omitted.

It's really time to start distributing ES6 via npm. All current browsers support ES6. It's now generally faster than equivalent ES5, it minifies better, tooling is better, etc. It's the app that should compile all the code to run in the target environment if needed. This is what we've done in the new Polymer CLI / polymer-build: we compile all dependencies but only if necessary.

All current browsers support ES6. That's debatable, particularly when you factor in bugs. However, even if they did, it seems unwise to assume that all relevant users for all or even most projects will be on the latest evergreen browsers. Several large groups, including business users on IE and mobile users on slightly older devices, probably won't be. I know there's a certain type of web developer who would love for…

Chrome, Firefox, Edge, Safari and Opera all support ES6. That's the current version of all major browsers.

But, I'm not arguing that web sites should only serve ES6 to browsers, only that packages should be distributed as ES6 and the app should be responsible for compilation.

Re: React v15.5.0

#166

Post by spankalee »

debaserab2 wrote: post #59
Silhouette wrote: post #55

Earlier quoted context omitted.

All current browsers support ES6. That's debatable, particularly when you factor in bugs. However, even if they did, it seems unwise to assume that all relevant users for all or even most projects will be on the latest evergreen browsers. Several large groups, including business users on IE and mobile users on slightly older devices, probably won't be. I know there's a certain type of web developer who would love for…

This is a common theme I'm noticing a lot lately. Meanwhile, I check my product's browser breakdown and IE9/10 is still too significant to ignore. There's just no way our customers would be okay with this. Many are still locked on older IE versions due to (bad) corporate policies. I can't strongarm them into upgrading. Which leads me to wonder: are developers that are so willing to advocate breaking compatibility wit…

If your users need ES5, then compile to ES5. The packages you use can't know that though. I'm not advocating for breaking anything.

Re: React v15.5.0

#167

Post by debaserab2 »

matt4077 wrote: post #104
Silhouette wrote: post #55

Earlier quoted context omitted.

All current browsers support ES6. That's debatable, particularly when you factor in bugs. However, even if they did, it seems unwise to assume that all relevant users for all or even most projects will be on the latest evergreen browsers. Several large groups, including business users on IE and mobile users on slightly older devices, probably won't be. I know there's a certain type of web developer who would love for…

The situation has really improved, mostly due to auto-updating, increased competition between browsers, the iPhone's power to compel modernisation, and the resulting fading of proprietary technology like flash or ActiveX. Sure, google.com probably needs to support IE 6. For my own business, I'm not willing to make compromises for browsers below 2%. That currently means Safari 10, Chrome 56, and IE 11. And IE 11 is re…

That's crazy to me: you'd give up 2% of your customer size (and potential revenue?) just to make your dev workflow more convenient?

Re: React v15.5.0

#168

Post by fiatjaf »

STRML wrote: post #146
evilduck wrote: post #136

Earlier quoted context omitted.

https://gitlab.com/Rich-Harris/buble/blob/master/src/program... vs. https://github.com/babel/babel/blob/7.0/packages/babel-plugi... Maybe you could explain how this is the same thing?

Yeah, I'm actually completely wrong. My apologies to the Buble team. For whatever reason, I thought I saw an announcement of Buble essentially saying it was an opinionated feature-freeze of Babel with most of the configuration stripped out, but it appears to be a totally new project. That said, the two are very different tools. Buble appears to be essentially string manipulation (which Babel does to occasionally with…

> will break in mysterious ways perhaps months or years into the future

Since you already recognized you know nothing about Buble can you please stop making absurd claims about THINGS YOU DON'T KNOW?

What are specs, by the way? I don't care if Buble isn't following stupid specs. Browser vendors will change these specs a million times, Babel will follow up with new versions with a thousand breaking changes and require you to install a ton of packages, clean old packages, erase your hard disk and kill your neighbours. Buble will just keep working.

Re: React v15.5.0

#169

Post by spion »

spion wrote: post #33
garfij wrote: post #16

Earlier quoted context omitted.

> For each of these new deprecations, we've provided a codemod to automatically migrate your code. They are available as part of the react-codemod project. They gave you tools to automatically fix any new warnings that came from this. I honestly don't know how they could have made it any easier.

Unless you use typescript or coffeescript. In which case you're on your own.

Interesting, I didn't expect a downvotes. If this is factually incorrect, please do point it out. I looked at the tool and it seems it only works on plan JS and Facebook's JS dialect (flowtype)

Re: React v15.5.0

#170

Post by growtofill »

debaserab2 wrote: post #167
matt4077 wrote: post #104

Earlier quoted context omitted.

The situation has really improved, mostly due to auto-updating, increased competition between browsers, the iPhone's power to compel modernisation, and the resulting fading of proprietary technology like flash or ActiveX. Sure, google.com probably needs to support IE 6. For my own business, I'm not willing to make compromises for browsers below 2%. That currently means Safari 10, Chrome 56, and IE 11. And IE 11 is re…

That's crazy to me: you'd give up 2% of your customer size (and potential revenue?) just to make your dev workflow more convenient?

This can be justified. Multiple times I'd been in the spot when shipping of a feature by a certain date will get your contract signed. And this is dependant of how convenient your workflow is.
Post reply on HN