Stoids

7 ms·

1.
by Stoids 1y ago
As someone who created those horrifying RxJS monstrosities, I agree with most of this, which is why I caveated my concerns. Tanstack Query simplified a lot of these issues—separating server state and caching from client side state was a hug
2.
by Stoids 1y ago
Most UIs I've written in my career benefit from being modeled as FSMs. While I see the value proposition of the atom-based approaches, especially for basic applications, I can't help but become a bit hesitant about their scalabili
3.
by Stoids 2y ago
We aren’t good at creating software systems from reliable and knowable components. A bit skeptical that the future of software is making a Rube Goldberg machine of black box inter-LLM communication.
4.
by Stoids 2y ago
That's right, Effect lifts all types to a lazily-evaluated common type and provides combinators to work with that type, similar to RxJS with Observables and its operators. Retrying[0], observability[1], and error handling[2] are first-
5.
by Stoids 2y ago
I think going all-in on Effect in its current state is not something I'd do. However there's a subset of its functionality that I'm currently replicating with a bunch of different libraries: ts-pattern, zod, some lightweight
6.
by Stoids 2y ago
The fragmentation around runtime validation libraries is pretty crazy. The fact that half these comments mention some alternative library that mimics almost the exact API of Zod illustrates that. It is filling a necessary shortcoming in the
7.
by Stoids 2y ago
I do consulting for a few restaurants, and despite my experience building full-stack web applications, I find myself reaching for Excel for most of my deliverables. These are "applications" that "non-technical" restauran
8.
by Stoids 2y ago
Do you have any favorite resources (can be books, courses, blog posts) that teach with this approach from? I have been diving more into 3D and the shortcomings in my mathematical background are starting to show.
9.
by Stoids 2y ago
I have not used it in production yet, but it's been great for one-off scripts and side projects. Setting up a TypeScript Node environment with ts-node, ts-jest, ESM support, top level await, etc. is more annoying than it should be. Mor
10.
by Stoids 3y ago
I like the idea, especially the TS-like syntax around enums and union types. I've always preferred the SDL for GraphQL vs writing OpenAPI for similar reasons. Most APIs I've run into in my career would benefit from modeling their
11.
by Stoids 3y ago
ts-pattern has been a decent band-aid for the lack of native pattern matching, but obviously has downsides that could be avoided if it was built into the language. https://github.com/gvergnaud/ts-pattern
12.
by Stoids 5y ago
Thanks for the link! Hadn't seen that release, looks promising. I think this could definitely work for some of our newer apps that haven't fully bought into GraphQL yet. Not sure if the loader / action prop callbacks will be
13.
by Stoids 5y ago
Thanks for the links! Will certainly check them out, might even send me down memory lane a bit when I was first reading about these. Would love a full-fledged recap at some point—it's really interesting getting insight into the the int
14.
by Stoids 5y ago
Congratulations to the React team on the release! I've kept up somewhat with the development of these features since Dan first introduced some of the ideas at JSConf 3 years ago. It's interesting to see how the APIs have changed o
15.
by Stoids 5y ago
I use coc-nvim [0] for my development environment and love it. The VS Code plugin is a great start to get used to vim movement, but eventually you'll run into some limitations that end up being slightly annoying (albeit this was a few
16.
by Stoids 7y ago
I miss reading the 100 page threads on What.CD about which of the 40 different rips of the White Album was best. Alternatives have popped up, but it saddens me that we lost all of that collective comment history.
17.
Domain Modeling with Tagged Unions in GraphQL(dev.to)
3 points by Stoids 7y ago|0 comments
18.
by Stoids 7y ago
Jonathan Blow and no one else clearly.
19.
by Stoids 7y ago
Yes, almost any routing library will expose a Link component wrapper that properly sets those attributes.
20.
by Stoids 8y ago
I like the idea that the 200 line event dispatching state atom is more over-engineered than a framework that works off wrapped "observable" objects and uses ES6 proxy magic (MobX). Do proxies work in IE11? Didn't think you co
21.
by Stoids 8y ago
I'd love to read something about your experience. We are currently using Apollo for one of our newer projects. We've written Redux apps in the past and understand the tradeoffs and limitations that come with that approach. We real
22.
by Stoids 8y ago
Thanks Jason, this was very helpful for me. I think I was having trouble making the mental jump from reading the code as a normal function with state vs how a component instance is called and handled by React at runtime--your example helped
23.
by Stoids 8y ago
Thank you for the example, Jake! It was very helpful. You and Jason's answer cleared it up for me.
24.
by Stoids 8y ago
Perhaps I'm just a bit dumb here, but a few of these comments confused me. > However, this is a common source of mistakes if you’re not very familiar with JavaScript closures. > The problem is that useEffect captures the count fr
25.
Writing a Custom TypeScript AST Transformer(medium.com)
1 points by Stoids 8y ago|0 comments
26.
by Stoids 8y ago
Yikes... Interviewing sucks but half the reason interviewers ask these types of questions is to see your attitude and how you respond. Writing an Instagram clone in Angular doesn't really tell me much about your problem solving skills
27.
by Stoids 8y ago
To add onto this, using lodash + TS is not the most pleasant experience. A lot of that has to due with current limitations of the type system (mostly variadic types [0]), but I find myself having to provide lots of generics rather than rely
28.
by Stoids 8y ago
I appreciate you calling me out on my wording, because you are spot on. If anything GraphQL “bleeds” even more into my front-end code. I think the appropriate way to frame it is that GQL is a more targeted, holistic solution to the proble
29.
by Stoids 8y ago
GQL and gRPC are absolutely complementary. Having resolvers fan out to gRPC-backed microservices has been great at our company. We initially used protos for all of our service contracts (including server <-> web UI communication). Whi
30.
by Stoids 8y ago
That's probably unlikely to happen, as it falls out of line with the design goals of TS, but check out io-ts[0] for a library approach to this problem. [0] https://github.com/gcanti/io-ts

More ›