boubiyeah

10 ms·

91.
by boubiyeah 9y ago
That's pretty much the only thing I like from reason. it's still very goofy. <strong> (ReasonReact.stringToElement(string_of_int(count))) </strong> Compared to <strong>{ count }</strong> in React
92.
by boubiyeah 9y ago
It doesn't HAVE to, but usually libraries designed with a JS mindset don't lend themselves to type safety very well (JS coders like their magic strings and very dynamic types). Somehow React still managed pretty decently in that a
93.
by boubiyeah 9y ago
Well, typescript has a full time team complete with a project manager and all. Flow is more like a side project that is completely getting out of hand. typescript stole all of flow's best ideas and they have way more man-days to apply
94.
by boubiyeah 9y ago
The earth never had to face a menace so great as the homo sapiens though. Will it be resilient enough? What's good enough? that we and our debilitated livestock survive this technological "transition"? Is living in such a wor
95.
by boubiyeah 9y ago
Thank you for bringing back some sanity. Exponential population growth is not sustainable and will only make the poor, poorer (or not as poor but at the cost of health, etc).
96.
by boubiyeah 9y ago
Haha yeah. The magic of green threading is so misunderstood: Ok, it no longer blocks your UI thread but it takes AT LEAST as long as before to render (browsers still don't have an API to reliably schedule small chunks of work without a
97.
by boubiyeah 9y ago
Agreed youtube as a webapp brings no value whatsoever. Someone at google wanted to rewrite it with newer techs to update its CV? :) PS: It downloads that crappy polymer that weights more than 1.5MB... ffs
98.
by boubiyeah 9y ago
I get the same behavior on my phone with their new website too. Service worker infancy bugs?
99.
by boubiyeah 9y ago
I get what you mean and you are right in a way, but raw performance is not the only thing to consider. Yes, server rendered sites are usually an order of magnitude simpler to code than these JS-rendered solutions, and are often faster, but
100.
by boubiyeah 9y ago
Yeah, depends what you value. vue is "easier" with probably less boilerplate at the cost of more magic and less type safety due to magic string templates (if using typescript like I love to) Definitely not a good tradeoff for me,
101.
by boubiyeah 9y ago
It's evaluated once at script parsing/evaluation time so it's not really expensive.
102.
by boubiyeah 9y ago
You're saying "graphQL is always better than REST for new/small companies"; that's simply not true. It's a tradeoff. Same with (g)RPC. Just like you wouldn't buy and install 20 powerful servers to run kafk
103.
by boubiyeah 9y ago
Thanks for your reply. I've not ditched graphQL forever, but there's a lot of buy-in involved for what it could give me right now. The tech is quite intrusive on your web server. I didn't know people using redux also cached r
104.
by boubiyeah 9y ago
That's nice yes. Isn't it rare to deprecate fields though? And you can't be sure some of your clients are not overfetching "for convenience / just in case", especially if they don't use the full suite of F
105.
by boubiyeah 9y ago
Are you talking about a single client and its server? (a.k.a backend-for-frontend). This is not a hard problem to solve when you share a single programming language, with or without graphql. Because you can't possibly now what your API
106.
by boubiyeah 9y ago
It's all perceived performances, not real, raw performances. Synchronous react rendering will still be as slow as ever. This rewrite is a bit pointless to me, increase the complexity of using React on the long term (before, you could c
107.
by boubiyeah 9y ago
This is a POC in scala I put together rather quickly: https://github.com/AlexGalays/POC-api-aggregation How you would write a query: https://github.com/AlexGalays/POC-api-aggregation/blob&#x2F
108.
by boubiyeah 9y ago
GraphQL is above all, just an optimization. It optimizes the amount of bytes sent over the network. I'm very happy with REST APIs (maturity level 2/3) and see no reason to change as we've never had performance issues. Most co
109.
by boubiyeah 9y ago
Some quick rants. CSS is almost as bad as PHP when it comes to naming. Most flex related properties are prefixed with flex-; but some aren't (align-items, etc) so you now have tons of non prefixed properties that actually only work wit
110.
by boubiyeah 9y ago
I never coded native apps so forget my ignorance but how would you build an UI declaratively with swift? The turorial shows very imperative/mutative code indeed: @IBAction func setDefaultLabelText(_ sender: UIButton) { mealNameLabe
111.
by boubiyeah 9y ago
And with Typescript (or a linter, I guess) you would get a nice red line on that 1 out of a million line where a ; is needed. ; are eyesores to an already fairly technical debt heavy/bloated language.
112.
by boubiyeah 9y ago
Only a bit. I really like ML languages. The issue is that the ecosystem is still in its infancy.
113.
by boubiyeah 9y ago
I tried Flow 3 times and was always severely disappointed. It's just not as good as TS if you care about type soundness (both are unsound, but Flow just tries too hard to make compromises for mixed codebases) I always found tons of typ
114.
by boubiyeah 9y ago
Never understood why they loved it. Is it just so they can say "not my fault, our project is only using big name frameworks, DBs, etc so I did all I could?" Or is it because they don't even begin to understand what's goi
115.
by boubiyeah 9y ago
Well frontend frameworks are useless if you don't have much interaction :p
116.
by boubiyeah 9y ago
Me neither, thank god.
117.
by boubiyeah 9y ago
100% agree. Plus web components are underpowered, imperative turds. Reusable = Reusable within ONE family of applications using a similar stack. That's already pretty nice. UX guidelines keep evolving too and it will remain a business
118.
by boubiyeah 9y ago
No, a polyfill has to closely mirror an API. Polymer is inspired by web components but went its own way for several features.
119.
by boubiyeah 9y ago
google is pretty bad at frontend frameworks from my experience :D Polymer is an experiment that should have stayed in that state.
120.
by boubiyeah 9y ago
Well it's a good thing there are plenty of alternatives. React is big but it only does the view well (and half of state management -.-') it's not too hard to replace in a stack. I salute its main author, Facebook and instagra

More ›