Skip – A programming language to skip the things you have already computed
1–10 of 103 posts
Re: Skip – A programming language to skip the things you have already computed
#2Apparently this was a research project. Anyone have links to papers, conclusions, results? Should be interesting…
Re: Skip – A programming language to skip the things you have already computed
#3Anyone have some insider knowledge on the history of this project? I'm curious as to how a big multi-year create-a-language research project like this gets pitched, accepted, and finally sunset -- Was it a full-time project? Were there deadlines? Was this considered a success or a failure?
Re: Skip – A programming language to skip the things you have already computed
#4"supports ergonomic asynchronous computation"... because you wouldn't want any of your computations getting carpal tunnel or anything.
Re: Skip – A programming language to skip the things you have already computed
#5Anyone have some insider knowledge on the history of this project? I'm curious as to how a big multi-year create-a-language research project like this gets pitched, accepted, and finally sunset -- Was it a full-time project? Were there deadlines? Was this considered a success or a failure?
The page itself mentions the project took place from 2015-2018. There's also what looks like a devlog. I'm not sure how far back it goes but it may have the details you're looking for.
Re: Skip – A programming language to skip the things you have already computed
#6> The Skip project concluded in 2018 and Skip is no longer under active development at Facebook.
Just a warning if you're interested in using this.
Re: Skip – A programming language to skip the things you have already computed
#7Apparently this was a research project. Anyone have links to papers, conclusions, results? Should be interesting…
No papers unfortunately.
As far as results, we saw some great numbers for the effectiveness of the recomputation. The language is self hosted. And the type checker is currently incremental. On my machine the initial type checking of the compiler itself is in the ballpark of ~40s. Changing a file and getting new type errors returns in <0.5s
Re: Skip – A programming language to skip the things you have already computed
#8> The Skip project concluded in 2018 and Skip is no longer under active development at Facebook. Just a warning if you're interested in using this.
I would like to add that I intend to maintain it and build a community around it in outside of FB as it is mentioned on the front-page.
"The language, compiler and libraries are maintained as a side project by Julien Verlaguet, the main designer of the language."
Re: Skip – A programming language to skip the things you have already computed
#9How are the side effects tracked? I couldn't find it in a brief read of the source code. The documentation mentions sequence points at which previous side effects are guaranteed to have finished. But what actually tracks whether IO or state changes have occurred?
Re: Skip – A programming language to skip the things you have already computed
#10Apparently this was a research project. Anyone have links to papers, conclusions, results? Should be interesting…
We posted about some of those in the blog over the years. http://skiplang.com/blog
Some of the interesting ones:
- An overview of how memoization works and the MVCC model behind the scenes: http://skiplang.com/blog/2017/01/04/how-memoization-works.ht...
- How pattern matching is implemented and the tricks to make goto work in JavaScript: http://skiplang.com/blog/2017/11/15/simulating-goto-in-javas...
- The work done on making error messages much more helpful by understanding common idioms from other programming languages: http://skiplang.com/blog/2017/11/20/fixing-the-syntax-barrie...
- The macro syntax that elegantly solves a lot of use cases where dynamism is commonly used http://skiplang.com/blog/2018/07/24/macros.html