Player FM 앱으로 오프라인으로 전환하세요!
57: Staying the Course
저장한 시리즈 ("피드 비활성화" status)
When? This feed was archived on October 04, 2020 13:08 (). Last successful fetch was on January 04, 2020 14:08 ()
Why? 피드 비활성화 status. 잠시 서버에 문제가 발생해 팟캐스트를 불러오지 못합니다.
What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.
Manage episode 220727449 series 1531971
- Not really wanting to do JS at work, daily.
- I want to understand the underlying workings of it.
- I want more stable, elegant code. I keep trying to make custom types in JS, and it’s totally not working. Hence my interest in TypeScript lately. By defining the shape of the data that is allow, it removes an entire class of bullshit that I have to be reactive to in JS. And I really don’t like it.
- How can I do this better ?
- So why does this work? At first I wasn’t sure. I have this nagging sense that nested functions are difficult to reason about, this is about the time I struggled with the pipe operator (|>)
These let and where examples of using a lambda function may initially seem academic and contrived, but they’re the basis of one of the most important design patterns in JavaScript
It’s mind bending to me to have lambda expressions explained in a Haskell book, using JS. I need to remember all the little nuances of JS that I have absorbed over the years, and that other languages are the same.
JS using lambda functions to encapsulate scope.
Holy sh-nikes haskell uses lexical scope too. It even has a diagram.
Resources Follow- JavaScript to Elm - Twitter: @jstoelm
- Email: [email protected]
 
- Jesse Tomchak - Twitter: @jtomchak
 
91 에피소드
저장한 시리즈 ("피드 비활성화" status)
When? This feed was archived on October 04, 2020 13:08 (). Last successful fetch was on January 04, 2020 14:08 ()
Why? 피드 비활성화 status. 잠시 서버에 문제가 발생해 팟캐스트를 불러오지 못합니다.
What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.
Manage episode 220727449 series 1531971
- Not really wanting to do JS at work, daily.
- I want to understand the underlying workings of it.
- I want more stable, elegant code. I keep trying to make custom types in JS, and it’s totally not working. Hence my interest in TypeScript lately. By defining the shape of the data that is allow, it removes an entire class of bullshit that I have to be reactive to in JS. And I really don’t like it.
- How can I do this better ?
- So why does this work? At first I wasn’t sure. I have this nagging sense that nested functions are difficult to reason about, this is about the time I struggled with the pipe operator (|>)
These let and where examples of using a lambda function may initially seem academic and contrived, but they’re the basis of one of the most important design patterns in JavaScript
It’s mind bending to me to have lambda expressions explained in a Haskell book, using JS. I need to remember all the little nuances of JS that I have absorbed over the years, and that other languages are the same.
JS using lambda functions to encapsulate scope.
Holy sh-nikes haskell uses lexical scope too. It even has a diagram.
Resources Follow- JavaScript to Elm - Twitter: @jstoelm
- Email: [email protected]
 
- Jesse Tomchak - Twitter: @jtomchak
 
91 에피소드
모든 에피소드
×플레이어 FM에 오신것을 환영합니다!
플레이어 FM은 웹에서 고품질 팟캐스트를 검색하여 지금 바로 즐길 수 있도록 합니다. 최고의 팟캐스트 앱이며 Android, iPhone 및 웹에서도 작동합니다. 장치 간 구독 동기화를 위해 가입하세요.


 
 
 
 
