Well, that depends on how you look at it. They will be providing the extra content for a monthly fee, instead of selling expansions, no? So It's the same thing GW is doing, but just collecting the money a little differently.
If someone could be bothered to do monthly content right, I'd be happy. So far, it's mostly been pretty lame. Asheron's Call 2 had a system where they actually had plot each month, and all the new quests related to that plot... It was neat, but I always completed the new stuff in a couple days and was bored for the rest of the month.
Of course, I haven't managed to define 'do it right' either, because if I had, I'd have sold the idea to someone that could make it work.;) And Asheron's Call 1 still has monthly content/storyline updates. But yes, the content usually gets "discovered" too quickly, leaving you somewhat bored for the remainder of the month.
You're absolutely right there. It does only apply to the HTTP protocol, FTP was unaffected (as you can't really send someone to an FTP server to phish up their bank details, right?)
Granted, I do believe that banks do share some responsibility. I think they would be best served to do all of their pages as secure. Therefore minimize the chance for information to be captured. But still I can't solely blame them.
And it isn't to say that IE is without blame either... Lay off the crack. To say that Microsoft is somehow to blame for a bank choosing to not secure their online banking website with SSL is utterly bloody stupid.
Thanks to EOLAS, you HAVE to use Javascript to dynamically embed the and tags or you piss the user off with "Click here to activate and use this control" (applies to MSIE and Opera. Firefox kinda makes rude gestures at EOLAS instead)
Been looking at porn? Porn sites always ask you to "Install this registry file to enable our links to work" (which turns the user:password@host format URLs).
This format of URL for HTTP and HTTPS does NOT work on a stock WinXP SP2 installation. At all. They did not "forget" - it actually cannot be used.
Don't know about Opera, but IE simply wont connect to any URLs in the http://domain/ format. Returns "Invalid Syntax Error". Microsoft just got sick of all the phishers and disabled it within WinInet about 3 years ago.
And you're clearly a moron who can't read - you'll note the reply where I admitted I had not read the exact terms of the CLI's license, which is moronically written and unusable for any real purpose, as I was under the impression it used the Ms-PL which is theoretically GPL compatible. I was wrong, and admitted that.
If you're a representative of the Mono project, I hope the project dies horribly. No wonder people are reluctant to embrace open source if assholes like you are it's proponents. Go screw yourself.
No, I've run into that bug where their compiler had problems with white space characters. Having the editor built in made the problem worse - it would swap out all of the spaces and replace them with tabs, then screw up and tell you spacing was wrong if you let your program get too long. Why they did this for FORTRAN is beyond me. Why their compiler would barf over the issue is even more mysterious. Tabs and spaces are both white space and should be treated the same.
I'm a little curious on this - I don't know any languages where the compiler and editor are the same application - is this Visual Basic (versions 6 and below)? It's the only MS language I know of that actually is built this way. Yes, just this once I will agree that is a bit of an abomination when they do that, because you can't do awesome stuff like Build Scripts, decent debug logging, or anything like that - however I have never seen the C++ compiler, C# compiler, QuickBASIC or VB.NET compiler ever encounter issues with whitespace, and believe your ranting on that is just a bunch of FUD. I wasn't aware they ever built a FORTRAN compiler, so I'll defer to you on that one, much though it pains me.
I see your S key is still broken. Perhaps you should take a look at Newegg or Circuit City for a new keyboard?
Ah, twitter - I figured you'd show up. Can't have anyone say something even REMOTELY Microsoft friendly, can we? Since your opinion is meaningless anyway (see: Slashdot is run by Microsoft conspiracy) I'll expend as little effort as possible to refute your pathetic troll attempt.
// the fucking alpha cpp compiler seems to fuck up the goddam type "LPITEMIDLIST", so to work Visual Studio does not HAVE an Alpha CPP compiler, and never has had one. Visual C++ might have had one once, but that is not Visual Studio.
It's been a long time since I did anything with a MS compiler, but they were all just as buggy as anything else MS has done I fixed your spelling, since you can't seem to find your "S" key. Anyway, I've yet to see an instance of a buggy compiler released by them. Irritatingly hard to use, yes. Buggy, no. In fact, the "doing so fucks the build process" is more likely due a really bad build script rather than compiler, since I've never seen a compiler bug (or ever heard of one, for that matter - except from you)
Apple made the right move when the started using gcc I don't recall Apple ever using Visual Studio. Do you mean for Quicktime?
Hardly. It might increase Visual Studio's exposure, which in the opinion of the vast majority who've used it, is a really good product. It contrasts severely against the mediocrity (or downright crappiness, depending on which camp you occupy) of Windows itself.
I would have to say, I would be extremely pleased if I could hit "Build" in Visual Studio and know that the output works on Linux the same as Windows (with the obvious exception of if I was using System.Runtime.InteropServices functionality - but that could possibly be ported to SO support, no?) without even a recompile.
I wouldn't say Greenpeace is entirely devoid of profit either... I mean, they own SHIPS! Large ones! (Well, if the French stop blowing them up, anyway)
Well, actually, to clarify - our local Greenpeace sect has ships. I don't know whether Greenpeace America does.
Ok, correction to myself again, the CLI isn't released under one of the Open Source compatible licenses - this one has a "no commercial use" clause. Well, THAT sucks.
Still, my point about your attitudes stands.
Ok, I'm only half wrong then. The current release of the CLI is released under a license which is theoretically GPL-compatible (Ms-PL - although it might be amusing seeing how it would work since both have the "viral clause"). I will admit that it always seems to be one major release behind the framework itself (current CLI code release - 2.0. Current Framework release - 3.0)
The fact that you reject contributors just because they've seen the code (hell, it's probably not THAT inspirational) is more telling about your crappy attitudes than Microsoft's. Now I see why people are constantly saying "I hope the Mono project dies".
Nothing. Slashcode adds "rel=nofollow" to every link. This means that Google effectively ignores the link (though I do not believe that was the W3C's intention in creating it)
doubtful, whats to stop the program from forking a process that takes a capture of the actual 'please enter the user/pass' screen, then displaying that and read the keystrokes... A UAC prompt dims the background, creates a secure desktop (the same as the Ctrl+Alt+Del - think of it as a new TTY) and displays the dialog on the secure desktop. Absolutely NO processes can access the secure desktop unless they are running as a service within the LocalSystem context - yes, even to take pictures of. The UAC box is quite impossible to capture keystrokes from as well, because thr user session is not notified of any new keystrokes (well, that and the user session is in suspended animation) - obviously this can be defeated by a keyboard driver, but that's easier said than done.
Just because I disagree with you, does not make me a "troll". You folks seem to forget that.
I may not understand the source, but I can hire a programmer who does to fix it for me. -- example: Would you hire an architect to design you a new-build house and expect the architect to hide the floorplans from you? What would you do if you didn't like architect #1 and wanted to hire a replacement? I have no idea about house architecture (I'm a programmer, not an architect), but I know that if I have the plans I can find another expert in the area. I'm ignoring your example because it's not relevant - you didn't hire Microsoft to make Windows for you - when you hire a company to make you software you'd better damn well get the code! That said, when you buy prepackaged software from a vendor you already have an option if you find a bug - they call this "support", and the vendor provides it free of charge! That said, I think I would agree that open sourcing of any code for a product (not a version of a product) that the vendor can no longer support is the way to go (say I use Quicken, and Intuit goes out of business - I think that the Quicken code should be released unless someone can be found to support it)
I'm a programmer and I've found a really strange bug in this API call - when I pass a NULL pointer and a zero length, it does something really unexpected. Can I (a) just go and check the implementation of the call to see what the problem is, fully understand it and fix it, or work around it. Or (b) have to guess at what is going on inside this binary blob? [Situation (a) happened to me just this week when working with libxml2]. Your argument centres around the majority of users being programmers. This is not the case, and any vendor with APIs worth it's salt will provide developer support free of charge.
If you were presented with two operating systems, identical for what you wanted to do, but one came with source and the other didn't, which would you choose? Would you really choose the closed source one? Why? Closed source is just like DRM -- really bad for you the customer and only good for the one hiding the plans. Well, that depends. I'd probably go with whichever one gets the job done faster, with the best (and fastest) support. Given the attitude of the current Linux community to "outsiders" (especially those wanting support) I'd choose whichever isn't Linux. My Linux-fu is not strong, and I often encounter problems with using it (especially want to know why a decent text editor isn't pre-installed (vi is not an option!), or why the decent one is named differently on different releases (nano vs pico anyone?). It's this sort of thing that would cause me to select anything that isn't Linux).
BTW, Windows could be "source available" without being free of copyright (just as is the case with Linux in fact). Open source is not the same as truly free software.
Could be, but then you've got the whole trust issue. They don't really trust all the unwashed masses with the code (and can you really blame them, considering the sort of attitude they get anytime they do anything, even Good Things?). Really, how could they trust you not to give it away to your friend down the road who didn't buy a copy? Often, the advocates of open source forget that if any competitor can copy a company's code, there's no longer an incentive to innovate at all. Not forgetting that no company would ever bother making software if the profit was $0 because everyone can simply copy the code and share it with friends. It would be wonderful to live in a world where developers make complex software like Linux, BSD, OS X, or Windows just out of fun with no compensation, but the reality is that they have bills to pay and unfortunately the power company doesn't accept payment in Liberation, Love, and Fluffy Bunnies.
I hate replying to myself. Anyways, I'm slightly off here. The CLR is not the open source component, the CLI is. What the difference between the Common Language Runtime and the Common Language Infrastructure is, I don't know.
Well, that's wrong. The CLR was always open source. Licensed under Ms-PL (pretty open source developer friendly, surprisingly) and with a clickwrap contract stating that Microsoft pledges not to sue you for patent infringement (and granting worldwide, non-exclusive, perpetual royalty-free distribution rights) provided you don't sue them or any of their customers, it's one of the most open things they have (remember, if they try to sue you, they would have to use the argument "clickwrap contracts are not valid" - this is not in their best interest to do). I think the Mono devs even used this as a base! It is the framework that hits the Mono devs like a flying brick, because that is not open source.
Will it aid Mono? No, not really. The CLR is what they refer to, which is only the driver behind the Common Type System, Code Access Security model, the MSIL Interpreter and so on. Types, Classes and Namespaces within the framework are just that - framework classes. They aren't part of the CLR.
Slashdot Mirror
Tools > Add-ons > Blocksite > Options > Add > http://goatse.ca/
Man this is getting old.
If someone could be bothered to do monthly content right, I'd be happy. So far, it's mostly been pretty lame. Asheron's Call 2 had a system where they actually had plot each month, and all the new quests related to that plot... It was neat, but I always completed the new stuff in a couple days and was bored for the rest of the month.
Of course, I haven't managed to define 'do it right' either, because if I had, I'd have sold the idea to someone that could make it work.
You're absolutely right there. It does only apply to the HTTP protocol, FTP was unaffected (as you can't really send someone to an FTP server to phish up their bank details, right?)
And it isn't to say that IE is without blame either
Thanks to EOLAS, you HAVE to use Javascript to dynamically embed the and tags or you piss the user off with "Click here to activate and use this control" (applies to MSIE and Opera. Firefox kinda makes rude gestures at EOLAS instead)
Been looking at porn? Porn sites always ask you to "Install this registry file to enable our links to work" (which turns the user:password@host format URLs).
This format of URL for HTTP and HTTPS does NOT work on a stock WinXP SP2 installation. At all. They did not "forget" - it actually cannot be used.
Speaking of drugs... which have you been using? If you'd even read the damn SUMMARY you'd know that it's F-Secure pitching this idea.
I'm sure that they coincidentally are busy building SRS and DNS systems.
I meant http://user:password@domain/ format. Damn you SlashCode.
Don't know about Opera, but IE simply wont connect to any URLs in the http://domain/ format. Returns "Invalid Syntax Error". Microsoft just got sick of all the phishers and disabled it within WinInet about 3 years ago.
It's for support. MS intends to offer support services to the Dell SuSE customers, rather than Novell.
And you're clearly a moron who can't read - you'll note the reply where I admitted I had not read the exact terms of the CLI's license, which is moronically written and unusable for any real purpose, as I was under the impression it used the Ms-PL which is theoretically GPL compatible. I was wrong, and admitted that.
If you're a representative of the Mono project, I hope the project dies horribly. No wonder people are reluctant to embrace open source if assholes like you are it's proponents. Go screw yourself.
No, I've run into that bug where their compiler had problems with white space characters. Having the editor built in made the problem worse - it would swap out all of the spaces and replace them with tabs, then screw up and tell you spacing was wrong if you let your program get too long. Why they did this for FORTRAN is beyond me. Why their compiler would barf over the issue is even more mysterious. Tabs and spaces are both white space and should be treated the same.
I'm a little curious on this - I don't know any languages where the compiler and editor are the same application - is this Visual Basic (versions 6 and below)? It's the only MS language I know of that actually is built this way. Yes, just this once I will agree that is a bit of an abomination when they do that, because you can't do awesome stuff like Build Scripts, decent debug logging, or anything like that - however I have never seen the C++ compiler, C# compiler, QuickBASIC or VB.NET compiler ever encounter issues with whitespace, and believe your ranting on that is just a bunch of FUD. I wasn't aware they ever built a FORTRAN compiler, so I'll defer to you on that one, much though it pains me.I see your S key is still broken. Perhaps you should take a look at Newegg or Circuit City for a new keyboard?
// the fucking alpha cpp compiler seems to fuck up the goddam type "LPITEMIDLIST", so to work Visual Studio does not HAVE an Alpha CPP compiler, and never has had one. Visual C++ might have had one once, but that is not Visual Studio. It's been a long time since I did anything with a MS compiler, but they were all just as buggy as anything else MS has done I fixed your spelling, since you can't seem to find your "S" key. Anyway, I've yet to see an instance of a buggy compiler released by them. Irritatingly hard to use, yes. Buggy, no. In fact, the "doing so fucks the build process" is more likely due a really bad build script rather than compiler, since I've never seen a compiler bug (or ever heard of one, for that matter - except from you) Apple made the right move when the started using gcc I don't recall Apple ever using Visual Studio. Do you mean for Quicktime?Hardly. It might increase Visual Studio's exposure, which in the opinion of the vast majority who've used it, is a really good product. It contrasts severely against the mediocrity (or downright crappiness, depending on which camp you occupy) of Windows itself.
I would have to say, I would be extremely pleased if I could hit "Build" in Visual Studio and know that the output works on Linux the same as Windows (with the obvious exception of if I was using System.Runtime.InteropServices functionality - but that could possibly be ported to SO support, no?) without even a recompile.
I wouldn't say Greenpeace is entirely devoid of profit either... I mean, they own SHIPS! Large ones! (Well, if the French stop blowing them up, anyway)
Well, actually, to clarify - our local Greenpeace sect has ships. I don't know whether Greenpeace America does.
You are currently posting on Jobsdot. (I think Slashjobs sounds a bit like a "hardcore geek/nerd recruitment agency")
Ok, correction to myself again, the CLI isn't released under one of the Open Source compatible licenses - this one has a "no commercial use" clause. Well, THAT sucks. Still, my point about your attitudes stands.
Ok, I'm only half wrong then. The current release of the CLI is released under a license which is theoretically GPL-compatible (Ms-PL - although it might be amusing seeing how it would work since both have the "viral clause"). I will admit that it always seems to be one major release behind the framework itself (current CLI code release - 2.0. Current Framework release - 3.0)
The fact that you reject contributors just because they've seen the code (hell, it's probably not THAT inspirational) is more telling about your crappy attitudes than Microsoft's. Now I see why people are constantly saying "I hope the Mono project dies".
Nothing. Slashcode adds "rel=nofollow" to every link. This means that Google effectively ignores the link (though I do not believe that was the W3C's intention in creating it)
Just because I disagree with you, does not make me a "troll". You folks seem to forget that. I may not understand the source, but I can hire a programmer who does to fix it for me.OK, feeding the troll but here are a few:
-- example: Would you hire an architect to design you a new-build house and expect the architect to hide the floorplans from you? What would you do if you didn't like architect #1 and wanted to hire a replacement?
I have no idea about house architecture (I'm a programmer, not an architect), but I know that if I
have the plans I can find another expert in the area. I'm ignoring your example because it's not relevant - you didn't hire Microsoft to make Windows for you - when you hire a company to make you software you'd better damn well get the code! That said, when you buy prepackaged software from a vendor you already have an option if you find a bug - they call this "support", and the vendor provides it free of charge! That said, I think I would agree that open sourcing of any code for a product (not a version of a product) that the vendor can no longer support is the way to go (say I use Quicken, and Intuit goes out of business - I think that the Quicken code should be released unless someone can be found to support it) I'm a programmer and I've found a really strange bug in this API call - when I pass
a NULL pointer and a zero length, it does something really unexpected. Can I (a) just go and
check the implementation of the call to see what the problem is, fully understand it and fix it, or work around it.
Or (b) have to guess at what is going on inside this binary blob? [Situation (a) happened to me just this week when
working with libxml2]. Your argument centres around the majority of users being programmers. This is not the case, and any vendor with APIs worth it's salt will provide developer support free of charge. If you were presented with two operating systems, identical for what you wanted to do,
but one came with source and the other didn't, which would you choose? Would you really
choose the closed source one? Why? Closed source is just like DRM -- really bad for you the
customer and only good for the one hiding the plans. Well, that depends. I'd probably go with whichever one gets the job done faster, with the best (and fastest) support. Given the attitude of the current Linux community to "outsiders" (especially those wanting support) I'd choose whichever isn't Linux. My Linux-fu is not strong, and I often encounter problems with using it (especially want to know why a decent text editor isn't pre-installed (vi is not an option!), or why the decent one is named differently on different releases (nano vs pico anyone?). It's this sort of thing that would cause me to select anything that isn't Linux).
Could be, but then you've got the whole trust issue. They don't really trust all the unwashed masses with the code (and can you really blame them, considering the sort of attitude they get anytime they do anything, even Good Things?). Really, how could they trust you not to give it away to your friend down the road who didn't buy a copy? Often, the advocates of open source forget that if any competitor can copy a company's code, there's no longer an incentive to innovate at all. Not forgetting that no company would ever bother making software if the profit was $0 because everyone can simply copy the code and share it with friends. It would be wonderful to live in a world where developers make complex software like Linux, BSD, OS X, or Windows just out of fun with no compensation, but the reality is that they have bills to pay and unfortunately the power company doesn't accept payment in Liberation, Love, and Fluffy Bunnies.BTW, Windows could be "source available" without being free of copyright (just as is the case with Linux in fact).
Open source is not the same as truly free software.
I hate replying to myself. Anyways, I'm slightly off here. The CLR is not the open source component, the CLI is. What the difference between the Common Language Runtime and the Common Language Infrastructure is, I don't know.
Well, that's wrong. The CLR was always open source. Licensed under Ms-PL (pretty open source developer friendly, surprisingly) and with a clickwrap contract stating that Microsoft pledges not to sue you for patent infringement (and granting worldwide, non-exclusive, perpetual royalty-free distribution rights) provided you don't sue them or any of their customers, it's one of the most open things they have (remember, if they try to sue you, they would have to use the argument "clickwrap contracts are not valid" - this is not in their best interest to do). I think the Mono devs even used this as a base! It is the framework that hits the Mono devs like a flying brick, because that is not open source.
Will it aid Mono? No, not really. The CLR is what they refer to, which is only the driver behind the Common Type System, Code Access Security model, the MSIL Interpreter and so on. Types, Classes and Namespaces within the framework are just that - framework classes. They aren't part of the CLR.
So you caught the hint in the last sentence, eh?