At 2:10 you say Capacities confusedly calls sets collections. But in Capacities a Anytype set is just a query. And collections in Capacities are Anytype collection limited to one type. In my opinion the terminology of Anytype is insanely confusing.
I am just starting to 'try' Anytype and I'm finding it insanely fucking annoying because of all of the random connections, objects literalling everywhere. It's hell for someone with ADHD and there's no simple way to nest a folder structure.
The comment about "passphrase nonsense" unfortunately disqualifies the entire video, as the author has not understood the core approach of Anytype and omits the most important point that Anytype has for itself: data security, encryption and (if desired) data locality. I myself also know the struggle of the complexity of the application, but to simply dismiss this core element with "passphrase nonsense" just shows that the examination of the application was not deep enough to be able to make a qualified comparison.
Interesting argument; I think my position might've been oversimplified with how I portrayed it. I have no issue with security features, I just find a combination of a few random words to be needlessly complex. To me, it genuinely feels like a way to be more unique, rather than more secure. The only difference between the passphrase and a password is that Anytype chooses your phrase, thus preventing people from reusing their favorite password. But I don't find this a compelling argument for why a passphrase is better than a password - it feels like a method of ensuring security, even for people who don't care, at the cost of convenience.
There's a vacuum left from Notion now that they are focusing on enterprise and collaboration. I think capacities will grow faster as their tradeoffs seem more in line with growth
I downloaded Anytype first. Ok. Futzed around a bit. Then it was on to Capacities. Capacities clicked with me. It was easier to understand. Once I started linking all the objects - Daily entry =>create Person=> and @meeting/date go back fill in Person details, it got robust very quickly. Then went back to Anytype to compare it and I was "wait, there is Audio.Ok. It has 'album' 'artist'...cool. How do I create an Audio object using it's assigned traits??!! Yep, it could be this ignorant user, but double you tee eff?
At 2:10 you say Capacities confusedly calls sets collections. But in Capacities a Anytype set is just a query. And collections in Capacities are Anytype collection limited to one type.
In my opinion the terminology of Anytype is insanely confusing.
I am just starting to 'try' Anytype and I'm finding it insanely fucking annoying because of all of the random connections, objects literalling everywhere. It's hell for someone with ADHD and there's no simple way to nest a folder structure.
That's the point. It holds data the same way your brain does, but with added search, tagging (way better than heirarchy), and graph relation viewer.
The comment about "passphrase nonsense" unfortunately disqualifies the entire video, as the author has not understood the core approach of Anytype and omits the most important point that Anytype has for itself: data security, encryption and (if desired) data locality.
I myself also know the struggle of the complexity of the application, but to simply dismiss this core element with "passphrase nonsense" just shows that the examination of the application was not deep enough to be able to make a qualified comparison.
Interesting argument; I think my position might've been oversimplified with how I portrayed it. I have no issue with security features, I just find a combination of a few random words to be needlessly complex. To me, it genuinely feels like a way to be more unique, rather than more secure. The only difference between the passphrase and a password is that Anytype chooses your phrase, thus preventing people from reusing their favorite password. But I don't find this a compelling argument for why a passphrase is better than a password - it feels like a method of ensuring security, even for people who don't care, at the cost of convenience.
@@pianomacpower Anytype people - especially the devs are always very hostile if you point out any valid issues.
I would love it if I could choose to make a property/relation global or tied to a specific object type. Anytype's relations library makes me crazy.
There's a vacuum left from Notion now that they are focusing on enterprise and collaboration. I think capacities will grow faster as their tradeoffs seem more in line with growth
tried both, ended up going back to using notion. I just couldn't stand their quirks.
I downloaded Anytype first. Ok. Futzed around a bit. Then it was on to Capacities. Capacities clicked with me. It was easier to understand. Once I started linking all the objects - Daily entry =>create Person=> and @meeting/date go back fill in Person details, it got robust very quickly. Then went back to Anytype to compare it and I was "wait, there is Audio.Ok. It has 'album' 'artist'...cool. How do I create an Audio object using it's assigned traits??!! Yep, it could be this ignorant user, but double you tee eff?
I already know the apps, but i don't feel like I unterstand your decisions.
I am not trying to be a ANYTYPE Fan but anytypes entire app is OFFLINE
Thanks
Anytype accound making thing is just plane better for security and that's what they are aiming for