124816

7 ms·

31.
by 124816 16y ago
Most stats providers compute unique visitors using client-side cookies; not entirely accurate, but quite cheap. You're right though, it's a lot easier to use an existing (and free or nearly free) tool than to build your own.
32.
by 124816 16y ago
> I'd pay for analytics... You could just take how much you'd pay for analytics and buy some ads. :-)
33.
by 124816 16y ago
Alma Whitten might be uninformed. (Was this talk recorded? Do you have a link to it?) There are some options in the account UI that, if enabled, allow Google to do some analysis of your data. Link directly to their help center: http://www.
34.
by 124816 16y ago
> which is a spurious to start with -- simply documenting making an idea public is just as much of a defense The idea behind defensive patents isn't that they defend your use of that idea, but that they defend you from competitors who h
35.
by 124816 16y ago
I wonder what percent of those users have a 9700.
36.
by 124816 16y ago
I don't think it was ever released, was it?
37.
by 124816 16y ago
Many of these cars have a power button -- if the "key" is inside the car, the button is activated. When the car is on, and in park, it will turn off with a simple press of the button, but when in motion that does not work. (I've been told t
38.
by 124816 16y ago
Not sure if you saw the graph hidden in the side: "Complaints rose after Toyota recalled 3.8 million vehicles in November..." -- it makes the same case as you. Let's have an experiment: another manufacturer can institute a fake recall and s
39.
by 124816 16y ago
I know it seems retarded, but things like copying second life cost the company pretty little. Ten or twenty people's work for two years, thrown out and discarded. We're looking at a couple million down the drain. A lot for you or me, but no
40.
by 124816 16y ago
After several releases of your app, you'll have several wire formats in the wild. One of the main features of libraries like Protocol Buffers is that they can parse old messages, so you don't need to maintain an increasingly hairier parsing
41.
by 124816 16y ago
Both protocol buffers and thrift are primarily designed to handle older or newer messages (than your program was compiled with) gracefully. Speed and compactness appear to be secondary goals. (Especially for Thrift, which does not seem conc
42.
by 124816 16y ago
Going to reply to all your comments at this rate. ;-) Even with single-byte tags, the overhead can be quite significant; thus the packed = true option. Unfortunately I don't have any public protocols or data to show you, but by switching to
43.
by 124816 16y ago
Have you run benchmarks on this? If so, can you link me to them? It would be relatively easy to modify protobuf's parsing code to operate on the encoded byte rather than decoding field tags. If it's worth doing I'll do it. BTW, the default
44.
by 124816 16y ago
Protobufs allow you to define your service, but no RPC system is included.
45.
by 124816 16y ago
That weird new(T* )T(...) syntax is how you ask c++ to run the constructor of T on an existing T* . (In this case that T* would point to the stack.) Note that the memory at the T* shouldn't be a real T; or if it is, its destructor ought to
46.
by 124816 16y ago
Good post. Another focus of Thrift (and Google's "protocol buffers", its inspiration) is that modifying your RPCs in a forward compatible way should be easy and have well defined semantics. (Thus the need for a tagged-base stream.) And, old
47.
by 124816 16y ago
Looks like the main author of this is T.V. Raman: http://en.wikipedia.org/wiki/T._V._Raman Pretty awesome dude.
48.
by 124816 16y ago
This blog post is pretty incoherent. Backstory at: https://bugzilla.redhat.com/show_bug.cgi?id=581256 Looks like the Chrome guys want privs so they can increase the chance of renderer processes being killed if the OS runs out of memory. (
49.
by 124816 16y ago
Refresh often disables the cache, or at least does a bunch of if-modified-since requests. Better to type the url again and hit enter.
50.
by 124816 16y ago
I'm missing the back story -- tell me more about Peter Norvig's solver?
51.
by 124816 17y ago
Thanks for the tip. European law is relevant in this case as well, and I'm not sure it requires a strict monopoly over the market. That said, clearly if iPhones were a small part of the mobile ad platforms, nobody would care if Apple limite
52.
by 124816 17y ago
I have never seen "anti-competitive" being used in a positive light. A quick search shows it has mainly been used by prosecutors and plaintiffs to describe their adversary. You don't need to believe me though, here: http://en.wikipedia.org
53.
by 124816 17y ago
It would be interesting to know how coarse the data exposed to mobile ad providers is -- does anyone have any experience here? Were I implementing mobile ads, the precise location would stay on the device, and the information sent to the ad
54.
by 124816 17y ago
Nope, sorry. This has very little if anything to do with the user. Apple wanted to buy Admob, but Google got them instead. This change will prevent Admob ads from being well targeted on iPhone, and will prop up their (assumed to be upcoming
55.
by 124816 17y ago
This is fine, if you're OK with missing bounces. If the page takes a long time to load, or hangs, then it's likely the user will close the window before the script runs.
56.
by 124816 17y ago
Several browsers, including many versions of Firefox, had a bug relating to the status bar. The "waiting for ..." would only update after the first byte had been received from the next file. Thus, a slow resource would leave the status bar