4 ms·

I am old, too, but for me the term "full stack" only showed up during the last decade or so, in connection with web programming, meaning "frontend and backend".

• AtlasBarfed 3y ago
  It has a bit of infrastructure as code / drops implied, but ultimately it is a term to make "JavaScript programmer" sound more important.
  • cmrdporcupine 3y ago
    Yeah from a distance it seems the thing that has happened that significantly changed things is that JavaScript became an acceptable backend language. So the split between people who wrote JS on the front side of things, and people who wrote Java/Ruby/Python/C# (or, err, PHP or... going back... Perl) on the backend has mostly vanished. And the new term became "fullstack" which, I dunno, it's kind of a funny term. Having been out of web-facing things for a long time, I think I'd feel pretty alien being dropped into a TypeScript-on-Node codebase. I'd have no problem picking it up having played with it a bit over the years, but it still strikes me as a bit odd. And I find the JS frameworks out there like React etc absolutely terrifyingly overwrought.
    • AtlasBarfed 3y ago
      The only way a bespoke component model framework works is if everyone adopts it. All the multitude of Java component-based web rendering systems failed. Luckily for react everybody did basically adopt it so their component model did not fail. It is always funny to watch people mock Java in the 1.0 version of their framework and some other thing and then come back and look 5 years later and their stack is easily or greater and complexity than the old Java stacks.