1,062 karma · joined October 30, 2015
Looking forward to trying it out.
Nice to have a supported, pro-grade monitoring product that isn't priced per server, finally.
You can go without a connection for several minutes easily.
The article also unusually describes "thinking about keeping the suit under positive pressure." The vents in the suit have one-way valves, so it really isn't something you need to think about.
(-occasional researcher in a BSL4)
You can basically self-certify, but most serious companies will bring in an outside contractor on an ongoing basis to certify compliance. Staff needs to be trained, computers need to be managed, software changes have to be very thoroughly reviewed, updates become slow. It makes it pretty unattractive to enter into for a lot of devs.
As someone in the field I beg to differ :). And regardless of who pays in the event of a breach, the effects may be sufficient enough to shut down the company for future projects.
Last I calculated, it's nearly 5x the cost of comparable t2 on-demand EC2 instances. That can be mitigated if you have spiky traffic where you'd need to turn on several EC2 instances for less than an hour but are stuck paying for the full hour, or if you can scale to zero for extended periods of time.
Critical to us: you don't have the ability to serve concurrent requests from a single lambda worker, so if you're waiting for async IO (e.g. downloading from S3) then you're wasting money you wouldn't be wasting with EC2. You end up with one file per lambda worker, whereas we could handle about five files concurrently on a normal VM because of async IO. -- For us lambda was prohibitively expensive at scale. I suspect a fair number of people reporting significant savings vs EC2 had over-provisioned instances.
"The Engine will demand less equity in startups than is typical, allowing founders to maintain more control over their companies."
That's the planning doc for v8 optimization of ES2015+ and an interesting read.
The author says that Atlas is essentially "required" for bootstrapping. We simply use our cloud provider's "list-instances" command (with a filter) so that we don't rely on any third-party and never contact the internet. This is important to us for security and stability, and has kept our cluster running with over 1k members. We don't want to go down when Atlas or etcd's discovery service goes down.
Sublime I think still has the snippet for "optimized for loop" that runs in reverse. I have never seen that improve performance, and I didn't know that it could actually be harmful if used to initialize an array.
Nit: The spec makes no such demand, they can be anywhere. In v8 small TAs are indeed on the heap.
https://moz.com/devblog/amazon-ec2-spot-request-volatility-h...
From talking to AWS, when people pay above-on-demand prices, it's because they carelessly put in a huge bid.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436
[0] https://cloud.google.com/compute/docs/images/export-image
Most bioinformaticians I know are poor developers, have limited knowledge of existing algorithms, and/or have critically limited bio knowledge. As a result you get buggy, slow and unmaintainable software (see: all the MRI analysis software posts recently), reinvention of classical algorithms (anything from basic statistical tests to full on clustering methods) or tools lacking the full scope required to actually be useful.
I think MS could change this by having strong CS/SWEs with longer tenures than you see in academia, backed by more money and essentially unlimited computing resources, with a high profile name to win them collaborators who can share good datasets. (Compared with Google, they're not trying to generate data in-house as far as I've heard.) Some of the most notable advances in bioinformatics have come from applying decades-old algorithms that never made it to bio before then. Even if MS just accelerates this by applying people who know about these algorithms, that would be very helpful.
Awesome company with awesome products.