[Info-vax] And another one bites the dust....

[Arne Vajhøj]

On 2/21/2022 3:04 PM, Dan Cross wrote:
> In article <sv0obg$mnm$1 at panix2.panix.com>,
> Scott Dorsey <kludge at panix.com> wrote:
>> John Dallman <jgd at cix.co.uk> wrote:
>> [snip]
>> Someday you'll need to write Java.  It's like the baby food version of C.
> 
> It's funny, when I was in high school someone scolded me for
> basically saying that I would pick the most appropriate language
> for the problem at hand.  Some technician dragged me through the
> mud saying, basically, "you'll program in whatever language your
> manager tells you to."
> 
> Curiously, that never really happened.  Nowdays, I'm happy that
> I'm senior enough that I can largely decide these things for
> myself.
> 
> I did spend a year and change programming in Java.  The language
> itself isn't terrible, though verbose.  However, it does seem to
> be attached to what one might call a culture of excessive
> abstraction.  It sure seemed like an excessive amount of code is
> dedicated to various kinds of machinery plugging in providers,
> adapters, and all sorts of GoF design patterns, without actually
> doing much of anything.  :-/  "At what point do we actually add
> these two numbers together?" "Oh, you just implement this
> interface and create a factory that plugs into this DI framework
> and that code is generated for you."

Classic example is probably creating an XML document.

C#:

XmlDocument doc = new XmlDocument();
doc.Load(XML_FILE);

Java:

DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
Document doc = db.parse(new File(XML_FILE));

Arne