4 ms·
It's still very much used at SkipLabs. In fact, it's the language that SQLive is written in: http://sqlive.io http://sqlive.io Unfortunately, we use a propriet
by julienv 5y ago
It's still very much used at SkipLabs. In fact, it's the language that SQLive is written in: http://sqlive.io http://sqlive.io
Unfortunately, we use a proprietary fork of SKIP, so that's why the OSS project looks dead.
We might open-source our version some day, but no plans for now.
- jerye 5y agoThis sounds interesting... Though it doesn't seem like that domain is working.
- julienv 5y agoFixed! thanks!
- interpenetrate 5y agoIf 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 problem and that you can share your work.
- julienv 5y agoThanks! You can try the version in the site for testing if you want! If you want to build something, let us know!
- FridgeSeal 5y agoCheck out the work Materialize is doing as well - similar vein.
- interpenetrate 5y agoI did just that recently. They certainly seem to offer the most complete solution. Definitely worth keeping an eye on. 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?
- andrenotgiant 5y agoThanks for trying Materialize, (I work there!) What bugs did you run into with the Postgres Source? If you put them in a reply here or an email to andy@materialize.com we would be very appreciative of your feedback.
- interpenetrate 5y agoThanks for the reply. I'll make some time this weekend to reproduce my issues and send them your way.
- netfortius 5y ago... "proprietary fork" and "might open-source"... let us know when you change your stand
- vrotaru 5y agoWell Julien Verlaguet is the original author of SkipLang, so "proprietary fork" does not deserver the square quotes, IMO
- pure_simplicity 5y agoCitation to indicate what he was responding to, not scare quotes.
- samatman 5y ago> indicate what he was responding to I've started doing that in exactly this fashion `>*quote*\n`, precisely to avoid the er, mention/disparage distinction.