Live data from Hacker News

Au Revoir

blog.docker.com

71–80 of 305 posts

Re: Au Revoir

#71
post #54

I 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 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 :).

There is a slight irony in them being an infrastructure company.

Re: Au Revoir

#72

It always amazes me how you can convince a founder/CEO is not right man for the job, and slowly push him away. Companies that succeed are driven by burning vision, not by day-to-day operation people. It might make feel the companies run smoother for some time, but day-to-day executives are harmful to a company core vision leading to boring companies if they manage to sustain profitability in the long run at all.

Lets step away from the "company" aspect of it, because docker is also a project.

If this post were by someone named Linus, or Guido, (or Jobs) or any number of other names I can think of - people would be freaking out.

Yet the reaction so far is one thatI can only describe as "meh" - there wasn't a scandal (uber) there isn't a failure (intel) and people mostly (with exception) like the product.

I wonder what the future holds for docker after this change.

Also that art at the end, looks great but all I could think of was "fail whale" when looking at it (and not docker).

Re: Au Revoir

#73
post #54

Earlier 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…

I'm sorry, is your argument based on the current year? I presume you mean otherwise, but that's how it's written.

Re: Au Revoir

#74
post #27

Thanks Solomon for creating the inflection point of the container revolution. I'm a bit puzzled about where docker as a company has to go. But the enthusiasm that was unleashed is without par.

I'm going to second this - docker has literally opened up pathways that very well be underpinning 80% of all new projects.

Because of Docker I can bootstrap new employee's working environment in 5 minutes - everything is a container except they thing they are changing, commit, see.

Re: Au Revoir

#75
post #54

Earlier 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…

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 dozens of good SSGs, there’s really no excuse to use WP for a blog. The content doesn’t change between page loads, so why would you server-side generate the page dynamically on each page load? The way that it works is fundamentally wrong, and while it’s not very hard to fix with Varnish or WPSuperCache...why not start with the right tool for the job?

Re: Au Revoir

#76

I 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.

Re: Au Revoir

#77

It always amazes me how you can convince a founder/CEO is not right man for the job, and slowly push him away. Companies that succeed are driven by burning vision, not by day-to-day operation people. It might make feel the companies run smoother for some time, but day-to-day executives are harmful to a company core vision leading to boring companies if they manage to sustain profitability in the long run at all.

The people that have both are outliers, but massively successful: Bezos, Jobs, etc. But that just shows the importance of having both types of leadership in a company, because the type of drive that grows an innovative company isn't the same as what keeps them in the top spot. This isn't a simple binary variable, just about every company has had or will have to find their balance on this.

It may not be glamorous, but no matter how innovative or successful, someone (many people really) have to have an eye on day to day operations. A CEO should have vision, yes, but their job isn't just to have vision, it's to share that vision with the people under them, the day to day people that have to be in place, and will make the best day-to-day decisions only if they understand and share that vision.

Re: Au Revoir

#78
post #36

Earlier quoted context omitted.

Isn't it really hard to know what you would or wouldn't do in such a situation? What if he's just kinda tired, you know?

He’s in a position where the rational and realistic response to being tired could be as simple as delegating more and saying “from now on I’ll be working 3 days a week”. Our CTO doesn’t even show up for weeks at a time.

That's probably not the best solution for both the person (you hardly get any mental rest just by working a bit less) and the company (which probably needs a CTO, otherwise there wouldn't be one).

Re: Au Revoir

#79

I 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.

Docker hired a famous french comic book artist for all their graphics: https://twitter.com/laurelcomics

Re: Au Revoir

#80

I 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.

[deleted]
Post reply on HN