News for hackers. Stuff that matters.
Re:Always bet on text by monstermonster on Tuesday October 14, 2014 @05:26AM (#8452603)
Counterpoints to show that it is just a compromise: The complexity of unicode, collation, encoding, translation, language.

However you're 100% right!

Our application actually used text files on a network share with an indexer over the top as the database engine a long time ago. It worked really well and integrated with NT security and file locking for concurrency control, plus it was very easy to back up. A work of genius. However, NTFS doesn't scale well with lots of small files as it stores them in the MFT so it fell off a cliff eventually.

Re:Always bet on text by embolalia on Tuesday October 14, 2014 @09:25AM (#8453267)
Counter-counterpoint: all of your counterpoints exist or have equivalents in every other form of communication. You swap unicode (which is nearly universally agreed on) for H.264/Theora/VP8 and AAC/Vorbis/Opus, and you still have to deal with collation and translation/language (which, without transcription to text first, is pretty hard).
Re:Always bet on text by yawaramin on Tuesday October 14, 2014 @08:27AM (#8453076)
Would your app have been feasible then with something like SQLite?
Re:Always bet on text by monstermonster on Tuesday October 14, 2014 @10:49AM (#8453637)
We used something similar in the end I.e. SQL Server Compact Edition and sync the data with a master SQL Server instance.
Re:Always bet on text by autokad on Tuesday October 14, 2014 @09:46AM (#8453346)
i seen companies get around that limitation by storing multiple files into a compact file
Re:Always bet on text by monstermonster on Tuesday October 14, 2014 @10:52AM (#8453656)
Yeah we do that now. We store them in a big file in pages that contain rows and an externally visible network process allows us to manipulate the things.

(sql server)