This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
7756
Off-topic / Re: Post count fever
« on April 6th, 2011, 08:05 PM »In my tests serializing/unserializing a 1.5MB array was as fast as including a file with that array, which was much faster than JSON..for some surprising reason.
I benchmarked it a bit back and found that it was fastest to json_decode the array but the entire array was nested arrays of numbers, and we're talking a 26k string when JSON encoded. (Remember, for the majority of the time, the hurt of serialize isn't an issue, it's the hurt of json_decode vs unserialize vs raw array that we're interested in)
7757
Off-topic / Re: Post count fever
« on April 6th, 2011, 05:42 PM »
Putting it in the members table (and thus yoinking some of it out of the themes table) strikes me as generally a good idea.
Performance wise the cost is not too significant; if it were the only column in the members table that was a text column (as opposed to a varchar) I'd definitely be insisting on it being a separate table (whether that's one row per member or one row per setting per member is another matter)
Don't forget, we already have the themes table doing that, and while there's a semantic issue, it's worth remembering that for a lot of it, anything stored there for the user will be loaded automatically for them on bootstrap, so unless you have a lot of settings, it might be worth just reusing that.
serialize is good, but I've recently been hearing a few concerns about performance of it (especially compared to the json_* functions), though it's incredibly convenient for storing variable schema information (e.g. log entries that may or may not require more data than is normally available)
Performance wise the cost is not too significant; if it were the only column in the members table that was a text column (as opposed to a varchar) I'd definitely be insisting on it being a separate table (whether that's one row per member or one row per setting per member is another matter)
Don't forget, we already have the themes table doing that, and while there's a semantic issue, it's worth remembering that for a lot of it, anything stored there for the user will be loaded automatically for them on bootstrap, so unless you have a lot of settings, it might be worth just reusing that.
serialize is good, but I've recently been hearing a few concerns about performance of it (especially compared to the json_* functions), though it's incredibly convenient for storing variable schema information (e.g. log entries that may or may not require more data than is normally available)
7758
The Pub / Re: Wap2, imode?
« on April 6th, 2011, 03:12 PM »Think radical, that is how inovation takes place.
Dammit just zip me a copy to run on a local server so i can feast my eyes. The anticipation is killing me.
7759
Off-topic / Re: Post count fever
« on April 6th, 2011, 03:11 PM »
Like I've said before, did it not occur to you that some of these things have occurred to us?
And no, if you think putting the entire thing into a single class is a good idea, you probably misunderstood the point of objects.
And no, if you think putting the entire thing into a single class is a good idea, you probably misunderstood the point of objects.
7760
The Pub / Re: Wap2, imode?
« on April 6th, 2011, 10:50 AM »look at the source on a facebook page. the whole thing really is some form of java. and the server picks up on what version it needs to prepare and then sends it.
The other thing is most of that JS is used for semi-realtime updates against their massive server farm of which the PHP is mostly compiled with Hiphop; neither of these things (server farm, compiled PHP) are available to the vast bulk of users who would use Wedge, and I'm damned if I'm going to spend hours and hours trying to explain to idiots who just can't or won't read how to install it. Been there, thanks, I used to be support for Sphinx, the search component, and that was bad enough on trying to get people to compile it.
One other word that springs to mind with JS: accessibility. Show me a decent visual-impaired browser that can handle all the changes Javascript makes to the page without screwing it up and I'll show you many, many more users who don't have that.
Yes, it's all well and good to shoot for the stars and kick off a whole new paradigm, but that isn't where we're going, not yet. Wedge 1.0 is the retooling of SMF with new features and overhauling a number of things that should have been done years ago, not paradigm shifting.
7761
Off-topic / Re: Post count fever
« on April 6th, 2011, 10:45 AM »
Some of the DB structure changes have already begun; board access isn't stored in the boards table any more for this reason. Membergroups is the other biggie that needs to change.
7762
The Pub / Re: Wap2, imode?
« on April 6th, 2011, 02:33 AM »you got to remember, each client has a computer also. :)
if the server is running thin, pass it to theirs, they got plenty. :D
7764
The Pub / Re: Wap2, imode?
« on April 6th, 2011, 01:04 AM »
Given that there are currently absolutely no mods that work on it... it doesn't have one.
7765
The Pub / Re: Wap2, imode?
« on April 6th, 2011, 12:47 AM »dont even have the final list of what will be in wedge
whats wedges aeva
7766
The Pub / Re: Wap2, imode?
« on April 6th, 2011, 12:32 AM »
No, the idea to put good stuff into Wedge and keep out stuff that while cool, is impractical.
7767
The Pub / Re: Wap2, imode?
« on April 6th, 2011, 12:27 AM »Oh, I like that idea. Let's put it in Wedge! :niark:
7768
The Pub / Re: Wap2, imode?
« on April 6th, 2011, 12:20 AM »
Oh, don't get me wrong, I like hearing some of the ideas that are floating about, but there's a distinct divide between what's a cool idea and what we're going to add to Wedge.
7769
Off-topic / Re: If this is "The Pub"...
« on April 6th, 2011, 12:19 AM »* Arantor has a big scary shiny Meat Loaf mug to drink tea from, when he's not using the nice cups with dragons on...
7770
The Pub / Re: Wap2, imode?
« on April 5th, 2011, 11:48 PM »
That's the thing: I think pragmatic, not positive. A project I was working on towards the end of last year had to be scalable, by which I mean, single server, handling tens of thousands of concurrent live connections, and run it in PHP - I've been there, seen what's involved in making stuff like this work. It's specialised at best, at worst... it's that step beyond.