eric970

I love how at the end, they're all like "hey, our competitors do it too!"

You don't need data to back up bold claims when your ego is the size of a watermelon.

[rant] If you're going to claim that your strong opinions are facts, please treat them as such and give citations or back them up yourself. [/rant]

Ruby is not my favorite language anymore, but I still use it and see evidence that there is a huge place it fills in the dev community and ecosystem. I have never used a more expressive language. I'm stating this as a fact from what I have experienced, and I'm giving points that back it up. There are dozens of actively maintained Ruby projects, some of which are the most popular repos on GitHub. I don't see any evidence that the Ruby ecosystem is on a downward trend of activity and is "dying", so I have no reason to think otherwise.

This kind of stuff reminds me why I take breaks from HackerNews every once in a while -_- Yuck.

Storing IDs in session cookies is not something the Rails framework introduced. Smh. It's easier to blame someone else's code though.

So the provided solution is, essentially, to store a list of active user sessions in the database and use that as a reference during authentication?

I love this game. It starts out simple, but as your country's relations with other countries change, the rules for letting people in and the amount of security in place changes.

"Diet" and "weight loss" are often used interchangeably, sure, but can you think of any instances in which diet Pepsi or diet Coke has been advertised as actually causing weight loss (ie; the product itself is a weight loss supplement)?

I think the name "diet soda" needs to go, as it really is misleading, but (and I could be wrong about this) I don't think these companies have ever claimed their products make you shed pounds by simply drinking them.

I agree that calories can have different impacts on people. We all require a certain intake of calories to achieve a certain weight or build. There are a lot of different variables that make this happen, such as exercise, lifestyle, genetics, and so on.

But where is the evidence that a calorie-free beverage can have an impact on your metabolism? You're eliminating the idea of calories entirely with diet soda, so I don't see how your argument stands any ground.

Er, this whole topic can be a little misleading. I haven't found a single reputable study that claims diet soda itself causes weight gain. Rather, just as the reasoning in this article suggests, the only scientific fact they present is that the consumption of diet soda itself does not encourage weight loss.

Side note: Do any brands really advertise drinking their diet soda as a method of (actual) weight loss? I can't think of any that actually present it this way.

It goes on to say that substituting sugary soda for diet soda isn't enough for most people to stop gaining weight. This is probably because you're likely to substitue the calories and sugars for something else, since your body notices its getting less of something and will crave it.

Yet you have things like this:

"One large study found that people who drank artificially sweetened soda were more likely to experience weight gain than those who drank non-diet soda"

This again is a correlation with the typical behavior of a diet soda drinker. They're not drinking diet soda because they want to lose weight. Rather, they're drinking it because they don't want to gain weight. They could have a terrible diet overall and this alone does nothing but move the problem over into, say, consuming two scoops of ice scream after dinner everyday. All because the soda they had during lunch didn't satisfy their bodily craving of refined sugars.

So this is a case of correlation not being causation. These types of articles do nothing but encourage this error to propagate. Perhaps the term "diet soda" is misleading in itself, but perhaps telling people that drinking a calorie-free drink will make them gain weight is just as silly as telling people it will make them lose weight.

I love how people jumped all over Go on that thread, without having any idea of what they are talking about.

Gotta love the Internets.

Yeah exactly. This shit is ridiculous.

This might sound harsh, but...

Maintaining software is hard.

Blaming your own incompetence on a library or an entire language is easy.

I've been guilty of this at times, but when you get down to it, it's your job as a software developer to understand how your software works and how to maintain it well. This doesn't just include the code you write; it includes your tools, third party libraries, and the internals of the language (VM, compiler, etc.). Its not easy, but it's part of the job.

On a more positive note, versioning packages in Go is already possible and is starting to gain momentum. Check out http://www.gonuts.io/

Sounds right to me as well. But hey, isn't it much easier to blame the language and its VM? Or interpreted languages in general?

Has anybody seen their bulletins? Their first one advised people to go celebrate their "success" by drinking Champaign. Never mind that their exchange just lost ~half of its net value. Yuck!

And now, guess what MtGox advises everybody do? Go drink some Champaign! To celebrate their massive success! I'm not kidding-- look at their latest bulletin on why they're suspending trading for the rest of today.

You've got to be KIDDING ME. They don't seem to give two shits about their users or their money.

I'm sure it's been stated already... And well, I'm no Bitcoin fanboy, but didn't the price just go back up to what it was 2 days ago? That hardly sounds like a "crash" to me.

If it's as accurate as the team says it is, this is pretty astounding IMO. They'd have to be capturing some sort of baseline in the beginning of the conversation, and recording relative shifts of variables (ie; smile, eye shift/location) to come up with how "depressed" the person is. Just writing some software that says "oh this person is looking down" probably wouldn't cut it-- because shy people look down too. I noticed in the demo it seemed as if it started monitoring these things after certain questions were asked, which would be the correct way to measure a shift from baseline. Elicit a predictable period of what could be change and record.

I'm not an expert on the matter, but to be fair there are lots of things you can do to secure your wallet. Some of them are even discussed in that thread.

I also had problems. I couldn't create a new account with my IP address, even though I just moved in to my new apartment. I had to use Tor. Weird.

No matter what language or VM you choose, there are going to be tradeoffs. A good engineer understands these tradeoffs well and makes opinionated decisions with all the knowledge he or she has.

All the "my language is better than yours!" bashing is a result of being stubbornly opinionated and not willing to look at things from another perspective. There are always things that one VM will shine with where another will fall flat at, at vice versa.

Also, I don't think Ruby is nearly as bad as most people think. It's not as monolithically slow and vulnerable to exploitation as some people on HN claim. The VM is decent, and there are ways to tune the performance up that make it even "good". See, there's a tradeoff. The language is, IMO, fantastic, but you're going to take a performance hit for that that you need to deal with in some way or another. You're trading execution speed for "developer happiness", whatever that means anymore.

^ Excellent comment right here. +1 for educational value.

He didn't explain how DOCSIS works.

I'd try couchsurfing first! :)

Agreed.

LOL. I know this is a joke, but I'm actually a ruby dev myself diving into Go. I find it to complement Ruby extremely well. Both have their strengths and weaknesses.

I don't understand. Where's the context here? Had the library became mature enough to warrant a bump to 1.0? Or is this criticism of DHH?

Most of the attack vectors the author brings up don't relate to the OAuth2 spec per say, but to a poor implementation of it. Not escaping HTML, having your users getting phished, allowing arbitrary redirect_uri's to be set... These are things a security-conscious OAuth2 provider would never allow to happen. These are all things we have consciously avoided in our implementation.

I feel the author's frustration with the spec. I think that the OAuth2 spec could do a better job of outlining best practices and security, but calling it a terrible spec over the potential of poor implementation isn't right IMO.

Also, stealing an access token is far from "Game Over', as the author states. They're short lived and meant to mitigate the damage done by having one or even several leaked. Getting your hands on a Refresh Token would be closer to "Game Over". Although even then, it'd be trivial to have the compromise reported and expire the Refresh Token of that client and subsequently all access tokens.

ACTS came way later. There's a great article on the history and eventual (mostly) discontinuation of it here:

http://www.phworld.org/payphone/acts.htm

I was briefly on #phreak. Your handle sounds kind of familiar. Sad to say, I thought most of the regulars were elitest as hell and I never once saw an intelligent conversation go down on there.

It's funny how these days, those systems and variations of those systems (COSMOS for example) are STILL used. Talk about legacy systems. Not more than 10 years ago, people were still breaking into them.