So yeah, after that conversation I genuinely think that "Framework as a Service" describes what's interesting about the shift.
-
-
That probably slows down the vibrancy of framework evolution, but 13+ years after Rails it makes sense to bake it in for many people.
Show this thread -
I just hope that that doesn't mean we become reliant on Amazon (closed source) to add important fwk features we used to be able to do OSS.
Show this thread -
But generally the push and pull is that with enough demand comes new OSS solutions. Rails was harder to ops than PHP, still highly adopted.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.