178 karma · joined January 23, 2012
As for every country making their own laws - well, yeah? That's what sovereignty is all about?
THIS.
This is not stated enough in the value of gofmt - it's the standard formatting style for everything. I've worked in Java and C++ for a couple of decades, and while every team has had its own style guidelines, and occasionally tools to enforce them, even different teams in the same organization would have difficulty understanding each other's code.
The value of gofmt is that it's the only formatting standard, thus I never have to learn a new formatting style when reading the code for an open-source library, or coming in to a new job. It's exactly the same as what I've been reading for the last 3 1/2 years of working in Go.
(I picked 600 because that was the approximate number of machines we had at my last job, where we used Graphite maintained by one guy, part time).
You included a LOT of redundancy in your OSS list. Multiple timeseries databases. Multiple collection daemons. Multiple dashboards. Multiple alerting systems (Who in their right mind would use Nagios AND Icinga?). You're effectively arguing about maintaining multiple monitoring stacks, some of which are quited aged.
That may have changed somewhat in the TS 1.5 alpha - they're supporting more features on the ES5 target than they did in 1.4.
But yes, you still can't use ES6 features that TS doesn't know about.
When you write "standards" without implementation, what you get is the Object Management Group, which published spec after spec that are impossible to actually implement.
Standard disclaimer - I'm the author of Tessera.
We're looking for people to join our back end team (which is primarily Java, hbase, cassandra, high volume RPC services), and our web team (JavaScript, python/django, d3, etc...)
Our San Francisco location is a small, engineering and operations-focused office in SOMA. We have the feel of a much smaller company, but we operate at a scale of billions of events per day. If working on APIs that get called 40,000 times per second, all day, every day sounds interesting, you might like us.
Doing interesting things with a firehose of kafka events is also something we also do a lot of.
We support open source software and believe in good tooling (we just released a new project yesterday -- https://github.com/urbanairship/tessera; full disclosure - that was my project for our internal Hack Week recently, and we're now monitoring our metrics in production with it), and minimizing the obstacles to getting stuff done. We also believe in work/life balance, as well has having room for people to work on their side projects; most of our monitoring stack started as side projects!
In our backend stack, experience with Java, netty, protobufs, kafka, hbase, high volume TCP/IP messaging in general, designing and building REST APIs, postgres, postgis, cassandra, geolocation technology, automated testing and deployment are all valuable.
You can check out the official listings at http://urbanairship.com/careers, or send me a note at alpern@urbanairship.com
"You shall not [...] (iv) reverse engineer or access the Application in order to (a) design or build a competitive product or service, (b) design or build a product using similar ideas, features, functions or graphics of the Service or Application, or (c) copy any ideas, features, functions or graphics of the Service or Application, or (v) launch an automated program or script, including, but not limited to, web spiders, web crawlers, web robots, web ants, web indexers, bots, viruses or worms, or any program which may make multiple server requests per second, or unduly burdens or hinders the operation and/or performance of the Service or Application."
I learned more about the fundamentals of programming in one semester of compiler design than I did in the rest of 4 years of courses. It ought to be a requirement for any comp. sci. degre, IMO.
The receipt printer is $300. I boggled at that too, and then looked around, and that's really what it retails for (or close enough). I have difficulty understanding why it's so expensive, but do keep in mind that it's designed to work for years on end in a retail environment -- it's got to be overbuilt to last.
The Samsung tablet has a screen that's either the same size or slightly larger, and a lower 1366x768 resolution, and I have a lot of trouble using the windows desktop on it with anything other than a mouse (including the digitizer pen -- yes, it's more accurate than a fingertip, but you still have to hold it steady, and holding it steady enough to hit a 4mm target is pretty tough).
As a developer, it also doesn't help that Microsoft made a lot of noise about them being on the same kernel, even though there's hardly any API overlap between them.
I've seen the current state of the SDK and API, and while I understand porting to a new kernel was probably a lot of work for them, it makes even less sense considering that most of the WinRT APIs available in Win8 are not there in WP8 - it leaves me wondering what, exactly, they hoped to gain; so far it doesn't seem like a win for developers, and you can't write a full-featured native app for WP8. Maybe you'll be able to for WP9 (if the platform survives that long).