Live data from Hacker News

Au Revoir

blog.docker.com

61–70 of 305 posts

Re: Au Revoir

#62
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…

Fair enough. I took "this technology" to be a reference to Docker given the context.

Re: Au Revoir

#63

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.

Maybe he originally set up the blog using his work login and HR auto-deleted his credentials or account. Sounds like something that would happen around here...

Re: Au Revoir

#64
As a founder, of course, I have mixed emotions. When you create a company, your job is to make sure it can one day succeed without you. Then eventually that one day comes and the celebration can be bittersweet.

I've seen this before firsthand and it always looks painful. It's easy to look at something from afar and think, "why not just let it go?" But seeing the pain of letting go time and time again makes it seem far more difficult....

Re: Au Revoir

#65

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.

Companies that succeed are driven by burning vision, not by day-to-day operation people.

They are not mutually exclusive; thinking that they are is a recipe for failure.

Re: Au Revoir

#66
What Solomon is doing, walking away from the company he helped create, is probably one of the hardest decisions an entrepreneur may need to take. Good luck with everything!

Re: Au Revoir

#67

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.

Both are critical. You have a goal and then you make progress. Neither is enough on its own.

Re: Au Revoir

#68
Does this mean that Docker as a company is stable enough to function without one of its co-founders? Or does that mean that VC is taking it over?

Re: Au Revoir

#69

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 think Docker is too complicated; instead, I think a lot of companies misunderstand the benefit of containers aside from "my application boots faster"

Re: Au Revoir

#70

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.

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.
Post reply on HN