3 ms·

Yeah I was there for TextDrive too. That was more of a slap in the face because it was Dean Allen's personality that brought us in, but Jason Hoffman was runni

Yeah I was there for TextDrive too. That was more of a slap in the face because it was Dean Allen's personality that brought us in, but Jason Hoffman was running the thing, and he was really more interested in playing with Solaris than providing a stable service. The whole Joyent acqui-pivot (or whatever that was) was just the final fuck-you to those of us who thought it was a cool indie grassroots thing. As far as Svbtle is concerned, this appears to just be small operation downtime which is the poison you've chosen if you go that way. Can't say there's any "forever guarantee" that really means much. The best you can get is that if you sign with Oracle they'll guarantee to ratchet up that dependency to charge you more and more over time. Hard to beat that as an incentive for uptime.

shrubble 5y ago
Joyent did sponsor the work that led to NodeJS however, I think? While I wouldn't excuse any bad behavior, that is a point in Joyent's favor...
- deleted 5y ago
  [deleted]
- wut42 5y ago
  The Joyent that made Node wasn't really the Joyent that brought TextDrive, afaik. That company has a long history of.... fuckups, maybe ?
- spion 5y ago
  They did not.
  - chipotle_coyote 5y ago
    It's probably not accurate to phrase it as "Joyent sponsored the the work that led to Node.js", but it was essentially their project in the early 2010s. They were paying full-time salaries to Node and NPM's creators, and Ryan Dahl described Node as being "officially under Joyent's roof". https://groups.google.com/g/nodejs/c/lWo0MbHZ6Tc https://groups.google.com/g/nodejs/c/lWo0MbHZ6Tc (I remember, after TextDrive fell apart, making a rather sardonic blog post observing that if I were heavily involved with Node, I would be making contingency plans.)
chipotle_coyote 5y ago
To be fair to Allen and Hoffman, when Joyent and TextDrive "merged", Joyent's business was basically a SaaS mail/calendar/collaboration system called "Joyent Connector" and TextDrive was the supposedly complementary hosting platform. It was a couple years after the merge that Allen left and Hoffman decided to go full bore enterprise.
- dasil003 5y ago
  Yes, that's a good point. There was a longer window of time here which I had compressed in my mind because the shared hosting was so unstable that I basically wrote it off and stopped paying attention for a few years there.

shrubble 5y ago

Joyent did sponsor the work that led to NodeJS however, I think? While I wouldn't excuse any bad behavior, that is a point in Joyent's favor...

deleted 5y ago
[deleted]
wut42 5y ago
The Joyent that made Node wasn't really the Joyent that brought TextDrive, afaik. That company has a long history of.... fuckups, maybe ?
spion 5y ago
They did not.
- chipotle_coyote 5y ago
  It's probably not accurate to phrase it as "Joyent sponsored the the work that led to Node.js", but it was essentially their project in the early 2010s. They were paying full-time salaries to Node and NPM's creators, and Ryan Dahl described Node as being "officially under Joyent's roof". https://groups.google.com/g/nodejs/c/lWo0MbHZ6Tc https://groups.google.com/g/nodejs/c/lWo0MbHZ6Tc (I remember, after TextDrive fell apart, making a rather sardonic blog post observing that if I were heavily involved with Node, I would be making contingency plans.)

chipotle_coyote 5y ago

To be fair to Allen and Hoffman, when Joyent and TextDrive "merged", Joyent's business was basically a SaaS mail/calendar/collaboration system called "Joyent Connector" and TextDrive was the supposedly complementary hosting platform. It was a couple years after the merge that Allen left and Hoffman decided to go full bore enterprise.

dasil003 5y ago
Yes, that's a good point. There was a longer window of time here which I had compressed in my mind because the shared hosting was so unstable that I basically wrote it off and stopped paying attention for a few years there.