4 ms·
The early days of web development up to roughly the end of the 1990s technically were full stack. It's just nobody called it that at the time. It's only by the
by BjoernKW 8y ago
The early days of web development up to roughly the end of the 1990s technically were full stack. It's just nobody called it that at the time.
It's only by the early 2000s and the advent of architecturally complex, heavily back-end-leaning frameworks such as J2EE or JSP that front-end and back-end diverged. These frameworks had their benefit compared with the fast-and-loose way web apps often were developed before but they also introduced new problems.
Apart from inherent architectural issues these frameworks introduced a new crop of developers to web development that was at least somewhat averse towards how front-end development is done on the web. To this day, I still know developers who loathe JavaScript, CSS and HTML because "they're not the proper way of doing things".
Furthermore, with traditional desktop applications you also usually have a full stack attitude, although again it isn't called "full stack" in that case. Desktop application developers are typically expected to be able to write both UI code as well as business logic and database access code. Probably that's because with desktop applications there's usually only a single language you're dealing with.
- zozbot123 8y ago> Furthermore, with traditional desktop applications you also usually have a full stack attitude, although again it isn't called "full stack" in that case. Desktop application developers are typically expected to be able to write both UI code as well as business logic and database access code. Many GUI applications are actually based on a client-server pattern that mirrors the "front-end" v. "back-end" distinction. Often the "server" is a separate CLI app, or even a daemon/service with no interaction with the rest of the system other than via the platform IPC (COM, DBus, whatever). Consider the traditional large-scale "pattern" of desktop apps, viz. Model-View-Controller. The Model is back-end, the View-Controller pair (which is often tightly coupled anyway) is front-end.
- Novashi 8y agoDesktop and web development also got to ignore responsive design for a long time, and that revolution added serious complexity to HTML/CSS/JS and browser engines. You could slap a minimum desktop resolution on your product and call it a day.
- zozbot123 8y agoHTML/CSS were engineered to be device-independent and to separate styling from the underlying semantics, from day one. Properly understood, "responsive design" is a triviality; all good design is responsive design.
- Novashi 8y ago>HTML/CSS were engineered to be device-independent and to separate styling from the underlying semantics, from day one. These were business trends, not mechanical limitations. >Properly understood, "responsive design" is a triviality; all good design is responsive design. I have no idea what you mean by this. Responsive design means for a page to respond to different viewport constraints by re-arranging elements and making rules for different breakpoints that you choose to support. None of that is trivial unless this is another "it's not a hard CS problem so it's trivial" argument.
- tatersolid 8y agoRe-arranging elements optimally into different sized containers is clearly not trivial. It is an instance of the bin-packing problem, which is NP-complete.
- pseudalopex 8y ago1990s web development used a lot less JavaScript. Also, I think there is more of an expectation today for developers to be designers and vice versa.