HN Explorer

Ask HN: For those moving away from React what options are you considering?

17 points by adam_ellsworth ↗ HN
With the patent clause taking up much of the discussion when React is brought up and following that – that it may be in many companies' best interest to migrate to a different tech – what frameworks or approaches are you considering for larger frontend applications.

19 comments

[ 3.3 ms ] story [ 37.4 ms ] thread
romanovcode
Angular with NGRX is not bad. Vue if you don't like typescript.
webgroot
Does preact come under React's patent clause? My understanding is that both are completely different libraries. If people have concerns on react's patent clause, isn't it easy to migrate to preact?
kybernetikos
Unlike copyright, patents apply to anything that uses the patented method. This means that if Facebook have any patents on react (and so far I haven't seen anyone actually point to specific patents) they would apply to anything using the same techniques which would likely include any similar library.
owebmaster
It'd be interesting to see how the patent would be enforced if the company is outside US
[deleted]
(comment deleted)
sotojuan
Server rendered pages with little to no JS.

--

The patent clause generates discourse because HN commenters love to state the obvious, particularly when it's off topic (e.g. an article about React performance has a commenter rushing to say "but the patent sucks!" to generate a thread of comments about that).

In real life, no one cares (for better or worse). Companies and start ups are adopting React like they have for the past year(s).

LeeHwang
My company is switching to a combination of little to no js, vue.js, and jquery.

The big fear of c-level guys is to avoid another react legal situation. We've already had to dump angular, and after react, I now get enormous pushback on using any framework system that wasn't created internally.

jdavis703
Why were you required to dump Angular?
ripexz
We've been using Knockout.js at my company for the last ~4 years but we're in the process of switching over to Vue.js, or at least use it for new projects.
flavio81
I'm waiting for WebAssembly to receive stronger toolings and lib until a radically new way to program the frontend appears. Ah, and I will relish to see the end of the Javascript dominance of the browser. I can say that again. I would love to see Javascript kicked away of the browser and replaced with something less asinine that doesn't require transpilation (Babel, etc), nor a slow kludgy hack to have a weak type safety net (TypeScript).

Meanwhile, i'm sick of the current state of the art for the web frontend. It is currently so convoluted and unprofessional, that programming a Windows desktop application using the ancient, verbose Win32 API looks like heaven, compared to it.

In any case, if you need an alternative, Svelte looks good.

mars4rp
the problem is not JS, problem is people are not using the latest version of browsers. if you have to still support IE because your clients still use it, I don't see how WebAssembly can help!
jbreckmckye
Expect to keep waiting. WebAssembler does not interact with the DOM and probably never will do. It is being developed as an replacement to NaCl, not V8. Page scripting will still be done in JS for several years.
flavio81
>WebAssembler does not interact with the DOM and probably never will do.

Because it doesn't really need to. You can already bridge this gap by using javascript as a bridge or "glue" between WebAssembly and the DOM.

Example:

https://github.com/mbasso/asm-dom

> Page scripting will still be done in JS for several years.

There are people who thought that corporate web pages would be done in Flash (& Actionscript) for several years.