531 karma · joined December 17, 2013
With a language like JavaScript it can take a really long time to learn all the stupid stuff like when what this means. With Python it can also take a long time before you start having to figure out the various string representations, operator overloading and the crazy underscore variables. That kind of magical hidden complexity you see in other languages I don't think exists in Go, which makes it easy to learn.
With Go, I feel at least you can learn all that is Go in a week or so, and start building. Something like the "learn ruby/rails in 30 days" would never make sense to me given how easy it is to learn Go.
A lot of the expertise you see in Go comes from people who really know about the Go implementation. The way structs are represented in memory on different hardware, compilation optimization, the crazy stuff that most people are just not going to care about especially if they're going to run Go on some kind of cloud provider or in a vm.
Uh, Rackspace has built completely functional and running OpenStack infrastructure, multiple times over (many datacenters).
We can't stop interacting with the real world, but I imagine in the future most people wont. Current boredom is a reflection of our current technology and creative state in virtual worlds, not indicative of what the future will hold, it's only going to get better and while nature is amazing is so many ways human imagination trumps it. Whenever we do see something new we take it and add to it.
Modern day gaming is the beginning of something much more significant in my opinion.
As a software engineer this statement really bugs me. Once something is damaged in the real world you can't assume control over the system anymore. The part that cuts or provides the power to the laser might have been the thing damaged. Maybe if they had added a qualifier like "power should be cut" instead of such certitude.
It was a great learning experience though, because before I became a manager I thought that was like a natural progression, something that I had to do, something that I felt I couldn't shirk from, something where people recognized me for my skills, but in reality it's just a shit job, a dead end, unless you're one of the few who advances up the latter, because you know what, all of my managers and my manager's managers were all just relaying their manager's will down the pyramid.
When you are a software engineer you see things you do create value. You build things that work and do stuff. When you're a manager, I have no idea what I contributed. What did I do last week where I earned my pay? I have no idea.
Anyway, I'm glad I survived and am back to writing code. It involved getting a new job at a new place as soon as possible before I got too rusty. I was writing code at home all that time so that helped.
> Software still installs toolbars on Chrome too.
Chrome does not have toolbars. You cannot build a toolbar with Chrome, the browser has no extensions API to build such a thing. You also cannot programmatically install extensions. Windows software cannot install extensions into Chrome, barring some kind of malicious exploit or vulnerability in Chrome, Chrome will ignore them. They have to be installed by the user from the Google Web Store or via the developer tools, which has to be done manually.
I'd like to hear if anything I've said in the previous paragraph is wrong, I have never seen a toolbar in Chrome ever. You can't even build it into the website with scripts because of how those APIs work and anyway websites could detect that and I've never seen it.
> WebRTC isn't even half baked yet. Complaining that they don't release it to millions of devices as a feature is silly. It's great to see browsers experiment with new APIs that become standards... which leads me to: touch events.
This is bullshit, as we've built WebRTC into our application and it works perfectly in Chrome and Firefox. In addition there are entire businesses based around WebRTC availability so, you are mistaken here.
> Open source isn't something that makes the browser better at being a browser.
It matters to developers who build websites. I can debug my application all the way into the Chrome source, and have had to when JIT ruined my JavaScript.
Even 6 month updates are way too long, and I doubt that we'll see updates in that time frame anyway. The IE VM tools are slow and horrible, it's not usable, I've tried it. It's no replacement for native development and we're not going to support it. Maybe some draconian soulless corporation has made browser vm's an option to their poor mac engineers, but fuck if I'm going to do that. Your entire apologist response is factually incorrect or misleading. It's very misinformed and one-sided (although I also come across one-sided). Weird post anyway.
For me to care about IE, it would:
have to be available on Mac OS X.
have to have bigger market share in mobile
just have more people using it in general (because frankly it's not used much by any of the people we care about).
have much, much better development tools
Our development cycle is to develop in Chrome Canary, and proactively test and fix for Firefox. We don't test in IE but fix IE issues when someone complains about something not working in IE and if we have the time or think it's important enough.
Hoards of people dump insane amounts of money into a new, unproven and unstable currency technology. What could go wrong?
EDIT:
It's not petty to point out that a brand new repo that doesn't look like it works, has zero documentation has been seen by a handful of people is not a good example. This is for secure code. SSL. It's pretty important to get right. This isn't a a repo for a JavaScript accordion widget. It's SSL in Rust. I'd like to see SSL in Rust. I want Rust to do well, there's nothing petty, you're reading my tone wrong. It's hard to read intention over text, assume better than you are. I've been sitting in #rust on mozilla IRC for nearly a year watching them develop the language. I'm not just catching up on the latest by reading HN.
As for jfager's a decade vs more than 3 lines rebuttal: read my other responses where I specifically qualify on using C libraries. I am going to going to go ahead and guess you haven't done much raw SSL stuff. It is a ton of work. We're not talking 5 more lines of code. We're talking thousands of lines of code, and that it will be a decade before rust catches up with go. That's just an anonymous commenter making a shitty prediction that nobody will call me out on. My point is that Rust isn't ready. Go is. Stop comparing Go to Rust. Rust doesn't work yet. Don't use it unless you want to help develop the language. All you're going to learn is how to work with a specific half implemented language that can't do basic things yet. Read my original post. I don't hate Rust, I am contrasting the HN echo chamber to love of a language that you should not be using for anything right now. This is not a controversial statement, it's right there in a big highlighted disclaimer on the rust reference manual[1].
[1] http://static.rust-lang.org/doc/0.8/rust.html#disclaimer
Yeah opening up TCP connections and reading plain text http isn't hard, but there's no way to do any kind of SSL https requests with servo, which is kind of a nice thing right. And that's going to be a long long time before you ever see SSL. Have fun with those C libraries.
> personally i'm waiting for rust
See, this seems weird to me because Go is actually a language that you can build nice things with right now. Check out coreos's etcd[1] for example.
Rust on the other hand gets a lot of adulation in this echo chamber but is so, so far from completion that you're going to be waiting like a decade or so before you can do anything networking related with it. And personally the varying clumsy degrees to do the same thing many different ways in Rust (the various boxing and unboxing and other memory handling options) are a real turn off.
Comparing Go to Java is fair, and of course Java will come out on top given its maturity, but Go offers a lot of good things. Comparing Go to Rust is not, Rust is not ready for any kind of real world use.