krobertson

Most gasoline cars will get pretty low on gas with a full day on the track. I track and usually end up topping up some after lunch. Most tracks have gas there, and charge like $6-8/gal.

Often with Tesla, year people leave at lunch to go to the nearest supercharger. If tracks added some fast DC chargers, it would be a nice boost.

They even come stock from the manufacturer on many like the Porsche 911.

Derek's hashmap was faster than than Go 1.0's built in hashmap. With Go 1.1 or 1.1.1 (don't remember which one exactly), the standard one did become faster, though Derek had decided to stick with it as is. I can ask him what the reason was... I don't recall right now.

I hadn't seen runtime.Gosched() before, will take another look at it. Mentioned it to a coworker and they already knew of it, so maybe it was always switched to call it instead of sleep. :)

Yes... the primary case where it was biting us was with our testing suite. It was a set of functional tests that had multiple goroutines going.

It was something that had always passed and never been an issue on 1.0.3, but started failing 85-90% of the time on Go 1.1 with no code changes. :(

I hadn't looked at that issue before, but have definitely been bit by it.

On our main codebase, we experienced some major issues when moving from Go 1.0 to 1.1 from this exact issue. We had a goroutine that was doing some remote calls wrapped with a timeout, and the call was consistently timing out even though the remote service was perfectly fine (it was another service on the same box).

We found the cause was another goroutine running something in an for loop that didn't do anything that would allow a pause in execution for another goroutine. So, the scheduler just obsessed on that goroutine, running none of the others until that one was done, and by then the timeout on the remote call had expired.

We fixed up that case, but also found a few others were we simply added a very small sleep call... for no other reason than allowing the scheduler to evaluate other goroutines. Meh. It made sense when we finally tracked it down, but was one of those things where we had to pause and ask "really?"... and adding a sleep call with comments "yes, I am really calling sleep".

The remote package importing is quiet easy to work around and to lock on things. It actually forces you to think about the process and tracking more. But also, dismissing Go solely because if that doesnt do it justice. Same as any language...

(I work at Apcera)

Soon™

(I work at Apcera)

We didn't write our own HTTP server, but rather a framework that sits on top of it and makes it easier to use.

The logging library is quite unlike anything else we're aware of, and the goals of it were language independent. The author of it is giving a talk about the library and our experiences with Go at GlueCon next month.

The ORM is the one which is more a result of what we wanted not being represented by existing libraries, and the community being still smaller compared to Node.

However, with all those still considered, we've gained a lot of velocity with Go, better concurrency without doing full async development, etc. Personally, I've hated testing async code in the past with both Node and EM+Ruby.

(I work at Apcera)

The "15 minutes" part was hyperbole.

The timeframe referenced the length of the discussion of the two, not the knowledge the decision was based on. Several of us had previous experience with Node, and some of the team had prior Go experience.

"my fellow co-founder who just happens to have a lot more experience in the field of hacking and getting hacked"

I see irony in the "getting hacked" part. But seriously, if he is more experienced, then why do they have machines unpatched like that for 6 months?

"it seems it was indeed a kid who did not understand how to install a proper rootkit and cover up his tracks"

It is rather bold to be posting about how you just got hacked by not applying simple patches, and to then bash the "kid" who couldn't install a proper rootkit.

Sometimes it just interesting to walk down the datacenter aisle and look at others wiring... can see some where nightmares live, and others which are quite sexy and interesting to study.

I love f.lux, I just wish it was adjustable for that exact reason. It is winter, it gets dark out early... I don't want it to shift to night time mode at 5pm. I find myself hitting "disable for an hour" 1-2 times a day before I leave work.

However, when I get home and get back on my system, then I'm ready for night time mode.

I prefer the 20 second switch over so I know to turn it off fast. With the long transition, I find myself being annoyed for a while until its enough for realize I need to turn it off.

I'd love a simple "activate at sunset, but not before X:XX".