Either you have no idea what socialism means, or you're wilfully misusing the term.
The US is presently at the opposite pole from socialism, you'd do better to choose fascism (in the sense of govt being close to corporations) if you wish to exaggerate. Taxes are currently relatively low in the US. I still wouldn't want to live there though, because healthcare and education don't seem to be government priorities (relative to the UK for example). Military spending, in contrast, is at an all time high. Not all government is bad, contrary to received wisdom on this website.
I have yet to see a generic metadata tagger that people actualy liked to use and/or used heavily. So I think that an approach that presents a clean API to let a customized interface present the metadata to the user and the system in ways that make sense to each of them has a lot more value than a lot of key/value pair editing abilities.
Ever used labels in OS 9/OS X ? That's an example of simple meta-data that people use for all kinds of things. The overloading of meta-data in file names is another great example of the current dearth of options. One of my clients in publishing has page no, book no, image name, source, source id, all stuffed into image names, for want of a better option.
In my opinion Apple should get rid of extensions on file names too and just add them again at the boundaries where the system interacts with other file-systems (servers, email etc).
I know some of the clients I work with would jump straight to using custom metadata if they could have it - for labelling files during different stages of production, noting adjustements to images etc etc. In a work setting it would be invaluable. While photoshop supports adding meta-data to image files, having this ability at the system level would be invaluable (not everyone has photoshop).
All this is kind of a moot point though when comparing with Longhorn, as it won't have any kind of meta-data.
This adds up to the toy image _some_ claim the Macs have. Why would someone play around with a serious security bug there for 10 years? Well, a mitigating fact is that it was there for 10 years, but still it's bad to delay a fix because of a game.
Well, apart from the attempt to disclaim responsibility for a statement whilst still presenting it as credible (the '_some_ claim' statement), there's the gratuitous insult aimed at provoking others - 'toy'.
Why bother claiming Macs are toys in a story about an obscure bug? What does a toy mean to you? Ironically one of the most persistent criticisms of Macs is that current games don't play well on them, so they are in fact not very good toys.
Joking apart, although the internet will change the economics of Universities (perhaps more will operate on the model of the Open University in the UK), there will always be a place for qualifications certified by respected authorities in a domain and vetted, well edited, material to go with it.
Those friends of yours running OS X on vintage machines will soon be a thing of the past.
Well, they will still run a recent version of OS X, just not the latest version. Most application vendors are only now considering dropping 10.2 support, let alone 10.3.
Microsoft's numbers for longevity are good just now because their OS is 4 years old. When Longhorn comes out, it won't support machines older than a few years, because of the steep requirements, and then the shoe will be on the other foot as we wait for an update from Apple.
The best way to think of widgets is as applications which use webkit - they can do anything applications can do. If you download a widget it can potentially (via plugins) do anything on your system that an application could.
Weren't security zones a different concept designed to limit use of BROWSER plugins which used active-x and have system access, to ensure that they weren't used from untrusted sites on the internet? That doesn't really have anything to do with widgets - just because they use HTML etc doesn't mean they automatically use the internet or can be triggered from a web-site. You still have to download them.
So the important thing for Apple to emphasise is that people shouldn't download and run widgets from untrusted sources - unfortunately the low bar for entry on them does make it easy for script kiddies to disguise a malicious script as cute dancing cats or whatever. You could say the same about applescript apps though (for example).
Perhaps at some point they're going to have to come up with some kind of widget certification program.
An IDE should not be designed with 'casual users' in mind; it's a very different beast from iPhoto. I wouldn't make excuses for the lack of thought which went into xCode project preferences. They are a crude and confused interface to the command line switches. Preferences are stored in two places at once:
Build Styles Target Info
and it's not clear which to choose when editing a particular preference (until you know the program), unlike most other IDEs which just use targets. Choosing a different build style will require a 'clean target' to actually recompile the sources with the correct options, and this makes the distinction entirely pointless.
I use xCode every day, and there are times when I curse the poor interface. The plethora of menus is most unmac-like as well, all those options need to be organised in sub-menus, or placed in a cleaned up preferences dialog and project prefs/info. There are 14 main menus and 29 submenus hanging off them. The contextual menu for individual items in the Groups and Files list is a hodge-podge of different commands, many of which have nothing to do with the file being clicked on (General Preferences??!?)
Simple things like choosing to edit in an external editor is under 'File Types' in the prefs (took me a little while to find this), and if you choose to use an external editor you have to use 'Open As' in a contextual menu when you want to open in the xCode editor to set breakpoints. (Perhaps I've missed an option here).
The program seems to be me like it does an inadequate job of hiding its inheritance from PB and use of command line tools. Contrary to your assertion, important options are hidden/in two places at once and obscure options are left easily visible. It's also not particularly stable. However it's free and they are improving it and listening to feedback.
yep, just wait till you try copying a 17MB file on that thing for your freelance gig, the AMD system is at least 10/60 of a second faster.
All depends what he needs that machine for doesn't it. What's the software like on that AMD machine?
This is known as a grocer's apostrophe - I thought you might like to know. I did this occasionally till someone reminded me last year, now I try to avoid it : )
I don't think current grammar checkers are at the stage where they should be included in widely used applications. They are far too crude, prone to errors, and encourage false confidence of the form - if the computer thinks it's right, it must be ok. It'd be like including a search function which finds documents some of the time, but not always - it's worse than useless, it's misleading.
However spell-checkers are actually a good tool when used correctly, particularly ones which check as you type (as long as they don't correct as you type), because they encourage you to recognise and correct errors which might otherwise have gone unnoticed.
Maybe consider doing what we in the USA should have done,that is put a limit for XP installations on OEM computers and copies at the store . Make it like only 50% of the market to repair the os market from ILLEGAL monopoly practices.
You know, all they had to do was force MS to reveal the content of all its OEM contracts from now on, and explicitly ban them from any kind of coercion against OEMs who install other programs (ie force them to use the same price for everyone and stick to it, no coercive contracts).
That and ban tying products when selling to large companies.
I just went to have a look at your site and have a few questions.
Did you consider hiring a designer to spend a few hours doing a design for the site? Did you have a look at some of the competitors?
Did you consider using something other than slashcode? Admittedly editors missing in action is the biggest problem here, but the quality of the design/HTML is also a bit of an issue.
It's a fine line that has been hotly debated since the days of Socrates, but there is an important qualitative difference between those who do things that are ultimately "functional" (i.e. produce a product which in some way furthers the aims of survival and reproduction) and those things which are "artistic" (i.e. things which do not further survival or reproduction).
I'm sorry but Art as we define it today was practised as craft for centuries - right up to the 19C or so. Artists whom we esteem today for their creativity and innovation spent a lot of time working for pay - Leonardo, Michelangelo, Durer, Balzac, Dickens etc etc Sometimes the work is the better for it, sometimes worse - it was in no way divorced from the need to sell the art, in fact in many cases you could say it was directly inspired by it.
The concept of Art as unpaid angst is an invention of the Modernists, and not a very helpful one in my opinion.
Just because art is done for money does not make it a sell out; when it is done only for money, it could be called a sell-out, and unlikely to be very interesting (but sometimes is in spite of itself : ).
I wasn't talking about the order in the menu (which is obviously usually just sorted by date), but the order of the stack of locations which is used to navigate with the back/forward buttons.
When you go back and forth it becomes more complicated to know where to insert new locations. Most browsers (including Firefox) take the easy way out and throw away all locations forward of the current location in the stack when the user clicks to go to a new site, so the stack of back options is often only a few locations deep - as compared to the menu which of course grows with the number of locations visited.
Sometimes the most intuitive solution for the user is not the simplest one to program...
Actually, I've just been looking at history for a different kind of program, and was surprised by how counter-intuitive the browser ones are when I examined them. The Safari one doesn't reflect the menu, and removes previous moves when you take a positive action and aren't at the top of the history stack.
An easy solution is to flip the history ahead of the current position and insert it before current when the user chooses a new site.
ie (where '-' is current position and the user has come back to site c from site a)
a b c- d e
when the user clicks on new site f becomes
f- c b a d e
because the user just came to c back through b and a, so to them a and b are behind them now. Rather than starting it again with
f- c
As Safari does. Perhaps there are other orderings that make more sense - it'd be interesting to see how a lot of people use history, and how the current ones frustrate them - you don't have a link for that paper do you?
You can't just make a blind declaration and expect it to apply to all users.
You mean like the grand-parent did?
My point was for the vast majority of people the mac mini is far from obsolete, and doesn't have the built in obsolescence of windows (Viruses and Malware, along with slow-downs and reinstalls).
You sure won't be getting top of the line speed
err, you're talking about a discount computer, just what do you expect?
Punk kid grows up for trained only for war. He is rebelious, resourceful and ruthless as only children can be, and thus groomed for success. Only in the end he realises the grown ups haven't been telling the whole truth - he succeeds on their terms and yet is left with no moral compass.
A perfect counterpoint to The Lord of the flies; this time civilisation is the barbarity.
Go read the novella. You'll probably enjoy it far more than this film when it comes out. I hadn't heard of it before this evening either, but it's a nice way to spend a couple of hours. Of the other stories there Atlantis was interesting - the others I didn't really appreciate.
Sure, if you're lucky, maybe a copyright holder will allow you to publish a derivative work - if they like it, and usually only if they were specifically looking to extend their franchise. If, however, your work is a scathing refutation of the original author's opinions, or a long-dead author's estate is just being contrary, good luck with that. The law is on their side.
You are, deliberately I suspect, confusing commentary with derivative works. It is quite legal to comment on and cite copyright works (up to 10% I believe), what is not legal is to pass off your work as related to that of the original author, or to copy substantial portions of their work. Personally I think this is fair during the lifetime of the author, and it in no way contributes to the death of our culture.
The culture in question (that which is being copied and distributed on the internet en masse) is not particularly inspired or inspiring, which was my original point. If you don't find Hollywood films and pop music inspiring, create something original. Copying files via P2P does not in any way contribute to the vitality of our culture.
It's not any kind of razor, and it's not even attributed to a 'Hanlon'.
I fail to see why you view this vague, consensual, Wikipedia post as authoritative. The three authors cited aren't even pre-Napoleonic anyway (Heinlein,William James (WHO?), Robert J. Hanlon ). Heinlen indeed... I like how they put all of them before Napoleon or Goethe, who seems more plausible.
This quote sums it up (from one of the websites used as authorities)
"I did a search for Hanlon's Razor on the internet and was surprised that no one seems to know the origin. The author was my late friend Robert J. Hanlon of Scranton, Pa. - Joseph E. Bigler joeb43@yahoo.com"
I don't think this is on Wikipedia either:
- La vérité historique est souvent une fable convenue Historical truth is often an accepted fable
People have already done this for free - demonstrating huge file-size savings (translating directly to money for whoever runs this site, anyone there? !?), not to mention making it far easier to change the style of the site, adjust colours etc etc etc. I can't be bothered to dig up a link but there are several sites about it.
I think the point many of the posts complaining about limitations miss is that such a strategy would be aimed at people who aren't geeks.
It would be aimed at people who give up on their computer (and the data on it) because it gets a virus and they have no idea what's wrong, so they just buy a new one. People who use webmail all the time, who have a hard time finding their other documents as they can't remember where they saved them, and have a shaky grasp of concepts like directories and applications. An awful lot of people I know use webmail, even though they know in principle that it would be better to have their data in a place they control - it's just more convenient for them.
This kind of person would love a central service with basic WP, email, photo storage, and perhaps a simple spreadsheet accessible through their web brower - no matter where they are.
Southwood's plan is for the US to settle for building a simple 'relay satellite' and to get their glory probe into orbit around Europa so that they can claim all of the credit. Why would NASA want to do all of the hard work and spend all of the money to put an ESA orbiter at Europa??
Well, perhaps they'd be more interested in the science they could do than any perceived 'glory' from being the one who lands a probe.
Does all international co-operation have to be reduced to a squabble over who has the biggest satellite/flag/ball, and who gets to land where?
Perhaps they feel that both space agencies could benefit from the co-operation; Nasa because of lack of money for science missions, and ESA because of Nasa's experience with RTGs. Nasa has after all cancelled the Jimo mission due to lack of funds.
Come on... where is the cry when Apple lifted BSD and never gave Aqua back to it? This is a joke. You can't have it both way. If this company delivers a Mac-on-PC emulator that is 20% better than PearPC it's worth $50. That 20% could include useful things missing from PearPC like a real installer, documentation and support.
Hi Arben, no it's not ok.
PearPC is GPL, which is a very different licence, and Apple have given code back *even though they have no obligation to do so*.
Stop trolling.
PS, to say this junk is worth 50USD is laughable, I wouldn't trust anyone who rips off software in such a hack-handed way and tries to pass it off as his own. I certainly wouldn't run a binary on my computer from this company - wouldn't be surprised if the installer is a vector for spyware/adware and that's where they make their money.
Slashdot Mirror
Today, we're practically a socialist country.
Either you have no idea what socialism means, or you're wilfully misusing the term.
The US is presently at the opposite pole from socialism, you'd do better to choose fascism (in the sense of govt being close to corporations) if you wish to exaggerate. Taxes are currently relatively low in the US. I still wouldn't want to live there though, because healthcare and education don't seem to be government priorities (relative to the UK for example). Military spending, in contrast, is at an all time high. Not all government is bad, contrary to received wisdom on this website.
I have yet to see a generic metadata tagger that people actualy liked to use and/or used heavily. So I think that an approach that presents a clean API to let a customized interface present the metadata to the user and the system in ways that make sense to each of them has a lot more value than a lot of key/value pair editing abilities.
Ever used labels in OS 9/OS X ? That's an example of simple meta-data that people use for all kinds of things. The overloading of meta-data in file names is another great example of the current dearth of options. One of my clients in publishing has page no, book no, image name, source, source id, all stuffed into image names, for want of a better option.
In my opinion Apple should get rid of extensions on file names too and just add them again at the boundaries where the system interacts with other file-systems (servers, email etc).
I know some of the clients I work with would jump straight to using custom metadata if they could have it - for labelling files during different stages of production, noting adjustements to images etc etc. In a work setting it would be invaluable. While photoshop supports adding meta-data to image files, having this ability at the system level would be invaluable (not everyone has photoshop).
All this is kind of a moot point though when comparing with Longhorn, as it won't have any kind of meta-data.
yeah, I know, I read this site because it's written by humble yet well-informed and interesting people, who are careful not to make generalisations.
This adds up to the toy image _some_ claim the Macs have. Why would someone play around with a serious security bug there for 10 years? Well, a mitigating fact is that it was there for 10 years, but still it's bad to delay a fix because of a game.
Well, apart from the attempt to disclaim responsibility for a statement whilst still presenting it as credible (the '_some_ claim' statement), there's the gratuitous insult aimed at provoking others - 'toy'.
Why bother claiming Macs are toys in a story about an obscure bug? What does a toy mean to you? Ironically one of the most persistent criticisms of Macs is that current games don't play well on them, so they are in fact not very good toys.
I lerned evarytin I no on the internets.
Joking apart, although the internet will change the economics of Universities (perhaps more will operate on the model of the Open University in the UK), there will always be a place for qualifications certified by respected authorities in a domain and vetted, well edited, material to go with it.
Those friends of yours running OS X on vintage machines will soon be a thing of the past.
Well, they will still run a recent version of OS X, just not the latest version. Most application vendors are only now considering dropping 10.2 support, let alone 10.3.
Microsoft's numbers for longevity are good just now because their OS is 4 years old. When Longhorn comes out, it won't support machines older than a few years, because of the steep requirements, and then the shoe will be on the other foot as we wait for an update from Apple.
The best way to think of widgets is as applications which use webkit - they can do anything applications can do. If you download a widget it can potentially (via plugins) do anything on your system that an application could.
Weren't security zones a different concept designed to limit use of BROWSER plugins which used active-x and have system access, to ensure that they weren't used from untrusted sites on the internet? That doesn't really have anything to do with widgets - just because they use HTML etc doesn't mean they automatically use the internet or can be triggered from a web-site. You still have to download them.
So the important thing for Apple to emphasise is that people shouldn't download and run widgets from untrusted sources - unfortunately the low bar for entry on them does make it easy for script kiddies to disguise a malicious script as cute dancing cats or whatever. You could say the same about applescript apps though (for example).
Perhaps at some point they're going to have to come up with some kind of widget certification program.
An IDE should not be designed with 'casual users' in mind; it's a very different beast from iPhoto. I wouldn't make excuses for the lack of thought which went into xCode project preferences. They are a crude and confused interface to the command line switches. Preferences are stored in two places at once :
Build Styles
Target Info
and it's not clear which to choose when editing a particular preference (until you know the program), unlike most other IDEs which just use targets. Choosing a different build style will require a 'clean target' to actually recompile the sources with the correct options, and this makes the distinction entirely pointless.
I use xCode every day, and there are times when I curse the poor interface. The plethora of menus is most unmac-like as well, all those options need to be organised in sub-menus, or placed in a cleaned up preferences dialog and project prefs/info. There are 14 main menus and 29 submenus hanging off them. The contextual menu for individual items in the Groups and Files list is a hodge-podge of different commands, many of which have nothing to do with the file being clicked on (General Preferences??!?)
Simple things like choosing to edit in an external editor is under 'File Types' in the prefs (took me a little while to find this), and if you choose to use an external editor you have to use 'Open As' in a contextual menu when you want to open in the xCode editor to set breakpoints. (Perhaps I've missed an option here).
The program seems to be me like it does an inadequate job of hiding its inheritance from PB and use of command line tools. Contrary to your assertion, important options are hidden/in two places at once and obscure options are left easily visible. It's also not particularly stable. However it's free and they are improving it and listening to feedback.
yep, just wait till you try copying a 17MB file on that thing for your freelance gig, the AMD system is at least 10/60 of a second faster. All depends what he needs that machine for doesn't it. What's the software like on that AMD machine?
App's
This is known as a grocer's apostrophe - I thought you might like to know. I did this occasionally till someone reminded me last year, now I try to avoid it : )
I don't think current grammar checkers are at the stage where they should be included in widely used applications. They are far too crude, prone to errors, and encourage false confidence of the form - if the computer thinks it's right, it must be ok. It'd be like including a search function which finds documents some of the time, but not always - it's worse than useless, it's misleading.
However spell-checkers are actually a good tool when used correctly, particularly ones which check as you type (as long as they don't correct as you type), because they encourage you to recognise and correct errors which might otherwise have gone unnoticed.
Maybe consider doing what we in the USA should have done,that is put a limit for XP installations on OEM computers and copies at the store . Make it like only 50% of the market to repair the os market from ILLEGAL monopoly practices.
You know, all they had to do was force MS to reveal the content of all its OEM contracts from now on, and explicitly ban them from any kind of coercion against OEMs who install other programs (ie force them to use the same price for everyone and stick to it, no coercive contracts).
That and ban tying products when selling to large companies.
Hi,
I just went to have a look at your site and have a few questions.
Did you consider hiring a designer to spend a few hours doing a design for the site? Did you have a look at some of the competitors?
Did you consider using something other than slashcode? Admittedly editors missing in action is the biggest problem here, but the quality of the design/HTML is also a bit of an issue.
It's a fine line that has been hotly debated since the days of Socrates, but there is an important qualitative difference between those who do things that are ultimately "functional" (i.e. produce a product which in some way furthers the aims of survival and reproduction) and those things which are "artistic" (i.e. things which do not further survival or reproduction).
I'm sorry but Art as we define it today was practised as craft for centuries - right up to the 19C or so. Artists whom we esteem today for their creativity and innovation spent a lot of time working for pay - Leonardo, Michelangelo, Durer, Balzac, Dickens etc etc Sometimes the work is the better for it, sometimes worse - it was in no way divorced from the need to sell the art, in fact in many cases you could say it was directly inspired by it.
The concept of Art as unpaid angst is an invention of the Modernists, and not a very helpful one in my opinion.
Just because art is done for money does not make it a sell out; when it is done only for money, it could be called a sell-out, and unlikely to be very interesting (but sometimes is in spite of itself : ).
I wasn't talking about the order in the menu (which is obviously usually just sorted by date), but the order of the stack of locations which is used to navigate with the back/forward buttons.
When you go back and forth it becomes more complicated to know where to insert new locations. Most browsers (including Firefox) take the easy way out and throw away all locations forward of the current location in the stack when the user clicks to go to a new site, so the stack of back options is often only a few locations deep - as compared to the menu which of course grows with the number of locations visited.
Sometimes the most intuitive solution for the user is not the simplest one to program...
Actually, I've just been looking at history for a different kind of program, and was surprised by how counter-intuitive the browser ones are when I examined them. The Safari one doesn't reflect the menu, and removes previous moves when you take a positive action and aren't at the top of the history stack.
An easy solution is to flip the history ahead of the current position and insert it before current when the user chooses a new site.
ie (where '-' is current position and the user has come back to site c from site a)
a
b
c-
d
e
when the user clicks on new site f becomes
f-
c
b
a
d
e
because the user just came to c back through b and a, so to them a and b are behind them now.
Rather than starting it again with
f-
c
As Safari does. Perhaps there are other orderings that make more sense - it'd be interesting to see how a lot of people use history, and how the current ones frustrate them - you don't have a link for that paper do you?
You can't just make a blind declaration and expect it to apply to all users.
You mean like the grand-parent did?
My point was for the vast majority of people the mac mini is far from obsolete, and doesn't have the built in obsolescence of windows (Viruses and Malware, along with slow-downs and reinstalls).
You sure won't be getting top of the line speed
err, you're talking about a discount computer, just what do you expect?
The mac mini is obsolete.
Your point of view is obsolete.
Punk kid grows up for trained only for war. He is rebelious, resourceful and ruthless as only children can be, and thus groomed for success. Only in the end he realises the grown ups haven't been telling the whole truth - he succeeds on their terms and yet is left with no moral compass.
A perfect counterpoint to The Lord of the flies; this time civilisation is the barbarity.
Go read the novella. You'll probably enjoy it far more than this film when it comes out. I hadn't heard of it before this evening either, but it's a nice way to spend a couple of hours. Of the other stories there Atlantis was interesting - the others I didn't really appreciate.
Sure, if you're lucky, maybe a copyright holder will allow you to publish a derivative work - if they like it, and usually only if they were specifically looking to extend their franchise. If, however, your work is a scathing refutation of the original author's opinions, or a long-dead author's estate is just being contrary, good luck with that. The law is on their side.
You are, deliberately I suspect, confusing commentary with derivative works. It is quite legal to comment on and cite copyright works (up to 10% I believe), what is not legal is to pass off your work as related to that of the original author, or to copy substantial portions of their work. Personally I think this is fair during the lifetime of the author, and it in no way contributes to the death of our culture.
The culture in question (that which is being copied and distributed on the internet en masse) is not particularly inspired or inspiring, which was my original point. If you don't find Hollywood films and pop music inspiring, create something original. Copying files via P2P does not in any way contribute to the vitality of our culture.
It's not any kind of razor, and it's not even attributed to a 'Hanlon'.
:
I fail to see why you view this vague, consensual, Wikipedia post as authoritative. The three authors cited aren't even pre-Napoleonic anyway (Heinlein,William James (WHO?), Robert J. Hanlon ). Heinlen indeed... I like how they put all of them before Napoleon or Goethe, who seems more plausible.
This quote sums it up (from one of the websites used as authorities)
"I did a search for Hanlon's Razor on the internet and was surprised that no one seems to know the origin. The author was my late friend Robert J. Hanlon of Scranton, Pa. - Joseph E. Bigler joeb43@yahoo.com"
I don't think this is on Wikipedia either
- La vérité historique est souvent une fable convenue
Historical truth is often an accepted fable
We tolerate file sharing and defend those who do it because we know that the alternative is cultural sterility, decay, and evetually extinction.
I'm pretty sure that copying the latest crap from Hollywood/Universal Music is *contributing* to the decline.
; )
PS Extinction is surely hyperbole no?
People have already done this for free - demonstrating huge file-size savings (translating directly to money for whoever runs this site, anyone there? !?), not to mention making it far easier to change the style of the site, adjust colours etc etc etc. I can't be bothered to dig up a link but there are several sites about it.
:
I imagine it's more to do with this
the code base could be such a huge mess
No control. Less space than my home computer. Lame.
I think the point many of the posts complaining about limitations miss is that such a strategy would be aimed at people who aren't geeks.
It would be aimed at people who give up on their computer (and the data on it) because it gets a virus and they have no idea what's wrong, so they just buy a new one. People who use webmail all the time, who have a hard time finding their other documents as they can't remember where they saved them, and have a shaky grasp of concepts like directories and applications. An awful lot of people I know use webmail, even though they know in principle that it would be better to have their data in a place they control - it's just more convenient for them.
This kind of person would love a central service with basic WP, email, photo storage, and perhaps a simple spreadsheet accessible through their web brower - no matter where they are.
Southwood's plan is for the US to settle for building a simple 'relay satellite' and to get their glory probe into orbit around Europa so that they can claim all of the credit.
Why would NASA want to do all of the hard work and spend all of the money to put an ESA orbiter at Europa??
Well, perhaps they'd be more interested in the science they could do than any perceived 'glory' from being the one who lands a probe.
Does all international co-operation have to be reduced to a squabble over who has the biggest satellite/flag/ball, and who gets to land where?
Perhaps they feel that both space agencies could benefit from the co-operation; Nasa because of lack of money for science missions, and ESA because of Nasa's experience with RTGs. Nasa has after all cancelled the Jimo mission due to lack of funds.
Come on ... where is the cry when Apple lifted BSD and never gave Aqua back to it? This is a joke. You can't have it both way. If this company delivers a Mac-on-PC emulator that is 20% better than PearPC it's worth $50. That 20% could include useful things missing from PearPC like a real installer, documentation and support.
Hi Arben, no it's not ok.
PearPC is GPL, which is a very different licence, and Apple have given code back *even though they have no obligation to do so*.
Stop trolling.
PS, to say this junk is worth 50USD is laughable, I wouldn't trust anyone who rips off software in such a hack-handed way and tries to pass it off as his own. I certainly wouldn't run a binary on my computer from this company - wouldn't be surprised if the installer is a vector for spyware/adware and that's where they make their money.