plq

A quick google shows that there's still no way to disable browser cache in Chrome. How do you work around that problem? Or is it already fixed?

Syslog is definitely not on its way out. It's been in use for 30 years because it works. Perhaps this is rather Redhat trying its hand at the embrace & extend game by introducing proprietary tools? Forcing staff to train on such technologies (with pretty yet dysfunctional guis) will make migrating to other systems harder.

As for the free-form text "problem" this solution claims to address: Different daemons produce logs in different format simply because one's data won't fit in another's schema. And you can actually live with postfix and qmail producing logs in different formats about the same event because you have strictly one of them installed in your server. And in my experience, switching from one to another is a huge undertaking where rewriting your regexp hacks is a drop in a bucket.

What is the gibberish between 31.000 and 36.000 feet supposed to mean? Just an oversight?

the true facebook killer is going to be a "social markup" standard and its many implementations that has the potential to surpass the power the facebook platform gives to the advertiser, not another centralized service. (note how hosting your own social hub elegantly solves any privacy concerns you might have) given the amount of work that goes towards this (not much), I don't think facebook has much to worry about.

sigh. For how long will every paragraph from the Steve Jobs biography be buzzed as news? Just buy and read it, I'm pretty sure it'll be well worth both your money and your time.

Actually, it's from the same guy who implemented protocol buffers when he was at google. He re-implemented a better protocol buffers for facebook and chose to call it Thrift.

Assuming you mean "were cut-throat and sometimes downright rude [against employees]", I'd guess it's mostly because talent is much scarcer today than it was twenty years ago.

Disclaimer: I have never owned a handset from a maker other than Nokia :) I just want you guys back to the smartphone game.

> On the one hand, maintaining two OS teams for the same hardware would be a waste of resources.

Nokia will have to make a very serious platform decision in the not-so-distant feature. If resources spent on developing both will place that decision on sound arguments, I say it could be worth it. The tech scene is not (yet) persuaded that Meego is a dead end and a re-invented, unproven Windows Phone platform is the last chance to save Nokia.

Here's my dream scenario: Nokia offers the same hardware with two different OS selections and also has Qt working on both Meego and WP platforms.

This would obviously be a win-win situation for both the developer and the user. But this would be beneficial for Nokia as well, because:

1) It'd provide Nokia with hard data based on sales and user feedback on which platform performs better in real-world scenarios. Currently, the decision to drop Meego for WP platform is mostly based on "hopes and promises".

2) Having both platforms compete on even terms would also improve the overall Nokia experience on both platforms as this open and fair competition would motivate both the Microsoft and the Meego teams to do better.

So, why this wouldn't happen?

Why not put the version in the domain name? v1.api.example.com looks legit, and also implies that the api versions are indeed handled by different subsystems.

Avoiding SSL on the grounds of its overhead is premature optimization. Unless profiling reveals that the SSL overhead introduces significant delays (and the cost of getting a proper SSL Certificate is affordable) there's no reason to go without SSL.

That sounds nice but, what's the plan? The closest I could find was this: http://redmine.ruby-lang.org/projects/ruby-20/roadmap

i don't understand why codesearch has to go. granted, it felt a bit neglected lately, but it was truly useful.

i wish there was a way for google to open source their abandoned projects. i'm sure someone would be willing to offer a similar service by basing it what the google code search already does.

i wonder how the embedded sql syntax would handle multiple database connections.

the world is a scarier place now.

a moment of hush for mr. jobs.

I like how the buzz around server-side javascript is progressing slowly from "the next big thing!!!" to "okay, it has its shortcomings".

You will pry Python from my dead, cold hands :)

as usual, opera was first to implement that, a looong time ago. it also has auto fit width/height options, so i think it deserves a try as well.

congrats on launching! why not eat your own dog food and start a [sticky] list for feature requests? i think it'd be a nice way to get early adopters get hooked up.

Is it me or does this mean "cookies that can't be undeleted" contrary to the intended "cookies that can't be deleted"?

One should rather say "Non-deletable cookies".

me too, i like php. it's a decent templating language with some very advanced features. it even supports namespaces!

this is sure one hell of an explanation. here's a shorter one from me:

simply put, you need metaclasses when you want to overload the "instantiation operator". the __new__ in a metaclass is used for making changes to a class before instantiation, and __init__ is used for making changes after instantiation. the implicit first argument to __init__ and other instance methods in a metaclass (conventionally called self) is the implicit first argument to class methods in the metaclass instance (conventionally called cls)

note that "metaclass instance" and "class definition" are synonyms.

i can't think of a use case where __call__ would be useful, because it's technically the ctor of the metaclass instance. also, i think that using callables other than 'type' subclasses is being too clever with an already complicated concept, so i'd avoid doing it.

this is based on my practical experience with metaclasses, so i might have missed something. but that's all i'm using metaclasses for anyway.

While Apple's decision to not include Flash in IOS devices arguably accelerated its demise, Flash is going to be obsoleted by HTML5 at some time in the future anyway. So I wouldn't put it this way.

Flash going away is beneficial for Adobe as well, as they'll have one less cross-platform virtual machine to maintain that they distribute for free anyway.

Yes, but I guess they're rather looking for people who value the goal and not the path.

> I think I remember reading (someone correct me if I'm wrong) that broadly generalized, microkernels have better security at the expense of performance, vice versa for macrokernels.

that's true, but the "security" is not really what we perceive in the post-google, massively distributed era.

microkernels made sense back when key to uptime was hot-swappable devices. e.g. if your nic goes awry due to a hardware problem, it can crash its driver. in case of a monolithic kernel, this would in turn crash the os, whereas with a microkernel, the rest of the system should continue humming just fine. this makes replacing the failed component possible without causing downtime by shutting down the single node the service runs on.

but nowadays, we know how to set up systems so that taking down an entire node (gasp!) won't harm the operation of the service as a whole. so i don't think microkernels are that relevant anymore.

Basically, a <2kg laptop pc with ~13" screen with a 64-bit Intel CPU with decent linux support for critical devices. This generally means Nvidia GPU and NICs with intel chipsets.

While I like my gear efficient and portable, I don't know why I'm still on Gentoo.

google also records which search results are clicked by the end users, which is simply an implicit "like" button that was there since the beginning.

however, it looks like they've shipped 3.4.0 with a bug that randomly deletes filtered rows. (see here: https://bugs.freedesktop.org/show_bug.cgi?id=35345)

i don't want the "don't trust point-oh releases" mantra to stick around. we have release candidates for that purpose. i hope they'll improve their release policies.

i kind of expected this to be a more serious attempt at solving the current state of privacy policies being "hidden" behind overly long and complicated documents.

i think it's a brilliant idea to have a few standard privacy policies and/or terms of service documents where the service provider just fills in the blanks, a la GPL or BSD licenses.

seeing "our privacy policy is FPP" on a web service where FPP is a hypothetical document blessed by a reputable privacy advocacy group would certainly increase the appeal of that service amongst the ones who care.

one good property of xml is that it's also a database. it can be queried once inside, say, postgresql's xml type.

json lacks that level of support from mainstream relational databases, which makes it a waste of time for certain use-cases.

I kind of expected the XML to disappear in level 3. In its current form, this is a non-standard extension to HTTP.