News for hackers. Stuff that matters.
Re:JEP 430: String Templates (Preview) Proposed to Target Ja... by pron on Friday March 03, 2023 @06:41PM (#35016500)
Well, you know, even thirty years of experience as the custodians of one of the most successful programming languages is no guarantee of success with every feature, but that's why we have the preview process now that lets us figure out what problems people actually encounter -- which may well be different from the problems they, or we, think they would encounter -- before finalising the feature.
Re:JEP 430: String Templates (Preview) Proposed to Target Ja... by avgcorrection on Saturday March 04, 2023 @08:33AM (#35020649)
If I had a cent for every time pron appealed to Java’s age and “popularity” in technical arguments, I would have at least enough cents to use a dollar-sign in string template syntax.
Re:JEP 430: String Templates (Preview) Proposed to Target Ja... by pron on Saturday March 04, 2023 @08:51AM (#35020741)
That's cute, but that appeal is crucial because technical arguments that are divorced from empirical results in the field are a great way to spend a lot of time solving the wrong problems. For example, you can make technical arguments in favour of either VHS or Betamax, but while they both had superior solutions to two separate problems, one of those problems (recording time) ended up being a much more important problem for more people than the other. The purpose of engineering is not to enjoy intellectual puzzles, but to solve problems for people. If you insist that the team that does better than other teams, over and over for a few decades, is doing it all wrong, it's possible that what you consider to be right and wrong doesn't really fit with what's happening in the field.

The relatively new concept of preview features helps us do exactly that: gather information on what problems people actually encounter when working with a new feature as opposed to what problems some speculate they'll run into. The best way to influence Java's direction is not to speculate, but to report problems you've actually encountered to the relevant OpenJDK mailing list (amber-dev in this case). If the use of the \ or $ character actually turns out to be a real problem, we expect to find that out during the preview process (which will begin in JDK 21, out this September) and we'll reconsider, only we'll do it based on reports, not speculation.

Engineering is first and foremost about identifying what bigger problems more people actually need solving. Those who misunderstand that will forever be puzzled by why it is that the VHSes usually win over the Betamaxes and will continue betting on the wrong horses.

Re:JEP 430: String Templates (Preview) Proposed to Target Ja... by avgcorrection on Saturday March 04, 2023 @11:07AM (#35021818)
Well, I’ll agree that one shouldn’t be naive about the “technically superior” arguments. One has to look at why certain things succeeded. In an honest and non-ideological way (e.g. don’t blind yourself on the “technically superior” talking points, whatever that means).

I don’t really have a problem with a backslash over a dollar-sign. I just couldn’t resist...