Elon Musk, Twitter/X CEO, went to the data center and started unplugging things. You can’t make this stuff up! https://www.techdirt.com/2023/09/12/the-batshit-crazy-story-... Why “Elmo”? https://www.businessinsider.com/twitter-insiders-users-calli...
I got curious about the book mentioned, and found an EPUB:
Ya, in the past the messaging was more like "get the ergonomics of the cloud with the economics of owning your own hardware", I think it's confusing to just call it a "cloud computer"
Yes - that makes loads more sense to me. It's cool that you can spin stuff up and it's all integrated with the hardware - having seen fairly large VMWare installations and all the faff it takes to make them work, this seems really useful. I just don't think it's the same as the cloud, and the article seems to discount the main reason for the cloud: opex, letting you get started (and stopped) quickly and cheaply.
I might have the wrong idea of what these terms mean, but isn't avoiding capex the main reason for the cloud?
It may be a limited market. You need to be large enough for a private cloud to make sense, but above a certain size it also should be a no-brainer to have a competent ops team making you less dependent on a singular infrastructure provider.
Maybe 37signals type businesses, SMB tech startups with a serious, stable, non-high growth business model and a tech savvy team. If you're selling $500k boxes you don't need to sell a TON of them to make a hundred million dollar business. Unless their VCs expect Oxide to be a billion dollar company with a broader market.
Exactly what I was thinking. Since they are also getting out of the cloud.
Although I am not too sure if DHH will play well with Bryan.
Hey, nice resources, man! Thank you. No worries that you can't decide on the amounts, it's OK :)
My employer takes cost of living into account by multiplying your salary by the numbeo factor for where you live. Base salaries are all calculated for Cologne (HO) and then adjusted by the relative cost of living factor for your locale. (we're entirely remote)
What happens if you move to Hawaii mid way through your tenure?
My employer takes cost of living into account by multiplying your salary by the numbeo factor for where you live. Base salaries are all calculated for Cologne (HO) and then adjusted by the relative cost of living factor for your locale. (we're entirely remote)
What happens if you move to Hawaii mid way through your tenure?
Then your salary is recalculated - it's something which is explained by default during the interview process (as it invariably comes up)
Even more galling about that 20-30%: it is really, really hard to measure. Believe it or not, you can't measure the draw even in fans in a traditional rack-and-stack server enclosure (that is, they are either not on their own voltage regulators or not regulators that have PMBus support, or the PMBus support is not plumbed through the BMC -- or all of these). And these aren't the only fans! In a traditional rack-and-s…
I worked on designing computerized machinery in the past, and having sensors for as much stuff as possible just seemed like a good idea. We had quite a few current sensors for various components. Then we could do stuff like log in to the unit remotely when a customer had an issue, and diagnose based on if something was using too much current or zero current, and that beats having to send out a technician to go poke a…
In the traditional rack-and-stack, if a power supply fan dies, the power supply will shut down -- which is why a server has two of them. (And indeed, in commodity servers, the fan in the power supply is what is most likely to fail.) All of this becomes a bit of a self-fulfilling prophesy: because there are so damned many of them, the power supplies in rack-and-stack servers are really not great -- which means they are more likely to fail. This is all sidestepped by having conversion consolidated in the rack, running high voltage (54V) DC up and down the busbar that is converted by each sled. (That converter throws off heat -- but can then leverage the high quality fans in the sled.)
Dell's VxRail has been very popular and successful. Not perfect, but pretty good, and I think the market leader. HPE Simplivity has done well. Also, Nutanix.
VxRail's the market leader? Last I touched it, it was a mountain of integration faults and vendors pointing fingers at each other. Maybe it's easier in larger or more traditional environments, but I'd be apprehensive of hyperconvered if VxRail's the best available
Evo:RAIL from VMware had those issues, but Dell VxRail has been relatively smooth at scale IME.
Dell's VxRail has been very popular and successful. Not perfect, but pretty good, and I think the market leader. HPE Simplivity has done well. Also, Nutanix.
These seem to solve the ‘host your own cloud’ problem, but are still standard server blades requiring a ton of surrounding hardware and maintenance. Oxide is entirely integrated.
"A ton of surrounding hardware" is vague, generally speaking it's bog standard network switches that are needed.
Oxide is entirely integrated with their own custom (though based on OSS?) networking via Tofino based switches and software. Could be good, but a lot of subtle bugs can occur at this layer. It's a risk.
What happens if you move to Hawaii mid way through your tenure?
Then your salary is recalculated - it's something which is explained by default during the interview process (as it invariably comes up)
I am personally not a fan of this: early in my career, a colleague moved from the Bay Area to Boston to try to save his marriage (which sadly didn't work) -- and our employer adjusted his salary down accordingly. As you might imagine, the difference between the Bay Area and Boston is minimal -- they adjusted his salary down something like 4% -- but I just recall how dispiriting it was for him to have this massive, stressful (expensive!) life transition exacerbated needlessly. Employers don't factor in other elements of cost-of-living (can you imagine giving someone a pay bump when a kid goes to college -- or a reduction when they graduate?!), and I don't believe geography should be factored in either: pay people for their work, not their ZIP code.
I always had a feeling that Bryan and people around kinda took the tech first approach and it never really came to a proper fruition. I think the ambition behind the engineering marvels they did over time was certainly bigger. Dtrace, Fishworks, Joyent, then this... so why is that? Perhaps the fierce refusal of joining the mainstream side (Linux)? Fingers crossed, but...
You've been downvoted to oblivion, but let me add a personal rebuttal for anyone else that finds themselves here: I don't agree at all about "not coming to proper fruition": DTrace was an absurdly outsized success by any metric; Fishworks was if anything too commercially successful (we did nearly $100M of business our first year!); Joyent represented a successful exit to Samsung, etc. I have been extraordinarily blessed to be in the right place at the right time with the right folks several times over -- but never more so than at Oxide: our ambition is absurdly ambitious, but it has never felt more attainable!
All of that said: thank you for keeping your fingers crossed. ;)