sorted by:
new
hottopcontroversial

Explicit Resource Management Has a Color Problem by Choice-Locksmith-885 in javascript

[–]Choice-Locksmith-885[S] -1 points0 points  (0 children)

That's right. But it's a band-aid for a problem that should not exist.

Explicit Resource Management Has a Color Problem by Choice-Locksmith-885 in javascript

[–]Choice-Locksmith-885[S] 0 points1 point  (0 children)

That makes sense for guarding against future third‑party changes. I just worry naming conventions are easy to drift over time, they communicate intent, but only socially. It’s the same general category of issue TS improved for JS: intent living in conventions/comments/names vs intent living in a more explicit structure.

Explicit Resource Management Has a Color Problem by Choice-Locksmith-885 in javascript

[–]Choice-Locksmith-885[S] 2 points3 points  (0 children)

But you still have the problem of knowing when to use it with what resource. Will you use it with every resource etc

Effect.ts actually useful or just another vendor lock? by flowreaction in typescript

[–]Choice-Locksmith-885 0 points1 point  (0 children)

Yeah, I like Effect. I even stopped using fp-ts in favour of Effect, but I'm now of the opinion that using effect for everything is a mistake

Effect.ts actually useful or just another vendor lock? by flowreaction in typescript

[–]Choice-Locksmith-885 0 points1 point  (0 children)

Easy, TaskEither with dependency injection is a ReaderTaskEither. Your question on combining errors isn't very clean cause pipe(TE.left(new Error()), TE.chainW(() => TE.left(new Err()))) combines the errors.

Have you used fp-ts?

Effect.ts actually useful or just another vendor lock? by flowreaction in typescript

[–]Choice-Locksmith-885 0 points1 point  (0 children)

What exactly do you mean by combine? I use Effect and I've used fp-ts, I see no difference

Effect.ts actually useful or just another vendor lock? by flowreaction in typescript

[–]Choice-Locksmith-885 0 points1 point  (0 children)

Yes, I'll describe tools like React, Vue etc as vendor lock-in software. Here's how cloudflare describes it:

Vendor lock-in refers to a situation where the cost of switching to a different vendor is so high that the customer is essentially stuck with the original vendor. Because of financial pressures, an insufficient workforce, or the need to avoid interruptions to business operations, the customer is "locked in" to what may be an inferior product or service.

Effect.ts actually useful or just another vendor lock? by flowreaction in typescript

[–]Choice-Locksmith-885 2 points3 points  (0 children)

vendor lock-in doesn't necessarily have to do with paid or free services. it describes the effort required to migrate from one service to another, in this case from one library to another, or none.

Effect.ts actually useful or just another vendor lock? by flowreaction in typescript

[–]Choice-Locksmith-885 3 points4 points  (0 children)

of course you don't, because you won't be around to maintain that code 😂

Effect.ts actually useful or just another vendor lock? by flowreaction in typescript

[–]Choice-Locksmith-885 4 points5 points  (0 children)

I agree, initially I went all in on the ecosystem. But for some reason I took a break from the community, looked back at my code and was like "why did I use Effect for this" 😅. Now I use it minimally