3 ms·

It still bothers me when people talk about dynamic HTML these days. Just two weeks ago some team lead said it and I thought 'dude, that is so 90s'.

lostcolony 6y ago
It's also probably incorrect; DHTML didn't involve loading data via AJAX after the page loaded, but instead configuring the webpage on the client side after loading it. That said, ask them if they'd prefer the backend in PHP or Coldfusion.
- MentallyRetired 6y ago
  As someone who's been making websites since 1993, everything you said here has made me twitch in one way or another. I've been a ColdFusion team lead, a PHP developer and I used to write DHTML scripts. Also RIP to separation of concerns on the frontend (document [html], style [css] and behavior [js]) since it's all buried in javascript nowadays.
  - dsego 6y ago
    Rip separation of technologies (not concerns) and welcome to composable and soon dynamically run federated UI modules.
- bdcravens 6y ago
  Given that Wordpress can be targeted as an API for a SPA and Laravel is pretty hot, I'd say PHP isn't a bad choice. ColdFusion of course is pretty out of vogue, but places like Invision like it still. A better comparison would be with ASP 3 or Perl.
- Mountain_Skies 6y ago
  Sigh. Working in cybersecurity, it makes me sad to see how much ColdFusion is still in use, full of security holes that no one will fix because the original developers have long since moved on and current developers don't want to touch anything CF related with a ten foot pole.
- WorldMaker 6y ago
  1999 saw the release of XMLHttpRequest as an ActiveX control for IE 5. There certainly were IE-focused developers still referring to most of what they were doing as DHTML and yet doing the earliest AJAX stuff, back when the X still made sense that it stood for XML and XMLHttpRequest was the first and at the time only AJAX tool available in a web developer's toolbelt.
  - z3t4 6y ago
    Also don't forget about long-polling (long running request), or an iframe that refresh itself.
flomo 6y ago
Reminded me of the MS "DHTML Dude" blog. (no longer online, it appears.)

lostcolony 6y ago

It's also probably incorrect; DHTML didn't involve loading data via AJAX after the page loaded, but instead configuring the webpage on the client side after loading it. That said, ask them if they'd prefer the backend in PHP or Coldfusion.

MentallyRetired 6y ago
As someone who's been making websites since 1993, everything you said here has made me twitch in one way or another. I've been a ColdFusion team lead, a PHP developer and I used to write DHTML scripts. Also RIP to separation of concerns on the frontend (document [html], style [css] and behavior [js]) since it's all buried in javascript nowadays.
- dsego 6y ago
  Rip separation of technologies (not concerns) and welcome to composable and soon dynamically run federated UI modules.
bdcravens 6y ago
Given that Wordpress can be targeted as an API for a SPA and Laravel is pretty hot, I'd say PHP isn't a bad choice. ColdFusion of course is pretty out of vogue, but places like Invision like it still. A better comparison would be with ASP 3 or Perl.
Mountain_Skies 6y ago
Sigh. Working in cybersecurity, it makes me sad to see how much ColdFusion is still in use, full of security holes that no one will fix because the original developers have long since moved on and current developers don't want to touch anything CF related with a ten foot pole.
WorldMaker 6y ago
1999 saw the release of XMLHttpRequest as an ActiveX control for IE 5. There certainly were IE-focused developers still referring to most of what they were doing as DHTML and yet doing the earliest AJAX stuff, back when the X still made sense that it stood for XML and XMLHttpRequest was the first and at the time only AJAX tool available in a web developer's toolbelt.
- z3t4 6y ago
  Also don't forget about long-polling (long running request), or an iframe that refresh itself.

flomo 6y ago

Reminded me of the MS "DHTML Dude" blog. (no longer online, it appears.)