• 0

Reference: Starting a new list on React.js Web Programming, any help appreciated


Question

I am starting a new list on Web Programming using React.js at:

 

https://github.com/10UWP/The-React-List

 

It will cover React.js OSS tools with a Windows/Neowinian perspective. There will also be an emphasis on Live Page Editing and REPL etc to try and claw back some developer advantage when stuck using web based technologies for some projects. Another focus is to follow core React philosophy to eliminate the evil that is CSS and HTML as much as possible.

 

However, whatever opinions I bring to the table, I do view these lists as "inclusive" and the value of the list is a quick one-stop place to grab whatever anyone needs from a lot of alternatives so if someone suggests a great tool that completely is the opposite, it will get added for sure.

 

Right now, it is very incomplete and I'm looking for suggestions to add to it until it ends up like my UWP List:

 

https://github.com/10UWP/The-UWP-Tools-List

 

Basically, I want it to be an easy starter reference of tool sets  for the experienced C#/XAML developer to do some clean focused work and avoid the huge Hipster noise level of the Whack-A-Mole Web Design world. On GitHub, finding a good selection of UWP tools is not easy due to the horrible organization of GitHub so my list can really save people some time. For React.js, I think we have the opposite situation of a fire hose of JS-lib-of-the-week and the list will be good for non-web developers who don't live and breath the crazy web Hipster Culture on a daily basis.

 

I'm also starting a Machine Learning list which is currently empty:

 

https://github.com/10UWP/The-Cognitive-and-ML-List

 

 

Edited by DevTech
added Reference to the title to suggest old thread not get locke

7 answers to this question

Recommended Posts

  • 0

I find that the following work quite well together on the front-end:

  • React
  • Redux
  • redux-updeep - enforce immutability, update state with little boilerplate
  • redux-observable - easily compose anything async with RxJS
  • Flow - forget about prop types, we want real types
  • 0
  On 31/08/2016 at 15:22, vhane said:

I find that the following work quite well together on the front-end:

  • React
  • Redux
  • redux-updeep - enforce immutability, update state with little boilerplate
  • redux-observable - easily compose anything async with RxJS
  • Flow - forget about prop types, we want real types
Expand  

I will add your suggestions to the list.

 

https://github.com/10UWP/The-React-List

 

I'll create a new section for individual projects...

 

  • 0
  On 31/08/2016 at 15:22, vhane said:

I find that the following work quite well together on the front-end:

  • React
  • Redux
  • redux-updeep - enforce immutability, update state with little boilerplate
  • redux-observable - easily compose anything async with RxJS
  • Flow - forget about prop types, we want real types
Expand  

OK, I added your projects, but I also added the following note for Flow:

 

" **Warning** Flow has a serious defect or faulty design that appears to prevent installation on a Windows computer. Very unprofessional in 2016 to not test a project on the O/S used by 95% of the human population. This project was added based on user-feedback to this list but until this defect is repaired, it's simply not usable."

 

Microsoft owns a percentage of Facebook and normally they interop quite well, but the Mysterious is still alive and well in 2016. Perhaps, Typescript would be the Microsoft suggested way of adding types to JS, although Typescript appears to be far more sophisticated and broad in scope whereas Flow might have a place as a low ceremony tool, if it actually worked!

 

Thanks for your suggestions.

 

  • 0
  On 31/08/2016 at 20:05, DevTech said:

OK, I added your projects, but I also added the following note for Flow:

 

" **Warning** Flow has a serious defect or faulty design that appears to prevent installation on a Windows computer. Very unprofessional in 2016 to not test a project on the O/S used by 95% of the human population. This project was added based on user-feedback to this list but until this defect is repaired, it's simply not usable."

 

Microsoft owns a percentage of Facebook and normally they interop quite well, but the Mysterious is still alive and well in 2016. Perhaps, Typescript would be the Microsoft suggested way of adding types to JS, although Typescript appears to be far more sophisticated and broad in scope whereas Flow might have a place as a low ceremony tool, if it actually worked!

 

Thanks for your suggestions.

 

Expand  

I think that your warning would be more useful if it had a summary of the problem with a link to the GitHub issue.

 

Both Typescript and Flow are good tools. Some of the features that Typescript add to JS morphs the language to be more like C# or Java. Flow simply adds types to JS and doesn't try to do that. In the long run it could be that Flow is better suited to React and Typescript to Angular since React and Flow are both Facebook projects whereas Google have adopted Typescript for Angular.

 

Another thing to consider is that Typescript currently enjoys better tooling support, IDE integrations.

 

At the end of the day, JS is better off with type-checking than without :)

  • 0
  On 01/09/2016 at 04:01, vhane said:

I think that your warning would be more useful if it had a summary of the problem with a link to the GitHub issue.

 

Both Typescript and Flow are good tools. Some of the features that Typescript add to JS morphs the language to be more like C# or Java. Flow simply adds types to JS and doesn't try to do that. In the long run it could be that Flow is better suited to React and Typescript to Angular since React and Flow are both Facebook projects whereas Google have adopted Typescript for Angular.

 

Another thing to consider is that Typescript currently enjoys better tooling support, IDE integrations.

 

At the end of the day, JS is better off with type-checking than without :)

Expand  

Thank you for your thoughts and suggestions.

 

If you examine the UWP Tools List which is a work-in-progress that is further along than the React List, you might get some idea of the time involved and that I have a choice to:

 

  • add more material or
  • make the existing material more detailed and accurate or
  • divide my allocation of time for that hobby across a couple of lists

 

