17 ms·
Let me write a meta technology hype roadmap, so we can place these sorts of articles: * Old technology is deemed by people too troublesome or restrictive. * T
by StavrosK 8y ago
Let me write a meta technology hype roadmap, so we can place these sorts of articles:
* Old technology is deemed by people too troublesome or restrictive.
* They come up with a new technology that has great long-term disadvantages, but is either easy to get started with short-term, or plays to people's ego about long-term prospects.
* Everyone adopts this new technology and raves about how great it is now that they have just adopted it.
* Some people warn that the technology is not supposed to be mainstream, but only for very specific use cases. They are labeled backwards dinosaurs, and they don't help their case by mentioning how they already tried that technology in the 60s and abandoned it.
* Five years pass, people realize that the new technology wasn't actually great, as it either led to huge problems down the line that nobody could have foreseen (except the people who were yelling about them), or it ended up not being necessary as the company failed to become one of the ten largest in the world.
* The people who used the technology start writing articles about how it's not actually not that great in the long term, and the hype abates.
* Some proponents of the technology post about how "they used it wrong", which is everyone's entire damn point.
* Everyone slowly goes back to the old technology, forgetting the new technology.
* Now that everyone forgot why the new technology was bad, we're free to begin the cycle again.
- curun1r 8y agoWith hype always comes a throng of people who aren't capable of doing the necessary analytical thinking to solve their problem and who think they can substitute a magical pattern for designing their application instead of truly understanding their problem domain and building a real solution to that problem. Does that make it the fault of the technology/pattern? I don't think so. I think it just means that there's no magic bullets in tech and people who don't know what they're doing will always cause problems no matter what models they follow.
- JustSomeNobody 8y agoGreat summary! I wonder if you could fit Resume Driven Design in there somewhere. This should be the top post on articles like this. Just to keep it fresh always in everyone's mind.
- StavrosK 8y agoIn my experience, this is driven more about engineers wanting to play with the "new shiny thing" than people wanting to pad their resume, but I'm sure that happens a lot too.
- dsnuh 8y agoIn my experience, it's a bit of both, and they are mutually reinforcing. If you want to always play with shiny new things, you might be more likely to jump around to different places, which a padded resume helps with.
- johnchristopher 8y agoIt's rear-view mirroring though. Some CS tech from after the 60's proved to be useful.
- johnchristopher 8y agoSo, should we stick to PHP for web stuff or is JS here to stay ?
- entropie 8y agoI remember a time where javascript was somehow called "old" and obsolete and pretty anyone hated it.
- kllrnohj 8y agoJavaScript prior to ES6 was "old" and obsolete and hated. Building JS objects pre-classes is pretty terrible (to say nothing of the .bind(this) that is spammed everywhere without the => operator) JS has improved massively over the last few years, it's very nearly an entirely different language than what it used to be. There's a reason everyone was desperate to avoid writing JS not all that long ago be it the form of coffeescript, silverlight, flash, or GWT. ES5 JS sucks. Like... a lot.
- lgunsch 8y agoInteresting. I haven't touched, or even read, any JavaScript since well before ES6 arrived. I suppose I don't really know the language if it's changed so much (I've never even heard of JavaScript classes). I jumped on the JavaScript hater train and left the station.
- avarun 8y ago>I jumped on the JavaScript hater train and left the station. As does most of Hacker News with every technology they hate on.
- samsonradu 8y agoI’d still pick PHP between the two for usual web apps. There is beauty in the statelessness of PHP and also leverage on Nginx (+ Lua) for more critical and high-speed work. The issue I have with Node JS is that the entire ecosystem moves way too fast. However, when I need realtime interaction via WebSockets fe. it really feels like a good choice.
- copperx 8y agoI can't find the right place for Ruby on Rails here. It doesn't fit.
- Dirlewanger 8y agoRails was never really a major leap forward in anything, more so an evolution with convention-over-configuration and a strong community presence that established best practices early. It also hasn't been "cool" for years, it's an entrenched player that "just works". One could argue with all the Rubyists going to Elixir that's part of the cycle, but for many people that's been a net positive. And then there's those altogether dropping Elixir for Go...
- jules 8y agoRails was a major leap forward because the competition was really bad: PHP and Java Struts.
- wuliwong 8y agoI think that Rails using Ruby was a big deal. It was definitely different. Not sure if it was forward, backwards or lateral but it certainly was a big change beyond just "convention of configuration."
- cpursley 8y agoI doubt you'll find many people dropping Elixir for Go... And Ruby was a major leap forward ~ in productivity.
- dnautics 8y agoIf we believe the cycle model, then the people dropping elixir for go will come back when they're tired of dealing with kubernetes and when they realize that being a dynamic language isn't all that terrible (if done correctly).
- sanderjd 8y agoYeah, I think this is actually calling out a major weakness in the original comment's hype cycle model. Sometimes step #5 ("Five years pass...") doesn't happen in that way. Sometimes what happens is that the new technology has been found to be generally useful, though imperfect, as everything is. People may be evolving it in different directions, perhaps incorporating elements of the old technology the new one replaced, but it isn't being fundamentally abandoned. The tough part is that you don't know which version of step #5 will happen when you're surveying the world at step #4. If it was easy to figure this stuff out, they wouldn't pay us to try :)
- lossolo 8y agoExactly the same thing happened with SQL vs NoSQL.
- irrational 8y agoOr rather, relational databases and non-relational databases. This precisely played out at my company recently where a group moved from MongoDB back to a relational database.
- dlevine 8y agoAnd, in the end, everyone starts writing Java again...
- irrational 8y agoBut, I never started writing Java... ;-)
- pjmlp 8y agoI never stop doing it.
- BurritoAlPastor 8y agoA coworker of mine likes to say that Java developers never stop writing Java – they just start writing Java in other languages.
- resource0x 8y ago> Old technology is deemed by people too troublesome or restrictive. "deemed" is the keyword here. Old tech is "deemed" bad, new one is "deemed" good. Without any numbers attached, just by way of hand-waving and propaganda. And it's all "deemed" Computer Science :)
- 0x445442 8y agoComputer Science... Now there's an oxymoron. At most institutions the subject matter is not really about computers nor is it science, at least not in the physics or chemistry sense.
- filleduchaos 8y agoThat sounds like a rather narrow definition of science that will become even more obsolete in the years to come. With how far mankind has come, it's a little silly to think that "natural" systems will remain the only things that science is concerned with.
- SahAssar 8y agoI think that their point is that "Computer Science" does not seem very very interested in the provability of their science (the "Science" part) nor the applicability for general purpose computing (the "Computer" part).
- filleduchaos 8y ago> "Computer Science" does not seem very very interested in the provability of their science ...uh, what computer science are you talking about? Formal verification is a huge part of CS, and provability is a tiny part of what makes science science - systematic study through observation and experimentation. Science is a discipline, not in itself a fact to be proved. Also, what parts of CS do you think are inapplicable to general purpose computing?
- otras 8y ago
- digi_owl 8y agoAlternatively: Are stuck using the new tech, because implementing it burned bridges with the old tech.
- systemizer 8y agoyup. basically Hegel's dialectic: https://en.wikipedia.org/wiki/Dialectic#Hegelian_dialectic https://en.wikipedia.org/wiki/Dialectic#Hegelian_dialectic Thesis --> Antithesis --> Synthesis
- rstefanic 8y agoHow is this an example of the Hegelian Dialectic?
- dnautics 8y agoexactly, root comment's point is that 'synthesis' is missing, so there is no forward progress unlike the dialectic!
- swsieber 8y agoUnless we coin the term "macroservices"...
- systemizer 8y agowell, we can think of the synthesis as returning to monolithic services with the understanding the sufferings of microservices.
- strken 8y agoThesis: monoliths in one repo Antithesis: microservices in separate repos Synthesis: microservices in a monorepo
- xkgt 8y agoI kind of get what systemizer is saying. People may think of evolution of technologies as cycles but it is never that. A new technology 'Y' is always developed because the incumbent 'X' has some shortcomings. And even after a period of disillusionment when we revert back to 'X', it is not always the same. We synthesize the good points of 'Y' back to 'X'. Coming to this topic, I see Microservices as a solution to the problem of Continuous Delivery which is necessary in some business models. I can't see those use cases reverting back to Monolith architecture. For such scenarios, the problems associated with Microservices are engineering challenges and not avoidable architecture choices.
- jl6 8y agoWhat examples are you thinking of with “Everyone slowly goes back to the old technology?”
- irrational 8y agoNot OP, but recently a group at my company abandoned MongoDB and went back to a relational database after going through the exact scenario outlined by the OP (actually, the OP's comment so closely aligned with what happened that I actually wonder if he/she is actually a developer with that team at my company ;-)
- 52-6F-62 8y agoInteresting. I'm currently working MongoDB into a couple of projects I have going at work (they're not really outward facing except for potentially one generated view). For these projects it seemed to make a ton of sense given the rest of the stack, the nature of the projects, the deadlines I'm facing, and I've really loved working with it so far. Why did you end up moving off of it?
- Deadron 8y agoThe simple fact is mongoDB fails to have sufficient durability guarantees for business data when compared to a traditional RDBMS. That is one of the reasons why its so fast in comparison. A power loss event during data writes can and will lead to data loss. https://www.mongodb.com/blog/post/what-about-durability https://www.mongodb.com/blog/post/what-about-durability
- 52-6F-62 8y agoSounds like a "right tool for the job" situation. I thankfully don't have to worry about power loss (large company, teams dedicated to critical systems infrastructure in a big way), and a cron job can handle any archival concerns in the projects I'm running here. It does sound like they've improved much since 2011. Anyway thanks for the insight
- craigc 8y agoYup. Everyone wants to use the latest and greatest, but there is a reason that certain things like SQL have stood the test of time. I think the same could be said of the design world. There was a time not too long ago when designs actually felt polished and had real shapes, shadows, gradients. When you clicked on a button you actually knew you were clicking on a button. Then iOS 7 came along and everything became white and flat and buttons were replaced with text with no borders. I think we are slowly moving back to where we were ten years ago. PS How long until people start ditching React for jQuery?
- chrisco255 8y agoHa, JQuery. I just had to look at a legacy JQuery code base...and I shudder the thought of ever going back to that paradigm. Sometimes new patterns/frameworks/architectures do really change the game for good.
- timr 8y agoI still use jQuery regularly. It works well and doesn't get in the way. I'd rather work on a jQuery codebase written by a good engineer than a React codebase written by an average engineer, and there's no amount you could pay me to work on a Javascript codebase written by a bad engineer. The problem you've identified is that most code, in general, is terrible. The code written by people who chase trends tends to be worse than average.
- deleted 8y ago[deleted]
- chrisco255 8y agoI wouldn't. React makes it hard to FUBAR a front end. JQuery makes it stupidly easy to write a spaghetti code unmaintainable mess.
- timr 8y agoReact makes it easier for bad developers to do complicated things. They still end up writing spaghetti code.
- ascendantlogic 8y agoWhich is why I feel like after 20 years in the industry a good portion of people start consultancies realizing there's good money to be made on this hype cycle churn.
- ninkendo 8y agoIt's like a heat engine of hype that you can extract useful energy from. $_max = 1 - (H_c / H_h) That is, the amount of money you can extract via consulting is proportional to the ratio of "hot" to "cold", representing the minimum and maximum hype for a given technology during the cycle.
- sanderjd 8y agoBut does this timeline apply to microservices or monoliths? Methinks both...
- ergothus 8y agoThat's the point - we'll bounce between multiple paradigms growing frustrated at the problems and forgetting /failing to recognize the frustrations of the past ( and thus future) options. And not just with service paradigms, but with lots of technical areas. Heck, FP is being treated like it's a hot new thing.
- aaronbrethorst 8y agoReminds me a bit of Gartner’s “Trough of disillusionment.”
- bumholio 8y ago> Now that everyone forgot why the new technology was bad, we're free to begin the cycle again. We can very easily break the cycle by training a deep learning TensorFlow brain in the cloud, that will be fed the daily mouse gestures and key presses of all developers in the world. It's an awesome new technology that can solve any problem. Pretty soon the global brain will start to see patterns emerging, for example when developers post hype phrases on forums with unsubstantiated claims about the potential of some awesome new technology. As soon as a hype event is detected, a strong electric shock is commanded via the device the developer is using, thereby stopping the hype flow and paralyzing the devellllllllllllllllllllllllllll
- stcredzero 8y ago"But if he was shocked, he wouldn't bother to keep typing!" "Maybe he was taking dictation?!"
- TeMPOraL 8y agoWatch out for the more science-minded developers, though. https://xkcd.com/242/ https://xkcd.com/242/.
- marcosdumay 8y agoNah... This one was clearly paralized while pressing a key. His browser must auto-post HN comments after a short while.
- stcredzero 8y agoWith the last sentence, we now award the best hypothesis to dictation. https://www.youtube.com/watch?v=LJfowXTXOfU https://www.youtube.com/watch?v=LJfowXTXOfU
- marcosdumay 8y agoThat was the goal, thank you :) It's amazing how many stupid to the point of crazyness situations seem perfectly natural nowadays. Thank computers!
- LinuxBender 8y agoI agree with this summary 100%. I have witnessed and survived this cycle for a few decades.
- crimsonalucard 8y agoYou are describing "design" which encompasses things like modern art, designer clothes and design patterns. The thing with design is that it isn't a science or formal field of logic. I can use math to determine the shortest distances from point A to point B but I can't prove why a design for product A is definitively better than a design for product B. With no science we are doomed to iterate over our designs without ever truly knowing which design was the best.
- stelfer 8y agoAlso, write a treatise about how they discovered queueing theory... seems to be part of the pattern.
- jacques_chester 8y agoI noticed this too, but I have to admit that for someone with a weak mathematical background (like me), queueing theory is a bit hard to apply.
- toddmorey 8y agoThis cycle blankets every new technology as a misstep that we’ll revert back from. The real cycle is that we continually test new ideas and new approaches, learn their strengths and weakness, and ultimately keep what works and discard what doesn’t. Sure we miss the ball more than we connect. But take this example: We now have native JSON support since Postgres 9.2. So did we abandon the document model or learn more about how and where it might be appropriate? Some advancements are even more sweeping: I don’t think we’ll ever go back to FTP or even CVS from the Git-centric workflows we now have. Technology, in my experience, never seems to reward too much optimism or too much cynicism.
- wolco 8y agoGit centric workflows are ripe for change. FTP or sftp is still used very often.
- barkingcat 8y agoFTP workflows are so extremely widely used in today's world that it's inconceivable you think it's behind us.
- 9935c101ab17a66 8y agoMaybe in frontenddev/small companies/small largely static websites FTP pervades, but I'd argue that most developers that deal with any real complexity probably use some kind of source control system to 'share' files rather than some kind of FTP program. And I'd be very surprised if relative FTP usage hadn't decreased significantly over the last 3-4 years (But this is all quite anecdotal, and I could be wrong). Something that does surprise me is that Panic's Coda and Transmit apps still seem quite successful, so maybe my perception is out of whack.
- NicoJuicy 8y agoIsn't Google using a monolith as repository. Many would call that bad practice, I call it static typing benefits
- api 8y agoI'm watching this unfold with "serverless," which trades system administration for lock-in and other problems.
- PaulRobinson 8y agoIt's possible to do serverless without lock-in, in the same way it's possible to do containers without lock-in. At the moment serverless vendors make that hard, and the frameworks (like serverless.com) are still emerging to make that simple. For me the problem is most people don't think through the cost/benefits. Amazon don't ever get tired of saying "never pay for idle" in their sales pitches, but quite a lot of applications out there are never idle and can be quite accurately managed in terms of scaling, and therefore you're actually paying a premium for something you don't need.
- eric_b 8y agoPrediction: SPAs and GraphQL are quickly heading towards the last few bullet points.
- strken 8y agoAs someone maintaining a SPA that uses GraphQL, they're not really comparable. Everyone and their dog has a SPA, while GraphQL has been somewhat restricted by the small number of React users who dared to install the first version of Relay. GraphQL could wither like Backbone and Angular and nobody would really notice or care. An industry-wide shift away from SPAs would be something else entirely.
- aenigmaclamo 8y agoHave you ever tried to go back to no longer writing SPAs? Sure, it's easy to work with at first but then you start to realize that every framework and every language has different ways of doing all the niceties that you now expect. Asset pipelining, layouts, conditional rendering, and template helpers all end up becoming stuff that every language has to individually develop with varying levels of success. Even with those features baked in, you probably still want to modify the page using JavaScript, anyway, so then you have to re-render parts of the page without the aid of the expansive view system that rendered your page. And, of course, the more JS you put in your app, the more you have some bastardized hybrid of a SPA and a server rendered page.
- deanCommie 8y agoYou missed a crucial detail: > * Everyone slowly goes back to the old technology, forgetting the new technology. This step is just as misguided as cult-y as "Everyone adopts this new technology and raves about how great it is now that they have just adopted it." In some cases the technology WAS the right idea, just implemented incorrectly or not sufficiently broadly, and the baby ends up getting thrown out with the bathwater.
- wmccullough 8y agoI agree completely. I think that regardless of whether microservices works for anyone or not, they came about to address a real issue that we still have, but that I’m not sure anyone has fully solved. I think that microservices are an expression of us trying to get to a solution that enables loose coupling, hard isolation of compute based on categorical functions. We wanted a way to keep Bob from the other team from messing with our components. I think most organizations really need a mixture of monolithic and microservices. If anyone jumps off the cliff with the attitude that one methodology is right or wrong, they deserve the outcome that they get. A lot of the blogs at the time espoused the benefits without bothering to explain that Microservices were perhaps a crescent wrench and really most of the time we needed a pair of pliers.
- tabtab 8y agoThe problem is it's not clear when to use what. Some get confused and use it in the wrong place. Here are some questions to ask before you use microservices. Does the service need an independent and dedicated team to manage its complexities, or is it a "part time" job? Try a Stored Procedure first if its the second. Is the existing organization structure (command hierarchy) prepared and ready for a dedicated service? (Conway's law) Remember, sharing a service introduces a dependency between all service users. Sharing ain't free. Do you really have a scalability problem, or have you just not bothered to tune existing processes and queries? Don't scrap a car just because it has a flat tire.
- ericdykstra 8y agoHundreds of new languages, technologies, frameworks, etc pop up every year, but the odds of any one of them being durable in the long run is extremely low. See: The Lindy effect https://en.wikipedia.org/wiki/Lindy_effect https://en.wikipedia.org/wiki/Lindy_effect
- tluyben2 8y agoI have been doing some tech advice jobs on the side to see what's going on in the world and it's really scary what I found. Only yesterday I was talking with the cto of a niche social networking company that has a handful of users and probably won't get much more who was telling me the tech they use; Node, Go, Rust, Mongo, Kafka, some graph db I forgot, Redis, Python, React, Graphql, Cassandra, Blockchain (for their voting mechanism...), some document database I had never heard of and a lot more. A massive, brittle, SLOW (!) bag of microservices and technologies tied together where in 'every micro part' they used best practices as dictated by the big winners (Facebook, Google, whatever) in Medium blogs. It was a freak show for a company of 10 engineers. But this is not the first time I encounter it; 3 weeks ago, on the other side of the world, I found a company with about the same 'stack'. People really drink the koolaid that is written on these sites and it is extremely detrimental to their companies. PostgreSQL with a nice boring Java/.NET layer would blow this stuff out of the water performance wise (for their actual real life usecase), would be far easier to manage, deploy, find people for etc. I mean; using these stacks is good for my wallet as advisor, but I have no clue why people do it when they are not even close to 1/100000th of Facebook.
- myth_drannon 8y agoResume driven development. I've worked for a similar small company with barely any users/data but the tech choices were driven by how useful is the tech for their future job prospects and not the current or future needs of an organization.
- s73v3r_ 8y agoMaybe if companies gave sufficient raises and promotions, and actually tried to retain talent, then we wouldn't have this culture where people keep having to switch jobs, and therefore always be looking out for what will get them the next gig.
- fbonetti 8y agoI think engineers would still jump ship just as often even if they were paid more. When you really get down to it, most programming is pretty tedious. What makes it fun, for some engineers, is the opportunity to learn new things, even it means doing so at the detriment of the business.
- acjohnson55 8y agoOnly thing is, for any given real world tension between dual paradigms, it's arbitrary which one you label as old or new. At this point, the oscillation has been going on longer than anyone has been in the field.
- drb91 8y agoI mean, this is the nature of hype, including scientific paradigms, fast fashion, music tastes. But this narrative obscures underlying causes and basically assumes the underlying cause is human love of hype. However, this isn’t a 2d circle as you imply, but a 3d spiral: you do learn over time. You can see which patterns apply to which problems. There’s a tendancy in these narratives to bemoan the individual that represents culture, but the real pain is that you’re watching people learn things you already learned, and there’s this irrational reaction where you think “i learned this already; so should have they.” But none of this implies that we are losing knowledge, just that the curve of engineers is fatter at the inexperienced level.
- dnomad 8y agoWhat this actually looks like is a case of very imperfect knowledge transfer within the technology industry. What's interesting about the entire craze of microservices and containers and the cloud is that they are not a new technology. This entire architecture -- the so-called lambda architecture -- has been the standard approach to developing high-performance trading systems on Wall St. since the early 90s. The architecture is literally 30 years old and certain technologies (event sourcing, event driven architecture) are even older. The problem is that the all the best knowledge has clearly not made it out. For example, this design introduces a "Centrifuge" process that redirects requests to destination specific queues... congratulations you've just reinvented a message bus, a technology that goes back to the 80s. There is absolutely nothing new about virtual queues as described here but unfortunately the authors are likely not at all aware of the capabilities of real enterprise messaging systems (even free, open-source ones like Apache Artemis) and certainly not aware of the architecture and technologies and algorithms that underlie them and the (admittedly much more expensive) best-of-breed commercial systems. (I won't even go into the craziness of 50+ repos. That's just pure cargo cult madness.) Watching the web/javascript reinvent these 30 year old technologies is a little disheartening but who knows they may come up with something new. (Then again, recently the javascript guys have discovered the enormous value of repeatable builds. Unfortunately the implementations here all pretty much suck.) Still, we ought to perhaps ask ourselves why this situation has come about...
- markatkinson 8y agoYou could apply that pattern to a lot more than just the tech sector. It seems humans are doomed to this cyclical process of 3 steps forward 2 steps back. Maybe someone needs to create a cloud based serverless SaaS SPA web app developed in F# to help track this stuff and prevent it happening in the future.