61 karma · joined December 20, 2014
Been to the four corners and seven continents.
Lives in a Westy.
Maker of code and dinner.
"+!" If you want C-like behavior.
It'll be imperative with full dependent types as well.
Also interesting: cryptol, Irdis, coq, but the work is on making generic systems programming clear as possible in a static, imperative language without a titanic runtime or crawling along with superfluous assertions.
TLS is far too complicated with design-by-committee, special vendor extension sauce nonsense. Heck, the FIPS code was rushed and basically done at the behest of US/Canadian govts. OpenSSL should consider burning their deadwood and stop adding features until it gets its house in order.
There's no telling how large of an attack surface remains at the protocol level, in the codebase and with CAs being compelled to issue rogue certs for MITMs.
Moreover: Can TLS features be narrowed to focus on popular and high-value use-cases instead of SCTP, UDP, oh look a bird feature? It's fine for hacking on, but not production code. (If "TLS" is evolutionarily to "Perl," who's working on a "Python"?)
BTW: What ever happened to the cert WoT overlay 'moxie0 was working on?
Move fast, break a few things and
There's a million and N ways to die, both as a company and an individual, if you let them. Basically, expect failure as a default state, don't (or try not to) take it personally. Don't give up on something that people want (and will pay money for)... you may hit 2 to 5 patches where it's "this sucks, I wanna die" times. Get over it (you can if you really want it bad enough), move ahead. (If not, take a break and recover... Working crazy hours/conditions if it kills you doesn't help anyone.) Even if you have to live in a car or tent, put in the effort to make the best shot possible. It's basically impossible to die of starvation in Amerika at least... More caffeine, exercise and less "ambient eating"... Self-restraint is paramount. Get back in the saddle, get up off the ground, another biz model awaits expermentation... Maybe have some survivor bias eventually, if not start a practical business. It'll all work out, on way or another. Have a good time along the way. :) No one has a perfect formula or perfect advice, just do the best possible and hire people that do whatever it is much better.
(Picking cofounders carefully as one would their SO, because it's effectively marriage.)
The issue is whether it's worth having a bicycle that can turn into a car and a car that can turn into a bicycle. Most of the time, the execution on these is terrible at both.
Moka5 was basically running apps on packaged VMware hypervisors on Mac and Windows endpoints, but centrally-managed like Citrix Metaframe.
The better approach is simply wrap the app up in a read-only bundle, use an fs driver to redirect writes to a shadow vol and deploy it to endpoints without having N addl VMs to manage (so it can work ThinApp or client-side.). Even the OS minus config should really be a verifiable, read-only archive.
Disclaimer: I've had mtgs with Monica at Stanford. The similar word from both Citrix and Vmware is that that neither could develop sustainable professional relationships for an acquisition event to occur. Sad, but typical.
People demanding something for nothing doesn't scale, so it we must settle for something in between: Mutual value.
If form factors don't change, reusing the mounting hw, PSUs and enclosures can be doable. Some web shops wait until boxes die entirely before replacement while IT shops lifecycle out all gear (usually everything but racks) in 4-6 years.
These hotdog USB sticks aren't upgradable at all and they're limited to the processing power of 5-10W.
Also, how much power would be lost by all those cheap bricks compared to a single, efficient switching power supply?
It also would be 65 systems to maintain.
Renting a fraction (via cloud/VPS) of a green server (good PUE DCs and LP gear) is far cheaper and greener. But more importantly, waste fewer computing resources.
(This product line is DOA.)
Also, you'll need to setup a cloud cluster... A nontrivial task.