A (USA) Decillion is … 10000000000000000000000000000000000
Just a thought
TT
A (USA) Decillion is … 10000000000000000000000000000000000
Just a thought
TT
We’ll probably need to optimize the <$list> widget a bit first.
Number of stars in galaxy:
1000000000000000000000000
@Mark_S, with your dedication and @jeremyruston’s resolve I’m sure you could create the needed 1,000,000,000, stars to solve that minor problem.
TT
I think the bigger problem than the number and the name “10000000000000000000000000000000000” is how big you want each to be in size?
That would be possible with lazy loading I think, and running filters on the nodejs side.
If this is achieved, I will store more raw data in the tw and run more automatic analysis scripts!
Because I’m modest.
Kisses, J.
The width of Mount Rushmore in inches minus the length of my left little finger times 417 to the power of Ramsay…
I think this is an important discussion to have. UI changes and addon feature demands will keep changing with the trends, while the need to store more data will be an eternal demand.
Let us consider the existing scenario. There are [public Tiddlywikis that are close of 50 MB in size and 15000 tiddlers](https://h0p3.neocities.org which are reasonably fast in delivering content. However you can see the fractures when it comes to searching, hover previews and long dynamic lists. @h0p3 seems to have avoided a dynamic Table of Contents. Many of the lists are statically managed. I do not know if it is an intentional tweak to avoid further performance issues.
Imagine someone who takes 20 notes per day. In a year, that is close to 7500 notes. In ten years we reach a figure of 75k notes. Let us give it a comfortable blanket of 33% and make the number 100k. In ten years, I hope to upgrade my existing hardware and there will be considerable gains in browser performance. So these are my arbitrary limits which I consider reasonable - I should be able to use my existing laptop to manage a personal knowledge base of 100K notes for the next 10 years. Naturally the questions are:
Reference: A recent post in GG by Siniy-Kit - a long term and one of the most creative users of TW5
Your whole reply is really good! I need think about it a bit to reply to it well. My OP was a bit silly, but not too off the mark. I do think “looking ahead” is a good idea. If one thing is sure it is that “data capacity” exponential expansion is the singular hallmark of how computerisation has gone. Some of the detailed points you make are very much on-the-ball.
I will try reply later.
Best, TT
Good bit of ball park estimates here. At least if one has only one tiddlywiki. I have found it easy to “divide and conquer”. Divide a large wiki into more than one around structured areas, context etc… Smooth the interaction between wikis with some of the many interwiki features and tricks along with a search wiki with indexes to other wikis.
Throw in the file uploads plugin, skinny tiddlers or a node server for good measure, and stir.
I could name many other methods that can be made easy to use or automated.
Even the sky is not the limit with tiddlywiki, only our combined imagination.
Ciao @anon9140225, I can’t add much to your excellent post.
One thing though is it’s very likely that there will be significant expansion in ways to get text in. A big one being “speech to text” … For the avid journaler I could imagine them speaking to a TW many, many times a day … “TiddlyAlex, create a record. I just ate breakfast. Stop.” My point? I think increase of volume of inputs could escalate once some of the limitations of typing are overcome.
Just a thought!
TT