4 ms·

"Hi, my name is dokku, and I have no idea what you're talking about" :) This rant sounds just like any rant from old dev mocking a new tech. "This is less effi

"Hi, my name is dokku, and I have no idea what you're talking about" :) This rant sounds just like any rant from old dev mocking a new tech. "This is less efficient, this is too complicated, this can't be taken seriously, this won't last". Creating a character obsessed with "this is dead" hardly dissimulate the obsession with "this won't work". Do whatever you please, we don't care. But don't mock others about what they please. Passing through that, let's address the critics. Microservices and docker are not necessarily tied. I write only monolithic apps, and use them with docker through dokku. Etcd is a microservice problem, not a docker one. You don't need coreos or kubernetes to use docker in production. You need them if you want massively scaled applications, just like you would have many servers running the same app with replication without docker. Most of us don't need that (and those who need it probably won't find it more complicated than what is needed to do that without docker). If you don't want to manage servers, well, don't manage them. That's what cloud services are made for. But please tolerate some people love devops and not spending much direct money into infrastructure.

2100821021 10y ago
You mean B.S. written to impress investors and dominate a market segment for 2 or 3 years until the "founders" have a good exit.
icebraining 10y ago
Parody is just a light-hearted way of criticizing. You shouldn't take it personally (unless specifically targeted). In any case, the author of the post actually agrees with you: https://circleci.com/blog/it-really-is-the-future/ https://circleci.com/blog/it-really-is-the-future/
- oelmekki 10y ago
  Yeah, I tend more and more to be annoyed by some devs negativity every time someone is trying something new. I may take that personally, yes, not about docker and microservices, but because I'm always told to stop creating and use what already exists each time I'm trying to develop a new concept on sideprojects. I have to let that go, I guess. Thanks for the article, a lot of interesting things in it. It's funny how it's focused on the scaling problem. It may depend on which circles we're in, but it seems to me that what people were most interesting about in heroku was more the ease of deployment than the scalability. It probably depends on the size of your usual projects. Yet, what is interesting in docker is not just scalability. I find it way easier to code system dependencies with docker than with chef, that's already a big win. Also, I've stayed out of heroku for my own projects, mainly because of the cost. Docker, with dokku, allows me to have the same comfort one have on heroku, but with a 80€/mo server (handling about 15 small apps, and still having one third of memory available). And having several applications using several versions of ruby or postgres on the same server is not a problem anymore. In that regard, docker is not only interesting for people who have massive infrastructure to manage, but also to people who are used to self hosting and want an easier way to deliver.
collyw 10y ago
>This rant sounds just like any rant from old dev mocking a new tech. Probably because we have seen it all before, and there isn't much "new" most of the time.
- parasubvert 10y ago
  As an old dev that mostly (not completely) likes new tech, the novelty is often subtle, and almost always has a point to it. What is mock worthy are the attempts to make everyone's pet technology a floor wax AND dessert topping. But that's mostly VC funding at work
- oelmekki 10y ago
  I've been a professional developer for ten years myself, I've seen my part of hype. But I've seen way more people not even trying new things (and trying does not mean sticking with it on your main project), probably because they could not stand the idea that the experience they are so proud of could be invalidated in any way.

2100821021 10y ago

You mean B.S. written to impress investors and dominate a market segment for 2 or 3 years until the "founders" have a good exit.

icebraining 10y ago

Parody is just a light-hearted way of criticizing. You shouldn't take it personally (unless specifically targeted). In any case, the author of the post actually agrees with you: https://circleci.com/blog/it-really-is-the-future/ https://circleci.com/blog/it-really-is-the-future/

oelmekki 10y ago
Yeah, I tend more and more to be annoyed by some devs negativity every time someone is trying something new. I may take that personally, yes, not about docker and microservices, but because I'm always told to stop creating and use what already exists each time I'm trying to develop a new concept on sideprojects. I have to let that go, I guess. Thanks for the article, a lot of interesting things in it. It's funny how it's focused on the scaling problem. It may depend on which circles we're in, but it seems to me that what people were most interesting about in heroku was more the ease of deployment than the scalability. It probably depends on the size of your usual projects. Yet, what is interesting in docker is not just scalability. I find it way easier to code system dependencies with docker than with chef, that's already a big win. Also, I've stayed out of heroku for my own projects, mainly because of the cost. Docker, with dokku, allows me to have the same comfort one have on heroku, but with a 80€/mo server (handling about 15 small apps, and still having one third of memory available). And having several applications using several versions of ruby or postgres on the same server is not a problem anymore. In that regard, docker is not only interesting for people who have massive infrastructure to manage, but also to people who are used to self hosting and want an easier way to deliver.

collyw 10y ago

>This rant sounds just like any rant from old dev mocking a new tech. Probably because we have seen it all before, and there isn't much "new" most of the time.

parasubvert 10y ago
As an old dev that mostly (not completely) likes new tech, the novelty is often subtle, and almost always has a point to it. What is mock worthy are the attempts to make everyone's pet technology a floor wax AND dessert topping. But that's mostly VC funding at work
oelmekki 10y ago
I've been a professional developer for ten years myself, I've seen my part of hype. But I've seen way more people not even trying new things (and trying does not mean sticking with it on your main project), probably because they could not stand the idea that the experience they are so proud of could be invalidated in any way.