skysight-inc/HackerNews huggingface dataset:
Not everybody will return, but great deal many will. The fact is that these returning migrants are probably the best bet for increasing the welfare in the parent lands. Even if most of migrants do not return "home" - they still maintain connections with their birthplaces, thus indirectly (and indeed slowly) influencing the culture through osmosis.

>Yes, and it's not working. Even the leaders acknowledge that now. And before they get too comfortable they should remember Yugoslavia tried to do the same thing.

Hmm. Saying its not working is rash. It didn't work as well as optimists hoped for it also didn't works so bad as pessimists hoped for. What leaders are realizing now is not that EU integration isn't working. It's just that current approach is losing steam.

And one should note, that current approach was more of an amalgam of inertia and half assed attitudes than something coordinated and sincere.
“I’ve made the claim that the Chinese military can take it down in 30 seconds, no one can prove me wrong”

Is this the new journalistic standard at the New York Times now?
2D gameart for programmers (and others)
This is the fifth set of tutorials using free graphic tools like inkscape and gimp to create 2D game art. After getting a little sidetracked in the last part and creating some more character designs, I am finally back to animation in inkscape.

Part 5 is out and covers the basic animation setup and creation.
I'm not too sure about the left/right brain aspect (http://en.wikipedia.org/wiki/Cerebral_hemisphere#Hemisphere_...) but I agree with switching between logical and intuitive ways of looking at a problem, and immersing then allowing insight to come of its own accord.

It is by logic we prove,
it is by intuition that we invent http://www.gap-system.org/~history/Biographies/Poincare.html
Henri Poincaré biography
My recent reocurring suicidal thoughts while being hungover drove me to quit drinking altogether.

Now that I'm sober the motives for ending my life seem banal in hindsight. Cheers to your sister.
The thing I see coming up so much is arrogance. E.g. assuming "our" generation is so "sciency" and rational and previous generations were so superstitious and stupid.
As far as failures come, the only thing I have heard about diaspora are the following things:

* Source-code full of freshman's mistakes and security exploits. Basically not-to-be-trusted quality code, released to the public for deployment.

* All money invested in the project wasted without anything to show for.

* I know absolutely nobody using diaspora, expect one person.

* This person attempted to invite me, and diaspora failed to send me the invite email. Now he cannot invite me again.

It's a laughing stock. For the parts of the internet which has even heard about it. Which is the minority of the internet. As a social network this is a failure on absolutely every aspect I can find measures for.

The goals were admirable, but goals alone wont win you any credit. You have to get there as well. Diaspora didn't and most likely wont.
> I'm not saying they've achieved anything.

Clearly you're not aware of the CADIE incident a couple of years ago.

http://www.google.com/intl/en_us/landing/cadie/

Be sure to check the blog.

