Live data from Hacker News

Skip – A programming language to skip the things you have already computed

skiplang.com

101–103 of 103 posts

Re: Skip – A programming language to skip the things you have already computed

#101
post #100

Earlier quoted context omitted.

Shameless plug for something that does all of these things (perhaps not exactly as you want, but ..) https://github.com/frankmcsherry/differential-dataflow

Wonderful! I feel bad that I didn't follow the work after hearing about Naiad originally. Where might I go to read more about the fault tolerance story - I note that's an ongoing area of research in the README. Also the link to the Kafka adapter is dead, is that work ongoing or does the story end at the capture/replay API? (Happy to bombard you with email if that's any more manageable for you!) Reading the 'when not…

Durability is a student's research project at the moment. It's up and running for "Spark" style computations but the work has broader ambitions. In essence, all of the internal state in DD are easily (automatically) serialized LSM slabs, and it is cake to write them out and read them back (and almost cake to make sense of them).

    https://eurosys2017.github.io/assets/data/posters/poster21-Lattuada.pdf
Which Kafka link is dead? The work has quiesced because any next step seems to be involve assuming something about timestamps in the input. At the same time, it seems to take about 10 lines of code to write a Kafka source or sink, minus any careful worrying about acks for durability.

The DD and Adapton approaches may be a bit tricky to hybridize. Much incremental compute works by moving through a sequence of valid configurations, and DD's main departure is generalizing this to partial orders. So, maybe you could borrow ideas, but it would probably be original research to do so.

Email is great, as it is def no longer about skiplang.

Re: Skip – A programming language to skip the things you have already computed

#103
post #31

Earlier quoted context omitted.

> Skip is not meant to be a system programming language. So the comparison with Rust for example is difficult. Can you elaborate on this comment in the context of some of the other languages listed by the grandparent (Go, Swift, Julia, Nim)? Granted, writing bare-metal operating system kernels may severely limit practical options, but I can imagine using Go, Swift, and Nim for slightly higher level "systems programmi…

Right. It really depends what one means by "system programming". I would add Java/C# and many others to that list.

Generally system programming is that you're able to interact with the system without some sort of "bridge".

For that reason Java and C# cannot be counted as system programming languages, because neither of those can interact directly with the system they're running on.

Ex. C# needs PInvoke, where as C can just call system functions directly.

At least that's my understanding.

Post reply on HN