Reread his/her/its post very carefully. (S)He/It wasn't saying that developers shouldn't take pride in their work, (s)he/it was saying that software can rarely do the same amount of harm to people as a car can.
As far as Therac-25 goes, some software already is regulated because that kind of software would have greater consequences in terms of physical harm. I don't think anyone here would disagree that much medical software or other software in such high risk areas needs to be regulated due to their application.
I could not find anywhere within his/her/its post anything on whether developers should not take pride in their work. (S)He/It was simply making an analogy.
Let's not forget that Sony is one of the biggest movie producers around. I'm sure that they'll jump right on putting their movies into this Nintendo format.
Their reasoning for closing the source code is rather weak, IMO. If they didn't want to manage the code coming from other people, they didn't have to, and just say that they weren't accepting outside contributions.
I would have had more respect for the project if they kept it closed source from the beginning.
of course _someone_ will be able to make it better? but does that _someone_ really care too? or would they rather invest their time somewhere else, possibly in something they need? of course if you start a project that is needed by _all_ you'll get lots of help and the project will be successful. it's just finding that problem.
That isn't the point, at least not for the grandparent post. It's a learning experience for him. So what if someone doesn't improve it? As long as someone does, anyone, and it does not matter who, he still learns from the improvement.
There do seem to be some improvements listed. Foremost appears to be the ability to view a scaled version of the desktops in full screen instead of just the little icons in the pager. For instance, with 4 virtual desktops, they describe a scaled view where each desktop is essentially 1/4 of the screen. If you have two browser windows open in two different desktops, such a view would enable you to visually determine which is which. I don't remember seeing such a feature in other VWMs. They also describe animating the transition between this view and the full desktops via shrinking/expanding the active desktop. Sure, real new.
The point that I was trying to make was that it's not replacing X because X is inherently flawed, but rather that it is using a new architecture to implement new ideas that would be difficult to implement within the framework and mindset of X.
Have the higher-ups in the military gone insane? It seems to me that they are searching for the biological equivalent of Zero Point Energy.
It's all just a completely ridiculous idea, to me.
The best that they can do would be to pack all the nutrients they would need into as small of a package as they can or suppress regular biological urges, but that's not healthy, especially for someone who may be undergoing intense physical activity for five days straight.
Would you people please stop seeing this project as a X replacement (by which I mean that it is yet another X implementation, much like the freedesktop.org implementation)? By taking simple cursory glance at the website, I've easily determined that the relationship between X and Y is more like the relationship between *nix and Plan 9. This is an evolution of the graphical subsystem on *nix, not a replacement for X. It frees itself from the limitations of the architecture and mindset of X to take advantage of new hardware and ideas for graphical interfaces.
My kids always ask if they can watch me play zelda. It's too hard for them so they like to just sit and watch. I dunno what I'm gonna do when wind waker is over
That's a little ironic, considering Nintendo's supposed "reputation." After playing Windwaker, I can't see any kid being able to play the game and not be constantly frustrated. It's a very tough game that requires more motor skills and hand-eye coordination than most kids are able to muster.
That said, I absolutely love the game. It's not as great as Ocarina of Time (which is the best Zelda game ever), but it's definitely up there.
Competition is good for the software industry, good for Microsoft in particular (as Adam Smith pointed out, monopoly is a great enemy to good management), and most importantly, good for consumers. It is great for everyone when the open-source movement provides credible competition. At times, however, I do wish that all that passion, energy and skill went into something, well, a bit more
useful.
What does he define as useful? I can say, with certainty, that Mono was created for very practical and useful reasons.
He's wrong. What shouldn't be done is a rewrite while abandoning the old code. Rewrites should be done every so often so that the experience from the old code can be put into a new architecture, but the old code should be continued to be maintained until the new code is production-ready.
Slashdot Mirror
Where was it inferred that this was supposed to be easier? This is meant for musical typesetting, and, as was mentioned, is not a score editor.
Makes me wish I were still an egg within my mother's body!
Yup, and the jewel case was last seen in the back of my closet, at the bottom of my laundry.
Lindows? No, no, no, it's Lin---s now! It's Lin--..., *sigh*, never mind...
Reread his/her/its post very carefully. (S)He/It wasn't saying that developers shouldn't take pride in their work, (s)he/it was saying that software can rarely do the same amount of harm to people as a car can.
As far as Therac-25 goes, some software already is regulated because that kind of software would have greater consequences in terms of physical harm. I don't think anyone here would disagree that much medical software or other software in such high risk areas needs to be regulated due to their application.
I could not find anywhere within his/her/its post anything on whether developers should not take pride in their work. (S)He/It was simply making an analogy.
Let's not forget that Sony is one of the biggest movie producers around. I'm sure that they'll jump right on putting their movies into this Nintendo format.
Their reasoning for closing the source code is rather weak, IMO. If they didn't want to manage the code coming from other people, they didn't have to, and just say that they weren't accepting outside contributions.
I would have had more respect for the project if they kept it closed source from the beginning.
I thought that was a bit of a low estimate.
d4 g4n95+3r 1337 933k5 b3 pu77!|\|' 0n 73}{ 5m4<k d0w|\|!!!!!!!!!!!!!!!!!!!!!
Yeah, I was like, "Alright! Linux has finally caught up with Windows! W00t!"
of course _someone_ will be able to make it better? but does that _someone_ really care too? or would they rather invest their time somewhere else, possibly in something they need? of course if you start a project that is needed by _all_ you'll get lots of help and the project will be successful. it's just finding that problem.
That isn't the point, at least not for the grandparent post. It's a learning experience for him. So what if someone doesn't improve it? As long as someone does, anyone, and it does not matter who, he still learns from the improvement.
There do seem to be some improvements listed. Foremost appears to be the ability to view a scaled version of the desktops in full screen instead of just the little icons in the pager. For instance, with 4 virtual desktops, they describe a scaled view where each desktop is essentially 1/4 of the screen. If you have two browser windows open in two different desktops, such a view would enable you to visually determine which is which. I don't remember seeing such a feature in other VWMs. They also describe animating the transition between this view and the full desktops via shrinking/expanding the active desktop.
Sure, real new.
Oh, and I don't want to burn my lap.
Heh, yeah, that's for sure...
Will one of the lasers start carving "friends" into rocks on earth and be called MPU?!
(think Cowboy Bebop)
I thought you mentioned Janet Reno for some reason...now I'm greatly disturbed.
Yeah!!!! Free shrimp!!!!!!!!!!!!!!!!!!!!!!
(damn lameness filter)
The point that I was trying to make was that it's not replacing X because X is inherently flawed, but rather that it is using a new architecture to implement new ideas that would be difficult to implement within the framework and mindset of X.
Have the higher-ups in the military gone insane? It seems to me that they are searching for the biological equivalent of Zero Point Energy.
It's all just a completely ridiculous idea, to me.
The best that they can do would be to pack all the nutrients they would need into as small of a package as they can or suppress regular biological urges, but that's not healthy, especially for someone who may be undergoing intense physical activity for five days straight.
Would you people please stop seeing this project as a X replacement (by which I mean that it is yet another X implementation, much like the freedesktop.org implementation)? By taking simple cursory glance at the website, I've easily determined that the relationship between X and Y is more like the relationship between *nix and Plan 9. This is an evolution of the graphical subsystem on *nix, not a replacement for X. It frees itself from the limitations of the architecture and mindset of X to take advantage of new hardware and ideas for graphical interfaces.
That's a little ironic, considering Nintendo's supposed "reputation." After playing Windwaker, I can't see any kid being able to play the game and not be constantly frustrated. It's a very tough game that requires more motor skills and hand-eye coordination than most kids are able to muster.
That said, I absolutely love the game. It's not as great as Ocarina of Time (which is the best Zelda game ever), but it's definitely up there.
It's definitely important that the POS not be a POS.
What does he define as useful? I can say, with certainty, that Mono was created for very practical and useful reasons.
He's wrong. What shouldn't be done is a rewrite while abandoning the old code. Rewrites should be done every so often so that the experience from the old code can be put into a new architecture, but the old code should be continued to be maintained until the new code is production-ready.
G**-F&$!ING-DAMN! Every good name out there is taking, almost. I propose the name Hbleghtek. I'm fairly certain that one isn't used.