71–80 of 87 posts
Earlier quoted context omitted.
Lol, no one really. Just a few obscure organizations like NASA, Apple, Pud's DistroKid/Fandalism, Intel, AT&T, and tons of others. Oh and railo is a java framework, who uses java!? Its 2013!
According to Wired Java is experiencing a renaissance of sorts: http://www.wired.com/wiredenterprise/2013/09/oracle_java/
One thing that would be great here would be autocompletion. I often forget exactly what the syntax of "CREATE TABLE" is or which options I can use. The same goes for infrequently used SQL functions (now is that date_diff or datediff?). You could combine autocompletion with a doc panel that automatically updates to show the "quick reference" for the keyword you're currently typing.
Slightly off-topic, but one thing that always impressed me about Microsoft's LINQ as an alternative to SQL queries is that they considered autocompletion up-front in the language syntax. For SQL, it's a big challenge - you may type in 'SELECT', but your IDE still has no idea what relation(s) you're going to access, and so it can't reasonably autocomplete the possible fields you might want to use. It's an interesting…
Earlier quoted context omitted.
Slightly off-topic, but one thing that always impressed me about Microsoft's LINQ as an alternative to SQL queries is that they considered autocompletion up-front in the language syntax. For SQL, it's a big challenge - you may type in 'SELECT', but your IDE still has no idea what relation(s) you're going to access, and so it can't reasonably autocomplete the possible fields you might want to use. It's an interesting…
Would you elaborate on the weaknesses of LINQ you mentioned?
Earlier quoted context omitted.
Sorry, but it is completely logical to choose Ruby/Rails, Python/Django, etc over CFML in 2013 for web projects.
>ColdFusion is... not a particularly good choice these days for a variety of reasons. Not that I disagree with you, but I wonder if the reasons you have in mind are valid. A lot of the reasons one might assume CF sucks aren't really applicable (i.e. speed, security) any more than most other languages.
Earlier quoted context omitted.
Sorry, but choice of language means more than nothing. ColdFusion is pretty dead-end and not a particularly good choice these days for a variety of reasons.
Let me break it for you, nobody except you and some opinionated programmers on the web, cares what language you wrote website X or web app Y in. If it works, and you are able to maintain it - you won't hear a single word of praise from the 'users' congratulating you on your stellar choice of language. They'll rip you to shreds when it stops working but even then they'll never tell you off for choosing the wrong langu…
Earlier quoted context omitted.
Would you elaborate on the weaknesses of LINQ you mentioned?
To clarify: it was the SQL, not LINQ, language syntax (field selection prior to relation selection) that I was referring to as a potential weakness (but only once considered in the light of developer tools).
Not that it really matters to someone who is already familiar with SQL, however.
Earlier quoted context omitted.
Let me break it for you, nobody except you and some opinionated programmers on the web, cares what language you wrote website X or web app Y in. If it works, and you are able to maintain it - you won't hear a single word of praise from the 'users' congratulating you on your stellar choice of language. They'll rip you to shreds when it stops working but even then they'll never tell you off for choosing the wrong langu…
I understand your point of view, and in specific cases, the choice has little practical impact. However, when a business is dependent on an aging technology (language/framework/etc), the choice can have real consequences. As one example, when that very competent programmer who has expert level knowledge in this aging technology decides to move on, if the technology isn't well supported by a vendor, user community, an…
The consequences come for the poor bastards that have that old crap on their resume... Bus number notwithstanding...