Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
acemarke
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
51 ms
·
451.
▲
by
acemarke
6y ago
I'm genuinely sorry that you're angry enough to rant like this. You might want to look into some therapy or something - that kind of anger can't be healthy. In the meantime, we're going to keep working to support our us
452.
▲
by
acemarke
6y ago
Out of curiosity, any specific features of Rematch and Easy-Peasy that you specifically like that aren't covered in Redux Toolkit? I've actually got an RTK issue open asking for ideas and concepts that we can learn from them: htt
453.
▲
by
acemarke
6y ago
You might want to read my "Tao of Redux" posts and Dan's "You Might Not Need Redux" post, which explain why Redux was designed the way it is: - https://blog.isquaredsoftware.com/2017/05/idi
454.
▲
by
acemarke
6y ago
Have you looked at our official Redux Toolkit package? https://redux.js.org/tutorials/fundamentals/part-8-modern-re... https://redux-toolkit.js.org
455.
▲
by
acemarke
6y ago
General upvote for everything Shamus writes, really. His primary venue is his "Twenty Sided" blog, where he writes long-form critiques and commentary on specific games and the gaming industry as a whole: https://www.sha
456.
▲
by
acemarke
6y ago
Note that our official Redux Toolkit package is the recommended approach for writing Redux logic: https://redux-toolkit.js.org https://redux.js.org/tutorials/fundamentals/part-8-modern-re... It doesn&#
457.
▲
by
acemarke
6y ago
A deep clone is _not_ what you want here. A correct immutable update is better described as a "nested shallow clone", where you copy each specific level of nesting from the root down to the value(s) you actually want to change. A
458.
▲
by
acemarke
6y ago
Yes, the entire point of that page is: - You've gone through this whole tutorial sequence and should now understand how to write all this Redux logic "by hand" and why these standard Redux usage patterns exist - Now, here
459.
▲
by
acemarke
6y ago
It's important to note that there _are_ differences in how `useContext+useReducer` behave vs how (React-)Redux works, especially around when and how components will re-render: - https://blog.isquaredsoftware.com/2021&#x
460.
▲
by
acemarke
6y ago
Immutable updates in JS have always required making copies of each level of nesting that has to be updated [0]. However, that process is very tedious and error-prone due to writing lots of nested spread operations. Immer effectively does th
461.
▲
by
acemarke
6y ago
FWIW, I completely agree that people should focus on learning React itself first, and then pick up other libraries (like Redux) later, and we specifically make that recommendation in the Redux docs. That's also the kind of advice I wan
462.
▲
by
acemarke
6y ago
You don't _need_ Immer. But: - Writing immutable update logic by hand is really hard to do correctly and hard to read - Accidental mutations have historically been the number one cause of bugs in Redux apps Immer eliminates accidental
463.
▲
by
acemarke
6y ago
I pressed Pete on what he actually meant by that in the replies [0]. Eventually he listed some specific concerns: - The React ecosystem has fragmentation because there's many ways to do things, and he feels someone needs to start narr
464.
▲
by
acemarke
6y ago
To be clear, we now specifically teach that our official Redux Toolkit package is the standard approach for writing Redux logic [0]. RTK uses Immer internally by default [1], and I actually just wrote a brand new "Writing Reducers wit
465.
▲
by
acemarke
6y ago
Yes, I intend the site to have an entire "Data Fetching and Caching" section that would cover things like: - Common tools for making AJAX calls (`fetch`, `axios`, self-written wrappers around `fetch`, and when to use any of those)
466.
▲
by
acemarke
6y ago
Oh hey, I literally just wrote this page yesterday :) For background, I've had to repeatedly spend time answering questions all over that really boil down to people not knowing what problems specific tools solve and when it _might_ mak
467.
▲
by
acemarke
6y ago
Hey, not entirely! I also tweet about a lot of React stuff: https://twitter.com/acemarke/status/1365874077177700361 https://twitter.com/acemarke/status/1366102388399087619 and on rare oc
468.
▲
by
acemarke
6y ago
FWIW, we've got a #redux channel in the Reactiflux Discord where I and a couple other Redux maintainers hang out and answer an ongoing stream of questions. Not sure having specific "office hours" slots would work well for us
469.
▲
by
acemarke
6y ago
Yep, I'm a firm believer in using TS pragmatically. Type the obvious code (React component props, API responses, function arguments), and start by aiming for an "80% sweet spot" of type coverage. Don't get into argumen
470.
▲
by
acemarke
6y ago
I took over a legacy AngularJS 1.x MEAN app early last year. One of the first things I did was to convert it from using Gulp to building the client with Create-React-App's build tooling: https://blog.isquaredsoftware.com
471.
▲
by
acemarke
6y ago
Note that after I pressed Pete in the replies for details, he went into some actual specifics: he has concerns about things like thunks and sagas, and also is frustrated by people complaining about "React" when they really mean &q
472.
▲
by
acemarke
6y ago
On the flip side, I'm a strong proponent of using a GUI for many Git tasks: https://blog.isquaredsoftware.com/2021/01/coding-career-git-... but I also use the CLI for other tasks as well. For example, it'
473.
▲
by
acemarke
6y ago
Yep. As an example, see this pair of posts from 2017 on a distributed VR app with Redux actions over the network: http://jimpurbrick.com/2017/01/04/vr-redux/ http://jimpurbrick.com/2017&#
474.
▲
by
acemarke
6y ago
No, because Github Issues are single-threaded.
475.
▲
by
acemarke
6y ago
I recently switched from Disqus to Utterances, which uses a Github repo's issues as the source of comments: https://utteranc.es/ I used a Python export and conversion script that I found at https://pawamoy.g
476.
▲
by
acemarke
6y ago
> The frontend is a React app based on Redux Toolkit and Recoil.js Hey, great to see Redux Toolkit being used in the wild! Would love to hear your thoughts on using RTK, and I'm particularly curious about the combination of RTK + R
477.
▲
by
acemarke
6y ago
FWIW, I accumulated a bunch of docs writing resources while rewriting the Redux core docs tutorials last year: https://github.com/reduxjs/redux/issues/3609 I specifically recommend Divio's "Document
478.
▲
by
acemarke
6y ago
Exactly. I want to "tell a story" with my commits, and that story is really more of an idealized retelling of what I actually did. Five years from now, no one needs to know that I forgot to add that one line to a prior commit and
479.
▲
by
acemarke
6y ago
Heh. On my teams, I _am_ "that one guy who knows more about Git" :) I recently wrote an extended post that aims to help devs understand how Git works, available Git commands, and techniques for using Git effectively: https:/
480.
▲
by
acemarke
6y ago
Dan linked Kent's post on why the "same-element reference" bit matters at the bottom, but it's worth highlighting: - https://kentcdodds.com/blog/optimize-react-re-renders and I covered this as well
More ›