I'm getting a 504 Gateway timeout. Is the HN hug of death really affecting such a huge site?
[deleted]
Au Revoir
91–100 of 305 posts
Re: Au Revoir
#92I love the art made for the post. It's so emotional and powerful. The letter told the story, but the image made me feel the story. So simple, but yet so powerful. Also, @solomonstre has changed his Twitter profile picture. This is brilliant communication. He lets everyone know that he has moved on to other things, just from his profile picture. I think this is very interesting and clever.
Yeah, came here to say this https://i0.wp.com/blog.docker.com/wp-content/uploads/solomon... is awesome
Re: Au Revoir
#93I think their blog being hugged to death is a good example of how this technology (read: web backend tech in general, not containers) is still too complicated for people in general to use it for simple cases, like scaling the load of otherwise static content. (It's wordpress, but still) We need solutions that require less resources and smaller learning curves.
I've been mumbling under my breath about this since the 90s. The basic issue as I see it is that nobody wants to do the up front work of separating out static, client side dynamic, and server side dynamic. If that work were done then nominal load would be much less to begin with, and scaling up would be much more straightforward.
Maybe I'm misunderstanding your categories, but why would a server care about the distinction between "static" and "client side dynamic"?
Re: Au Revoir
#94Is it just a conscious joke at this point to put "incredible journey" in any of these types of announcements?
'Incredible journey' is usually reserved for software companies selling out or shutting down, neither of which is happening in this case.
The parent likely picked it up from the Twitter announcement:
"The entire #Docker team would like to thank @solomonstre for creating the containerization movement and his 10 years of service and innovation. Thank you for bringing us all along on this incredible journey – we look forward to continued collaboration https://dockr.ly/2ut6OyO"
Re: Au Revoir
#95Earlier quoted context omitted.
I don't know how their blog is hosted but wordpress in general is very chatty with the database backend, and I really don't think the site getting crushed by HN is indicative of fundamental issues with container technology. If it is then there is a long list of technologies that HN has exposed fundamental issues with by crushing their content sites :).
Oh I'm not pointing at container technology. I'm talking web backend technology in general. I mean this is 2018. No well known company's blog on AWS should ever go down at all, unless the AWS service in the region is down. The fact that it's down is not a Docker failure or a Wordpress failure or a Database failure, as there are widely known methods to scale all these things. The problem is that putting the puzzle tog…
If Docker's blog was their core product, I would probably be more likely to agree. The truth is, they don't get ROI from engineering their blog to anticipate or quickly respond to all the traffic of a major announcement, because those are few and far between. The level of complexity is moot because the benefits will only outweigh a very small cost.
They build container tech. That doesn't mean they will benefit from engineering the best solution for everything they do.
Re: Au Revoir
#96Earlier quoted context omitted.
Oh I'm not pointing at container technology. I'm talking web backend technology in general. I mean this is 2018. No well known company's blog on AWS should ever go down at all, unless the AWS service in the region is down. The fact that it's down is not a Docker failure or a Wordpress failure or a Database failure, as there are widely known methods to scale all these things. The problem is that putting the puzzle tog…
I'm sorry, is your argument based on the current year? I presume you mean otherwise, but that's how it's written.
Yes, and it's a perfectly fair argument.
Content hosting sites are supposed to host content. That's what they do. If a site doesn't work under unusual but not outrageous conditions, it's fundamentally broken and not fit for purpose.
The industry should be much less tolerant of excuses for tools and systems that perform poorly under load. It's had a couple of decades to get this right now. How is it acceptable that this is even a problem?
Re: Au Revoir
#97Earlier quoted context omitted.
Having read this I wonder what really went down. I get that his shares are fully vested, but personally I would not walk away from such a role at a company with this kind of growth and mind share.
He’s put his heart and soul into the company for 10 years, is wildly successful, and doesn’t think he’s the best person for this next phase. I don’t think any back alley drama needs to have happened.
Maybe he doesn't want to be that person?
Founding a company is much different from running it.
I'd consider founding exiting for the first years, but later rather boring.
Re: Au Revoir
#98Earlier quoted context omitted.
Static site generators are an infinitely better choice for making actual blogs. Wordpress has evolved into a CMS similar to Drupal or Joomla with all the available plugins. You can make it into a store or a wiki or basically anything, but you probably shouldn’t. Wordpress was really cool back in the PHP5 days, but Moveable Type and other “old school” static CMS generators always scaled better. Today with node and the…
Try getting 5+ marketing people to learn git and GitHub sometime and let me know how it goes.
For just the blogging portion, you can just add the blog posts directly through github (the markdown files for posts).
https://help.github.com/articles/creating-new-files/
But yeah, it’s less user friendly. I’m sure someone will make a good solution for this soon.
Re: Au Revoir
#99I think their blog being hugged to death is a good example of how this technology (read: web backend tech in general, not containers) is still too complicated for people in general to use it for simple cases, like scaling the load of otherwise static content. (It's wordpress, but still) We need solutions that require less resources and smaller learning curves.
We need more static page generation like Jekyll. It doesn't make sense that an entire blog needs to be dynamically generated all the time. Dynamic contents can be fetched using ajax, but the rest should be static HTML.
Static content can and should be cached, not necessarily pre generated. Thus you can use your site as is and handle caching with whatever you need. It also takes care of semi static (slowly moving).