4 ms·

While I do agree that it is still possible to use the "old" technology for web development, I don't agree that there is "no reason stopping you" from using them

While I do agree that it is still possible to use the "old" technology for web development, I don't agree that there is "no reason stopping you" from using them. I'm a recent CS graduate. In my final year's project, I was working on a website using PHP on the backend. My advisor told me that I would fail if I didn't use anything "more advanced", so I had to learn and work on Laravel. After college, I applied for a lot of jobs as a web developer, and every single on of them requested that I learn one or more front-end frameworks. I always show them some websites I made with pure HTML5-CSS-JS on the front end, and they seem to like them, but when they learn that no flashy framework was used, their tone changes. So yeah, unless someone is able to rely entirely on freelancing or launching a startup, there are reasons stopping me from not using frameworks.

rileymat2 6y ago
There are some nice elements to many frameworks that make you wish you had just used one to start. - xss protection - responsive to phone sizes - i18n - ect, ect, ect But more to the point I currently work on a SPA that did not use a framework when it was created by the original developer, and what you end up with is a homegrown undocumented unsupported insecure mess.
- Cpoll 6y ago
  Sufficiently complex software written without a framework becomes a framework, but one without the benefit of other users testing it for you.
- wizzwizz4 6y ago
  Plain HTML comes with XSS protection by default: just don't let users add arbitrary HTML to your page, and you'll be fine. Plain HTML is responsive to phone sizes, unless you do _really weird_ things with CSS (which, incidentally, also provides simple ways to be responsive to phone sizes, if you still want to do weird things). Internationalisation is a useful feature of frameworks, but the other two aren't really.
  - deleted 6y ago
    [deleted]
arpa 6y ago
Your advisor is an idiot.

rileymat2 6y ago

There are some nice elements to many frameworks that make you wish you had just used one to start. - xss protection - responsive to phone sizes - i18n - ect, ect, ect But more to the point I currently work on a SPA that did not use a framework when it was created by the original developer, and what you end up with is a homegrown undocumented unsupported insecure mess.

Cpoll 6y ago
Sufficiently complex software written without a framework becomes a framework, but one without the benefit of other users testing it for you.
wizzwizz4 6y ago
Plain HTML comes with XSS protection by default: just don't let users add arbitrary HTML to your page, and you'll be fine. Plain HTML is responsive to phone sizes, unless you do _really weird_ things with CSS (which, incidentally, also provides simple ways to be responsive to phone sizes, if you still want to do weird things). Internationalisation is a useful feature of frameworks, but the other two aren't really.
- deleted 6y ago
  [deleted]

arpa 6y ago

Your advisor is an idiot.