Not really.
I’ve just read that thread again. And most arguments there for globals are weak and don’t survive a second view.
But I admit that both attempts (globals vs. locals) have their own benefits – and pitfalls.
I would say, that the benefits of local restricted Properties clearly overweight.
Hoping you don’t feel offended, I would call it a “dirty workaround” that’s full of pitfalls.
It’s so: I see that there are problems with locals only.
But globals cause more, and also more complex, problems.
What I could imagine, is that SOME Properties could easily work global.
Creation date is such an example.
I believe nothing can go wrong if this Property’s scope remains global (I can be wrong, the devs will know it better).
But my already given example:
Temperature: 50
Temperature: 50
is a trouble maker if one of these Properties comes from a Space of an USA guy who means the values in Fahrenheit, while the other (but identical named) Property comes from a Space of a Europaen who means them in Celsius.
Either you hold them somehow separate, but then you can’t show them in one single column (then you have no benefit from their global scope), or you merge them into one single Property with global scope and you’ll get problems.
This is only one example.
And it doesn’t help to do what you’ve suggested (embracing one Property’s name), because in this moment, you have de facto made two separate Properties with slightly different names, so that they cant become shown in one column of a View (except you use a Mini app that merges them). So, no benefit from the global scope.
No matter what we do we, will always have this or that problem.
But it’s meanwhile clear for me, that globals are the much bigger trouble makers.
If you have encapsulated data, you have much more possibilities to do whatever you want with them. In case that’s necessary, a Mini App can help a lot.
But if you merge them deep down in the data structure (globals), you spill beer into spilled milk and you have a hard time to get the beer into the fridge.
As long as the beer remains in its bottle and also the milk remains in its container, you have way more freedom to make with them whatever you want.
You can hold them separate, or you can mix them in a highly controlled way.
– Nevertheless, I appreciate that you put your thoughts into the community!
You’re always very welcome and I like your input!
We all have our opinions. And I was once in your fraction (pro globals). But meanwhile, I’ve changed my mind completely and I believe I’ve understood the principles, that I did not even saw before.
And honestly: now, where I’ve understood the principles, I could bite myself that I’ve never seen it before!
Yes, there remain some problems (no matter what we do).
And that’s the reason why a hard migration is necessary, even if it hurts.
We must get rid of the nasty globals and all the other ballast from stone age. Only then we’re free and can finally enjoy a zippy, lively App that simply works without frictions and without issues if it comes to import/export, backup/restore and so on.
You also wouldn’t want to run a Windows 3.1 computer today.
Btw.:
Actually I try to put more or less “real” data into AnyTwo, that are connected to each other, similar to my real Anytype space.
At the moment, I try that with my music Collection.
Each song has an artist. In some cases even more the one (cover versions).
And because most of my music comes from YouTube, each song is also connected to an YT-Channel.
To manage that, was never really convincing in Anytype.
But in AnyTwo, by using a new principle that I haven’t shown in a video yet, I was able to improve the old functionality without having more effort to manage everything.
AnyTwo solves here some problems that I’ve always had.
There are still two flaws (unfinished functions), but I’ve already reported them so that they become solved quicker.
As you already know, just today came version 0.1.5 and it was a HUGE update where so many things became improved!
Even scrolling thorough the long list is a little exhausting. Unbelievable how fast the devs work!
And it was a pure joy to see how many of my own reports and request have become done!
And the work flow now:
Things that have been for me always a 15 seconds slow task in Anytype, are now a quick and frictionless feeling “click, click, click, ready” -thing in AnyTwo!
Still things to do for the devs, but the target line is not only in sight, it’s already half in reach.

