boubiyeah

7 ms·

31.
by boubiyeah 8y ago
I agree the trackpad is unnecessarily large. It works much better than the competition though.
32.
by boubiyeah 8y ago
I feel exactly the same way. Just bought the new 2018 model and I can't shake the feeling they're completely off-track. The trackpad and screen are excellent, the OS is okay but boy, that thinness chasing is so dumb! I make many
33.
by boubiyeah 8y ago
How is dart superior to TS? This is so uninformed. Just like your view of what a type system does. Dart is very poorly designed, and they managed that even without the constraint of being 100% compatible with good old broken javascript. It
34.
by boubiyeah 8y ago
Not sure what you mean. React is 5 years old. Frontend development is more volatile by nature as devices changes, UX guidelines change, etc but overall React was very stable during these years. But even Java changed A LOT in 5 years... You
35.
by boubiyeah 8y ago
I want to say Great work, even if it's not done yet. The react team obviously works well together, the vision is here and as an engineer who's been doing frontend work for 15 years (using flex, vanillaJS, various home-made framewo
36.
by boubiyeah 8y ago
"Just use javascript" to workaround the many language limitations then? :D In that case, why not use typescript for everything? Being pure is nice and all but it's not a goal in itself, especially if the language is extremely
37.
by boubiyeah 8y ago
Some people's package.json is the stuff of nightmares
38.
by boubiyeah 8y ago
I think it's just that while it works, they don't want to bet on Elm's future and would rather learn new techs.
39.
by boubiyeah 8y ago
I'm not confusing anything, but regardless of which solution ones chooses, the implementation is nothing but trivial and people usually turn to fully ready implementations like apollo.
40.
by boubiyeah 8y ago
If you're using graphQL just for that... You can expose a POST endpoint that can follow relation (GET) links recursively, starting from a base resource. It's a bit of work but still far less than implementing a good schema, resolv
41.
by boubiyeah 8y ago
I know about apollo caching, but it's strictly inferior to HTTP caching which has tons of options (Vary, Etag, etc) Caching per user is still going to mean tons of cache misses. Caching based on the query hash means you're going t
42.
by boubiyeah 8y ago
Another PRO of strict APIs is that they're dead simple to cache. Tons of customization = caching hell.
43.
by boubiyeah 8y ago
it's possible yes. Though sometimes the speed limit is very, very low and it gets annoying to have your eyes constantly on the speedometer.
44.
by boubiyeah 8y ago
A 3 km/h speed over the limit is not in the same category as many other law breaks... It's become such a cash cow in Europe.
45.
by boubiyeah 8y ago
You're always expecting a specific type, whether the type or schema is made explicit by the language or not.
46.
by boubiyeah 8y ago
JS vs Elm simply cannot be reduced to "classes". Classes is only a tiny part of what's broken in JS. TS (coupled to "JS, the good parts") saves the day though, but I have no idea how avoiding classes also somehow ma
47.
by boubiyeah 8y ago
Not sure why you get downvoted haha
48.
by boubiyeah 8y ago
It's a made up statistic. GraphQL reminds me of the NOSQL movement. Everyone wanted to try one of these systems, even when they were completely broken at the time (e.g mongodb) And yet, most apps will do just fine with a classical SQL
49.
by boubiyeah 8y ago
Yeah... I wouldn't count on retirement too much.
50.
by boubiyeah 8y ago
I don't know if this was ironic or not but it made me chuckle. Many people actually DO use technologies that are absolutely not required but which bring incidental complexity because it's fun and hot right now. Seriously, graphQL
51.
by boubiyeah 8y ago
you are seriously mistaken about react then. The whole point of MV libs is that you maintain a model (domain and/or UI) and the UI just redraws itself. JQuery is 100% not needed even for the most complicated React apps.
52.
by boubiyeah 8y ago
It aged so poorly! Really liked it before React came out though.
53.
by boubiyeah 8y ago
The other huge difference is how much React beneficiates from static typing (typescript for instance) whereas just like angular, vue templates and all the glue code cannot possibly benefit from it. A vue or angular app is almost as typed ch
54.
by boubiyeah 8y ago
And component logic is very imperative and error prone... e.g attributeChangedCallback and batched renders. The webcomponent spec feels so outdated already compared to what modern libs do.
55.
by boubiyeah 8y ago
No. Vanilla React just give you the option to store state of any size in any component.
56.
by boubiyeah 8y ago
Exactly. And there are tons of techniques to do so. For instance, Stripe is a payment service (you would think a payment service is the number one choice for transactions/locks/etc right?) implemented on the good ol unreliable int
57.
by boubiyeah 8y ago
You wrote "React take the strongest stance" but you meant redux right?
58.
by boubiyeah 8y ago
That's just a more Object Oriented Redux (or less, if we consider OOP is originally message passing), and probably without all the connect optimizations. I'm not a fan of Redux either, but I fail to see what problems this approach
59.
by boubiyeah 8y ago
But now you have a new problem: Managing the freshness of that cache.
60.
by boubiyeah 8y ago
Seems common in Asia. I had the same experience in cambodia. One example: - I was very, very sick (Traveler's diarrhea) and we were about to embark for a 5 hours minivan trip with a guy without a driving license. - 5 minutes before dep

More ›