One company with all-male board & management team buys another company with all-male board & management team.
Samsung Acquires Joyent
201–210 of 256 posts
Re: Samsung Acquires Joyent
#202Cloud orchestration, Container Orchestration, Kubernetes... I think I am getting old and starting to understand how my parents feel about technology. I am developer, but mostly work on desktop apps, or embedded devices or lataly on some MVC applications. But reading things like "A Container-Native Stack for Modern Applications and Operations Increase development velocity while simplifying operations." I have no idea…
So, you build a web app and it gets popular. It needs one load balancer, 5 app servers, at least two database nodes for replication, a redis cluster for caching and queuing, an elasticsearch cluster for full text search, and a cluster of job worker servers to do async stuff like processing images, etc. In the ancient past, like when I'm from, you'd write up a few different bash scripts to help you provision each serv…
this is one of the best comment on HN! Love it!
Re: Samsung Acquires Joyent
#203In case anyone's curious, I blogged about the backstory of the acquisition.[1] tl;dr: We at Joyent are elated, and we believe that this will be a huge win for our customers, for our technologies and for the communities that they serve! [1] https://www.joyent.com/blog/samsung-acquires-joyent-a-ctos-p...
Congratulations Bryan, I learned so much from you in such a short period of time, forever grateful, good roads!
Re: Samsung Acquires Joyent
#204If anyone has a good background, what exactly does Joyent have that is so valuable?
It seems that NodeJS has moved out of Joyent. They have hosted container support that seems to run on solaris, which seems interesting, but a bit too much of buzz-wordy from their website.
I am not very familiar with this, so will be great if someone can explain a little bit. I read the comments around orchestration, but am more interested in Joyent's value proposition.
Re: Samsung Acquires Joyent
#205Re: Samsung Acquires Joyent
#206Hey, maybe Joyent can finally afford to refund the people who supported it when it was textdrive and then went back on their word! Snarky I know but I'm still bitter about how it was all handled..
As a fellow early textdrive supporter, I'm pretty happy with the value I got out of the deal. I'm still using my free strongspace account 10ish years later. I think there was some email about a free hosting account I could theoretically use with some company, but I never looked into it. Honestly, textdrive's hosting was never really of a quality I could use in a professional context anyway. I understand some bitterne…
It wasn't about the money or the value I got out of it.
For me, it was the way I felt like I was treated.
It felt like, hey, we've pivoted the company but we still have to support these old users and they are becoming a pain, let's give them a credit on something that's kinda like what they paid for and be done with them.
Then when enough people complained, then they tried to find some solution at the last minute and even that felt dubious.
Let's try to cobble something together that's barely working for these people and make it someone else's problem.
I totally take the "lifetime" deal with a grain of salt but it wasn't like the company folded because it ran out of money or wasn't successful. It was more like we got successful so we forgot about the little people.
Re: Samsung Acquires Joyent
#207Earlier quoted context omitted.
So, you build a web app and it gets popular. It needs one load balancer, 5 app servers, at least two database nodes for replication, a redis cluster for caching and queuing, an elasticsearch cluster for full text search, and a cluster of job worker servers to do async stuff like processing images, etc. In the ancient past, like when I'm from, you'd write up a few different bash scripts to help you provision each serv…
Wau thanks, that is an excellent explanation. I appreciate that it start with things I know and understand ("so you build a web app"/"bash scripts"/"puppet") and builds on that explaining what problems each consecutive steps /layer of abstraction/ solves. Now I wonder.. how many projects actually needs these kind of solution when even StackOverflow can do without it (they are in the range of few servers)? I would ima…
I think it's clear that the vast majority of profitable businesses, online or off, don't need the scale these services provide. But providers to these business can benefit from the scale to provide better, cheaper services. For example, the resurgence of the Static Web: ie site generators (ie Jekyll) and vendors offering hosting for these services (ie bitballoon, netlify, aerobatic, neocities, etc...).
Really, why should cost anything to have basic, low-traffic, site on the internet today? That's the quetion I ask myself.
Re: Samsung Acquires Joyent
#208Ok... Let's start on iojs 7!
Re: Samsung Acquires Joyent
#209Earlier quoted context omitted.
That's awesome. Are these just comments with a high karma, or is there some other magic going on?
Seems like a combination of length and karma — or maybe length and karma just happen to correlate? There are short ones in there too. Hmm.
My guess is it's a simple time-decay-weighted karma-based formula. That is, karma * e ^ -age. "Best" vs "top" may be the difference in net karma vs gross positive karma.
Re: Samsung Acquires Joyent
#210Cloud orchestration, Container Orchestration, Kubernetes... I think I am getting old and starting to understand how my parents feel about technology. I am developer, but mostly work on desktop apps, or embedded devices or lataly on some MVC applications. But reading things like "A Container-Native Stack for Modern Applications and Operations Increase development velocity while simplifying operations." I have no idea…
So, you build a web app and it gets popular. It needs one load balancer, 5 app servers, at least two database nodes for replication, a redis cluster for caching and queuing, an elasticsearch cluster for full text search, and a cluster of job worker servers to do async stuff like processing images, etc. In the ancient past, like when I'm from, you'd write up a few different bash scripts to help you provision each serv…
Just because of how clearly you have explained it, I would surely want to buy your book when it releases. As of now, I know nothing about Docker except one or two buzz lines. And by reading your book when it releases, I am sure I can get a full picture. BTW, who will be target audience for your book?