Only made it about a third of the way through but it seemed like latter day Xtra Normal MongoDB/web scale shtick[1]. [1] https://www.youtube.com/watch?v=b2F-DItXtZs
It's the Future
41–50 of 146 posts
Re: It's the Future
#42Ughhh this. I just want to give my project to a PaaS and let them figure out everything. I was looking into Google App Engine, but they didn't support some language features I wanted (e.g. Java 1.8, Servlet 3.X["I know, programming in Java? You're stuck in the past"]). So I looked into their new Container Engine. But like this article points out, it makes deployment 500000000 times more complicated than it should be.
Re: It's the Future
#43What do the new containers add on top of that (or other than that)? Only the option for more services (not just web app, but database, different languages, whatever)?
It seems odd having to worry about that kind of thing.
Re: It's the Future
#44A seeming eternity ago I let Maven convert apps into war files that supposedly could be deployed into any web application server. What do the new containers add on top of that (or other than that)? Only the option for more services (not just web app, but database, different languages, whatever)? It seems odd having to worry about that kind of thing.
It seems odd having to worry about things that aren't Web apps? Why?
Containers are also language-agnostic. .war files are only for JVM languages.
Re: It's the Future
#45Earlier quoted context omitted.
Seems to be the problem with a lot of technologies. If you're a HN reader, you can start to get the feeling that you're falling behind if you're not doing these things. Even though they are totally inappropriate for the majority of us who are working on smaller systems.
Often there's some tension between individual career development and what makes sense for the project and company. Ideally, managers create opportunities for people to exercise the former in a sandbox (e.g. some variation of "20% time"), without YAGNI-ing up the project. Sorry did I say sandbox? I meant container.
Re: It's the Future
#46It really is striking how products like Docker, even while delivering incredible value, continuously fail to message themselves in an intelligible way. If you go to https://www.docker.com , you see: "Build, Ship and Run. Any App, Anywhere." Jesus Christ. I get that you're The Future, but make the value prop for me here, at least. Why should I use Docker? What parts of my stack does it replace? When does the cost-bene…
Re: It's the Future
#47Earlier quoted context omitted.
New, new hotness is React Native (or whenever FB decides to make it also available on Android) and JSBlocks.
New, new, new hotness is Aurelia! Get with the times! http://aurelia.io/ Edit: just wanted to point out that this post was only partially satirical. I absolutely am in love with Aurelia atm.
Re: It's the Future
#48It really is striking how products like Docker, even while delivering incredible value, continuously fail to message themselves in an intelligible way. If you go to https://www.docker.com , you see: "Build, Ship and Run. Any App, Anywhere." Jesus Christ. I get that you're The Future, but make the value prop for me here, at least. Why should I use Docker? What parts of my stack does it replace? When does the cost-bene…
One problem we've encountered is that the audience for Docker is incredible broad - much broader than you might imagine when reading Hacker News for example. It is extremely common for CIOs, IT directors, and various business managers to just pick up the phone to ask us (or our partners) what Docker is all about. So it's difficult to tell a story which satisfies all audiences.
But I don't think that excuses everything. We are definitely better at building our product than at explaining it.
One interesting side-effect is that, if you've been exposed to Docker-related marketing (in a broad sense), most of it probably didn't originate from us, the creators of Docker. This is sometimes problematic because Docker is so polarizing: depending on who tells you about it you will get such a different, often distorted picture of reality. Either Docker is a miracle cure for every disease on Earth (indicating an over-enthusiastic Docker fan, or a vendor trying to sell something to Docker fans), or it's a scourge sent by the gods of the Unix valhalla to punish mankind for techno-hipster false idols such as javascript and php (indicating a jaded Docker-skeptic, or someone trying to sell something to Docker-skeptics). Either way, it creates a lot of noise. And as you point out, there might be less noise if we ourselves did a better job at explaining when using Docker is, or is not, a good solution.
Re: It's the Future
#49Ah, l33t for system architects. A few days ago, the CTO of Soylent, the food drink, was describing their elaborate computer infrastructure. They have one (1) product and a simple web site. Based on their sales volume, they do about two sales a minute. That could run on a HostGator "Hatchling" account for $4/month, using one of the seven off the shelf shopping cart/payment programs HostGator offers.