boubiyeah

6 ms·

1.
by boubiyeah 5y ago
I understand all the hook rules and all the gotchas around stale closures. But I don't want to have to deal with those as part of my everyday, regular programming, it's just stupid. React is no longer productive and hooks are way
2.
by boubiyeah 6y ago
It's just an implementation detail.
3.
by boubiyeah 6y ago
I just can't take the irony of the Elm leadership trying to come across as inclusive.
4.
by boubiyeah 7y ago
I must have some very womanly traits then. When I first joined my engineering school, I felt so bad/inadequate because all the guys were like "yeah this is easy, I totally got this" and I was like "really? it's not
5.
by boubiyeah 7y ago
But that's the simplest union type. You could have: type Result = {type: 'ok', value: string} | {type: 'err', value: string}
6.
by boubiyeah 7y ago
It was! The new result just isn't all that much better. They got trapped in their own bubble of complexity.
7.
by boubiyeah 7y ago
Not sure why Evan is not being more transparent regarding this renaming. It would be easy to just say "yes, I got a bit carried away with the naming and my big future plans, but the community reaction made me realise perhaps it was not
8.
by boubiyeah 7y ago
Yes it's terrible naming. The more abstract the naming, the harder it is to reason about. Plus, JS/TS already have proper union types without a need for a construct like Either. A better naming for 99% of cases is (like found in E
9.
by boubiyeah 7y ago
They work best if your team has low standards and just settle with whatever the framework has choosen for you. I'm not surprised it's fine for many.
10.
by boubiyeah 7y ago
Wasn't event baited
11.
by boubiyeah 7y ago
Trump is 1% of the U.S.A problems. He's more or less just a dumb symptom.
12.
by boubiyeah 7y ago
No more reason now than 2 years ago.
13.
by boubiyeah 7y ago
No matter the underlying technology, "lightweight, truly reusable UI components" is almost an ideologic dream, at the web scale. (some companies might achieve it on their own scale with a lot of effort, but not sure for how many y
14.
by boubiyeah 8y ago
type IJustWantToExperiment = any You could use the allowJs typescript flag and mostly use JS files at first; perhaps only typing a few models.
15.
by boubiyeah 8y ago
There's a big difference though: persistent data structure libs are heavy to send over the network. What we need is immutable data structures in the platform.
16.
by boubiyeah 8y ago
This entire blog post is well written garbage. There is no content.
17.
by boubiyeah 8y ago
That header animation was cool only the first 50 times I saw it
18.
by boubiyeah 8y ago
I agree with the general sentiment. The difference is even more pronounced once you start typing your code. TS/TSX = 100% typed arbitrary template DSL = 0% typed and now these string template based on interpolation = 5% typed: Only the
19.
by boubiyeah 8y ago
what if it being more productive for you has nothing to do with these magic strings? :)
20.
by boubiyeah 8y ago
Of course it's unintuitive. I see dev veterans make the mistake all the time. JS was so poorly designed. An implicit (not passed as an arg), dynamic this parameter. You couldn't be more cheeky than that really. something like cons
21.
by boubiyeah 8y ago
react is not based on logicless templates. Their very first presentation in 2012 or 2013 made that clear. It's a feature.
22.
by boubiyeah 8y ago
But managing state is quite hard in general. Angular proudly advertises it solves all problems you can have on the frontend but I would take react state + utils over angular's magic templates, rxjs and bindings any day.
23.
by boubiyeah 8y ago
React was never a view-only library. Pete Hunt always said he saw React components as mini MVC modules. it's even less true nowadays with features like Context or suspense to supplement the component states. Redux was kind of a tempora
24.
by boubiyeah 8y ago
Man, this argument is so dumb indeed... Even dumber than the "Hey, why should we care about the environment since a few countries can decide not to"
25.
by boubiyeah 8y ago
Really like typescript. You could code an algorithm with very dynamic types then expose its API with very rigorous typing (TS's type system can go pretty advanced)
26.
by boubiyeah 8y ago
Devs like you is the main reason why the web is much, much slower than it could be. Perhaps it's time to start reading about UX , browser JS parsing speed, how JS executes, etc. Making your dev life easier is nice, but don't forge
27.
by boubiyeah 8y ago
This. People often have a beef with the very wild npm ecosystem with tons of libs of varying quality, abandonned projects, bloated libs, etc but mostly it comes down to the standard library being anemic.
28.
by boubiyeah 8y ago
Gave me seasickness. And I'm not even sick on boats.
29.
by boubiyeah 8y ago
Very true. The US unleashed orders of magnitude more hell than that, abroad. Why should we be so biased?
30.
by boubiyeah 8y ago
Looks like pretty average code to me.

More ›