11–20 of 148 posts
This is awful. Code Search is an indispensable tool for finding reference code and real-world uses of various libraries. I don't know of anything on par with it.
So sad to see this one go -- but I think it will make for another opportunity to allow a competing site like koders.com to iterate on building a product that developers would love to use...I hope.
sharing on google reader also shared on google buzz as well though.
buzz was awesome for link sharing via a bookmarklet to my professional audience (compare to facebook bookmarklet for life stuff). plus isn't there yet -- plus doesn't expose RSS feeds to work with my audience's existing workflows. damn. any word on a plus RSS api? i want my stream, and i want my +1 feed. i was looking into the +1 stream yesterday, seems like google made it as hard as possible to hit from javascript -…
You might like to take a look at Handpick:
You'll be able to create different groups of people to collect links for via a bookmarklet throughout the day and send them via a single email at the end of the day.
Krugle found no results. Koders found results, but the response time was very large.
Both have a long way to go in being a viable Code Search replacement.
Hopefully Code Search just gets rolled into the primary Google search product.
NOTE:
I was just looking over the Koders results. It is tokenizing 'pthread_t' as 'pthread' 't', so the top results are not what I would consider useful. I'm sure I can change some settings to get proper tokenization for my languages identifiers, but that is more work up front.
There's a competitor to google code search at least: http://www.koders.com/ Actually, I'm kinda glad they're phasing stuff out. It shows courage to do that, a lesson probably hard learned at google. They have a myriad of products, but would probably do much better with them if they thoroughly finished them before release.
does this mean google reader sharing now goes to plus? Me and a close group of friends use google reader a lot for sharing and commenting, personally more than i ever use plus or facebook. sharing on google reader also shared on google buzz as well though.
I'm glad it's all moving to +. I can only assume that sharing from Reader will be connected to + at some point. There's currently a workaround for this, but it's ugly.
There's a competitor to google code search at least: http://www.koders.com/ Actually, I'm kinda glad they're phasing stuff out. It shows courage to do that, a lesson probably hard learned at google. They have a myriad of products, but would probably do much better with them if they thoroughly finished them before release.
Yes, one of the things Larry Page talked about in the earnings call yesterday was aggressive project pruning and focus. I agree that this is a good sign of Page's leadership.
Edit to comment below:
"Trying and failing is a far better outcome than never having tried at all" is a great mantra for individuals or even small startups, but I am not sure how it applies here. I am still bitter over Google abandoning Notebook (which I was quite a heavy user of) and canning Calendar Public Search (search!!). I then reluctantly allowed my team to use Wave, only to have that one canned after building a process around it. No, it is not better for me that they tried and changed their minds (they did NOT "fail" technically), because I could have picked another product at the time that did intend to stick around.
People look at Google, with all the money and people that it has, and ask "How much could it POSSIBLY cost to keep Code Search going? How is it possible that Google can't afford it?". The only answer I can come up with is (1) It can afford it (2) But it doesn't care to.
So sure, if you are happy to see Google launch stuff that it has no commitment to, great for you. I'm having better luck taking chances with startups and their products. At least they have skin in the game.
Edit #2: @joebadmo - but that is exactly what I think when I see a new Google product - "will it reach such large levels of adoption so that Google will keep it". And I keep getting it wrong - even for products like Wave and Code Search which I thought surely they are used internally and so will be kept around if only because of that - nope, either they are not used internally (if not, why not?) or even that is not protection enough.
Sure, startups and small-person concerns are also risky propositions, but let's not forget the numbers. 100,000 users are a "failure" for google, but they are a wild success for a small startup, at least the ones not looking for a big exit. If you inlcude app writers as "startups", their longevity is phenomenal - I have never had an app stop working on me because somebody turned a sever off somewhere. Perhaps I have been freakishly lucky. The only other product I have had to stop using because it was pulled was wesabe.com.