skysight-inc/HackerNews huggingface dataset:
Procedural has a static state of flow working from the program controling the data and OOP has a lose state of flow working with the data controlling the program. Would that be a easier true definition?

Another way to look at this is if you have say a physical button that the user can toggle on or off and it is lit up by code. Doing this is processed by procedural code then the code will know what state the button is and if any processing limitations will be slow in processing if the button is on or off as could be indicated by slow transition to respond to the light going on or off.

Now using OOP code the code that controls the light being on or off is would in general isolated from the processing of the state of the button and can lead to the the button showing on with the light on yet the processing code still thinking it is off. IE the code has no fixed static processing path and as such can lose state of if the button is on or off. This can lead to the button being off and the underliying code thinking it is on as they desync. Sorry if not the best explanation but is based upon a example I've seen in real life. The example was a phone busy/not busy button and the lovely C++ object oriented code got into a kefufle thinking the butotn was on when it was not after the operator had played track and feild on the button tapping away at it real fast out of bordem. The next result was the call processing system thought the phone was not busy when it was and tried to route a call which it was unable to do and the upshot was the entire phone system crashed.

OOP has it's uses, but it also has it's downsides, like all approaches it is the right tool for the job. Just that error handerling in OOP can get more complex than boring old procedural code which is alot easier to deal with, when it comes to exceptions as the processing state is static.

Another way to look at it is physical gears - procedural code is a fixed gear and OOP is a gear cog that can change in size and whilst you will see the end result you have no idea what size the dynamic OOP cog is.

Realy can be a hard one to explain without examples and it does lack a classic Hello World example.
At the risk of essentially slashdotting myself or making my web host very angry at me, I have stripped out the passwords so that the only component remaining is the email addresses, in case you want to check whether you were part of the breach. (I was not! hooray!)

I am hosting this at: http://drostie.org/yahoo_leak.txt . If I receive too much traffic I may simply pastebin it.
Software albatross
EDIT Operations Research and Computer Programming
I appreciate that you've set up real domains for demonstration purposes, but wouldn't it be better to transfer ownership to Mozilla so they show up in the whois record? I don't mean to nitpick, but details matter when trying to promote such a sensitive protocol. There's no way I'm going to try out an authentication demo at a random privately owned domain.
>3) Curious to know what hardware you're using. I'll add a way to turn off the background in a few minutes.

Chrome on Windows 7 20.0.1132.47 m

Core2 Duo @2.66GHz

4GB of memory

64 bit

It's really just the fading effect that slows things down. I'm running at 1920x1080 on a Quadro NVS 160M.
Syntactic Sugar Is More Than Dessert
A Facebook ad bug is re-offering expired promotions to customers
Well, part of the reason I got them and part of the reason they're hurting my feet is that they are completely flat soled, with almost no cushioning. I'm transitioning quite well to a mid-step gait when walking, and eventually I want to be running mid-step or on the ball, rather than toe to heel.
To a point. But there aren't enough hours in the day to become an expert in buying everything one has to buy, and in many cases predicting the durability of something is really difficult.

I guess this is in large part why brands are so valuable, as they give consumers a seemingly easy quality heuristic.
The author is saying since Node is async by default and rails is not that, that node is better? For one, Rails neither async or sync. The programmer decides what to do. Two, Rails is a Framework, Node is a quasi language/framework. Want to do something completely async in Ruby use EventMachine. Zomg you're now async.

And really, MVC is no longer a good pattern for backends? That makes perfect nonsense. V = JSON, C = Things Interacting with HTTP, M = Domain Objects.

Out of curiosity, are they are any mature ORM's for Node? ActiveRecord has been around for quite a long time. You don't simply clone 8 years worth of development time.
I was at this specific session. I was one of those who left early.

I honestly didn't think it worked out and most people I talked to after the session didn't think it worked either. To put it lightly: People had rather mixed impressions.

He was progressively writing Node.js-code without explaining any of it in detail. His way of illustrating what his code was doing, was by cross-referencing his Node-stuff to some Ruby-based BDD framework.

How do I connect that to Node? Do I need Ruby to run node?

It came off wrong to most people. Especially with the techo-music glaring in the background, some people thought he just wanted to show off how cool he was and brush his own ego.

Other's complained that if you could actually follow his demos, you already knew the stuff he was demoing, so what was the point? So what had you just learned?

And like he said: Some people directly told him it was a waste of time.

IMO it was an interesting idea taken too far.

He makes it come off as a success, but I think that is disingenuous. This session probably disappointed more spectators than any other session on that conference. And I say that as someone who knows how good Rob can be when he's at his best.

So don't be afraid to experiment. But be prepared to see your experiments fail. Every now and then they will. Even for a guy like Rob. Especially when you take it to the extreme, like he did here.
What if there was a database of compromised email accounts and their passwords. Responsible websites could poll this database on a daily bases and reset the passwords of members who's accounts have been compromised on other websites. This way, if people use the same password on all websites, the responsible websites operators will protect their members accounts from being compromised.

