"If you've played the alpha and it rocks, and you're sure that it will rock when it comes out... how exactly is it vaporware?"..... again RTFM
"As in previous years, software locked in the pre-release, beta-testing stage is considered vaporware, even if it's widely available. It hasn't shipped until it's shrink-wrapped."
if it counts for.NET server... it counts for Doom III
and with the paragraph preceeding the one I quoted... sounds like Doom III should be in the top ten.
"As in previous years, software locked in the pre-release, beta-testing stage is considered vaporware, even if it's widely available. It hasn't shipped until it's shrink-wrapped."
Strattelites are supposed to be 7.5 to 13 miles in the sky with a range of 5-10 miles (all the different press releases aren't so clear)... or about (root sum of the squares) 9-18 miles from the strat to the most distant point.
phased-array only gets you 9 __KM__, or under 7 miles
As a former Sanswire/Tsunami customer I have personal reservations as to their ability to pull it off.
They're having enough trouble with the merger maintaining services (down for 3 weeks, won't be up until the new year) and making stupid decisions (like disabing outgoing SSH at a university!!!!!).
Incidently my Software Engineering instructor (who introduced me to Brooks and the horrors of real world development), worked on a few of those projects.
pursuit of models and methodologies is a diminshing-returns game. Have a model. Have a methodology. Stick to it. But never mistake this means for an end unto itself
I doubt Brooks would have said it any differently.
According to Brooks Good and Fast never happen together. If you think they can be accomplished at the expense of cost (by perhaps adding more programmers), then you haven't read "The Mythical Man Month" (the book which spawned the TINSB chapter). On the other hand it may be possible to find or train programmers good enough to accomplish "good" and hopefully "fast".
The answer is finish that degree and hope your institution teaches you enough about these principles: effective design, KISS, machine states, and proper error handling.
After a few years in the field I've found that these, paired with knowledge of a language and it's libraries is as close as you are going to get (although I'm still working on perfecting the second one)
nope, not news... how about something at least 5 years old? like making a tactile-transducer to strap to your lay-z-boy, make those quake/ut2k3 rockets really hit http://www.hometheaterhifi.com/volume_4_2/tac tile. html
or my current fav design (for no particular reason, other than it looks cool), the passive reflex enclosure http://www.diysubwoofers.org/prd/
From their comments, they should review Debian.;->
I don't think they even understand the differing phillosophies between Windows and Linux distros...
ALL BINARY BASED DISTROS WILL HAVE DEPENDANCY PROBLEMS FOR ONE SIMPLE FACT: There is (almost) NO amount of quality control or procedures that will allow 3rd parties to blindly submit packages (esp library packages).
This is complicated by the fact that binary-only commercial products often ship as RPM, but without enough release & quality control because Linux is a second-class citizen in the developer's world.
Debian avoids these problems by: 1) accepting packages to be maintained in the proper format by their developers, who can compile and link against the correct libraries and avoid dependency problems... and 2) by including many many more libraries in the standard distribution than any RPM based distro.
Never the less, Debian testing & unstable experience dependancy problems. Unless you run unstable and don't update for a few months you won't (to my experience) have an unresolvable dependancy.
Mac OS X's framework structure makes it much easier to maintain and link against multiple libraries. Their application configuration phillosophy (no registry, no dll's.. hmm NetInfoManager might be breaking that) and new tools (xml/dtd based configuration) prevent many other installation & maintinance problems.
Windows has only begun to avoid the old "DLL hell" (i.e. dependancy problems) that have existed for ages. When you uninstall a Windows program have you uninstalled all of the DLL's that came with it, or did you risk a missing dependancy? When you install a new application have you ever found that an old one doesn't work? Was it a DLL or a registry or an application extension problem? All of these are dependency conflicts.
Windows XP's rollback features promise to solve some of the DLL hell at the cost of disk space & complexity. Other standardizations (MSFT's ODBC api's, DirectX, Driver Certification) have avoided many dependancy conflicts, but some problems (file extension mapping, registry brokenness, broken links, uninstall leftovers) have existed for so long that developers simply work their way around them instead of developing new standards as gnu/linux tends to do (for example, package managers themselves, the menu and alternatives systems).
Slashdot Mirror
my comment was purely based on your interpretation of "vaporware" which sadly contradicted the article
your argument for the actual release date has merrit, however Doom 3 is still highly anticipated and could be included in the lineup
helll yeah
"If you've played the alpha and it rocks, and you're sure that it will rock when it comes out... how exactly is it vaporware?" ..... again RTFM
.NET server... it counts for Doom III
"As in previous years, software locked in the pre-release, beta-testing stage is considered vaporware, even if it's widely available. It hasn't shipped until it's shrink-wrapped."
if it counts for
and with the paragraph preceeding the one I quoted... sounds like Doom III should be in the top ten.
RTFM
"As in previous years, software locked in the pre-release, beta-testing stage is considered vaporware, even if it's widely available. It hasn't shipped until it's shrink-wrapped."
not enough... do the math
Strattelites are supposed to be 7.5 to 13 miles in the sky with a range of 5-10 miles (all the different press releases aren't so clear)... or about (root sum of the squares) 9-18 miles from the strat to the most distant point.
phased-array only gets you 9 __KM__, or under 7 miles
That, plus Sanswire has a bad reputation to overcome.
sanswire is going down the tubes too AFAIK... (I dropped their service like a bad habbit)
you can witness them losing customers as we speak
As a former Sanswire/Tsunami customer I have personal reservations as to their ability to pull it off.
They're having enough trouble with the merger maintaining services (down for 3 weeks, won't be up until the new year) and making stupid decisions (like disabing outgoing SSH at a university!!!!!).
Witness the carnage here: at their support forum
right link this time
link
google to the rescue
4 69 15&cid=4818984
http://interviews.slashdot.org/comments.pl?sid=
in addition every software system inside such an aircraft is tripply (or more) redundant
Incidently my Software Engineering instructor (who introduced me to Brooks and the horrors of real world development), worked on a few of those projects.
I doubt Brooks would have said it any differently.
According to Brooks Good and Fast never happen together. If you think they can be accomplished at the expense of cost (by perhaps adding more programmers), then you haven't read "The Mythical Man Month" (the book which spawned the TINSB chapter). On the other hand it may be possible to find or train programmers good enough to accomplish "good" and hopefully "fast".
The answer is finish that degree and hope your institution teaches you enough about these principles: effective design, KISS, machine states, and proper error handling.
After a few years in the field I've found that these, paired with knowledge of a language and it's libraries is as close as you are going to get (although I'm still working on perfecting the second one)
The confusion being "Zoo York" was destined to be in a yet uncompleted CD of Requiem remixes.
Absolutely!
WSU's cs460 (and 360) use Minix in an introduction to programming operating systems.
how about... "Wicked City"
...if they keep the rape and bludgeoning of small deformed children
I wonder if they can get Mr Miagi to play the spazzed-out scientist?
crazy, there are however a few account placed in Seattle that my firends and I have never been able to find a published account of.
didn't you know? the darwins are nearly all fabricated...
a guy with weather baloons in a lawnchair? nope, I don't think so.
> You might also think about filing a complaint with the FBI that the guy knowingly filed a false accusation.
If you want to work in any area where your records go under much scrutiny (some fields in the millitary, security, etc...) this is a good idea.
nope, not news... how about something at least 5 years old? like making a tactile-transducer to strap to your lay-z-boy, make those quake/ut2k3 rockets really hitc tile. html
http://www.hometheaterhifi.com/volume_4_2/ta
or my current fav design (for no particular reason, other than it looks cool), the passive reflex enclosure
http://www.diysubwoofers.org/prd/
From their comments, they should review Debian. ;->
I don't think they even understand the differing phillosophies between Windows and Linux distros...
ALL BINARY BASED DISTROS WILL HAVE DEPENDANCY PROBLEMS FOR ONE SIMPLE FACT:
There is (almost) NO amount of quality control or procedures that will allow 3rd parties to blindly submit packages (esp library packages).
This is complicated by the fact that binary-only commercial products often ship as RPM, but without enough release & quality control because Linux is a second-class citizen in the developer's world.
Debian avoids these problems by: 1) accepting packages to be maintained in the proper format by their developers, who can compile and link against the correct libraries and avoid dependency problems... and 2) by including many many more libraries in the standard distribution than any RPM based distro.
Never the less, Debian testing & unstable experience dependancy problems. Unless you run unstable and don't update for a few months you won't (to my experience) have an unresolvable dependancy.
Mac OS X's framework structure makes it much easier to maintain and link against multiple libraries. Their application configuration phillosophy (no registry, no dll's.. hmm NetInfoManager might be breaking that) and new tools (xml/dtd based configuration) prevent many other installation & maintinance problems.
Windows has only begun to avoid the old "DLL hell" (i.e. dependancy problems) that have existed for ages. When you uninstall a Windows program have you uninstalled all of the DLL's that came with it, or did you risk a missing dependancy? When you install a new application have you ever found that an old one doesn't work? Was it a DLL or a registry or an application extension problem? All of these are dependency conflicts.
Windows XP's rollback features promise to solve some of the DLL hell at the cost of disk space & complexity. Other standardizations (MSFT's ODBC api's, DirectX, Driver Certification) have avoided many dependancy conflicts, but some problems (file extension mapping, registry brokenness, broken links, uninstall leftovers) have existed for so long that developers simply work their way around them instead of developing new standards as gnu/linux tends to do (for example, package managers themselves, the menu and alternatives systems).
good luck with that dynamic lighting
ok, this is lame moderation... don't waste your points on me, mod up the parent or move on to a new story
roger dodger, people browsing at +2 won't see it...
since I'm not mod today I can't mod it up