How do you handle global state?
-
OK, not completely language-independent - but independent of particular implementation of Bourne shell.
-
So it's really more like writing .NET code that runs on Mono than language-independant.
-
Yes. Except Mono at least tries to be like .NET. I'd rather compare it to Python-2-and-3-compatible code, or C++-compatible subset of C.
-
This is still terribly unclear to me. Perhaps a car analogy would clear things up?
-
Like trying to make sure the engine from your Porche will fit straight in to a VW Beetle?
-
Because car analogies are best IT analogies.
Language independence of scripts isn't like a car that can go over road, sand, water and ice. It's more like a car that can drive on autobahn, dirt track and railroad without much difficulties.
Edit: and blakeyrat is like that guy who yells about how all hovercrafts are terrible because they're full of eels.
-
Language independence
Language independence really isn't. It's just using the common subset of a family of languages.
-
So is platform independence.
-
Ah, yes, the No True Independence fallacy.
-
Language independence of scripts isn't like a car that can go over road, sand, water and ice. It's more like a car that can drive on autobahn, dirt track and railroad without much difficulties.
Did you mean a Hi-Rail truck?
-
Yeah, kinda. Though I'm not sure of their off-road capabilities.
-
Yeah, kinda. Though I'm not sure of their off-road capabilities.
Good enough to get over a dirt track, at least -- ROW roads tend to be unpaved.
-
Technically, the first Beetle used a Porsche motor.
-
Technically, the first Beetle
usedis a Porschemotor.
Given it was designed by the man himself ;)
-
You've been awarded the Pendant++ bash
-
Pendant++ bash
That's a bit violent, isn't it? Can't I just get a Pendant++ nudge instead?
-
Yeah, that's why I used those particular cars. The drive train would probably break if you tried it though, which in this analogy would probably be a runtime error after successful compilation or sonething
-
Damn it, too much coding for the day.
-
DI framework
GAAAAAH!
Sorry. Flashbacks again.
Luckily I managed to push most of the memories out of my brain, but I did use a DI framework once. I think it was Castle Windsor, and between piss-poor documentation, tons of boilerplate, having to rework the whole project to fit the DI structure, some things flat-out not working together with the framework (while CW has a log4net component, we used a custom wrapper around it, and I don't remember why, but it turned out not to be injectible without modifications I couldn't do), and the whole thing generally turning out to be pointless since we weren't unit testing that part of code anyway, I'd rather not do this again.