My favorite tech poem is Radia Perlman's "Algorhyme". She's the inventor of the spanning tree protocol.
Algorhyme
I think that I shall never see
a graph more lovely than a tree.
A tree whose crucial property
is loop-free connectivity.
A tree that must be sure to span
so packet can reach every LAN.
First, the root must be selected.
By ID, it is elected.
Least-cost paths from root are traced.
In the tree, these paths are placed.
A mesh is made by folks like me,
then bridges find a spanning tree.
Radia Perlman
Though I appreciate the idea of 'storing bandwidth' by just sending lots of qubits ahead of time, that ignores the extra communication overhead needed of tracking them: When Bob receives a qubit from Alice, he needs to know which of his qubits it's paired with. That implies that Alice needs to send not just her qubit, but also some kind of identifier that will allow Bob to match up the received qubit to its proper Bell pair. That identifier, and any protocol overhead needed to keep these identifiers in sync between bob and alice, will consume bandwidth, and reduce the 2x gain.
Perhaps the attackers are drawn to sites they believe will later publicly document the attack, to learn whatever they can on how the operations team responded.
I've got a passing interest in Erlang, and also saw the existence of Elixir http://elixir-lang.org/ , which uses the Erlang VM. Could someone from either language's community comment on if they see a strong future for Elixir?
It runs on Erlang's VM. So there are chances if you pick one up or another you'll be able to at some level inter-operate.
It is up to you, try one and another one. Some people have big issue with Erlang's syntax. I actually kind of like it, so I prefer Erlang.
Others find Elixir more approachable, it reminds them of Ruby for example. Elixir has macros so you can do some nifty things with them. Those kind of blow my mind when I read them so I am afraid I would get too "clever" with them.
You can call Erlang from Elixir fairly easily so you can take advantage of libraries you find for Erlang.
So kind of up to you. Whatever you like or whatever gets you more productive and interested.
Think of elixir as a nicer and more approachable erlang. It compiles to the same byte code. It's very young but I think once it hits v1 it will have a very bright future I think.
Because instrumenting the frontend should be easy. (Let's just say that's the visible part of the iceberg). We've opened up the hood in a new way, enabling full x-ray visibility into the frontend (and a lot more that will surface in due time). Ok, we know. That's a little cryptic. We look forward to being able to say more, and in the meantime, if you're really curious, try reverse-engineering what we're doing from our jobs page. You'll see we have some tasty ingredients.
We've just finished seed funding, and are looking for our second and third engineers.
Software Engineer - Javascript Frameworks Expert
Are you tired of sprinkling blobs of Javascript instrumentation code throughout your applications? Have you explained the importance of the waterfall graph in DevTools a zillion times? Do you think that movie theatres should play compilations of Paul Irish videos? If so, this position might be for you.
Qualifications:
Demonstrable expertise with multiple programming languages
Expert understanding of web technologies (Javascript, HTML, CSS).
Expert understanding of at least one frontend Javascript framework (Backbone, Angular, Ember, Knockout, etc).
Substantial experience with Chrome DevTools.
BS/MS in Computer Science or closely related field.
Bonus points:
Experience as a team or project lead.
Experience with d3 or other Javascript data visualization libraries.
Experience creating applications with node.js.
Familiarity with WebKit or Blink internals.
Software Engineer - Core and Backend Lead
You will work on the architecture and implementation of our core service. This includes both the core Sessionbox technology to monitor and analyze our customers' production web applications, as well as the backend infrastructure that will keep our service available and scalable.
Qualifications:
Demonstrable expertise with multiple programming languages
5+ years creating and scaling web application backends (including node.js)
Deep understanding and implementation experience with HTTP proxies.
Expert knowledge of at least one NoSQL database (Mongo, Cassandra, etc).
BS/MS in Computer Science or closely related field.
So I'm not sure why this is HN material, but as I have recently co-founded a company (www.sessionbox.com), and just purchased a new printer because of it, I'll pipe up.
When you start a company, there's a ton of paper involved:
- corporate paperwork, including founding documents, stock agreements, advisor forms, etc.
- business contracts: lawyers (corporate, IP, etc), recruiters, office space, etc.
- and most recently, your first big expense report once the seed money lands and you want to pay yourself back.
My old consumer cheapo printer died just when I was trying to get the offer letter out to our (soon-to-be) first employee. The printer just locked up, with all the led's blinking, and I kept power-cycling, to no avail.
While reviewing printers, I decided that the new one needed a "scan to email" feature. Be warned, however, that some cheap printers have a feature that they call "scan to email", but what they mean is: if you hook up our printer via usb to your pc, we'll open outlook for you and attach your scan to it. frak that, man.
What 'scan to email' should really mean is: I walk to the (wirelessly connected) printer/scanner; I put something in the doc feeder; I then use a little display to either a) punch in someone's email address or b) look up frequent email addresses. And then I hit a button, and it scans them, and the printer mails it to them. (As in, it speaks smtp.)
So I ended up with the HP 8600 Plus. The "plus" is important - the plain 8600 does not have scan to email. It's been fine so far, though my bar is probably low.
The BeOS userland api had base classes with reserved functions that were there solely to reserve space in the objects vtable becase of the fragile base class problem:
My rough estimate was ~$14,000 for 24 hours of 10,000 windows instances:
24 hours of 10,000 non-persistent on-demand Windows micro instances in Amazon West: $7200
Assume 0.5 mbit/sec average to each instance over 24 hours (105TB): $5020
AWS data rate from aws is currently 0.
If I understand their pricing, cyclecomputing adds a 20% upcharge: $1440
I'm unfamiliar with the HTC/HPC space but I'd highly suggest running with just a few micro windows instances with some kinda dummy job to verify they work well enough for your purposes. For what I've tried to use them for (website + database type of demo machines) they've been just about unusable/ way too unresponsive to get much done. Linux micro are good enough for most stuff I need but not windows ones.
While not that big a charge relatively speaking -- you'll need to include EBS as well since micros only have EBS
- EBS space (10c/GB/month) -- I'd imagine 10GB minimum per machine though AWS provided instances have 30GB.
- Est: (10,000 machines * 10GB * $0.10) / 30.4 (avg days in a month) = 328.95
- EBS IO (who knows? depends on what you do) -- rate is 10c/ 1 million IO ops.
I followed cloud pretty closely at the conference.
My biggest take away was that: if I'm going to do public cloud... I'll contract out a company to deal with the details of bringing up the cluster/images.
