skysight-inc/HackerNews huggingface dataset:
"Alliance with Microsoft seems to be the only sensible choice for Nokia at the moment. True story."

Many people disagree with you. Imagine that.

I suspect you're not old enough to remember the fate of some other Microsoft "partners" of this sort.
To various extents and with varying effects, BTW.
emailed bro.
Are you trolling?

> as far as i can see nokia could differentiate themselves a hell of alot more and with far more confidence with android then with ms win mobile.

GP had a whole bunch of reasons why going with MS is probably a better strategic decision for Nokia. You have given none to counter those.

Regarding playing favorites: so what. That's business. Live by the sword, die by the sword. Could have made the same argument regarding favoritism about Symbian a few years ago before Nokia bought them out completely.
I knew they were about twice as fast, but seeing it like that...holy cow!
clickable URL: http://receivd.com/early-access
wow, now that is embarassing in firefox. all fixed(?) sorry.
i don't get it, you mean why CA?
Ah, OK, I should have noticed! Thanks.
I've been using Awaken for OS X, similar... good idea to be web based though

http://embraceware.com/awaken/
Books: Milan Kundera, VS Naipaul, Orlando Figes

Essays/blogs/etc: Tim Keller, Matt Taibbi, and John Dolan (along with his pen-name Gary Brecher)
Linux wasn't viable when SGI started selling NT workstations. BSD might have been viable. (It would still be viable now.)
Great article. Will CBS apologize? Will they learn anything from this? Since they don't seem to have suffered financially from their irresponsible reporting, I am afraid the won't change a thing.
Apple, Intel.
> Are you trolling?

no
True, although the Python compiler operates invisibly and transparently. kbutler makes a good point too. I'll clarify my original distinction: it's whether source code is executable without needing additional tools, and thus the knowledge and environment and dependencies needed to use them.
Low-cost video chat robot
Here's one take:

Look at Samsung, LG, and HTC. All of them are making both Windows Phone 7 devices and Android ones; if Windows Phone 7 takes off, they're in the race, but if it doesn't, they'll have other stuff that's working for them.

Now look at Nokia. The difference isn't what Nokia will be doing --- making Windows Phone 7 devices; it's what they won't be doing --- making Android phones. They've taken a big, risky bet, which they could have hedged, and haven't. And the platform they've bet on is one which allows manufacturers less freedom to customize and differentiate themselves than the one they've shunned. Heck, if they just shipped stock Android, that would differentiate them from most of the phones on the market. (Contrast to Windows Phone 7, where Microsoft is being very restrictive in what manufacturers can dink. Nokia may get more freedom than some as part of this deal, but not nearly as much as the HTC Sense experience for Android.) And you could try to say that they don't have resources to handle multiple platforms --- but if that's the issue, why are they still talking about shipping Maemo?

In short, this is still different from what other manufacturers are doing, but based on the announced terms of the deal, it's not really clear why it's better, and it is pretty clear why it might be worse. There might be unannounced terms of the deal that change that calculus, but for now, people can only judge from what they can see.
Odd that, too. Are you using your same Google account on both computers?
They don't exist anymore! It may appeal to your Schadenfreude to know that shortly after this they went bankrupt - because I wasn't there and so they couldn't complete contracts and got sued into oblivion by their clients.

I guess I'll mention the basic problem was I had a contract with them licensing one of my patents to them when I went to work there. They then told me they wanted me to transfer complete ownership of my patent to them when it became an issue that they wanted to license it to another company, which my license did not allow (non-transferable) and they didn't want to pay for. I said no, and so they fired me, but told me if I gave them the patent I could come back to work - blackmail!

The other company then wanted to hire me and deal with me directly, and that's when my former employer launched legal proceedings and sabotaged my new job offer.

That is when I found out that a qualified and experienced IP attorney who knows the law costs a lot more ($600/hr) than a regular family attorney ($100/hr). My attorneys were top guys nationally and were very clear that the company had absolutely no case whatsoever on any of their claims.

It soon became apparent though that the company attorney was scheduling meetings with my attorneys solely for the purpose of bleeding me dry. For example, company attorney would demand to meet with multiple members of my firm to discuss things, and then talk slow, fumble with papers and act stupid, at a cost of $2400/hr to me because there were 4 attorneys there. My attorneys told me straight up that that was what the deal was and they called the company on their BS but the company kept trying these tactics. Eventually the company got buried in their own bad karma and gave up, but it still cost me a fortune to deal with and stole a year from my life and caused incredible stress and dismay. Lesson learned was that it simply does not matter that the law is on your side and the other people don't have a case if they are acting in bad faith.