I know there are a ton of holes with this but maybe this initial idea could lead somewhere.
and programmer dvorak :D
Edit: I want to apologize if I come across as harsh. This topic is near and dear to my heart. So, please understand that my tone is not directed at you.

> However it's worth noting that they cover everyone for the equivalent of what we pay in the US for Medicare and Medicaid alone.

Everyone is covered, but not all medical conditions are covered. Yeah, if you break your leg, it's great. Having a child? Peace of cake. You don't even see a bill. Things just happen. In that way, it's nice. But when it's serious? No. Serious conditions that require years of effort, or major surgery? It falls down.

And the quality of care is below what we've found in the US.

It looks pretty on paper. My wife was a big fan of the Canadian Health Care system, before she had to rely on it. She feared the US system, until she experienced first hand how it could help.

No system is perfect, but do not imagine for a moment that the Canadian system is in any way a better way. I am serious when I equate what Quebec did to my son as nothing other than pure abuse.
'Oh that's neat so Puppet's kinda like Group Policy?"

"I'm not sure I've ever heard of Group Policy"

It cuts both ways. There's an infinite number of things to learn and a finite amount of minutes in a day. People that are too broad and know everything may never end up developing a deep understanding of a few things to be really productive.

There are certainly people that can straddle both worlds of *nix and Windows, but really how is a user of Microsoft's cozy development ecosystem any different than a user of Apple's cozy ecosystem? People seem to love the latter's setup but chastize the former.
I don't think so. The only evidence that the passwords were stored in the clear is that some "strong" passwords were broken. But if you look at the LinkedIn dump (which was hashed) there are plenty of strong passwords that were broken.
Funny you should bring up the Phantom. This thing reminds me so very much of the phantom. I remember trying to buy a Phantom dev kit and just being told that they're "coming soon" for ages. Then they came out with the Phantom lapboard, and folded.

I don't know if it's the look of the console, or the way this was all presented, but it's all far too reminiscent of the Phantom for me. I'm staying well clear of this.

Just an aside: I miss my dreamcast, best controller ever.
Usability Analysis of Visual Programming Environments
Please don't recommend CodeIgniter. I'm not normally one for swathing "x is bad" judgements, but CI is simply not in the same league as the other frameworks you mentioned.
Amazon Driving Towards Same-Day Delivery Operations
> I don't know why more people don't talk about this.

They do. People dismiss it, calling them the exceptions. The problem is, a lot of people in Canada can't simply come to the US to get care, nor do they realize they could.

Every time someone proposes Canada as a model, I trot out my story in the hopes someone will realize that their is a dark side.

No. Never again. It was no better than child abuse.
1. It's not always true that things that are more expensive are also higher quality. But the reverse is true: things of higher quality are more expensive. Because they're made of better materials, because they were grown naturally, because they were made of natural ingredients, because they were tested... better stuff is usually made with more effort or better material.

2. Because of #1, distinguishing genuine high quality stuff from a simple ripoff takes critical thinking. People don't like thinking too much, don't like analyzing, and critical thinking is unpopular especially in United States of America.
http://www.youtube.com/watch?v=u5um8QWWRvo
Yes, indeed. I was blown away when I read his about page. So many people yap about their years of knowledge and that PHP has all these problems and can be fixed this way and that way, but when told to shut up and fork the language and do it. They say "I can't, because I don't know C', yet this 17 year old is doing just that.

Kudos.
They have HUGE incentives for hiring veterans, as well as any kind of "disadvantaged minority" (read: not white or Asian)

My best friend for 20 years, who is probably the smartest and most capable guy I've ever known, graduated with a software engineering degree (and a crappy GPA due to his pursuit of non-school software stuff at the expense of his school projects). He happens to be black, and he couldn't get hired anywhere due to his GPA. He goes to DC, immediately gets interviews. Now, here's the funny part: These assholes who called him for phone interviews were asking, multiple times!, if he was indeed "African American"? One of the females who called him from a very,very large contractor I shall not name said the words, "ok, I was just confirming because you don't sound like it." (meaning she didn't think he sounded black.)My buddy, ever the cleverest guy around, responded "I'sa do the numbahs too mastah." LOL
The Google style guides are cool but not newly revealed.

They've also been discussed previously here:

HTML/CSS (2 months ago):

http://news.ycombinator.com/item?id=3886966

C++ (1 year ago):

http://news.ycombinator.com/item?id=2242314

JavaScript (2 years ago):

http://news.ycombinator.com/item?id=1524626

Python (2 years ago):

