In the US, there are only three reasons you can sue for this. 1) The company promised via explicit or implied contract that they wouldn't. (Exceedingly unlikely.) 2) You complained about safety and they fired you in retaliation. 3) They fired you for your race, age or gender.
Since most companies employee people "at-will", they can essentially fire you for any damn reason they want, as long as you aren't a whistle-blower and as long as their reasons aren't discriminatory in specific ways.
Some farmers in the great plains discovered that if they coiled barbed wire underneath the massive power lines running along their property, they could power their houses for free.
The power company was baffled be the unexplained power drain for months.
If you are going to make the analogy, you are going to have to make it right. If you go to tell the cops that someone stole something from you, the very first question they will ask is "what did they steal?"
They won't take a response like "well, just wait until the court date!" seriously.
I never use antivirus software and I have never gotten any of these stupid Trojan horses. Why? Because I am not a moron, and because I don't use Outlook or Outlook Express.
(And it's not a matter of clueful versus neophyte users. My wife doesn't know a "C:" from a "/", but I managed to teach her how not to open a suspicious attachment in about ten minutes.)
Who cares if it's obsolete in 5 years? The interface only allows up to 128 Mb. In five years, that'll be too small to care about. (Equivalent of 12 Mb today, if Moore's law holds.)
Of the competing formats, only Compact Flash supports larger sizes. Sony's already building a successor to the memory stick to get capacities above 128 Mb, and it'll almost certainly not be compatible, so memory sticks will be obsolete in 5 years anyway, regardless of whether or not the format is open. But the same is true with the competing formats.
I have an older version of the Yepp (The Yepp-NEU) and while the sound quality is good, my experience with it is generally not good. Only a few months after purchasing it, the battery cover came off, requiring jury-rigging with tape to get it to work. The spring inside is too strong and the rest of the material too fragile. Also, it originally required using Real Jukebox to load music on it, and this software just completely sucked at it, often hanging when copying or failing to recognize the player. Eventually Samsung released their own software, which is better as while it still hangs, it doesn't fail to recognize the player. My experience was negative enough that though I still use the player, I would never recommend a Samsung, or buy another myself.
An IPO is basically selling part of your ownership in a company for money. As with any stock, if you think the company will be worth more money in the future, and you don't need the money you'd get from the sale, you are better off not doing it.
It's no more a "straight jacket" then "assert" is.
It's a matter of telling the compiler what you expect so that the compiler can tell you if what you expect is wrong.
It catches bugs.
You may be interested to know that there were many C++ container libraries that used "derive from object" and runtime casting long before templates were even part of the language. They've been dumped in favor of template containers precisely because template containers have advantages over them. I've used both, and I've also used both Java and C# containers extensively, and believe me, I'd rather be able to tell the compiler what to expect.
No, confusion between strings and ints isn't a major source of bugs...but when you've got a lot of different classes and a complex hiearchy it is a different story.
As for design patterns...I find your comments amusing given that the canonical design pattern book used the ultimate dynamic OO language, Smalltalk, in all its examples.
I'm a C#/C++ developer, so I'm in pretty much the same boat. When I'm writing C++, I use templates heavily. When I'm writing C#, I bitch and moan about the lack of templates.
Templates are a pretty straightforward trade of space for speed. Given the cheapness of memory these days, that's not a bad trade.
Though personally, I find little bloat to speak of. It has been literally a decade since I had to worry about memory size. (As opposed to worrying about speed literally yesterday.)
The largest C++ project I'm working on write now is about 7,000 lines of code. It makes heavy use of both the STL and templates. It runs about 500k on disk and seems to take between one and three megabytes of memory when run.
And in fact, anyone who wrote C++ programs under DOS and/or Win 3.1 used a compiler that had pointers of differing sizes. (Though using nonstandard keywords like "near" and "far".)
Slashdot Mirror
IANAL. However, I just spent two weeks in a jury on a "wrongful termination" case.
In the US, there are only three reasons you can sue for this. 1) The company promised via explicit or implied contract that they wouldn't. (Exceedingly unlikely.) 2) You complained about safety and they fired you in retaliation. 3) They fired you for your race, age or gender.
Since most companies employee people "at-will", they can essentially fire you for any damn reason they want, as long as you aren't a whistle-blower and as long as their reasons aren't discriminatory in specific ways.
Yup. That's why you ream 'em for all you can get when they have no choice, and immediately look for other work elsewhere.
[insert joke about it being hideously ugly with templates here.]
{I did not read the article itself because it is, of course, slashdotted)
Some farmers in the great plains discovered that if they coiled barbed wire underneath the massive power lines running along their property, they could power their houses for free.
The power company was baffled be the unexplained power drain for months.
If you are going to make the analogy, you are going to have to make it right. If you go to tell the cops that someone stole something from you, the very first question they will ask is "what did they steal?"
They won't take a response like "well, just wait until the court date!" seriously.
(And it's not a matter of clueful versus neophyte users. My wife doesn't know a "C:" from a "/", but I managed to teach her how not to open a suspicious attachment in about ten minutes.)
Uh...I was the guy who wrote the original comment. I had "compiled" in there because it was mentioned in the post I was replying to.
Probably about as many as the number of "// TODO: Place code here" in Visual C++ projects.
Hence the for "visual" UI development clause.
BASIC wasn't so bad, before some company or other (can't remember which right now) decided to make a compiled version for "Visual" UI development.
Does anybody seriously think he can have another hit like Daikatana again?
What I hate about your programming language is that it doesn't work like mine does.
I don't think the hardware to support the learning approaches used by multi-layer networks was there until the eighties.
Of the competing formats, only Compact Flash supports larger sizes. Sony's already building a successor to the memory stick to get capacities above 128 Mb, and it'll almost certainly not be compatible, so memory sticks will be obsolete in 5 years anyway, regardless of whether or not the format is open. But the same is true with the competing formats.
OS/2 started as a joint IBM/Microsoft OS.
(nt)
I have an older version of the Yepp (The Yepp-NEU) and while the sound quality is good, my experience with it is generally not good. Only a few months after purchasing it, the battery cover came off, requiring jury-rigging with tape to get it to work. The spring inside is too strong and the rest of the material too fragile. Also, it originally required using Real Jukebox to load music on it, and this software just completely sucked at it, often hanging when copying or failing to recognize the player. Eventually Samsung released their own software, which is better as while it still hangs, it doesn't fail to recognize the player. My experience was negative enough that though I still use the player, I would never recommend a Samsung, or buy another myself.
Putting off an IPO can be the greedy thing to do.
Microsoft was one company that waited a very long time before going public. This is one reason why it is the founders who are still in control today.
You can just create wrapper classes, ala "boost::any".
Also note that C++ is flexible enough to do it the java way. For example:
:internal(s) {}
:internal(i) {}
class Object {};
class String : public Object {
public:
String(string s)
operator string() { return internal; }
private:
string internal;
};
class Int : publoc Object{
public:
Int(int i)
operator int() { return internal; }
private:
int internal;
};
stack<Object&> MyStack;
Then you can do it the "Java" way. If you don't feel like typing that code, boost has a library that does the same thing.
It's a matter of telling the compiler what you expect so that the compiler can tell you if what you expect is wrong.
It catches bugs.
You may be interested to know that there were many C++ container libraries that used "derive from object" and runtime casting long before templates were even part of the language. They've been dumped in favor of template containers precisely because template containers have advantages over them. I've used both, and I've also used both Java and C# containers extensively, and believe me, I'd rather be able to tell the compiler what to expect.
No, confusion between strings and ints isn't a major source of bugs...but when you've got a lot of different classes and a complex hiearchy it is a different story.
As for design patterns...I find your comments amusing given that the canonical design pattern book used the ultimate dynamic OO language, Smalltalk, in all its examples.
I'm a C#/C++ developer, so I'm in pretty much the same boat. When I'm writing C++, I use templates heavily. When I'm writing C#, I bitch and moan about the lack of templates.
Though personally, I find little bloat to speak of. It has been literally a decade since I had to worry about memory size. (As opposed to worrying about speed literally yesterday.)
The largest C++ project I'm working on write now is about 7,000 lines of code. It makes heavy use of both the STL and templates. It runs about 500k on disk and seems to take between one and three megabytes of memory when run.
And in fact, anyone who wrote C++ programs under DOS and/or Win 3.1 used a compiler that had pointers of differing sizes. (Though using nonstandard keywords like "near" and "far".)