When you say 'support', what you are thinking is 'help desk'. When we (developers) think about support, we are thinking 'bug fixes' and 'security patches'. When M$ EOLs VB6, a community of developers cannot 'support' it, unless we have the source code so that we can release patches and upgrades. This product does not become like F/OSS in the ways that matter most.
BTW, if the source code were available, then there would also be an opportunity for a support company to spring into existence, who could offer commercial support. Once again, I don't mean 'help desk', I mean someone who can help their customers find quirks/bugs in VB and fix them!
It will be a combination of factors that helped PJ's production be so successful visually. Some factors may include:
- Talented artists.
- Modelling (as you mention). ...
also:
- A very good story, very well written
- A story whith which fans are familiar
- A literary basis which most viewers already know/accept to be 'high quality', no need to convince them of that fact.
Hey, here is a new way for small countries to profit: Sign on to the copyright conventions. Have citizens publish hugh quantities of material, never mind the quality. Then try to extradite foreigners for copyright violations.
A similar way for those countries to use copyright laws to their advantage:
1) Impose draconian measures (like 20 years in prison and a fine equal to five years salary) for copyright infringement.
2) Allow M$, RIAA and other US content publishers to keep charging US-equiv prices for their goods (like 3 years of avg worker salary for a copy of M$ Office).
3) Enforce the laws with gusto.
4) Watch your local artists and software industries earn the majority of your citizens' spending on 'IP', instead of watching cultural and technological mindshare favor foreign products.
5) Watch the local version of 'reasonable' amounts of cash-for-IP stay inside your economy, instead of a small percentage of users sending relatively high amounts of cash outside your borders to the US (while the rest just infringe copyrights). Whether you tax that money or not, you will create a more powerful and vibrant economy for your country.
6) Watch your local companies use OpenSource apps where possible, thus further "empowering" your local software consulting and support companies.
The real question is: have the current American copyright laws passed the 'tipping point' where they a hindering "the Progress of Science and useful Arts"? I believe that this is the case for patent laws, but I am not sure about copyright laws.
Re:Looking at the distribution ...
on
Women Leaving I.T.
·
· Score: 2, Interesting
I don't personally agree with the lack of business orientated programming. Most programming is business orientated. The distinction between software development and hacker development seems a bit vague to me, i'm not even really sure where you are coming from.
Most professional (read paid) programming is business oriented as a goal, but the way in which the software is developed can be white-shirt-and-blue-tie waterfall methodology with weekly TPS reports, or it can be more like, "we are a team of geniuses who grok software development at a deep level, get all of the process out of our way; we have work to do." The latter development style can produce better software or worse software, depending entirely upon the individual competencies of your team members. If your goal is high quality and soonest (rather than most predictable) delivery, and if you have a team that can meet these goals following the second 'methodology', why not exploit that fact?
Other more familiar with Agile Programming than I am have commented that AP (incl XP) is more like the old pre-waterfall style, but with up-front safeguards (such as unit tests) built-in. I can't confirm or deny, but it may be that the style of AP feels 'right' to geekier people, but less geekier programmers (even very good ones) might dislike that mode of working. *If* it is true that women programmers (even very good ones) are on the less geeky side, then maybe that is why they are turning away from development.
This is neither a troll nor flamebait. These are not opinions that I hold dear, just possibilities to consider.
You are all being silly, by neglecting the fact that this is a solar-powered system, not a closed loop. The turkeys eat vegetable matter to produce muscle-mass and crap. The vegetable matter used solar energy for photosynthesis. Turkey offal and turkey crap are both storage media for solar energy.
Yes it is in poor taste, and whoever leaked it should be fired if they can be identified. OTOH, maybe this blog shouldn't be For Internal Use Only. Why shouldn't Intel customers (aka nearly all of us) be reading this stuff? We know about AMD, no surprises there.
You are correct about access to the code, but in my experience there is another factor at work here. It seems that developers who spend a lot of time working with (not even necessarily contributing to) OpenSource software develop superior skills for reading source code.
Maybe it is a kink of who we are (if you are good at reading code, you gravitate toward OpenSource), or more likely, if you have to read a bunch of code to get a project to work in your environment, you become proficient at reading and understanding undocumented code.
Many of my co-workers can program, but without documentation, lots of comments, and a 'project roadmap', they can't figure out what an old function is supposed to do (which is often not what it does!) OTOH, our Linux guys (sorry, they happen to be all guys) can usually glance at a couple of pages of code and make some really good guesses as to: what is going on, the intent of the original programmers, and the skill-level of the original programmers.
It's not stealing from the poor to give to the rich if the tax system is 'progressive' and charges the rich a higher percentage.
This service should be free, because it would be very expensive to charge fees, and require authentication to ensure that only fee-paying customers can use the network. I have seen (sorry, no citation) reports that more than half of the cost of running a long-distance phone company goes toward billing the customers! You have to keep track of who-called-who and when, then you have to collate and print bills, send them out, track payment (and non-payment), etc. Perhaps that is the reason for the popularity of the new all-you-can-eat plans (like mine from Verizon).
Wifi is a service that is difficult to bill for, and more difficult to use if authentication and billing are required. Treat the service like streetlights.
And never underestimate the presence of old-school programmers who are too stubborn to learn anything but C(++), basing their justification on largely unfounded "efficiency" concerns.
And don't underestimate the amount of work that goes into maintaining old systems. When your project has over a million lines of C++ code in your version control system, how much Java do you really want to introduce? How will you tie this new Java code into your project, CORBA? And do you really want to end up with a project that contains 40 different flavor-of-the-month languages? That kind of miasma is why the DoD tried to standardize on Ada.
One argument against your "If you want it, you pay for it." model is that some services are difficult to bill. Think about streetlights; should we make everyone pay 0.1 cents every time they pass a streetlight? Do they get a discount if they have a dork-beam strapped to their forehead? Setting-up password-restricted wifi, and then setting-up a billing department means that a service that could be provided for $1/user/month now costs $10/user/month, plus the hassle of having to sign-up for the service and set-up your laptop with authentication. The 'turn it on and it works model' is much easier. Perhaps this should be a government service, just because it is 'unnecessarily' difficult and expensive for a private company to administer.
Not just freeciv, but did you miss the fact that Loki sold Civilization:Call To Power for Linux before they went belly-up? I still play it on my old SuSE box occasionally.
For one thing, Postgres supports inheritence between tables. Sort of like: CREATE TABLE x INHERITS TABLE y (...) (x will have all of the columns of table y plus whatever other columns you specify). That syntax is probably wrong, because I have never wanted to use that feature. Postgres is a great relational database, however, and I have used it in many mission-critical projects (not life-threatening, just critical to the continued existence of our company) since 1997.
Actually, that is not true. A scientist is often forced to "observe" an event by observing the traces that that event leaves behind (in one sense, every visual observation is only an observation of the light particles 'left behind' after an event).
We can observe changes in skeletons, and genotypical and phenotypical (confirmed by DNA testing) similarites, and their changes over time. We can observe changes in available moisture over time by looking a a cross-section of a tree trunk. We can observe evolutionary changes through the fossil record, and from DNA.
Bzzzz. Wrong! I run three Linux machines at (my workstation, my wife's workstation, and a NAT/DBMS/storage server) and the NAT server is hooked to a RoadRunner cable modem. Many of our members in the Suncoast Linux Users Group also use RoadRunner. In fact, I suspect that Linux users are more likely to have broadband than non-Linux households, because Linux users are more likely to be power users.
No. I am the copyright owner of any line(s) of code that I write, unless I specifically assign those rights to someone else. Contributing code to a GPL'd project does not automatically change the ownership of that code. The GPL does not force anyone to assign their rights, only to grant a license.
For official GNU projects, I think that ownership is required to be assigned to the GNU Foundation, just so that they will have a legal leg to stand on; you can't sue someone for copyright infringement unless you own the 'ip' that was copied.
Slashdot Mirror
BTW, if the source code were available, then there would also be an opportunity for a support company to spring into existence, who could offer commercial support. Once again, I don't mean 'help desk', I mean someone who can help their customers find quirks/bugs in VB and fix them!
How exactly does one do that to a Wyse-50?
It's a bloated, unsecure, expensive, unstable piece of...wait, you don't mean the OS do you?
- Talented artists.
...
- Modelling (as you mention).
also:
- A very good story, very well written
- A story whith which fans are familiar
- A literary basis which most viewers already know/accept to be 'high quality', no need to convince them of that fact.
A similar way for those countries to use copyright laws to their advantage:
1) Impose draconian measures (like 20 years in prison and a fine equal to five years salary) for copyright infringement.
2) Allow M$, RIAA and other US content publishers to keep charging US-equiv prices for their goods (like 3 years of avg worker salary for a copy of M$ Office).
3) Enforce the laws with gusto.
4) Watch your local artists and software industries earn the majority of your citizens' spending on 'IP', instead of watching cultural and technological mindshare favor foreign products.
5) Watch the local version of 'reasonable' amounts of cash-for-IP stay inside your economy, instead of a small percentage of users sending relatively high amounts of cash outside your borders to the US (while the rest just infringe copyrights). Whether you tax that money or not, you will create a more powerful and vibrant economy for your country.
6) Watch your local companies use OpenSource apps where possible, thus further "empowering" your local software consulting and support companies.
The real question is: have the current American copyright laws passed the 'tipping point' where they a hindering "the Progress of Science and useful Arts"? I believe that this is the case for patent laws, but I am not sure about copyright laws.
I don't personally agree with the lack of business orientated programming. Most programming is business orientated. The distinction between software development and hacker development seems a bit vague to me, i'm not even really sure where you are coming from.
Most professional (read paid) programming is business oriented as a goal, but the way in which the software is developed can be white-shirt-and-blue-tie waterfall methodology with weekly TPS reports, or it can be more like, "we are a team of geniuses who grok software development at a deep level, get all of the process out of our way; we have work to do." The latter development style can produce better software or worse software, depending entirely upon the individual competencies of your team members. If your goal is high quality and soonest (rather than most predictable) delivery, and if you have a team that can meet these goals following the second 'methodology', why not exploit that fact?
Other more familiar with Agile Programming than I am have commented that AP (incl XP) is more like the old pre-waterfall style, but with up-front safeguards (such as unit tests) built-in. I can't confirm or deny, but it may be that the style of AP feels 'right' to geekier people, but less geekier programmers (even very good ones) might dislike that mode of working. *If* it is true that women programmers (even very good ones) are on the less geeky side, then maybe that is why they are turning away from development.
This is neither a troll nor flamebait. These are not opinions that I hold dear, just possibilities to consider.
And we'll even criticize your grammar and spelling, so that you don't look like a total idiot when your senator (or their aide) reads your letter.
aka
and wheel even critisize you're grammer and sp so you dnt look like a total ID10T when you're senator (or there aid) reads you're letter
You've actually read a piece of software documentation? Are you sure that you're in the right place? This is /.
You are all being silly, by neglecting the fact that this is a solar-powered system, not a closed loop. The turkeys eat vegetable matter to produce muscle-mass and crap. The vegetable matter used solar energy for photosynthesis. Turkey offal and turkey crap are both storage media for solar energy.
Yes, I recently read "The Cluretrain Manifesto".
Maybe it is a kink of who we are (if you are good at reading code, you gravitate toward OpenSource), or more likely, if you have to read a bunch of code to get a project to work in your environment, you become proficient at reading and understanding undocumented code.
Many of my co-workers can program, but without documentation, lots of comments, and a 'project roadmap', they can't figure out what an old function is supposed to do (which is often not what it does!) OTOH, our Linux guys (sorry, they happen to be all guys) can usually glance at a couple of pages of code and make some really good guesses as to: what is going on, the intent of the original programmers, and the skill-level of the original programmers.
This service should be free, because it would be very expensive to charge fees, and require authentication to ensure that only fee-paying customers can use the network. I have seen (sorry, no citation) reports that more than half of the cost of running a long-distance phone company goes toward billing the customers! You have to keep track of who-called-who and when, then you have to collate and print bills, send them out, track payment (and non-payment), etc. Perhaps that is the reason for the popularity of the new all-you-can-eat plans (like mine from Verizon).
Wifi is a service that is difficult to bill for, and more difficult to use if authentication and billing are required. Treat the service like streetlights.
And don't underestimate the amount of work that goes into maintaining old systems. When your project has over a million lines of C++ code in your version control system, how much Java do you really want to introduce? How will you tie this new Java code into your project, CORBA? And do you really want to end up with a project that contains 40 different flavor-of-the-month languages? That kind of miasma is why the DoD tried to standardize on Ada.
One argument against your "If you want it, you pay for it." model is that some services are difficult to bill. Think about streetlights; should we make everyone pay 0.1 cents every time they pass a streetlight? Do they get a discount if they have a dork-beam strapped to their forehead? Setting-up password-restricted wifi, and then setting-up a billing department means that a service that could be provided for $1/user/month now costs $10/user/month, plus the hassle of having to sign-up for the service and set-up your laptop with authentication. The 'turn it on and it works model' is much easier. Perhaps this should be a government service, just because it is 'unnecessarily' difficult and expensive for a private company to administer.
"No real men use Notepad!"
Forty-two days after Duke Nuke'm Forever hits the shelves.
Not just freeciv, but did you miss the fact that Loki sold Civilization:Call To Power for Linux before they went belly-up? I still play it on my old SuSE box occasionally.
For one thing, Postgres supports inheritence between tables. Sort of like: CREATE TABLE x INHERITS TABLE y (...) (x will have all of the columns of table y plus whatever other columns you specify). That syntax is probably wrong, because I have never wanted to use that feature. Postgres is a great relational database, however, and I have used it in many mission-critical projects (not life-threatening, just critical to the continued existence of our company) since 1997.
Here's an excercise:
* go find an activity that is completely pointless
* create a mythos the gives meaning to the activity
* Profit?
We can observe changes in skeletons, and genotypical and phenotypical (confirmed by DNA testing) similarites, and their changes over time. We can observe changes in available moisture over time by looking a a cross-section of a tree trunk. We can observe evolutionary changes through the fossil record, and from DNA.
Bzzzz. Wrong! I run three Linux machines at (my workstation, my wife's workstation, and a NAT/DBMS/storage server) and the NAT server is hooked to a RoadRunner cable modem. Many of our members in the Suncoast Linux Users Group also use RoadRunner. In fact, I suspect that Linux users are more likely to have broadband than non-Linux households, because Linux users are more likely to be power users.
No. I am the copyright owner of any line(s) of code that I write, unless I specifically assign those rights to someone else. Contributing code to a GPL'd project does not automatically change the ownership of that code. The GPL does not force anyone to assign their rights, only to grant a license.
For official GNU projects, I think that ownership is required to be assigned to the GNU Foundation, just so that they will have a legal leg to stand on; you can't sue someone for copyright infringement unless you own the 'ip' that was copied.