That even though they are both illegal, they're not the same thing. Murder is illegal too, but you don't go around calling people who make unauthorised copies of copyrighted material murderers, do you? Why not? They're bot illegal, aren't they?
By "preseeded configured values" do you mean you can put stuff into the debconf database and skip the questions? Do you have a reference to a HOWTO describing that? And also some documentation on how to run a script between the first and second stage installer? This all sounds very interesting..
I've actually been looking for some of these ebay-for-coders sites. Do you have any URL's?
Re:Firefox versus Mozilla
on
Firefox Hacks
·
· Score: 1
A few of the plugins for firefox only work in firefox.. Don't remember which, though, but they were enough to convince a cow-orker to switch from Mozilla to Firefix.
It took me about this long to figure out, what you were trying to tell me and I'm still not totally sure..
If what you're saying is that you want something where you can differentiate between something you refer to as "public", "protected" and "private" stuff, then yes, you're probably stuck with Java.
If however, you're willing to compromise and get the EXACT same thing but you have to call it e.g. "static" instead of "private", you might find that other languages and paradigms support this as well. Any non-braindead langauge (and even Java) support some degree of scoping.
It REALLY pisses me off every time someone says that the only way you can have modularized code is in the OO paradigm. Modularization and OO have NOTHING to do with each other. Putting stuff into modules instead of a huge monolith is _good_ _coding_ _practice_. And it's good coding practice no matter which programming paradigm you're using.
I doubt that very many would argue that monolithic spaghetti code is a good thing, because it very seldomly is.
The OO zealots have invented a new word for modularization ("encapsulation") and then they believe they've invented it and now own it. There's nothing new about it and there's nothing OO about it.
Go read a book or something. Get wiser. Lose the OO hype.
In Denmark it's very common to have such a clause in your contract. However, it's almost just as common to NOT have any compensation for it. The cool part is that Danish law demands that a proper compensation be granted to the employee in case of such a clause. No compensation => Clause is null and void.
Attackers can reset connections last year?!?
Why didn't anyone tell me this before?
That even though they are both illegal, they're not the same thing. Murder is illegal too, but you don't go around calling people who make unauthorised copies of copyrighted material murderers, do you? Why not? They're bot illegal, aren't they?
By "preseeded configured values" do you mean you can put stuff into the debconf database and skip the questions?
Do you have a reference to a HOWTO describing that? And also some documentation on how to run a script between the first and second stage installer?
This all sounds very interesting..
I've actually been looking for some of these ebay-for-coders sites.
Do you have any URL's?
A few of the plugins for firefox only work in firefox.. Don't remember which, though, but they were enough to convince a cow-orker to switch from Mozilla to Firefix.
"i" is the third character under the number 4 ???
What's that supposed to mean?
It took me about this long to figure out, what you were trying to tell me and I'm still not totally sure..
If what you're saying is that you want something where you can differentiate between something you refer to as "public", "protected" and "private" stuff, then yes, you're probably stuck with Java.
If however, you're willing to compromise and get the EXACT same thing but you have to call it e.g. "static" instead of "private", you might find that other languages and paradigms support this as well. Any non-braindead langauge (and even Java) support some degree of scoping.
Open yOOr eyes, man.
It REALLY pisses me off every time someone says that the only way you can have modularized code is in the OO paradigm. Modularization and OO have NOTHING to do with each other. Putting stuff into modules instead of a huge monolith is _good_ _coding_ _practice_. And it's good coding practice no matter which programming paradigm you're using.
I doubt that very many would argue that monolithic spaghetti code is a good thing, because it very seldomly is.
The OO zealots have invented a new word for modularization ("encapsulation") and then they believe they've invented it and now own it. There's nothing new about it and there's nothing OO about it.
Go read a book or something. Get wiser. Lose the OO hype.
In Denmark it's very common to have such a clause in your contract. However, it's almost just as common to NOT have any compensation for it. The cool part is that Danish law demands that a proper compensation be granted to the employee in case of such a clause. No compensation => Clause is null and void.