(By far my favourite piece of Google whimsy, for the detail and number of teams involved) (You're right, muro)
If you're serious about smuggling data in pointers, there's probably a lot of mileage on the other end of the pointer if you're writing 64-bit code. While 32 bits can address 4Gb, you only need another 8 bits (say) to get a terabyte, leaving maybe 24 bits to cram with whatever you feel like.
Steam Hacker says Valve left an FTP server open to the world
The spam filter wouldn't let me link straight to the tweet, but I thought this would be good to post anyway:

https://twitter.com/TehWongZ/status/135081031144456193
Well, companies' needs and suits' needs intersect at some point. You have to be smart enough to see that intersection and to propose things that look good on both sides.
Traffic accident would have been my first guess, being the most common death cause amongst the people I knew. I didn't think of suicide till I read the comments.
Pogue incidentally hits an important nail:

"Now, choosing an e-reader is a big decision. Each company’s books are in its own proprietary format, and you can never sell or donate them."

This also applies to 'appstore' accounts. However many thousands have been spent, they are not designed to be transfered to heirs or buyers.
SAP has start-up ambitions
Specious bit of hand-waving featuring made-up numbers. My rule-of-thumb is to disregard people who plead virality, especially if they call themselves marketeers.

High sales get you into the top 10 lists which is really worth having (you can call that viral if you're desperate), otherwise high sales increases both the support burden and the likelihood of negative reviews.

However, an app like this has niche appeal (writers) and there is no doubt that exposure within that niche is beneficial. So word of mouth is important, but is not gained by simplistic approaches. Promotion within the niche is likely to be more productive than promiscuous price cutting. For a game, a different strategy would be appropriate.
I think he has a really interesting POV but the conversation as a whole is definitely a very informative dialog on the value of try/catch in an async environment. As they say, read the whole thing...
My personal concern with the walled garden is that a lot of the content I care about is niche 25 year old+ stuff (like old Amiga computer magazines). Ordinary users will learn to pick up on this as/when/if they start running into situations where they lose access to content because a provider stops providing access to something they care about or goes out of business.

I have no idea what portion of regular users will ever even want to access content that is obscure enough at any point in time to not be offered by providers like Amazon, but my guess is it's never going to be all that huge, and as long as devices like the Kindle offers some way of getting user supplied content onto it, then it will likely never matter all that much to ordinary users.

This is what it boils down to, I think: A walled garden is fine as long as there's a public park outside where you can do the stuff that's frowned upon in the walled garden. If I have to pick one or the other, on the other hand, I'd pick the public park any day.

I'm getting more and more inclined to pick up a Kindle. My biggest issue is that I refuse to buy DRM'd content because of the walled garden issue, and so the content offering has not yet been compelling enough.

It will never replace a more open device for me, but they're cheap enough that picking them up for the purpose of media delivery on rental plans of just stuff I don't care if I own would be attractive even if buying DRM'd content is not.

After all, I pay a fortune in cable fees to add in all the available movie channels - if Amazon offered me an option with similar selections of content that'd cost me a similar amount every month (whether charged monthly or per download/view), then I'd have no real reason to care if it's a walled garden.
I never read other people's code. In theory, you could use exceptions for nonunusual events... I've programmed a lot of things and I think I did that just once.

Here's how it is... operator overloading is really neat, but really only helps with matrix math and complex numbers, possibly more. It's only good when it's commonly understood what the operators do. To a noob, lots of things might be like algebra... in fact, only math is like math.
RV Safety Tips – A Checklist for Your Home-on-Wheel
The top 25 books for web designers and developers
Book Cheapest Hotels
Yatrii offers online booking cheap hotels, hotel packages, tour packages, travel packages, cheapest hotels, hotels in India, domestic hotel packages, cheapest hotel packages, holiday packages at affordable cost.
Acne Causes, Treatment, Prevention and Natural Remedies.
The problem with try/catch, really, is that it makes a tremendous amount of visual noise, which makes sense for critical operations that might crash everything, but just don't make sense when you can tolerate certain errors or checking for proper output with with a conditional looks better and is more appropiate.

Obviously then you have an issue with language conventions. How do you check for the returns of a method that does an in-place modification without returning anything? What happens when Null is a proper return value? What about having to access specific members or registers to check?

Perhaps, much like logging frameworks, we may need to categorize throwable actions by their importance, or think of a new convention that can handle such things more easily.
Macintosh programmers used to do this. Used to.

http://en.wikipedia.org/wiki/Mac_OS_memory_management#32-bit...
sorry - removed my previous comment in the meantime. It was obvious it's a joke, so I figured my comment is just noise.

And now I can replace it with even more words :)
I find it very saddening that so many people here are speculating that Ilya committed suicide. It's disrespectful to speculate, especially in such a case. Get a life.
Until evidence proves otherwise I'm going to assume this is just an attention seeker, not anyone actually behind the hacking.
This part really sunk in for me in Bruno Jouhier's reply:

> "So the big mistake I've always seen people make is being too "nervous" about exceptions and feeling that they have to do something about them as close as possible to the point where the exceptions were raised. They need to the exact opposite: feel relaxed about exceptions and let them bubble up."

Hadn't really thought about it in that way, but I find myself employing this pattern where possible - having said that, with async callbacks it can be hard to bubble up when you essentially have multiple logical processes occurring.

Haven't found a solution to this in my own codez yet but I feel a little twitch in my eye whenever I have to do:

try {
something = JSON.parse ...

because there's no native `JSON.validate` method.

Not complaining though, definitely not worth losing sleep over .. yet.
This is the standard in many languages and one that I believe that java got wrong. It was a little rushed with the whole concept of forcing everyone to handle all exceptions concept and building so many exceptions in for silly things like connection failures and parsing errors that reasonably can be expected to happen constantly in the normal runtime of an application.

I follow the rule in almost every language that my app should still be able to run normally if all try catches were remarked out, otherwise I should be handling something better. Exceptions are expensive and don't always back out nicely when they unwind in most languages.

In Objective-C, we play C rules more often then not and almost never use exceptions (except for assertion exceptions). Rather most errors have a ( out NSError ) pointer if they need to pass up errors.

In Python, it's more pythonic to ask for forgiveness than to check before hand so exceptions happen all the time. I'm not sure how I feel about that though but it seems to work well enough.
I am sure they would have covered some fad in the science & technology section. Like some vague research claiming that wine is good for heart or chocolate is good for memory etc.

The truth is that most of Indian dailies are not fit for reading any science related news or even news for that matter.
Conquest? Isn't it Pestilence?
SELF IMPROVEMENT: EASY SELF IMPROVEMENT Pt 2
Anybody who wants to judge try/catch should first go and read about Common Lisp's condition system. See for example the chapter about conditions and restarts from the excellent book "Practical Common Lisp" by Peter Seibel:

http://www.gigamonkeys.com/book/beyond-exception-handling-co...

Notice I'm not saying you should go and program in Common Lisp, just that you should understand those ideas before you engage in any sort of meaningful discussion about exceptions, errors and error handling in general. Because, you know, some things have already been thought about and invented. Don't re-invent them.

And on a more practical level, in languages with dynamic binding it isn't difficult to provide error handlers and "send" them up the call chain, so that in case of an exception your handler gets called, fixes the problem, and lets the called function continue. You can do all that using try/catch as a low-level tool, I've seen it done in Clojure, using JVM's exception system.
I agree with your sentiment - it is, however, questionable to bring this up in threads like these where the community is still reeling from a loss. While I believe cryo preservation is a good idea in general, you must know that most people don't do this and are in fact strongly opposed to the idea. That means you are unlikely to convince people who are not already in favor of the concept. Also in this special case please keep in mind that the guy committed suicide, so talk about cryonics is just about the opposite of what is needed right now.

Saving people from destruction includes much more mundane things, such as getting timely and competent help when mental health problems arise - and, just as importantly, striving to keep a community friendly and supportive. Clinical depression is often a chronic and idiopathic illness, but crises can still be triggered by external influences and social support does play a critical role in the way an afflicted person deals with their problems. And that is something we should be working on.
Icinga - a Re-architected Nagios fork
Game of Life in a WebGL shader
It's probably not a good idea to rely on this. Though x86-64 is (currently?) limited to a 48-bit virtual address space, it's designed so that the upper 17 bits must be all 0 or all 1, and those bits may be used in the future.

https://secure.wikimedia.org/wikipedia/en/wiki/X86-64#Virtua...
This seems to be exactly the attitude of Go:

"We believe that coupling exceptions to a control structure, as in the try-catch-finally idiom, results in convoluted code. It also tends to encourage programmers to label too many ordinary errors, such as failing to open a file, as exceptional.

Go takes a different approach. For plain error handling, Go's multi-value returns make it easy to report an error without overloading the return value. A canonical error type, coupled with Go's other features, makes error handling pleasant but quite different from that in other languages.

Go also has a couple of built-in functions to signal and recover from truly exceptional conditions. The recovery mechanism is executed only as part of a function's state being torn down after an error, which is sufficient to handle catastrophe but requires no extra control structures and, when used well, can result in clean error-handling code."

http://golang.org/doc/go_faq.html#exceptions

In Go, if there's a programmer error, call panic(); if there's a non-programmer error, return it as a second return value.

[Added] Plus, it's obvious to see where people ignore errors:

f, _ := os.Open("filename")

"_" is a throw-away variable to indicate that this value won't be used in the code. It's obvious that the programmer decided to ignore the error.

f, err := os.Open("filename")

If you don't use "err" later, this won't compile.

f, err := os.Open("filename")
if err != nil {
// handle error
}

This code handles error.
I'm not sure how I'm supposed to read this... I guess I need an account?
Bruno Jouhier's response nails it. It's funny, but for whatever reason I almost always disagree with Isaac's (perfectly reasonable) points of view.
> Try/catch is goto wrapped in pretty braces. There's no way to continue where you left off, once the error is handled.

...

> But still, nothing is as bad as the common "On Error Resume Next" that so many terrible VB programs start with.

Assuming "On Error Resume Next" does what I think it does, you can't complain about both of these at once.
Drop Shipping Wholesalers
> Of course that could just reflect a lack of imagination in NYT journalism

Don't underestimate that factor. Journalists, even really good ones, have no clue about technology at all.
Stunning Video Of Earth From 240 Miles Up
Basically, yeah.

All lower end devices end up with basically same batch of ASIC, anyway just due to cost.

Most switch stuff, however basically comes down to needing more hardware. Cam costs a certain amount, packet buffers cost a certain amount (Or wormhole switching silicon costs a certain amount), etc. None of that you can ever really move into software. At least not decently.
The exception that proves the rule :)
Yeah, there are a whole bunch of things you could try, but i think a standard Gaussian blur on the edges would solve your problem.
> space elevators are a niche at best

What does that even mean?
The abstraction-optimization tradeoff
NBC Sports - See It
"The really nice thing about the cb(error, result) approach is that it constantly reminds the programmer that you must acknowledge that failure may come from any request you make."
On the other hand, there is a limited pool of potential customers in this world. If you have a pool of 100, better to sell 10x for $10 today than 100x for $1. In the first scenario, you have 90 more customers to pursue tomorrow. In the second, you either need to make a new unrelated product with a new purpose or different audience (ex. Sony), expand your audience (Nintendo + Wii) or invalidate/depreciate the old one (Apple) to secure any more sales.

Edit: I forgot, there is also, extend your product (DLC)
Sometimes Google Groups ask for an account, sometimes don't -- not sure why.
Anyway, here's the post: http://pastie.org/2861111
Relon Free WordPress Theme
Hello! We're a tiny Indian startup: Kabutar! - its kinda like reddit for the real world. Try us out, pretty please? :) www.kabutar.in | http://itunes.apple.com/us/app/kabutar!/id477970251?mt=8
Servidor Asterisk e Nokia E71
YouTube tests redesign highlighting videos, subscriptions and more
I'm not sure that's the angle many people are actually taking, though. It is possible to take the approach of being independent for creative control, and making money is a means to that end (so you don't have to sell yourself to a corporation). It's very tempting to subtly infuse everything with the selling goal, though, where all your decisions have this nagging backdrop of "will this sell? how will this contribute to my personal brand?" etc.

It's pretty difficult to keep the selling boxed up even if you want to, and really have it be only a means to an end that isn't the main influence on what you do. Even independent businesses that make a conscious effort not to have all their decisions driven by marketing (say, Dischord Records) don't entirely succeed, and it's probably even less the case for people who don't have that kind of active "anti-selling-out" mindset.

It might even be harder, in some cases, than in a normal job. There are a lot of corners of the corporate world where you can make decisions either entirely, or at least mostly, based on technical considerations, because how it's going to make money is someone else's job. The limit case is corporate research labs, where e.g. Bell Labs employees spent very little time thinking about whether their research was sellable; but in a more limited way it appears in lots of places. If you're an independent technical researcher, it's much harder to keep your thoughts off the selling angle, because your livelihood more directly depends on whether your research output will produce revenue.
Hotels Pushkar
IOS 5  نیامده جیلبریک شد
The core of the post:

try/catch, which blurs the line between errors
that are *mistakes* (accessing a property of null,
calling .write() on a stream after .end(), etc.),
and those which are expected application-level problems
(invalid data, file missing, and so on).

Totally agree.
But what is your alternative? Doesn't checking the return code of every statement also make a tremendous amount of visual noise?

I've seen C code where about 80% of the code is dedicated to error handling and corner cases. Before every statement it has to check the current error status, and after it the return value... it's almost unreadable.

With try/except/finally a lot of that can be cleaned up, by handling the errors higher-up in the call hierarchy where they make sense to handle.

I see a lot of critique of exceptions, but haven't seen one better alternative yet, at least one that doesn't require switching to an obscure programming language.

Edit: this does assume that exceptions are used properly: for errors that should bubble up, not as extra return value.
OS X Lion uses tagged pointers for some CF objects: http://objectivistc.tumblr.com/post/7872364181/tagged-pointe...

Search for OBJC_IS_TAGGED_PTR in http://opensource.apple.com/source/objc4/objc4-493.9/runtime...
Document Services
When it comes to finding great designs for your corporate documents, finding a company that delivers exactly what you need are few and far in between. Some will create flashy designs that don’t really match your company’s image. Others, meanwhile, have designs that look as if they were made by pre-schoolers. You don’t want any of that.
For more information please visit:- http://www.documentdesign.com.
World's worst website?
Why the Lumia 800 is the first device I would switch to from an iPhone
I don't think it's only the fear of putting things out there that might reflect negatively, but also the temptation of putting things out there that might reflect positively. I actively try not to do it, but I do find myself participating in even online discussion groups with one eye towards potential "personal brand" building. Am I just posting at HN for the discussion, or to build a platform?

Or: I used to submit essays to Usenet or Kuro5hin, mostly out of a desire to stimulate discussion and get feedback. But now I post them on my blog, and when I'm writing them there's, consciously or not, always this background thought of where I'll advertise that post so people read it, whether it'll get me new RSS subscribers, etc.

I even sometimes think, on the occasions where I've written a long-ish Wikipedia article from scratch, that if I were really doing it right, maybe I should've posted it on my personal blog instead of submitting it as a Wikipedia article--- because I can't fully capture the personal-brand-building at Wikipedia. I'm sure there are people who do give in to that temptation, too.
Doodle 4 Google 2011 India Winner - Varsha Gupta
Today, 14-11-2011 Google looks like so pretty.Did you check that there is something cool yet special about the Google Doodle? Look at the today's Google Doodle on Google's home page.Wondering what Indian musical instruments have to do with the Doodle on children’s day.
I take it you think there are MBA types that wander around NSA headquarters, grab the dragonfly-size spy robots and bring them to market?
Hotel near Delhi Airport,Delhi Airport Hotel,Cheap Hotel in New Delhi
The Secret of Absolute Abundance and Wealth
Create, Manipulate Documents Programmatically in SharePoint Sites
Aspose.Total for SharePoint helps to convert various types of documents into other file formats in SharePoint. But if users want to add functionality for creating new documents from scratch or edit and manipulate existing documents programmatically in your SharePoint Sites, the Aspose.Total for .NET can used for that. Aspose.Total for .NET product suite provides different components to work with a large number of document formats. By adding these components to your SharePoint deployments, you can take your SharePoint Sites to the next level.
There is a link error: "flow" should link to http://en.wikipedia.org/wiki/Flow_(psychology). You forgott the trailing ). Beside that, the title of your articles is just "Hi".
Delogierung
Class action service
Goal Group offers a whole host of solutions for class actions, tax reclamation and bespoke software development.