5 ms·

I had to work on quite a few coldfusion sites in the 1998 to 2010 timeframe. I found having to write brackets for each and every statement to be tiring; <cfif>

I had to work on quite a few coldfusion sites in the 1998 to 2010 timeframe. I found having to write brackets for each and every statement to be tiring; <cfif> <cfelse> <cfset var mystuff "johnnyb"> Eventually, they incorporated cfscript which let you write stuff that was more like the c derived languages. But they did not port every <cftag> function over to cfscript. Terrible oversight. If you had to resort to ending your cfscript to fall back to a cftag it made the code really ugly. <cfdump> was ahead of its time. It came out way before php var_dump. <cfquery> was really powerful. It let you take any database result and then treat that result as though it were a database itself. So you could query a query so to speak. Something else I remember is how many ColdFusion devotees I worked with. I never understand how people get so attached to a language (ColdFusion, Ruby), a company (Apple), or a database (Postgres, MongoDB). It becomes some kind of cult. So many defensive ColdFusion programmers I had to deal with. Edit to add another memory. Old ColdFusion would use YES for true and NO for false. That would cause a lot of headaches when dealing with other systems that had no notion of YES or NO.

tombert 2y ago
> ventually, they incorporated cfscript which let you write stuff that was more like the c derived languages. But they did not port every <cftag> function over to cfscript. Terrible oversight. If you had to resort to ending your cfscript to fall back to a cftag it made the code really ugly. I never used cfscript for this reason. I felt like if I couldn't use every feature of the language, then there's no point in messing with it. I definitely miss cfdump sometimes. It was ridiculously useful for what it did. > Something else I remember is how many ColdFusion devotees I worked with. I never understand how people get so attached to a language (ColdFusion, Ruby), a company (Apple), or a database (Postgres, MongoDB). It becomes some kind of cult. So many defensive ColdFusion programmers I had to deal with. Yeah, even when I doing that job (2012), Coldfusion was falling out of favor, and I would mention to my manager that we might want to start transitioning to Railo or rewriting stuff using Java EE or something, and would get extremely defensive about it. He was more polite than this, but he basically said something that implied that I didn't know what I was talking about and Coldfusion will still be used for years and years to come. I guess he was half right :)

tombert 2y ago

> ventually, they incorporated cfscript which let you write stuff that was more like the c derived languages. But they did not port every <cftag> function over to cfscript. Terrible oversight. If you had to resort to ending your cfscript to fall back to a cftag it made the code really ugly. I never used cfscript for this reason. I felt like if I couldn't use every feature of the language, then there's no point in messing with it. I definitely miss cfdump sometimes. It was ridiculously useful for what it did. > Something else I remember is how many ColdFusion devotees I worked with. I never understand how people get so attached to a language (ColdFusion, Ruby), a company (Apple), or a database (Postgres, MongoDB). It becomes some kind of cult. So many defensive ColdFusion programmers I had to deal with. Yeah, even when I doing that job (2012), Coldfusion was falling out of favor, and I would mention to my manager that we might want to start transitioning to Railo or rewriting stuff using Java EE or something, and would get extremely defensive about it. He was more polite than this, but he basically said something that implied that I didn't know what I was talking about and Coldfusion will still be used for years and years to come. I guess he was half right :)