|
|
|
|
|
|
by dmitry-vsl
996 days ago
|
|
|
>> That is, how leporello handles a codebase that's partially written in freestyle JS and not the subset that leporello specify handles? Leporello is based on the idea that you can have much more powerful dev experience (time-travel debugging, better debugger UX) if you adhere to functional code. Look at the recent news from Jetbrains [0]. They presented predictive debugger for their .NET IDE. They called it "a game changing look into the future" and it is actually a huge improvement of ergonomics. But with FP, you get predictive debugger for free. It is just a trivial consequence of not having data mutations. So inside the function, each name is binded to single immutable value. If you have freestyle JS, then Leporello is not a good fit for you. It requires some buy-in from a developer. The good thing is that you still write plain vanilla javascript, without non-standart extensions that require some kind of transpilation. [0] https://news.ycombinator.com/item?id=36940937 |
|
|