• 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.
  • Posts

    • For anyone looking for a lightweight formatting-free text editor, I recommend Notepad3.
    • This looks really dumb, especially if it costs $100+. Noone who cares about using a flight yoke would touch that thing, people who don't care are probably fine using the analog sticks on their controller, so who is it for?
    • A) "they shouldn't be making money off of those [free videos]"?? That is literally their business model, making money off videos that users post...if you don't feel like that should be allowed, then are you saying YouTube shouldn't exist. B) Yes, the example I gave is a net-negative transaction. If YouTube makes money from others who are following their rules, it doesn't change the fact that the person using an ad-blocker is costing them money. C) YouTube has always operated at a loss...kind of invalidates your entire argument. As I always say, I don't care what you do, I will not even say you are wrong for doing it. That is purely your choice. Just be honest enough to say something like "Google is rich, I honestly don't care." Perfectly fine reason. Don't act like there is some imagined justification for why it isn't breaking the rules.
    • You can now present content from your camera feed in Google Meet by David Uzondu Google has a new feature rolling out for Google Meet that lets you directly present video from an external camera feed right into your meetings. This means if you have a document camera for showing physical papers, a dedicated external camera for a better angle, or even output from a video production tool, you can now pipe that into Meet as a presentation source. This new option supports video up to 1080p at 30FPS. This "present from camera" function offers a more integrated way to handle certain video inputs compared to some existing workarounds. For instance, it might prove less complicated than a setup with OBS Studio where you arrange your various video sources into scenes, activate the virtual camera output, and then navigate Google Meet's settings to specifically choose "OBS Virtual Camera" as your video input before you can even start presenting that customized feed. Alongside this camera presentation feature, Google's announcement also mentioned several improvements to the general screen sharing experience in Meet. Initiating any type of screen share is faster now, and video quality during screen sharing has also been sharpened, with better handling of dynamic content like scrolling text or embedded videos. To reduce interruptions, if a second presenter stops sharing their screen, any previous presentation will now automatically resume. For those wondering when they can get their hands on this, the rollout for the camera presentation feature and these screen sharing enhancements has begun for Rapid Release domains. Users on Scheduled Release domains will start seeing it from June 11, 2025. Google notes that it could take up to 15 days for these features to be visible to all eligible users. Most Google Workspace accounts, including Business Standard and Plus, various Enterprise and Education tiers, and Workspace Individual subscribers, will have access. This new presentation option joins other recent Google Workspace enhancements. For instance, Gemini in Google Drive can now summarize changes to your files, offering a quick way to get updated on what you missed in documents since you last opened them.
  • Recent Achievements

    • First Post
      James courage Tabla earned a badge
      First Post
    • Reacting Well
      James courage Tabla earned a badge
      Reacting Well
    • Apprentice
      DarkShrunken went up a rank
      Apprentice
    • Dedicated
      CHUNWEI earned a badge
      Dedicated
    • Collaborator
      DarkShrunken earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      382
    2. 2
      +FloatingFatMan
      177
    3. 3
      ATLien_0
      174
    4. 4
      snowy owl
      169
    5. 5
      Xenon
      134
  • Tell a friend

    Love Neowin? Tell a friend!