Twitter | Search | |
Islam Attrash
Software Engineer at Fiverr
2,935
Tweets
231
Following
486
Followers
Tweets
Islam Attrash 14h
Replying to @liran_tal @Idan_Co
Yeah, I like it for a while. But once I started writing React and lodash/fp I knew for sure that it's not ready yet. Type inference with not being forced to type everything is missing for the functional concepts.
Reply Retweet Like
Islam Attrash 14h
Replying to @gadifed
😄😅
Reply Retweet Like
Islam Attrash Aug 20
Replying to @getify
But don't forget the fact that most of the accident were caused by "Human Factors" and not stupid machine. Remove the human factor will help so much.
Reply Retweet Like
Islam Attrash Aug 20
Replying to @liran_tal @Idan_Co
Yeah. It's because it's less chars :-) I write almost of my time with Native JavaScript in my React Apps. TypeScript don't play well enough with FP & React & Redux.
Reply Retweet Like
Islam Attrash Aug 18
😂😂
Reply Retweet Like
Islam Attrash retweeted
WellPaidGeek Aug 17
Job specs be like: You need * JavaScript * React * Redux * Node * Mongo * E2E testing * Docker * Kubernetes * AWS And I’m like: “You need to be paying me 3 salaries because that’s 3 jobs”
Reply Retweet Like
Islam Attrash Aug 10
Replying to @kvlly
I spell it as: ko-ber-ne-tes
Reply Retweet Like
Islam Attrash retweeted
Kent C. Dodds Aug 3
Replying to @kentcdodds
For added context. My 18 year old brother was killed in a car-related accident over 20 years ago. I was 10. If he'd had even the level 2 autonomous driving features of many modern vehicles, he would still be alive today. I'm excited by the progress, but we can do better.
Reply Retweet Like
Islam Attrash Aug 4
Replying to @lenaggar
Can you explain what they are? I asked because I don't recognize the phase
Reply Retweet Like
Islam Attrash Aug 4
Replying to @lenaggar
Design systems?
Reply Retweet Like
Islam Attrash Aug 3
Replying to @sgrove
Lodash
Reply Retweet Like
Islam Attrash Aug 3
I saw ReasonML and I like it (but haven't the chance to try it). Hope that we can use it at some point in the industry.
Reply Retweet Like
Islam Attrash Aug 2
Replying to @galstar @hmemcpy
I loved and used TypeScript for 3 years but since I entered the functional world using lodash_fp and React I saw some weakness points.
Reply Retweet Like
Islam Attrash Aug 2
Replying to @galstar @hmemcpy
With Typing each and everything even if called once without any automatic inference then the cost defeats the benefits. You need to type all your mapStateToProps because you didn't inline it in the connect call. I'm glad with Functional JS without types for now
Reply Retweet Like
Islam Attrash Aug 2
Really nice comparison!
Reply Retweet Like
Islam Attrash Aug 2
Replying to @hmemcpy
I don't see a value for TypeScript in a dynamic functional world since I got the typings only in injecting inline functions. Once I define functions alone and refer them by variables then I must explicitly type them down which Type inference make it out-of-box.
Reply Retweet Like
Islam Attrash Aug 2
Replying to @tadmanter @AdiPolak
Don't forget that I wrote this for JavaScript integration into the Ruby world which makes the unified API very valuable. Search for: php-lodash, Golash, Rustlash, Rudash. I think I see the benefit of unified API
Reply Retweet Like
Islam Attrash Aug 2
Replying to @tadmanter @AdiPolak
Also you can do so in JavaScript. [1,2,3].map(...).filter(...).slice(...). But still Lodash is popular in use for other reasons.
Reply Retweet Like
Islam Attrash Aug 1
Replying to @tadmanter @AdiPolak
Doing rudash_fp will make it more functional and composable which native ones don't behave as so.
Reply Retweet Like
Islam Attrash Aug 1
Replying to @tadmanter @AdiPolak
Lodash must functions already exist in Native JavaScript but it's popular because of his API that native don't support like filter by slice object/hash (even deeply), nil safe, type safe, nice defaults and much more.
Reply Retweet Like