Just a heads up: https://singleops.com/contact/join-our-team/ is a 404 for me.

Would it not be possible to write a contract that has intentionally random results? Could you not use the timestamp or some other piece of data to flip a coin to determine the outcome?

Does the EVM prevent this in some way?

I did some searching but I'm not sure I know what to look for either.

Clicking on the "Features" link in the footer under "Navigation" takes you to /faetures, which of course is a 404!

Thanks a bunch, fixed this just now. It's great how can you spend loads of time on finding typos in the regular copy and then let something like this slip through.

The title is a bit misleading in my opinion, but it was a good success story nonetheless. Congrats to Brad and the team.

Edit: By title I meant subtitle. I think it was changed on HN.

Just FYI, the image at the top doesn't look that great on my retina display!

Thank you for the info @binofbread, I didn't know that. Could you please send me a screenshot to diegoloop@icloud.com? That would be great! Thank you!

Should be better now. thanks :)

I would love to sign up, but when I click to create an account, I get redirected to the home page.

You have to sign up through the homepage. It could be more clear.

+1 - This one caught me off guard for a second. You have to complete the two challenges on the home page before it'll let you sign up.

The sign in we have there is just for current users. To sign up just take the challenges on the homepage - Good luck!

I see. It was very confusing to click "Sign In" then click "Don't have an account? Enlist Now." and be redirected to the home page. Looks cool though, thanks.

Edit: I now see the intended flow, but there was no indication that I had to complete the first 2 levels to be able to sign up.

My hand cannot do 9 the way you describe. My pinky is too stubborn.

I'm running into a similar issue and fairly new to angular. In fact, the tutorial I followed even set up the server calls to use the _id field when looking at a specific model (ie leagues/{{ league._id }} ). What's the proper way to go about fixing this?

You can always create functions that refer to the private element:

MyObject.prototype.id = function(){return this._id;};

Which gives you: leagues/{{ league.id() }}

so what the point of introducing a "private" access modifier that doesnt exist in javascript since one can still access privates? looks like pure politics within google.

A breaking change like that shoved at the latest minute? you bet it is.

> shoved at the latest minute

The pull request was opened 3 weeks ago with plenty of discussion.

3 weeks of discussion for a breaking change is "last minute" in my book

why didnt you think about having this feature optional? class based controllers are optional yet,because of them you introduce a feature that affect function based controllers ?

> why didnt you think about having this feature optional?

Opt-in security features aren't very useful.

> class based controllers are optional yet,because of them you introduce a feature that affect function based controllers ?

That's how competing constraints work out sometimes.

We're always looking to improve though. The code is open source, so feel free to submit a PR or fork it if you disagree. :)

Don't use 1.2.0 until it's reverted or write a getter.

Well said, thanks for the insight.

I don't think learning Rails right now is a bad thing. I've been doing some side projects in it for ~2 years and definitely don't regret it. As some other folks in here have mentioned, there is always going to be something newer and better out there. If Rails is your first or even one of your first web stack experiences, it is a great way to learn the fundamentals and it makes learning the next new thing that much easier. In short, the "next big thing" is ever changing and I don't think anyone would call Rails old. It's just no longer new.