Linked by Thom Holwerda on Sat 11th May 2013 21:41 UTC
Windows "Windows is indeed slower than other operating systems in many scenarios, and the gap is worsening." That's one way to start an insider explanation of why Windows' performance isn't up to snuff. Written by someone who actually contributes code to the Windows NT kernel, the comment on Hacker News, later deleted but reposted with permission on Marc Bevand's blog, paints a very dreary picture of the state of Windows development. The root issue? Think of how Linux is developed, and you'll know the answer.
Permalink for comment 561488
To read all comments associated with this story, please click here.
RE[11]: Too funny
by Alfman on Tue 14th May 2013 02:08 UTC in reply to "RE[10]: Too funny"
Alfman
Member since:
2011-01-28

satsujinka,

"How would implementing an SQL database on top of plain text be less flexible and less accessible than SQL? That is plainly a contradiction."

That's not what I said, I said if you were to build your own custom database over top file system primitives, it's unlikely to be as flexible or accessible as an SQL database. The applications that I know of which do use a file system database are quite limited and not even remotely close to being SQL-complete (for example postfix mail queue). Anyways, given that all text logging systems to my knowledge use a flat files and not a file system database, I'd like for us to move past this particular issue.



"A CSV variant (i.e. DSV) is already understood by the standard tools. So considering MySQL uses CSV, there's no reason why we couldn't implement a query engine that can co-exist with the standard tools. And why not provide that compatibility if we can?"


The thing is, once you have data in a database, you wouldn't ever have a need to use the standard text tools to access the data since they're largely inferior to SQL (unless of course you didn't know SQL).

I don't object to your choice of using a text database engine if you want to. CSV is often a least common denominator format, which is simultaneously a strength (because it's pervasive) and weakness (because it lacks alot of the more advanced features a database can normally provide). But the choice is yours to make.



"Performance issues are a different matter. For log files, there probably won't be any problem... however, as I've said already; you can do indexing on plain text. You just have to add the appropriate semantics to your text format."

How do you index a plain text file using standard tools and then go on to query your records via that index? Wouldn't you need to write customized scripts to build and query the index? It seems to me that you need to rebuild custom tools frequently every you want to do something that SQL has built in.

Reply Parent Score: 2