roc
why-did-you-render
| roc | why-did-you-render | |
|---|---|---|
| 23 | 47 | |
| 3,549 | 10,799 | |
| 3.1% | 0.6% | |
| 10.0 | 7.1 | |
| 6 days ago | 5 days ago | |
| Rust | JavaScript | |
| Universal Permissive License v1.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
roc
- Roc a fast, friendly, functional language
-
Roc – A fast, friendly, functional language
Their FAQ is an eminently reasonable breakdown of their choices:
https://github.com/roc-lang/roc/blob/main/FAQ.md
I don't fully agree with all of the reasoning, but it's a reasonable position to stake.
-
DreamBerd is a perfect programming language
If you forget what parametrisation and functions are, then Roc's modules look like they actually do that.
-
What If? Driven Development
Reminds me of: https://github.com/roc-lang/roc/blob/main/FAQ.md#why-doesnt-...
-
Current Issues with the Qt Project – From the Outside Looking In
> How would a user interface written in a functional language look?
Maybe you're not aware of Elm?
https://elm-lang.org
Elm is really functional, unlike the likes of React that are just partially, kind of functional.
There's an attempt at bringing Elm to the desktop, the Roc language... here's an UI example written in Roc:
https://github.com/roc-lang/roc/blob/main/examples/gui/hello...
-
Why and How We Retired Elm at Culture Amp
What are your thoughts on the direct descendant, Roc? [0] I know it's pre v0.1 so maybe you don't have any, but as a fellow Elm lover it seems pretty compelling on the surface albeit less directly frontend-dev focused.
[0] https://github.com/roc-lang/roc
-
The Spinnaker Programming Language
I might be misunderstanding something, but, for example, look at this "host"/platform: https://github.com/roc-lang/roc/blob/main/examples/cli/tui-platform/host.zig
- Roc's standard library was briefly written in Rust, but was soon rewritten in Zig.
-
When Zig is safer and faster than Rust
You are not alone. The other day I was checking out a new programming language and the author rewrote the unsafe rust part to zig: https://github.com/roc-lang/roc/blob/main/FAQ.md#why-does-ro...
-
Ask HN: What Happened to Elm?
Check out Roc[0][1] by Richard Feldman; it's early-stages (perhaps earlier stages than Elm?) but from everything I've seen it looks a bit like a spiritual successor to Elm, though focused more on native applications (but still seems to have its sights set on webassembly support too)
[0] https://www.roc-lang.org
[1] https://github.com/roc-lang/roc
why-did-you-render
- Too many rerenders in react?
- Lag issues with RN
- After a year developing with react, I think I've been doing all wrong
- How can I stop a component from reloading all the time?.
-
How to speed up React Native screen when full of TextInput?
Check out why-did-you-render. It may tell you some more information.
-
Why and How We Retired Elm at Culture Amp
It's a combination of many things, but imo one of the worst is all the footguns regarding state and the rerenders they cause
https://emnudge.dev/blog/react-hostage
It's so easy, that we monkey patch react to debug it https://github.com/welldone-software/why-did-you-render
Plus the vdom... Isn't great, the bundle size puts react at an inherit disadvantage, and the community has a knack for over reliance on bloated packages
-
7 Proven Practices to Boost Development Speed and Project Quality
When we implemented the MVP of the fintech app, we had a quite complicated form. At that time, I was still young and inexperienced. And eventually, we realized that our project was slowing down. We had to spend additional hours figuring out the reason. We had many unnecessary re-renders because we ignored basic rules related to props in React. I wanted to do everything possible to avoid such situations in the future. So, I added to the project linters like this and an additional starting configuration to package.json to run why-did-you-render. In short, this plugin issues a warning if something is re-rendered unnecessarily and suggests how to avoid it. Also, we included running Lighthouse in headless mode. Some people say that premature optimizations are bad, but for me, it's a principle: do it right from the start.
- Free code review
-
Is there a way to detect unwanted mutations in a React component?
maybe somethin like https://github.com/welldone-software/why-did-you-render
-
React Dev Tools: much worse experience with functions/hooks
This might help you out a bit.
What are some alternatives?
lean4 - Lean 4 programming language and theorem prover
craco - Create React App Configuration Override, an easy and comprehensible configuration layer for Create React App.
articles - Miscellaneous articles. The readme is the table of contents.
use-what-changed - A React hook and an easy to use babel-pugin to debug various React official hooks
purescript-flame - Fast & simple framework for building web applications
nextjs-rewrite-test
create-react-app - Set up a modern web app by running one command.
react-render-tracker - React render tracker – a tool to discover performance issues related to unintentional re-renders and unmounts
package.elm-lang.org - website for browsing packages and exploring documentation
react-devtools - An extension that allows inspection of React component hierarchy in the Chrome and Firefox Developer Tools.
purescript-cookbook - An unofficial Cookbook for PureScript
razzle - ✨ Create server-rendered universal JavaScript applications with no configuration