The good part was that I came out of it a lot wiser and since then I absolutely will not deal with any company that insists I agree to terms I don't feel are completely fair. That decision is still the right one, decades later, and completely changed the amount of BS I was dealing with in jobs. Any one who feels uncomfortable with any clause should not agree to it and be firm. If you have talent, you will find work for reasonable people and that work will be better paid and less stress than dealing with the jerks.
I disbelieve.

I was debugging performance problems in high performance websites before I ever began to try to fill in some of my severe holes due to not having taken CS. Thus I can say from first hand experience that a little quantitative thinking is enough to debug many real life performance problems. Absolutely no knowledge of operating systems and computer architecture required.
haven't gotten it to work either. For an alarm clock to be unreliable is pretty bad.
Add a few decoys.
This is the same guy that made the awesome wiimote 3d goggles (TED talk here: http://www.ted.com/talks/johnny_lee_demos_wii_remote_hacks.h... )

EDIT: Added TED talk link.
These days platform choice is irrelevant. All modern platforms have tools available for doing basically anything a software developer will ever do, and doing it well.

Unless what you're doing requires some specific feature of some specific platform (i.e. you're either developing the platform itself, or you're doing it wrong), go with what you know.

And if you aren't proficient in using any of these platforms and are looking for a recommendation on where to start on your software development career, you should probably reconsider.
He was hired by MS and worked on the Kinect team afterwards.
Not all content is king on Wall Street
The Engineer-Driven culture at Nokia and its problems
I second this, we actually did significant research on this at our firm and the reality is developing JavaScript based UI's reduces UI development effort significantly, there are several factors that contribute to this from an event based programming model, to not having to transfer state between layers. Sufficient to say a white paper could be written on that subject alone.

Anyway, progressive enhancement kills all of the advantages of JavaScript application with the exclusion of more advanced UI features and simulated responsiveness. None the less, rather than reducing or evening the development cost burden with server side web development, it actually increased it because all of the server side development must be done and then a client side framework must be bolted on top of it. It is quite honestly the worst of both worlds because it spikes the complexity of the solution.

The numbers that we gathered in our research and post mortums of projects supports the conclusion that it is actually more cost effective to build two independent UI's one JavaScript UI and a reduced feature set server side based UI and route client to each according to capabilities.

Further, for many client the monetary outlay of developing the server side UI to support the < 1% client base that could not use a JavaScript UI was more than would ever be recouped for the investment.

In one of the analysis that we did it was actually cheaper to send the clients that did not have access to a supported JavaScript compatible browser a new machine than to spend the development effort to build out an independent system.

In all cases a better business case could be made for spending those development funds on alternative platforms like iPhone / Android / mobile client or IVR systems.

The segment of the market that cannot access JavaScript based applications is a very small segment and it is dwindling every day. For most web applications a business case cannot be made for progressive enhancement to chase this segment; especially when alternative platforms are added to the analysis. In almost all cases the time and money was better spent chasing those non-web segments for growth.

Please note this information is specifically related to web applications (web-based desktop application replacements) and not web sites like a news site. Web Apps are my companies specialty and we don't build web sites so none of this info should be construed as advice for article oriented web sites. Put simply, I do not know that these conclusions would hold true for building something like HN, they are true for building something like Salesforce.com.
It never fails to amaze me how otherwise very intelligent and thoughtful people remain stuck believing in God. I must say I can't help feel a little less impressed with people when I learn they are theists.
some interesting points raised in the post, but perhaps one should first distinguish between the different types of management:

1. project management
2. people management
3. executive management

i think your argument is mostly towards project and people managers. project managers own the mechanical tasks of scheduling, resource allocation, aligning priorities, assessing status, assessing risk, updating stakeholders, etc. these are important things that perhaps would be wasteful if assigned to a developer. but let's say for the sake of argument that the developers are quite capable of taking on these activities along with development, design, and architecture tasks, which i've experienced, there are a larger set of tasks that typically need to be dealt with that may have nothing to do with the current project whatsoever such as hiring, developing talent, retention, attrition, motivating, refining and building good processes, balancing budget, developing company culture, setting, aligning, and influencing direction, etc. attrition is particularly an example that should most definitely be put into the hands of a manager, i.e. you wouldn't want a fellow employee to decide that you're fired, this is not the easiest conversation, i assure you. and when it comes to raises, how would a team of engineers decide who gets what piece of the pie?

to your point or some commenter's point about managers costing more than developers, i've managed lots of people that have made way more than me. and i've been very fortunate to see both sides of the spectrum in terms of great managers versus dead wood, you can learn a lot from both types. but management, at the core, is dealing with people, and personalities are never easy to deal with, developers/engineers being no exception.

ultimately i'd love to see a flat hierarchy where everyone could self manage and the science of management could be absorbed into everyone.
It always amazed me that Avaya, Cisco and other Telepresence companies have not built one of these.
But without controlling their software, Nokia's almost entirely surrendered control over their product direction to Microsoft. Contrast it to Apple, where having their own hardware and software lets them do things like the retina display upgrade. In Nokia's case, MS says "This is what the OS is capable of," and Nokia has no choice other than "Ok, we'll make a touchscreen with some buttons that comply with your interface conventions."

They're going from a mobile phone company to a widget manufacturer. It's a position not very different from where Dell, Gateway, HP, etc have been in control of product design, but unable to innovate in ways that would really improve the customer experience. So they're relegated to hardware design (within some pretty narrow constraints) and differentiating their computers by loading some shitty bloatware on and saying "<competitor> doesn't have a dock on all four screen edges like we do!"

There's still money to be made in the hardware business, but it's not something I'd aspire to were I in the cellular industry. It's better than being put out of business, but Microsoft's lack of direction in OS design is likely to hobble them as they try to compete with Apple's ecosystem. I mean, WM7 tried to copy iOS 1 and say "Nah, you don't need copy/paste". Apple's continued to make progress toward a capable mobile OS, and MS still hasn't fixed it. Do you see them having a good chance at competing in the long run?

My prediction: Nokia and WM7 won't be able to compete on features or design, so they'll compete on price. As the smartphone market portion continues to grow, a lot of it will be on the bottom end, with people moving from crappy featurephones to crappy smartphones. If they can find a market niche, it'll be the people who just say "I want a phone," and not anybody who knows or cares any more than that. Which is a pretty big market to be calling a "niche," but it's got slim profit margins. Maybe they can make up for it in volume.
I would assume for a content oriented site the most optimal development path would be a CMS as opposed to custom development. Something like Drupal or Wordpress is going to give you a significant time to market advantage over developing a site in either a server side or client side framework.
Sheet Music Books Requests
In Egypt, the revolution succeeded because the army didn't fire on protesters. In China... things have been different, and they probably still are.
In general, how does suing the government work?

Isn't the judicial system a part of the government. Can't it just decide to throw away the lawsuit anyway, even if there was no ready available "secrets" excuse?

I know the lawsuits happen, but in theory how does it work?
I'd say mathematics is closer to the hacker spirit than startups or icky things involving money & bureaucracy.

I like the proof of quadratic reciprocity by way of group theory. A novice might think the proof has no practical "utility". But Gauss invented it, and it's called the "jewel of arithmetic", so that's more than enough utility to me. Besides, doing it this way also shines light on the way group theory can be applied to other areas entirely, such as deep theorems in number theory.

Here's a short proof of the quadratic reciprocity using group theory by an exceptional high school student:

http://www.thehcmr.org/issue2_2/math_minutiae.pdf
Sorry, I should have been more clear.

As I understand it, Oracle's standard employment agreement includes language saying you agree that Oracle owns every idea you have while employed by them, whether on "paid hours" or not, whether related to databases or software in general or not - if you're a database engineer for Oracle and you invent a better tap washer, Oracle seem to think they'll own your plumbing related invention. There's workarounds for at least limited exceptions to that standard rule, but it's apparently unusual and required signoff at many levels above the typical workers management.
Yet another validation of the long-standing hypothesis that in the age where a kid with a laptop can come up with technology that takes over the internet, pushing tech as a process in a factory is the path to irrelevance.
faster than the speed of light is undefined behavior.

Edit: In the video he orbits the earth faster than light could make the trip. Then again his blur trail is way to big etc so IMO just take it as artistic license / bad science fiction.
Perhaps. If Android was chosen Nokia could put many of their displaced Symbian developers to work on a Nokia application ecosystem and services platform. This would allow them to use Android without having to pay Google.
Car keys replacement
lol:

FEED: The hacker community is full of very cantankerous and opinionated individuals. Have you gotten much grief for being so open about your Christian beliefs?

WALL: I've had no difficulty with it....I see God looking down on all these weird, cantankerous people, and kinda liking them, in an artistic fashion....There are certainly a bunch of what I would clearly label sinners out there....
Eh, I seriously wouldn't rely on a website to wake me up. Computer pukes. Power outage. Etc. I'll stick with my trusty cell phone which will stay powered up even through a power outage. BTW, my song is "I got you babe" by Sonny and Cher. +1 for anyone who get's the joke. ;)
With the benefit of retrospective, the comments are seriously hilarious.
It sounds like you wanted to study software engineering, not computer science. It's a shame that most universities don't offer both, just as they might offer both physics and mechanical engineering.
Get $9/mo Grooveshark Anywhere and earings for $20
Totally unaffiliated with Grooveshark but I stumbled on this: http://store.grooveshark.com/

Going to buy now
Whoa, Groundhog Day?
Thank god. I thought the Microsoft puppet was going to be the next Microsoft Bob/Clippy/Search dog.
Series 10 episode 8 is also a good one. Richard Hammond gets to drive a Renault R25, circa 2005. He had a hell of a time even getting the thing onto the track. The pit crew actually had to tow the car back to the garage to warm it back up; the tolerances on those motors are so tight that, when cold, they are effectively seized.
"I've found that any feature branch that lives longer than a week becomes essentially impossible to integrate - in the time necessary to bring it up to head, head has changed enough that you then need to integrate it again, and so on."

DCVSs don't stop you from doing your commit, doing a naive merge, and then optimistically pushing. That option is still there, and is partly why so many people rebase before pushing their changes. Of course, pessimistic integration is equally available as an option.

If you find the overhead so high, it suggests that it's process holding you back and forcing you to pessimistically integrate, rather than the DCVS doing so.
China environment documentary gets Oscar nomination.
PhotoImpact can do about 90% of what you can do in photoshop and it's much easier to learn/use.

Not to mention a fraction of the price. There's a free trial, give it a shot.
Why? Different axioms are just different, and they can't be argued logically because logic only follows from the axioms. The only arguments you can make for axioms are how useful they are and, more importantly, how well you think they reflect reality as you understand it. If one of his axioms is that not every truth has objective empirical evidence to support it, how can you formulate an argument against that? All you can say is that you don't see the world as operating that way, but you certainly can't use logic or reason to argue that he's incorrect.
Where do stereotypes of geeks come from? The situations they are put in.
3.5L V10 moving to 3.0L V10s to 2.4L V8s now.

Sound of an F1 engine is truly amazing. Just as awesome are the down-shifts. 7th to 3rd.
Planning out Freelance Graphic Designing Business?
If you want to choose Graphic Designing Business then this article is best for you. You will get important points and actions to take before starting the business or during this business.
Android may be open source but realistically how far can anyone diverge while maintaing compatibility, consistency, and the ability to push updates out in a timely fashion? At least with Microsoft they are entering a formal agreement. All these details have probably been worked out. Microsoft may have offered to let Nokia into the inner-circle of WM development. They may have agreed to have MS developers work very closely with Nokia for customizations. Hard to say without knowing all the details but it's doubtful Google would have agreed to the same terms since they simply don't need Nokia.

It reminds me of this story about K-9 developers wanting to re-integrate some of their enhancements back into ASOP and Google's response was basically 'nahhh' or Google giving Motorola sweetheart access to Honeycomb while leaving other tablet makers moaning & groaning on the CES floor. Those types of things probably contributed to Nokia's choice. Nokia wants to be actively involved in OS development. Their own efforts failed. Nokia being a somewhat old fashion sort of company was probably not comfortable with the uncertainty behind Google's rather blackbox-ish control of Android. In an ironic way Microsoft was actually offering more flexibility and openness of development plus all the perks of free marketing dollars, joint promotions, and generally being treated like a first class citizen with a contract to define the exact terms of the relationship.
Cheap&Discount Software- http://www.softbuy.com/ 
Daily software discounts, buy cheap and discount software online. Best prices and coupon codes for popular software programs.
exactly. Despite being a fan of Android I'd have been disappointed if they headed in that direction. Adopting Android would have been surrendering and becoming 'one of the crowd', they needed a point of differentiation, rocking up late to the Android game wasn't going to turn that company around.
Not for Apple. OTA updates are great, but if the carriers don't play ball customers should still be able to plug their phones in and easily upgrade.

WP7 has the advantage of having Apple-style end-to-end integration, giving them a very natural place to issue non-OTA updates.
Manufacturing the dream: Game changing new production
When handed one of these, put it in your desk. Same with second and third copy. If they ask for it before hire, say you need time to read it.

If that fails, write an addendum that neuters the document. "Nothing in this agreement precludes posting online, writing, blogging, coding, or contributions to open source software provided that no code or technology specific to company XYZ is disclosed." Most employers won't pay their lawyer to review your addendum and bang, you have your rights back.
It's not even a new thing. Accenture and the other big accounting firms used to do this all the time.
I'm getting to the point where i don't want to sign any contracts with any future employer or client. At least, nothing but the bare minimum needed. NDA's, for example, increasingly look to me as a joke and more trouble than they're worth.
Yep... same account, same browser (Chrome), and both Macs.
Yes. Specifically the Motorola/Honeycomb deal. There were some unhappy Android tablet makers at CES. That plus Google dropping 2.3 source about 2 weeks before CES leaving so many companies showing off 'dated' 2.2 products on the floor -- not endearing. Practically speaking it may not be a major issue but I think Nokia has a little too much pride for that. You can bet good money Nokia will be showing off the first WM8 device.
Word of the day: "Entryism".