6 ms·
Just before yesterday, I read an article here praising the "Offline First" principle. And as for everything related to software, I am reading again what was goo
by begueradj 5y ago
Just before yesterday, I read an article here praising the "Offline First" principle. And as for everything related to software, I am reading again what was good is bad, and what was bad is good. All you have to do for a successful clickbait is to wait until someone shares his opinion so that you can finally write something against it... (most of the time, just for the purpose of saying you're against)
- esrch 5y agoThe other article you mention comes from the same website: https://rxdb.info/offline-first.html https://rxdb.info/offline-first.html. It's in an opinion section, giving the arguments from both sides.
- typingmonkey 5y agoYes. I have written both of them, mostly to make sure I trigger 100% of people, no matter if they like offline first or not. I mean, read all these comments on both articles. People say offline first does not work, then they say that every software is offline first by default and it is nothing new. It was totally worth it spending two 3 days on it :)
- somenewaccount1 5y agoAnd you know what, I AM triggered! I feel like you missed the most important point of "offline first" is that your data belongs to you and does not need to be shared to the cloud in order to have tremendous value. The code/logic to enhance your data should be shipped to you, rather than the other way around.
- typingmonkey 5y agoThat gave me a smile :) Yes, I totally missed this side of the dice. Having your data stored locally, being in control, being able to reset the state to it's origin, export the local state as json and import it somewhere else, knowing what is stored and how long.
- 9935c101ab17a66 5y agoHahahaha, the same author is responsible for both of them. It's weird to see someone start ranting about 'clickbait' when this is in fact the opposite. The original piece advocated for an `offline-first` approach with RXDB. This piece (also a part of the RXDB docs) openly and transparently acknowledges reasons why the RXDB methodology might not be for you. > And as for everything related to software, I am reading again what was good is bad, and what was bad is good Before baselessly accusing someone of writing and submitting clickbait, maybe spend a little more time reading the content and evaluating the context.