31–40 of 129 posts
What is the benefit compared to the private use of Redis? Redis is under BSD licence and continues to be very actively maintained and used.
On the other hand, using redis (/skate) for storing files was the inspiration for creating kvass.
The built-in server and remote support is pretty nice! API seems solid, and I dig the QR codes.
Earlier quoted context omitted.
The name can be read as an acronym of ‘Key-Value ASSociative store’, but also alludes to the beverage: https://en.wikipedia.org/wiki/Kvass
Picture in README.MD really tells you that author is aware of kvass (the drink). This repo actually made me google up that wiki page to get an answer: "Is this drink really called kvass elsewhere, not only in my country?". Yes it does it seems.
For personal use, I’ve had good luck storing things in files. Then when I need those those things, I read the files.
This seems unnecessarily snarky. You can make anything sound silly by reducing its functionality to the most basic level possible, ignoring all aspects of ergonomics and packaging. And you could make this comment about any storage engine. Like the infamous Dropbox comment here.
Earlier quoted context omitted.
This seems unnecessarily snarky. You can make anything sound silly by reducing its functionality to the most basic level possible, ignoring all aspects of ergonomics and packaging. And you could make this comment about any storage engine. Like the infamous Dropbox comment here.
Fair. The project could do a better job of explaining what benefit is it has over the file system API.
And syncing between file systems across a network is hard. (Before you say it's easy you can just do X, Y, and Z... remember that infamous Dropbox comment.)
For personal use, I’ve had good luck storing things in files. Then when I need those those things, I read the files.
This seems unnecessarily snarky. You can make anything sound silly by reducing its functionality to the most basic level possible, ignoring all aspects of ergonomics and packaging. And you could make this comment about any storage engine. Like the infamous Dropbox comment here.
A simple one paragraph why at the top of this project's README wouldnt be amiss.
Earlier quoted context omitted.
This seems unnecessarily snarky. You can make anything sound silly by reducing its functionality to the most basic level possible, ignoring all aspects of ergonomics and packaging. And you could make this comment about any storage engine. Like the infamous Dropbox comment here.
Dropbox explained itself pretty well. A simple one paragraph why at the top of this project's README wouldnt be amiss.
> Its trivial to set up and operate kvass across multiple devices
> remember the file we stored earlier? Let's get a shareable url for it!