Earlier quoted context omitted.
How is this an example of the Hegelian Dialectic?
exactly, root comment's point is that 'synthesis' is missing, so there is no forward progress unlike the dialectic!
Unless we coin the term "macroservices"...
Goodbye Microservices: From 100s of problem children to 1 superstar
271–280 of 782 posts
Re: Goodbye Microservices: From 100s of problem children to 1 superstar
#272Earlier quoted context omitted.
So, should we stick to PHP for web stuff or is JS here to stay ?
This argument is less about specific technologies, and more about patterns and practices. For example: web UI started as declarative (HTML -> PHP), and then transitioned towards more imperative (jQuery, Backbone, Angular), and is now moving back towards declarative (React, Polymer)
I don't really understand calling Perl declarative... I would consider the Perl CGI services I used to work on to be quite a bit more imperative than the Rails applications I've worked on. Similar with PHP, though I can see where peppering the imperative code into the declarative HTML could be considered more declarative.
Re: Goodbye Microservices: From 100s of problem children to 1 superstar
#273Earlier quoted context omitted.
I can't find the right place for Ruby on Rails here. It doesn't fit.
Rails 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 al…
If 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).
Re: Goodbye Microservices: From 100s of problem children to 1 superstar
#274Let 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 h…
Yup. 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 whi…
Ha, 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.
Re: Goodbye Microservices: From 100s of problem children to 1 superstar
#275Earlier quoted context omitted.
So, should we stick to PHP for web stuff or is JS here to stay ?
This argument is less about specific technologies, and more about patterns and practices. For example: web UI started as declarative (HTML -> PHP), and then transitioned towards more imperative (jQuery, Backbone, Angular), and is now moving back towards declarative (React, Polymer)
There's nothing declarative about HTML except for its extremely limited use case of rendering text.
Re: Goodbye Microservices: From 100s of problem children to 1 superstar
#276Let 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 h…
Yup. 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 whi…
The test of time isn't always a good metric. html, css and javascript is a huge hack, yet it has withstood the test of time.
SQL to me is a huge design flaw despite it's ubiquity. On the web bottlenecks happen at IO and algorithmic searches. Databases are essentially the bottlenecks of the web and how do we handle such bottlenecks? SQL; A high level almost functional language that is further away from the metal than a traditional imperative language. A select search over an index is an abstraction that is too high level to be placed over a bottleneck. What algorithm does a select search execute? Why does using select * slow down a query? Different permutations of identical queries causes slow downs or speed ups for no apparent reason in SQL. SQL is a leaky abstraction that has created a whole generation of SQL admins or people who memorize a bunch of SQL hacks rather than understand algorithms.
Re: Goodbye Microservices: From 100s of problem children to 1 superstar
#277Earlier quoted context omitted.
unless they have 100 developers for 100 services. That cure is worse than the disease. Every service works differently and 80% of them are just wrong, and there’s nothing you can do because Tim owns that bit.
But if you can explain to the team or the CTO why Tim is doing it wrong and how it is impacting X, Y and Z, then Tim will fix or be sent else where, no?
No, not unless you’re somehow able to make the team, the CTO and Tim feel good at the same time. If you figure that part out let me know.
Re: Goodbye Microservices: From 100s of problem children to 1 superstar
#278Let 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 h…
Yup. 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 whi…
Absolutely. The flat design thing is a pet peeve of mine.
Re: Goodbye Microservices: From 100s of problem children to 1 superstar
#279Earlier quoted context omitted.
How is this an example of the Hegelian Dialectic?
exactly, root comment's point is that 'synthesis' is missing, so there is no forward progress unlike the dialectic!
well, we can think of the synthesis as returning to monolithic services with the understanding the sufferings of microservices.
Re: Goodbye Microservices: From 100s of problem children to 1 superstar
#280Let 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 h…
> 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