4 ms·

You're right; convoluted architecture has as much to do with Java as polar bears have to do with the arctic. They're two completely different things.

by dkarl 16y ago

lukesandberg 16y ago
Fun fact: its called the arctic because of the bears. The word arctic comes from a greek word meaning northern bears. http://en.m.wikipedia.org/wiki?search=Arctic http://en.m.wikipedia.org/wiki?search=Arctic And that is also why the antarctic has its name...because there are no bears there, just penguins.
- al-king 16y ago
  While it's certainly named for bears, that appears to be be a folk etymology: as the Wikipedia article you link suggests, the Arctic is named for the northern bear constellations Ursa Major and Ursa Minor, so called since the time of Homer. The word Antarctic has been in English since the C14th ( http://www.etymonline.com/index.php?term=Antarctic http://www.etymonline.com/index.php?term=Antarctic ); a continent opposite to the Arctic was hypothesised long before Antarctica was discovered in the 17th century. Antarctic, then, means "opposite of north" rather than "no bears" - though I suppose the Ursa constellations were also not in the north :) and it's a nice mnemonic.
Retric 16y ago
I think there is a correlation between limitations of Java and how people use it. If functions where a first class operator a lot of the architectural fluff would be truly pointless. However, because of language limitations people start to think of "flexibility" as a feature and try and make a an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp
dspeyer 16y ago
The design goal here is that you can get factorials by calling a function, but decide how to compute them (cached or not, with the ability to add new algorithms) by changing state. A dubious goal, but not completely insane. In python, it would be 15 lines, and simple. No utils, factories, algorithms or singletons. I imagine it could be done in more reasonable java than this, but could it really be done cleanly and compactly?

You're right; convoluted architecture has as much to do with Java as polar bears have to do with the arctic. They're two completely different things.

by dkarl 16y ago

You're right; convoluted architecture has as much to do with Java as polar bears have to do with the arctic. They're two completely different things.

lukesandberg 16y ago

Fun fact: its called the arctic because of the bears. The word arctic comes from a greek word meaning northern bears. http://en.m.wikipedia.org/wiki?search=Arctic http://en.m.wikipedia.org/wiki?search=Arctic And that is also why the antarctic has its name...because there are no bears there, just penguins.

al-king 16y ago
While it's certainly named for bears, that appears to be be a folk etymology: as the Wikipedia article you link suggests, the Arctic is named for the northern bear constellations Ursa Major and Ursa Minor, so called since the time of Homer. The word Antarctic has been in English since the C14th ( http://www.etymonline.com/index.php?term=Antarctic http://www.etymonline.com/index.php?term=Antarctic ); a continent opposite to the Arctic was hypothesised long before Antarctica was discovered in the 17th century. Antarctic, then, means "opposite of north" rather than "no bears" - though I suppose the Ursa constellations were also not in the north :) and it's a nice mnemonic.

Retric 16y ago

I think there is a correlation between limitations of Java and how people use it. If functions where a first class operator a lot of the architectural fluff would be truly pointless. However, because of language limitations people start to think of "flexibility" as a feature and try and make a an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp

dspeyer 16y ago

The design goal here is that you can get factorials by calling a function, but decide how to compute them (cached or not, with the ability to add new algorithms) by changing state. A dubious goal, but not completely insane. In python, it would be 15 lines, and simple. No utils, factories, algorithms or singletons. I imagine it could be done in more reasonable java than this, but could it really be done cleanly and compactly?