• 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 suspect this was primarily developed with the Switch 2 in mind, which would explain the poor visuals. It seems like they're hoping the nostalgic GoldenEye 64 crowd is still loyal to Nintendo consoles. Unfortunately, this might be yet another title limited by development for underpowered Nintendo hardware.
    • Amazon's Lab126 ventures into "Physical AI" with new robotics team by Paul Hill Amazon has announced that it’s forming a new agentic AI team within its secretive hard research and development division, Lab126, to begin work on physical AI. Specifically, the company is looking to develop an agentic AI framework for use in robotics, which could start to impact blue-collar jobs, especially at its warehouses. Agentic AI is one of the latest developments in AI, superseding the previous generative AI that took off with the launch of ChatGPT. Agentic AI models are special because they can complete multi-step actions for the user to complete complex tasks. Thanks to all the visual and audio capabilities added to generative AI in previous years, these agentic models can perceive their environment, reason, plan, and act to achieve goals with minimal human intervention. If Amazon can successfully bring agentic AI to robots, they will finally be able to interact with the real world in a way they can’t today, as software running on a computer. Many people are concerned about AI’s impact on white-collar jobs right now, but when Amazon develops physical AI, it will also affect blue-collar manual work. The work is going to be carried out by Amazon’s R&D company, Lab126. It was set up over 20 years ago and has created many iconic Amazon devices, including the Kindle, Fire tablets, Amazon Fire TV, Amazon Echo devices, and more. Who it affects, and how The biggest impact of physical AI developed by Lab126 will be on Amazon’s warehouses and logistics. The company said it wants to create robots that can perform tasks based on natural language instructions. As usual for a big tech company, Amazon claims that these robots will be assistants, but it’s difficult to see how they won’t reduce the need for people. Solely based on Amazon’s plans to automate work in its factories, customers will see an indirect impact from the move through faster deliveries and potentially lower costs. The decision by Amazon to focus on agentic AI in robots is pretty interesting because so far, we’ve mainly been hearing about agentic AI limited to computer applications, such as intelligent web browsers like Opera Neon. Why it's happening Amazon has a reputation for being an efficient company, particularly when it comes to the employment of warehouse workers who are known to have strict restroom breaks. Creating robots that can help speed up warehouse activities will further boost efficiency at the company and could potentially reduce its costs and improve safety. The beginning of work on physical AI is just the next evolution of AI that we could start to hear about in the coming months and years. As agentic AI gets better, companies will be looking to see what they can advance next and physical AI may be where they choose to go next; it certainly seems like this is what Amazon has settled on in this move. If Amazon’s physical AI doesn’t lead to mass layoffs of warehouse employees, it could drastically boost worker safety. Employees could potentially be less fatigued from moving around so much, which could lead to better concentration and fewer accidents. Right now, Amazon claims that these robots will only be assistants and not replacements. While Amazon will certainly be a leader in physical AI, given its massive wealth to throw at the problem, once the technology is available, it will likely be available for sale to other businesses to use, too. Caveats and what to watch for While it’s a notable development, it still sounds like Amazon is in the early stages of developing these physical AI systems, given that it has only just set up the team. We also don’t know what specific products Amazon is planning to build or the timelines for deployment. Ever since generative AI came onto the scene, there has been discussion of AI safety. With AI moving into the physical world, it will also bring up discussion about the safety concerns. Current measures are mainly concerned with AI software running on computers, not when it interacts physically with the world. Finally, and probably the biggest concern, what will these “assistants” do to people’s jobs? Companies will likely find themselves bringing in fewer new hires initially, but it could also displace people from their jobs. Source: CNBC
    • Nintendo Switch 2 launches, where to buy and a list of games that it may not support by Sayan Sen Nintendo announced the Switch 2 back in early April this year and then followed that up with more details related to performance and hardware features later. The company touted 10x the performance of the Switch. However, on the flip side, the battery suffers, and you also need new microSD Express cards for storage. For those who need a refresher, here are the technical specification details of the Switch 2: Specification Details Dimensions Approx. 166mm x 272mm x 13.9mm (with Joy-Con 2 attached); Maximum thickness from control stick tip to ZL/ZR buttons: 30.7mm Weight Approx. 401g (console only); Approx. 534g (with Joy-Con 2 controllers attached) Screen 7.9-inch capacitive touch LCD; 1920x1080 resolution; HDR10 support; VRR up to 120 Hz CPU/GPU Custom processor made by NVIDIA Storage 256 GB UFS (a portion reserved for system use) Communication Wireless LAN (Wi‑Fi 6), Bluetooth; Wired LAN available in TV mode via dock Video Output Up to 3840x2160 at 60 fps via HDMI in TV mode; Supports 120 fps at lower resolutions; HDR10 enabled Audio Output Linear PCM 5.1 channel via HDMI; Stereo speakers Microphone Built-in monaural microphone with noise cancellation, echo cancellation and auto gain control Buttons POWER and Volume buttons USB Ports 2 USB Type-C ports (bottom port for charging/dock connection; top port for accessories/charging) Audio Jack 3.5mm stereo mini plug (CTIA standard) Game Card Slot Supports both Nintendo Switch 2 and Nintendo Switch game cards Expansion Slot microSD Express card slot (compatible with cards up to 2 TB; other microSD cards can copy screenshots and videos) Sensors Accelerometer, gyroscope, brightness sensor Battery Lithium-ion, 5220 mAh; Approx. 2–6.5 hours lifetime; 3-hour charge time in sleep mode Dock Approx. 115mm x 201mm x 51.2mm; Weight: approx. 383g For those looking to get one, major retailers like Walmart, GameStop, Best Buy, and Target have all confirmed that they will have limited console stock from time to time so you will need to be on alert and check back. Nintendo has also published a full list of games that may not work on the Switch 2: Borderlands 3 Chrono Cross: The Radical Dreamers Edition Crash Bandicoot N-Sane Trilogy Guilty Gear XX Accent Core Plus R KarmaZoo Marvel vs. Capcom Fighting Collection: Arcade Classics Mortal Kombat 1 Overwatch 2 Star Wars: Knights of the Old Republic II: The Sith Lords Star Wars Republic Commando Super Mega Baseball 4 Tombi! Special Edition Tony Hawk's Pro Skater 1+2 Touhou Genso Wanderer Reloaded Ty the Tasmanian Tiger HD Warriors: Abyss However, keep in mind that Nintendo last updated the support list last month on May 27th and the company may still be testing these. So keep an eye on the official list of games on this webpage here on Nintendo's site. Have you managed to pick up the Nintendo Switch 2? Let us know in the comments.
    • Court orders Apple to keep web links in the App Store, eroding its iOS payment monopoly by Fiza Ali Apple has been ordered to continue permitting web links and external payment options in the App Store after its bid to halt court’s ruling was declined today by a higher court. Earlier this year, in April, a federal judge decreed that Apple must allow developers to include web links in their iOS apps, remove restrictions on link formatting, and enable external payment methods without taking a commission on transactions. Apple immediately appealed and sought an injunction to delay implementation of the order while the case progressed. However, the United States Court of Appeals has now refused Apple’s emergency request to stay the district court’s order. In its decision, the panel held that Apple had not demonstrated a sufficient likelihood of success on appeal, nor that it would suffer irreparable harm if the order were enforced. The court also considered potential prejudice to other parties and the public interest, concluding that an immediate suspension was not warranted. This ruling makes it much harder for Apple to overturn the April decision, which came from a lawsuit initiated by Epic Games. Epic first sued Apple’s App Store policies in 2020, claiming that the company’s restrictions harmed competition. While Epic did not prevail on every count, the court did rule that Apple must allow developers to inform users of alternative purchasing options at better prices. Despite that narrow victory, Apple repeatedly failed to conform to the terms from the original 2021 ruling, prompting the judge in April to issue a more detailed order outlining precisely how the App Store must be “opened up”. In response to the April ruling, prominent third-party apps have swiftly implemented web-based purchasing links. Both Spotify and Amazon’s Kindle app now include buttons directing users to purchase subscriptions via their websites, bypassing Apple’s in-app payments. Additionally, Fortnite has made a comeback on iOS after around five years, presenting users with the choice between Apple’s in-app payment system and Epic’s own payment and rewards mechanism. According to Epic CEO Tim Sweeney, there is presently a 60:40 split in usage favouring Apple’s system over Epic’s, though the gap appears to be narrowing. An Apple spokesperson, Olivia Dalton, issued a statement expressing the company’s disappointment: For now, Apple must comply with the existing injunction. Unless the Appeals Court later overturns the ruling, developers can continue to include web payment links, and Apple’s longstanding monopoly over iOS payment processing may continue to erode. The ultimate resolution will depend on the outcome of the ongoing appeals, which could set a significant precedent for how app marketplaces operate in the future. Source: The Verge
  • Recent Achievements

    • Rookie
      GTRoberts went up a rank
      Rookie
    • 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
  • Popular Contributors

    1. 1
      +primortal
      397
    2. 2
      +FloatingFatMan
      177
    3. 3
      snowy owl
      170
    4. 4
      ATLien_0
      167
    5. 5
      Xenon
      134
  • Tell a friend

    Love Neowin? Tell a friend!