http://news.ycombinator.com/item?id=1311126
Great article and still wonder that not more people got the idea of Node, Mongo and related tech. Rails isn't bad and full of good ideas and a rich ecosystem but at the same time it's terribly aged in lots of areas.
I've been sitting around thinking about implementing a user system on my current (and first) website to try and keep people returning to the site to see people responding to their stories etc.

Now I'm wondering whether to use Persona or build it myself from scratch.
Repair the cracked glass face of an Apple iPhone 3G
100,000 Android Users Infected with Application-Buying Trojan
"Internet Explorer 9, on the other hand, is a damn good browser."

No. It's not.
I am involved with a Rails project where the creative developer decided a single-page app was what we needed. We use the views/partials as fetching pieces, calling them via ajax calls and all is well. The added benefit is every unit of namespace has its own home, so SEO for everything is achieved. I am a huge advocate for the newer and better, but Rails is a great solution for single page applications. Also, it's great to write code in Ruby whenever one can; cmon, life is too short!
> comments on HN or elsewhere are no more or less valid than what wikipedia says

I'm not going to be dragged into a discussion based on such a ridiculous premise.
Procedural has a static state of flow working from the program controling the data and OOP has a lose state of flow working with the data controlling the program. Would that be a easier true definition?

No. (What is "static" vs "loose"? :)) Procedural programming is a control flow pattern. OOP is a data arrangement pattern. You may be thinking of GUI systems with single-threaded control loops and callbacks, which is another kind of control flow pattern, but it is orthogonal to OOP. People who use OOP can, within the methods or in calls to their objects, use a procedural approach, a functional approach, and/or a callback approach. For different control flows, there are sometimes more appropriate/maintainable data arrangements.
This is kind of strange. Wouldn't it enhance Viacom's negotiating position if people are watching directly rather than through DirecTV? i.e. Viacom can point out that people don't need DirecTV and that will make DirecTV cave.
Please don't recommend CodeIgniter. I'm not normally one for swathing "x is bad" judgements, but CI is simply not in the same league as the other frameworks you mentioned.

I wouldn't have a few years ago, but the current version seems decent enough. Out of interest, what're your main complaints with it?

I'm not a huge fan of CI, but would prefer it to my personal bugbear, CakePHP.
eh, I guess my problem was more with this idea that expensive stuff usually lasts significantly longer. From what I've seen, it usually doesn't. Expensive stuff usually isn't optimized for use per dollar.

If the expensive stuff is giving you value on another axis? like the higher thread count sheets being more comfortable or what have you? that's great. I buy luxury items too. And I am willing to pay significantly more for tools that are easier or more comfortable to use.

I was just taking issue with the idea that expensive stuff is usually cheaper in the long run.

You should buy luxury items when you think the enjoyment you will get out of them is worth more than the money you spend on them. If someone tries to tell you that the luxury item is actually cheaper in the long run than the 'value' item, (the item actually designed to maximize use per dollar) well, I suppose it's possible, but it's pretty unlikely. You should be very, very suspicious.
It's really quite sickening to see. The guy papsosouid has a reddit account, and he's an MRA/rape denialist. So there's that.
I've found that debuggers actually help me understand a program. Even when I'm not necessarily trying to fix something, having a debugger to track all the local variables and is a lot easier than trying to keep in all in my head. (Caveat: I'm less of a programmer and more of a data guy who writes some code here and there).
Obat Kanker Hati
Obat Kanker Hati Stadium Lanjut ? jawabannya Daun sirsak dan manggisObat Kanker Hati Stadium Lanjut ? jawabannya Daun sirsak dan manggis
Hi Sam,
Thanks for the kind words =)

Largely front-end & back-end dev. So HTML/CSS/jQuery, Ruby/Rails/SQL. Been playing around a bit with Ember, so that can fit in there somewhere.

Unfortunately, not iOS stuff (at the moment).

If the MVP is iOS client with a server component, let's discuss it and see. I may not be able to do the iOS client - but maybe just the back-end. Or maybe I can work with someone (they do the iOS client, and I do the back-end).

Email me if you are still interested, or leave me your email address and I will reach out to you.

Thanks.
This could of been from a hack done years ago, milked for all entirity in secret and then released years later. Alot of passwords would still be the same, people habitualy if not controlled to change there passwords every N days will not bother unless some event dictates thay should and then if they can avoid it then alot will sadly. Sadly the human finger fits perfectly into the human ear and this is how alot of people handle alot of problems.

Now that all said if you look at any password system you will find common passwords and if you allow your user to use things like football teams, there own username and words like "god" "jesus" etc then you will get a standard statistical spread. The only conclusion you can make is if you get a million needles and chuck them in the air and do it twice that in pile A and pile B you will find some that point north, its the way it goes.

So what does sony and yahoo have in common - passwords picked by humans, used by humans - just like alot of password systems, be they hashed, tripple hashed or plain old text.
U.S. Moves Unmanned Underwater Mine Seekers To Persian Gulf
On using Hacker News to validate a product idea involving NLP and PHP
We had this revelation already back in 2002!