In the case of Flow, I was trying to be low key by using the word "defect" instead of "designed by country bumpkins who took a dependency on a Linux-only library" - Facebook also has a live debugging environment with the same issue. I can rant I all want on internal Facebook Fanboyism that might have been to root cause of a poor decision, but at the end of the day they are open sourcing internal projects that they use, for the benefit of all mankind and my take on it as a Windows Developer with a skeptical eye on the usefulness of web technology and its Hipster Culture is simply to point out to other developers, possible paths through the maze that can possibly approach the beauty and elegance of C# and XAML. Rx.js is one gateway that I consider to be a good approach and can lead one to the door of Facebook and the React/Flux architecture.

 

There are many other approaches of course but that's a list for someone else to present. I wish I could present a plan to make Flow more universal since it seems like a great idea but for now hacking on the internals of Flow is way beyond the scope of what I am trying to accomplish.

 

 

  • 0
  On 01/09/2016 at 06:28, DevTech said:

Thank you for your thoughts and suggestions.

 

If you examine the UWP Tools List which is a work-in-progress that is further along than the React List, you might get some idea of the time involved and that I have a choice to:

 

  • add more material or
  • make the existing material more detailed and accurate or
  • divide my allocation of time for that hobby across a couple of lists

 

In the case of Flow, I was trying to be low key by using the word "defect" instead of "designed by country bumpkins who took a dependency on a Linux-only library" - Facebook also has a live debugging environment with the same issue. I can rant I all want on internal Facebook Fanboyism that might have been to root cause of a poor decision, but at the end of the day they are open sourcing internal projects that they use, for the benefit of all mankind and my take on it as a Windows Developer with a skeptical eye on the usefulness of web technology and its Hipster Culture is simply to point out to other developers, possible paths through the maze that can possibly approach the beauty and elegance of C# and XAML. Rx.js is one gateway that I consider to be a good approach and can lead one to the door of Facebook and the React/Flux architecture.

 

There are many other approaches of course but that's a list for someone else to present. I wish I could present a plan to make Flow more universal since it seems like a great idea but for now hacking on the internals of Flow is way beyond the scope of what I am trying to accomplish.

 

 

Expand  

Do you have a GitHub link to the issue with Flow? I'm not being argumentative - I really want more information on this (and track progress). The project ostensibly ships a Windows binary. It's possible that Flow via bash on Windows might work too.

  • 0
  On 02/09/2016 at 04:45, vhane said:

Do you have a GitHub link to the issue with Flow? I'm not being argumentative - I really want more information on this (and track progress). The project ostensibly ships a Windows binary. It's possible that Flow via bash on Windows might work too.

Expand  

Thanks for directing my attention to this. I only have so much time and normally go with whatever text is on the GitHub page which in the case of Flow reads out (still) as :


 

  Quote

 

https://github.com/facebook/flow

Requirements

 

Flow works with:

 

Mac OS X

Linux (64-bit)

 

There are binary distributions for Mac OS X and many variants of Linux; you can also build it from source on almost any 64-bit Linux variant.

 

Expand  

Obviously somebody on the Facebook dev team is a *#$* presumably high enough on their management chain to have influence but reason appears to have prevailed finally although there is no indication if the root cause was addressed.

 

https://github.com/facebook/flow/issues/6

 

Issue #6 - opened Nov 14, 2014 and closed Aug 1, 2016 - which produced this blog entry:

 

https://flowtype.org/blog/2016/08/01/Windows-Support.html

 

windows.gif

 

 

Download at:

 

https://github.com/facebook/flow/releases

 

Edited by DevTech
Added download link for Facebook Flow
This topic is now closed to further replies.
  • Popular Now

  • Posts

    • The New Outlook is horrible at best. The one thing they push so hard at is that stupid ad that has to stay on top to promote their stupid Office 365. They can go to hell with that BS.
    • Nvidia shares Windows hotfix driver 576.66 for FC 25 crashes, browser video bugs, and more by Sayan Sen Nvidia has been on a roll lately with its release of hotfix drivers, which are essentially emergency display driver updates meant to fix issues.. The company's GeForce RTX 5000 series graphics cards have been plagued with several issues, and these hotfixes as well as the regular GameReady driver updates, are being pushed out to clear up the software side problems. The first hotfix was released in early March with version 572.65 that resolved black screen bootups. This was followed by another, version 572.75, that addressed clocking issues. After that, version 576.15 helped fix Windows Sleep and Modern Standby-related temperature monitoring bugs. With the latest hotfix driver update, 576.66, Nvidia says that it has resolved a video playback bug in web browsers that can lead to red-green flashing and similar corruption of that nature. Aside from that, the driver also fixes multiple game crashes including EA Sports FC 25, and more. Nvidia notes that the new hotfix driver is based on its latest GameReady driver 576.52. As a refresher, that driver added support for Nvidia's new RTX 5060. The full changelog for the new hotfix driver 576.66 is given below: Dune: Awakening may crash during gameplay [5273568] EA Sports FC 25 may crash during gameplay [5251937] [RTX 50 series] Dragons Dogma 2 displays shadow flicker [5252205] [RTX 50 series] Video playback in a web browser may show brief red/green flash corruption [5241341] Clair Obscur: Expedition 33 may crash [5283401] If you are encountering problems like the ones described above on Windows 11 or 10, you should definitely try updating the driver to the hotfix version here. In order to download the update, head over to Nvidia's official website on this page where you can also view the driver's release notes.
  • Recent Achievements

    • Week One Done
      jrromero17 earned a badge
      Week One Done
    • One Month Later
      jrromero17 earned a badge
      One Month Later
    • Conversation Starter
      johnwin1 earned a badge
      Conversation Starter
    • One Month Later
      Marwin earned a badge
      One Month Later
    • One Year In
      fred8615 earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      242
    2. 2
      snowy owl
      156
    3. 3
      ATLien_0
      144
    4. 4
      +FloatingFatMan
      138
    5. 5
      Xenon
      131
  • Tell a friend

    Love Neowin? Tell a friend!