monos

i'm never quite sure how important replication is for a DB to succeed. up until recently i didn't need it, and now oracle provides master/master - so that's transparent for me. and i don't have to worry about how to setup the apps to be master/slave aware.

who really is using mysql replication. and how interesting was a master/slave setup - the only kind of replication provided up until 4.1 (2004). i would imagine if you know howto setup your apps to work with only one master, you would know about postgres.

would really be interested if any middle-sized (not slashdot) websites use mysql replication (which setup) and since when.

yeah, and all the rules read to me as being aimed towards "have mercy with the reader", which applies to writing code as well :)

hm, my xmonad shows gimp with multi windows free floating. wich makes more sense for the current gimp.

maybe i'm thinking of the wrong kind of content they want to crawl, but isn't it easier to provide special crawlable, plain html pages (possibly hidden to users or provided as an "accessible" version).

it's an easy to understand piece about the advantages of win7 vs winxp, as perceived by the average (definitly not HN-reading) user.

that, for me, reads like the ads on TV selling drugs.

please ask your doctor / sysadmin which OS to use, not that guy on TV / tech column. or else we will make fun of you.

sorry for ranting so much, but it drives me crazy. my girlfriend actually was asking about windows7, how much she needs it and how much better everything is going to be.

of course i will encourage every normal person i know to install windows7 (just to get rid of IE6 within the next years, hopefully).

exactly.

part of it reads as if he was defending it against macos (mentioned it 6 times).

then he describes in excruciating detail small GUI improvements that gnome (or any other wm i guess) pushed through in 6month (oh wow windows-previews in the taskbar).

he admits that in the area of networking there is still room for improvement but at least "now you can see all available wireless networks by just clicking on an icon in the taskbar". way to go!

but windows wins in other areas: windows7 has "some of the same kind" (!?) of multitouch gestures the iphone made popular. yeah.. how would i even..

Compatibility is also satisfactory: firefox, adobe, etc. work. good job MS! though he fails to mention that they don't work out-of-the-box. how could they: they are not in the box.

let's just hope their migration plan gets better when the next BIG THING gets pushed out in 10 years... or so. improving shouldn't be hard: it's not possible to upgrade without whipping your HD - assuming you now have an XP install.

oh right: that's basically everybody.

right, thx.

doesn't change the diagrams in the linked article though, they are images: http://www.digitalbuzzblog.com/wp-content/uploads/2009/10/Br...

the general trend is probably correct - social websites are gaining moment. still i don't like these graphs.

we can not measure visitors (only devices, but you can do some statistical approximation - that's what they do for sure). but this gets even vaguer if you are not the owner of the site and don't have total access to all data.

we don't know how google calcs those "numbers", not even how they get approximated (they are not really statistics - Y axis is not labled).

it could very well be - and probably is, i've been in the webstats buiz - that the way they come up with this is by adding some artificial, best-guess multiplier to correct for not having enough real data.

---

the way to do those web statistics right is:

* have an open consortium with all the major players come up with an algorithm that satisfies them [1]

* apply that algorithm, it will output numbers that are in some correlance to the real, but unobservable truth [2]

* more important: the statistics of those websites are now comparable to one another. because the algorithm & factors are the same for everyone [3]

* rinse, repeat, adapt

[1] it is unlikely that they will publish this algorithm, since it will contain strange, seemingly arbitraty factors like "multiply by 1.2 during summertime, because people are less online and we don't want tooo much of a down curve"

[2] like "visitors" or "time spent on site"

[3] no, we don't know that's the case with google's data

I know what you mean. When I have lots of event-handlers in a prototype I like to assign

  var self = this;

but that's bikeshedding

sorry, but why would carry the extra _obj around? why not simple do it like in my example above?

easiest & most flexible is still this:

  var myNamespace = {};
  myNamespace.foo = function() {
      var privateFoo = 1;
      this.publicBar = "test";
      
      var privateFn = function() {};
      this.publicFn = function() {};
      return this;
  }

  // usage
  myFoo = new myNamespace.foo();

as crockford says & in my experience http://javascript.crockford.com/private.html

this also allows you to do prototypal inheritance, which is not possible with other "module patterns" - whatever that is, they are just singletons.

also:

http://dev.opera.com/articles/view/javascript-best-practices...

agreed.

rules on serverside are a bit different. especially the module pattern is a must there.

in the future you might be able to pick one of those module loaders http://wiki.commonjs.org/wiki/CommonJS

pretty pretty please

this is exactly the wrong answer. i guess you are trolling.