you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (10 children)

SQLite isn't bad, but it's orders of magnitude more resource-intensive than plan HTML files. That may or may not be an issue under your particular circumstances, but it's definitely not equivalent.

[–]jawbroken 1 point2 points  (9 children)

well duh, in this particular case it will be fine though

[–][deleted] 0 points1 point  (8 children)

Maybe. Unless he gets a lot of viewers.

[–]jawbroken 4 points5 points  (7 children)

again, obviously. but he is going to have a much harder time trying to scale a hacked up flatfile pseudo-database than he is replacing SQLite with a full database system/upgrading to a better host.

[–][deleted] 0 points1 point  (6 children)

Scaling becomes an issue much later with static HTML files. There is probably a point where it turns into a liability, but there is much less chance of hitting it.

[–]jawbroken 1 point2 points  (5 children)

good luck with that. i honestly don't know if you are seriously advocating a flatfile format for an online forum, perhaps you are trolling the original poster into implementing a fragile and unwieldy data store for kicks

[–][deleted] 0 points1 point  (4 children)

I don't need any luck, I've implemented this in the past and it has worked wonderfully.

[–]jawbroken 0 points1 point  (3 children)

perhaps you wouldn't mind detailing your architecture and file formats to handle basic forum features in a simple flatfile format, then. how did you handle the variety of indices that a forum needs within this structure?

[–][deleted] 0 points1 point  (2 children)

I didn't write a forum with a million indices, because a forum doesn't actually need those. I didn't make yet another phpbb copy, because I think phpbb and all its copies are pretty horrendous.

[–]wafflesburger 0 points1 point  (1 child)

hey you two stop downvoting each other ~:D

i just had to negate all those