• 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

    • I don't usually complain about articles here, but this is just ridiculous, you couldn't ask your precious AI to write something about tech instead? This literally has nothing to do with tech.
    • Microsoft's "Athena" AI: A blueprint for your own dev team's productivity boost by Paul Hill Last month, Microsoft made many developer-oriented announcements at its annual BUILD conference. One of the tools that it announced at the time was called Athena, an artificial intelligence agent that lives in Microsoft Teams and aims to speed up product development processes. Now, however, Microsoft has released the blueprint of Athena so anyone can begin implementing a similar helper for their work. Rather than just another chatbot, Athena is a deeply integrated agent accessible through Teams that helps to connect people, tools, and data throughout the product development process. Athena is smart enough to work out what needs to happen next and helps team members get it done without having to go to different applications - Athena controls it all from Teams and you just have to communicate in natural language. Athena can be embedded in several developer workflows including Teams, Azure DevOps, and GitHub. Perhaps the greatest thing about Athena is that it’s not a new product being sold by Microsoft, but rather a methodology and open-source template (Dex) that organizations or individuals can take to build their own AI agents, allowing for more customization. To get started with Athena, you'll want to set up the Dex agent. Microsoft has also published a breakout session video about Athena so you can take a deeper dive. Who it affects, and how The primary beneficiaries of Microsoft’s decision to release Athena open source are engineering teams everywhere who will be freed from boring, repetitive tasks such as pull request (PR) reviews, work item management, and security checks. This will let them get on with coding new features and innovating - something that Microsoft has been pushing hard for since the start of the latest AI revolution. For product managers and engineering leaders, Athena also looks set to be incredibly useful as they will get better real-time visibility into the status of projects, if a release is truly ready for launch, and to ensure the team is aligned. Organizations from small to large will be able to benefit from using Athena. Due to its open-source nature, Athena can be tailored to meet specific development processes. This could unlock faster delivery cycles and improve code quality across the board. Why it's happening Athena is already being used internally at Microsoft by over 2,000 of its engineers. The Redmond giant explained that this has led to “measurable gains” in speed, quality, and focus. Aside from faster review cycles for developers, Athena is also surfacing release-blocking bugs earlier, enabling the consistent completion of security and privacy workflows, and providing quicker health assessments so that teams can gauge the overall health of their software delivery. By handling all these more boring tasks, Athena can free up developers to build more features into their projects. It also has the potential to speed up delivery times so that end users can use the new software faster, and with potentially less bugs. We often hear the term “democratization” in tech, a process that makes technologies more accessible and affordable. According to this definition, Microsoft’s release of Athena delivers on democratizing AI for developers as its open source and allows people to integrate AI Into their workflows, without starting from scratch. The move also aligns with Microsoft's AI strategy, that is, putting it all throughout its products. Copilot is probably the most notorious for its omnipresence in essentially every Microsoft product including Windows and Edge. Unlike Copilot, developers get a bit more freedom with Athena, but it’s still tied up with Microsoft products, namely Teams and GitHub. Caveats and what to watch for While it’s great that Microsoft is making its Athena blueprint accessible, one issue is that developers may still find it a bit complex to implement as there are still specific customizations organizations will want to make. Additionally, this solution involves a more involved setup process as outlined in the GitHub README. Another thing organizations should be wary about is data privacy and security implications when it comes to integrating with sensitive internal systems. Organizations that are working on secretive projects probably wouldn’t want to use Athena as this could put sensitive code in the hands of third parties. It’s not only technical issues that need considering either, there is also the human element. Some people may have concerns about AI hallucinating or ethical concerns around job security that could hurt adoption. To this end, Microsoft has reaffirmed that Athena is supposed to assist teams only, not replace team members. While Athena can be extremely useful, as shown by the results internally at Microsoft, human oversight and judgment will still be vital. Complex decision and creative problem-solving in development are some areas where a human still needs to be involved. Source: Microsoft
    • How could it not be optional? ChatGPT isn't going to guess people's credentials :P
    • Mmmm, spread too thin into 2 quite different things
  • 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
      176
    3. 3
      ATLien_0
      171
    4. 4
      snowy owl
      169
    5. 5
      Xenon
      133
  • Tell a friend

    Love Neowin? Tell a friend!