2 ms·

OK, so now you're arguing the meaning of "modern", but perhaps you should refine your original point. Do you have specific examples of incorrect applications of

OK, so now you're arguing the meaning of "modern", but perhaps you should refine your original point. Do you have specific examples of incorrect applications of the label "modern"? Are you just objecting to vagueness?

zogrodea 3y ago
I didn’t write the very first post we’re all commenting on, but I think the objection to vagueness is in that very first post. “My point is that ‘modern’ can sometimes be a vague and overused term. Instead of relying on this label, it's more informative to understand what specific technologies, practices, or improvements a project brings to the table.” I don't have any stats to bring up to decisively say one way or another, but people express discontent about modern JS framework churn, yearning for server-side templates solutions of old and other complaints about "modern" software. That might or might not be misguided, but it exists.
- cratermoon 3y ago
  If the objection is "don't use the term ’modern’ as if it automatically means better”, I agree, but there are also other terms that are essentially marketing speak, and not just for software. Right now we're seeing a rash of “AI-enabled” claims, as if just evoking that two-letter acronym is a selling point. Even words that once had specific meanings, like "agile" or "smart" (as in smart homes, smart cars, smartwatches, etc) have been co-opted as some kind of feel-good claim. The OP seems to argue for describing the concrete and specific benefits and risks of technologies and practices, and comparing those with the organization's goals and problems. I stand by my suggestion to tighten up the the original observation and provide more specifics for “modern” when used vaguely. What connotations have become associated with the term, and what implications are problematic when using “modern”?

zogrodea 3y ago

I didn’t write the very first post we’re all commenting on, but I think the objection to vagueness is in that very first post. “My point is that ‘modern’ can sometimes be a vague and overused term. Instead of relying on this label, it's more informative to understand what specific technologies, practices, or improvements a project brings to the table.” I don't have any stats to bring up to decisively say one way or another, but people express discontent about modern JS framework churn, yearning for server-side templates solutions of old and other complaints about "modern" software. That might or might not be misguided, but it exists.

cratermoon 3y ago
If the objection is "don't use the term ’modern’ as if it automatically means better”, I agree, but there are also other terms that are essentially marketing speak, and not just for software. Right now we're seeing a rash of “AI-enabled” claims, as if just evoking that two-letter acronym is a selling point. Even words that once had specific meanings, like "agile" or "smart" (as in smart homes, smart cars, smartwatches, etc) have been co-opted as some kind of feel-good claim. The OP seems to argue for describing the concrete and specific benefits and risks of technologies and practices, and comparing those with the organization's goals and problems. I stand by my suggestion to tighten up the the original observation and provide more specifics for “modern” when used vaguely. What connotations have become associated with the term, and what implications are problematic when using “modern”?