Back then, I was working for a startup that had a product similar in concept to Rails but based on Apache/TCL developed around 1998. The initial architecture ideas were taken from AOL Server, in case anyone still remembers it.

Around 2001 we reached the conclusion that it wasn't scaling any longer for the type of loads that we needed, and more a better language infrastructure was required.

After some research, the framework was ported to .NET, on those days still beta, but their JIT could already yield much more performance than our home grown solution.
This seems like overkill. Why does each unit have a 256GB SSD when there is a central server with 4TB of storage?
I agree. Time is our most valuable resource and it's a cost/benefit matter as to whether it's worth your while looking in-depth at purchasing options for a particular type of product.
Makes sense to me. Maybe Google should lower the rates a little. I'm sure Google would prefer to earn $10 with reduced fees from $15 than earn 0$ and create a competitor.
Also, check out Chicago Boss!
That would require much bigger production and creative quality.
Smooth Voxel Terrain
Semaphore is great -- the first hosted CI I've tried that actually works well.
I don't get it, because I have being doing asynchronous server side programming for years in C, C++, C#, Java.

It is already enough that I have to deal with JavaScript on the UI side.
Why Android Fragmentation Is Still a Problem
Chromebook Google Drive integration is both handy and slick
"they had at last confirmed the existence of the elusive Higgs boson"

Last I heard they have not yet found the Higgs boson, they found something that is LIKE the Higgs boson. Is this not correct?
> enough hours in the day to become an expert in buying everything one has to buy

Provided that it's usually the case that people buy far more than they strictly need to, might not some level of requisite knowledge about a product help determine whether one allows or disallows oneself from a purchasing it?

I know, in my own case, that I've become increasingly wary of purchases (given a price point, say, above $50) if I haven't had enough time to understand just what the hell it is I'm buying. This runs from things like bed comforters to headphones to deck chairs to pants to video games.

Generally speaking, my level of regret over a purchase is inversely proportional to the level of knowledge I had of that product and its ecosystem at the time.
Just out of curiosity, is "discover" really the correct terminology here? Didn't these scientists, more correctly, observe the Higgs? Not only that, but didn't they also observe phenomena that coincides with the existence of the Higgs without actual observation?

I'm not arguing with the title, simply curious as to what the correct terminology is for when something is previously hypothesized as being in existence.
I like that you starting numbering at 0 - very apropos.
I'm not sure why Sinatra was not considered in the mix here. Sinatra is great for building simple APIs in Ruby. Heck, Express essentially started out as a clone of Sinatra for Node.

One challenge in the Node community is the ecosystem. There are not nearly as many libraries in npm as there are in RubyGems. Of that small set of libraries, a large portion of these have been abandoned. Of that smaller set that haven't been abandoned, there are large portions of missing functionality, are not very stable, or are constantly changing.

There are certain cases that Node works really well for right now, like building real-time chat apps. But having worked on some medium-scale Node projects recently, I constantly find myself re-implementing Rails functionality or rewriting common Ruby gems due to the lack of mature libraries.
Well, apparently the homeless man was sent by the DOD... http://www.reddit.com/r/AskReddit/comments/weo8j/today_a_hom...
As I recall in my reading of SICP, one of the first big chapters actually hints towards OOP but has you designing it from the ground up. They never call it OOP, but it is heavily leaning towards it; they just happened to set it up using closures (see relevant humorous quotes below). I am referring to the stuff about setting up a virtual function table that switches to the appropriate method based on the type of the data so that multiple developers can write their own way while honoring agreed interfaces/protocols.

"Objects are a poor man's closures." -- Norman Adams (?)

"Closures are a poor man's objects." -- Christian Queinnec (?)
This guy only used 302 from a dump of 453,491 passwords to come to these conclusions. I can imagine no reason why he'd intentionally invalidate his analysis by using such a low sample size unless this conclusion doesn't actually hold when you use a significant sample. I am highly skeptical.
The placebo effect appears to be massive, at least where it's been studied (wine, for example). I'm happy to admit that, as a general rule (coughjaguarcough), higher prices indicate better quality, I just don't think it translates into better value (again, as a general rule).

Sure, highly functional things, like shoes and a bed, probably warrant paying more even though the value isn't proportional. Paying 50% more for shoes that you wear 8 hours a day which are 25% better (comfort, health, style) makes sense to me. But jeans, kitchenware, cars, medicine, food, electronics..the list goes on and on where I feel that, again, in general, cheaper is better.

As studies have shown, money should be spent on buying experiences...not things. It's the trip to Spain that'll make you happy, not the $1500 DSLR camera that you use to take pictures while you are there.
Amplifying Tests to Validate Exception Handling Code