Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "crdt"
So we are a development company, we have some remote coders.
This one is very good coding BUT
Sometimes he disappears and then comes back with an history, the other day he said his grandpa was about to die of cancer so he had to go to see him.
Three days ago, he had to finish a landing page manager, in React. just a form and unzip (nodejs server side) the files... It was not so difficult.
He said was going to finish later that day.
Then he disappeared, for 3 days!
And i got a message from him on facebook saying he got robbed and he was going to rent a laptop to continue working.
Then i asked if he had any progress on the code before that happened. and he started sending
me screenshots of the code , but in one screenshot i was able to see a part of the desktop background. Checked on the history of files @ Slack and that was his background lol.
Please guys , don't do these kind of things.
If he had told me that he needed to study or something i would have understood him
Now i feel i cant trust him anymore.
Moral: Lies/attitudes like these one can have a big negative effect on your life and you will miss some big opportunities!10
It promised full-blown CRDT functionality. So I decided to adopt it.
Disappointment number one: you have to use CouchDB, so your data model is under strict regulations now. Okay.
Disappointment number two: absolutely messed up hack required to restrict users from accessing other users’ data, otherwise you have to store all the user data in single collection. Not the most performant solution.
Disappointment number three: pagination is utter mess. Server-side timestamps are utter mess. ANY server-side logic is utter mess.
Just to set it to work, you need PouchDB itself, websocket adapter (otherwise only three simultaneous syncs), auth adapter (doesn’t work via sockets), which came out fucking large pile of bullshit at the frontend.
Disappointment number four, the final one: auth somehow works but it doesn’t set cookie. I don’t know how to get access.
GitHub user named Wohali, number one CouchDB specialist over there, doesn’t know that either.
It also doesn’t work at Incognito mode, doesn’t work at Firefox at all.
So, if you want to use PouchDB, bear that in mind:
1. CouchDB only
2. No server-side logic
3. Authorization is a mess
4. Error logs are mess too: “ERROR 83929629 broken pipe” means “out of disk space” in Erlang, the CouchDB language.
5. No hosting solutions. No backup solutions, no infrastructure around that at all. You are tied to bare metal VPS and Ansible.
6. Huge pile of bullshit at frontend. Doesn’t work at Incognito mode, doesn’t work at Firefox.8
It's almost 2 am now. I was up till now, trying to make pouchdb and couchdb cross-domain authentication work.
The whole replicable state of art needs a hero, the one no-backend solution that actually works and don't make you lose sleep.