Then learn to program. I could write 1000 lines of Java/whatever that would be useless too. What about the argument that most languages are more or less equivalent - unless you have a Turing machine it's not going to get much more powerful. I could claim to have written the same app as you but mine works.
Anyway, the irony here is that on another subject you'd complain MS software is insecure...
Why is.net a dead-end? I could write that.Net is taking off, there's articles about Java being "so last century", etc. but that would be just as unsubstantiated. I work in an internal IT department of a large UK company and.Net is pervasive enough that it'll be around for years. Dead-end because it's limited, dead-end because it's rare or dead-end because it's an MS product?
No problem here, surely. Bloke caught for doing something wrong. Large organisation protects its IP.
Asserting that code in the public domain might cause security problems is just spin consistent with protecting IP. It's PR and would anyone here expect anything different. Might not be convincing but MS wants its code to itself, sees it as IP and wants to keep control over it. How is this different to any other organisation? Deride MS for being closed but if it acts consistently, where's the problem?
Wasn't there a war recently where the justification didn't really appear to reflect reality? Unless this guy is some kind of freedom fighter then where's the issue?
Two things: firstly, the honours are political for the government (which decides them) not the Queen. Secondly, if we didn't have a monarch here in the UK we'd still need a head of state. I, for one, would prefer the current situation over the possibility of President Blair (*shivers*).
As for VB it's not that bad, surely. Anything can be taught badly and teaching C# or Java and then OO in terms of how the language uses it rather than how general OO is and how the language happens to implement stuff would be bad too.
I wouldn't advocate it but there would be some advances (I'm not necessarily trolling here): it's a reasonable introduction to event based programming. Pre-dotnet syntax is a little inelegant (DIM is an anachronism at best). I'd agree it's not ideal because you'll start learning the IDE rather than the language.
And in real-life it had its uses. I was involved in a quick two-week project in VB to create a simple management reporting tool because the Java developers quoted six months worth of effort for the same functionality. This isn't dissing Java but sometimes some developers cannot see the wood for the trees. Yes, they'd have an MVC based architecture with lots of abstraction but the VB version was very simple and maintainable. As the saying goes if you just have a hammer, every problem will look like a nail.
Cool - I should had added SmallTalk to my list, which is similar (iteration is object based too). You're right about the two being clones. Will check out RoR as it sounds interesting for this reason (and I imagine a little more popular than SmallTalk at present).
If Java's sold as being free (as in beer, because of the Eclipse IDE), then there's not necessarily an immediate advantage over C#. There's Visual Studio Express editions of VB and C# which are similarly free. (And presumably your Uni will have this and/or the full version.)
... at least on language merit, which is almost certainly likely to be bias.
Which might prove more useful on a CV (and PHBs don't necessarily care if you can do one you can do any)?
If you learn OO, then Java vs. C# is largely irrelevant. There's some minor syntax differences and a whole host of library issues but nothing that's as important to knowing the underlying concepts.
Which class has more women in it? (Okay, a joke but if the distinction is that slight you may as well use something to decide. And g/more/any/, etc.)
Learn OO and go from there. And if you know enough to understand co-variance then you'll get a job if I interviewed you - lots of people claim to be "OO-experts" but crumble when challenged with anything more demanding that the first few pages of any language book.
And, finally, when looking at books - particular the non-academic language specific ones - go for anything that describes how concept X works, not how language Y implements concept Y. E.g. interface vs. implementation inheritance is a core OO idea. It's not language specific. Java and C# are more similar than they are different. (With apologies to Z-fanboys wanting to suggest either r0x0r, etc.)
Are you new here? Opportunity to take a cheap shot as MS. Taken! Should there ever be a story about a MS employee saving a puppy from drowning they'll be someone here to moan about it.
So when John Seigenthaler is libelled, the crowd shout: he could edit it to make it correct.
When a Wiki bod edits their own entry it's wrong.
I know this is/. a place where reason comes a distant second to dogma, but sheesh, really. At least having it every which way means you're never wrong, right?
Two computer science students, both male, are talking:
CS Student 1: Oh! Guess what happened to me this morning!
CS Student 2: What?
CS1: I was walking through the park and this woman cycles up to me, stops, removes all her clothes, throws herself to the ground and says: "Take whatever you want"
CS2: Gosh! What did you do?
CS1: I took her clothes.
CS2: Good call - you already have a bicycle, don't you.
Yeah, and my grandmother have never fucking heard of Linux either. That must be shite too.
Try opening a fucking window, take a look around and discover what's going on in the world. Frankly, if you've not heard of the Pixies you've not real interest in alternative music have you.
Opera may be a fine browser, but we already have a really good (and open) thing going on with Firefox.
For some other topics choice is a good thing. But you're implying it's a good thing as long as you choose the same alternative.
If there's any truth here perhaps they want a closed source alternative to FF. Could happen and it'll be free from any perceived downsides to the Mozilla license.
As for intentionally wedging, again this is choice. It's not IE (boo) and FF (yah) and it needn't be. As for why anyone would choose Opera over Firefox: I did. I actually paid for it too. It's small, fast, and as far as I've experienced "just works" (at least the browser; not interested in the mail client, never used it). In some threads about FF you'll have users admitting - gasp - it can be resource intensive and even crash sometimes. There's also a minor plus point in using a minority browser as it receives less attention with respect to exploits. (FF isn't free of these, although, yes, they get fixed quicker than IE, etc.)
Finally, as you say, it's a fine browser. So why not?
It's possible to parse malformed English quite easily. There's a Steven Pinker book that (Language Instinct) that describes hxw xts pxssxblx tx rxxd wxthxxt vxwxls.
There's certainly lots of pounding but it's a simple rule that's usually applied incorrectly. As for missing apostrophes, it's more a case of adding them where they don't belong.
I just think it's odd that if you make a small technical error around here you'll get picked up on it. Suggest there's a need for reasonable grammar and you're a grammar nazi. What gives?
Anyway, not a criticisms of the editors in particular - but they could proof for this stuff when they check the story's not a dupe. Oh....
On a related subject, there's a story about a newspaper columist who sets a competition. There are a few deliberate grammatical errors in the column and a prize for anyone spotting them all. Lots of entries are received detailing a greater number of unintentional errors.
Anyway, it'd be nice if at least/. editors used "its" correctly. And contributors used paragraphs. And I'd learn to type...
Depends. You might read "it's" as meaning possessive but others will infer that if the author can't handle basic grammar then the content of their expression is somewhat lacking too.
It's not difficult. After all if this is a techical group discussing fairly technical issue with some accuracy a simple grammar rule should be manageable. "its" is possesive; "his" and "hers" do not have apostrophes. "It's" like "don't" is an abbreviation and does.
It can be awkward subject because a pedant is a person who can apply one simple rule more than you can. Using preprepositions at the end of sentences, misusing "which" and "that", etc. follows. However, "it's" versus "its" is trivial. Make an effort guys.
Note: I'm more than open to amusing criticisms of any spelling, grammatical or spelling errors in the above. I'll read replies and try to avoid similar errors in future. Like many here I'm write code every day. I'd hope I'd learn something doing this to improve. Why must basic grammar be something that you leave behind when your basic education finishes?
Slashdot Mirror
Then learn to program. I could write 1000 lines of Java/whatever that would be useless too. What about the argument that most languages are more or less equivalent - unless you have a Turing machine it's not going to get much more powerful. I could claim to have written the same app as you but mine works.
Anyway, the irony here is that on another subject you'd complain MS software is insecure...
[Mono is] just a much a dead-end as .NET.
Why is .net a dead-end? I could write that .Net is taking off, there's articles about Java being "so last century", etc. but that would be just as unsubstantiated. I work in an internal IT department of a large UK company and .Net is pervasive enough that it'll be around for years. Dead-end because it's limited, dead-end because it's rare or dead-end because it's an MS product?
OOP isn't the end of it though; it's no silver bullet. Still if you can desribed OO co-variance you're doing better than anyone I've ever interviewed.
And if they released new versions every year they'd be damned for perpetuating a constant upgrade path.
No problem here, surely. Bloke caught for doing something wrong. Large organisation protects its IP.
Asserting that code in the public domain might cause security problems is just spin consistent with protecting IP. It's PR and would anyone here expect anything different. Might not be convincing but MS wants its code to itself, sees it as IP and wants to keep control over it. How is this different to any other organisation? Deride MS for being closed but if it acts consistently, where's the problem?
Wasn't there a war recently where the justification didn't really appear to reflect reality? Unless this guy is some kind of freedom fighter then where's the issue?
C++ is evolving via committee, so its growth tends to be both slow and seemingly ridiculously complex.
OT: So's Wikipedia but there it's apparently a good thing...
Will the detail be in the dupe?
Two things: firstly, the honours are political for the government (which decides them) not the Queen. Secondly, if we didn't have a monarch here in the UK we'd still need a head of state. I, for one, would prefer the current situation over the possibility of President Blair (*shivers*).
As for VB it's not that bad, surely. Anything can be taught badly and teaching C# or Java and then OO in terms of how the language uses it rather than how general OO is and how the language happens to implement stuff would be bad too.
I wouldn't advocate it but there would be some advances (I'm not necessarily trolling here): it's a reasonable introduction to event based programming. Pre-dotnet syntax is a little inelegant (DIM is an anachronism at best). I'd agree it's not ideal because you'll start learning the IDE rather than the language.
And in real-life it had its uses. I was involved in a quick two-week project in VB to create a simple management reporting tool because the Java developers quoted six months worth of effort for the same functionality. This isn't dissing Java but sometimes some developers cannot see the wood for the trees. Yes, they'd have an MVC based architecture with lots of abstraction but the VB version was very simple and maintainable. As the saying goes if you just have a hammer, every problem will look like a nail.
Cool - I should had added SmallTalk to my list, which is similar (iteration is object based too). You're right about the two being clones. Will check out RoR as it sounds interesting for this reason (and I imagine a little more popular than SmallTalk at present).
Thank you.
If Java's sold as being free (as in beer, because of the Eclipse IDE), then there's not necessarily an immediate advantage over C#. There's Visual Studio Express editions of VB and C# which are similarly free. (And presumably your Uni will have this and/or the full version.)
What about learn the concepts, and the rest is syntax?
As a C#, Java and VB developer with no exposure to Ruby and/or Rails what's is there conceptually that would be new?
... at least on language merit, which is almost certainly likely to be bias.
Which might prove more useful on a CV (and PHBs don't necessarily care if you can do one you can do any)?
If you learn OO, then Java vs. C# is largely irrelevant. There's some minor syntax differences and a whole host of library issues but nothing that's as important to knowing the underlying concepts.
Which class has more women in it? (Okay, a joke but if the distinction is that slight you may as well use something to decide. And g/more/any/, etc.)
Learn OO and go from there. And if you know enough to understand co-variance then you'll get a job if I interviewed you - lots of people claim to be "OO-experts" but crumble when challenged with anything more demanding that the first few pages of any language book.
And, finally, when looking at books - particular the non-academic language specific ones - go for anything that describes how concept X works, not how language Y implements concept Y. E.g. interface vs. implementation inheritance is a core OO idea. It's not language specific. Java and C# are more similar than they are different. (With apologies to Z-fanboys wanting to suggest either r0x0r, etc.)
Are you new here? Opportunity to take a cheap shot as MS. Taken! Should there ever be a story about a MS employee saving a puppy from drowning they'll be someone here to moan about it.
But that'll make you wrong and them right. Or something.
Firefly and Futurama both get cancelled early.
The X-Files stops four years too late.
So when John Seigenthaler is libelled, the crowd shout: he could edit it to make it correct.
When a Wiki bod edits their own entry it's wrong.
I know this is /. a place where reason comes a distant second to dogma, but sheesh, really. At least having it every which way means you're never wrong, right?
Two computer science students, both male, are talking: CS Student 1: Oh! Guess what happened to me this morning! CS Student 2: What? CS1: I was walking through the park and this woman cycles up to me, stops, removes all her clothes, throws herself to the ground and says: "Take whatever you want" CS2: Gosh! What did you do? CS1: I took her clothes. CS2: Good call - you already have a bicycle, don't you.
When this software is widely available it'll bring joy to husbands everywhere: now we'll know what the wife is thinking.
But perhaps "100% annoyed for no apparent reason" isn't going to be useful information...
Yeah, and my grandmother have never fucking heard of Linux either. That must be shite too.
Try opening a fucking window, take a look around and discover what's going on in the world. Frankly, if you've not heard of the Pixies you've not real interest in alternative music have you.
Opera may be a fine browser, but we already have a really good (and open) thing going on with Firefox.
For some other topics choice is a good thing. But you're implying it's a good thing as long as you choose the same alternative.
If there's any truth here perhaps they want a closed source alternative to FF. Could happen and it'll be free from any perceived downsides to the Mozilla license.
As for intentionally wedging, again this is choice. It's not IE (boo) and FF (yah) and it needn't be. As for why anyone would choose Opera over Firefox: I did. I actually paid for it too. It's small, fast, and as far as I've experienced "just works" (at least the browser; not interested in the mail client, never used it). In some threads about FF you'll have users admitting - gasp - it can be resource intensive and even crash sometimes. There's also a minor plus point in using a minority browser as it receives less attention with respect to exploits. (FF isn't free of these, although, yes, they get fixed quicker than IE, etc.)
Finally, as you say, it's a fine browser. So why not?
You're Mrs. Jameson, my former English teacher, aren't you?
It's possible to parse malformed English quite easily. There's a Steven Pinker book that (Language Instinct) that describes hxw xts pxssxblx tx rxxd wxthxxt vxwxls.
There's certainly lots of pounding but it's a simple rule that's usually applied incorrectly. As for missing apostrophes, it's more a case of adding them where they don't belong.
I just think it's odd that if you make a small technical error around here you'll get picked up on it. Suggest there's a need for reasonable grammar and you're a grammar nazi. What gives?
Anyway, not a criticisms of the editors in particular - but they could proof for this stuff when they check the story's not a dupe. Oh....
And I've no problem with this. Why should I? ;)
On a related subject, there's a story about a newspaper columist who sets a competition. There are a few deliberate grammatical errors in the column and a prize for anyone spotting them all. Lots of entries are received detailing a greater number of unintentional errors.
Anyway, it'd be nice if at least /. editors used "its" correctly. And contributors used paragraphs. And I'd learn to type...
Depends. You might read "it's" as meaning possessive but others will infer that if the author can't handle basic grammar then the content of their expression is somewhat lacking too.
It's not difficult. After all if this is a techical group discussing fairly technical issue with some accuracy a simple grammar rule should be manageable. "its" is possesive; "his" and "hers" do not have apostrophes. "It's" like "don't" is an abbreviation and does.
It can be awkward subject because a pedant is a person who can apply one simple rule more than you can. Using preprepositions at the end of sentences, misusing "which" and "that", etc. follows. However, "it's" versus "its" is trivial. Make an effort guys.
Note: I'm more than open to amusing criticisms of any spelling, grammatical or spelling errors in the above. I'll read replies and try to avoid similar errors in future. Like many here I'm write code every day. I'd hope I'd learn something doing this to improve. Why must basic grammar be something that you leave behind when your basic education finishes?