"In Skip the = operator introduces a new variable, but unlike other languages the = operator alone can not modify an existing variable." Using != to assign a value feels really strange to me. I know some languages use := but in those languages typically it's because = is an equality operator. I'm sure there are some exceptions but != just so universally means "not equal" to me.
But it's not just `!=`, it is `!variable = value`, see [1]. That does not look like "not equal" operator. [1] http://skiplang.com/docs/lvalues.html
Skip: A programming language to skip the things you have already computed
81–90 of 119 posts
Re: Skip: A programming language to skip the things you have already computed
#82Earlier quoted context omitted.
But it's not just `!=`, it is `!variable = value`, see [1]. That does not look like "not equal" operator. [1] http://skiplang.com/docs/lvalues.html
Although !x mean "not x" pretty universally.
Re: Skip: A programming language to skip the things you have already computed
#83Re: Skip: A programming language to skip the things you have already computed
#84Earlier quoted context omitted.
If done right, SQLive is the sort of thing that could entirely change the way many applications are written. Solving the problem of real time collaboration at the database level has been a dream of mine for years. Unfortunately I'm doubtful that existing RDBMSs will be able to integrate such a thing, seeing how shoddy implementations of materialized views have been. I really hope you are successful in tackling this p…
Check out the work Materialize is doing as well - similar vein.
I had to pass because of its prohibitive license (for now) and the head-scratching bugs I ran into with the direct Postgres source. I also had some concerns about the complexity Materialize would add to architecture of the sort of small apps I typically build.
I know this is unappreciative of the complexity of the problems that Materialize solves, but it would be so nice if Postgres just had observable (with triggers), no-compromise incremental materialized views.
What sort of experiences have you had with Materialize, if any?
Re: Skip: A programming language to skip the things you have already computed
#85Looks interesting but here's what I don't understand. So many programming languages do not show example code on the homepage. That's like if Mazda didn't show cars on their homepage. Sure, you won't really know what it's like to drive it without getting your hands dirty but at least let me see the trim.
In the spirit of testing: Mazda doesn't show cars on their home page. Here is mazda.com: Forbidden You don't have permission to access / on this server. You have to add www. to mazda.com before you can see any damn cars. And it's just one car I see; some fat SUV that looks like it's about to give birth to a pair of sporty twins.
Who said mazda.com is the homepage, and not www.mazda.com?
Re: Skip: A programming language to skip the things you have already computed
#86Earlier quoted context omitted.
In the USA, Mazda is at mazdausa.com, not mazda.com. There are eight cars on the front page.
So, whats your point? Does that change anything?
Re: Skip: A programming language to skip the things you have already computed
#87http://skiplang.com/docs/lvalues.html
I think some of the phrasing there ("the variable x is going to be updated to point to a new copy of the object pointed to by x where field1 has the value 0") would really benefit from some graphics. Nothing fancy, something similar to what the Rust book does for ownership would help.
https://doc.rust-lang.org/book/ch04-01-what-is-ownership.htm...
Re: Skip: A programming language to skip the things you have already computed
#88Re: Skip: A programming language to skip the things you have already computed
#89Skip was meant to gradually replace Hack, but the FB codebase turned out to be too tangled to gradually convert to the reactive paradigm, and a big rewrite was not possible, so FB pulled the plug, then Julien kept on pushing the project independently.
Re: Skip: A programming language to skip the things you have already computed
#90Guessing if something has side effects instead of making it explicit makes me already want to run away when I think about debugging.