I think the cost of getting photoshop to run under wine might be higher than the cost of porting it to Linux directly.
The Linux "API" (if that's the appropriate name) is well documented and understood. On the other hand, you can think of Wine as being an incomplete implementation of Win32 with a higher percentage of unknown bugs than the real thing.
Unfortunately as is the case in closed source, there's no guarantee that a user's bug will be fixed or that a user's feature request will be implemented just because the code is open source. I don't think there's much evidence that users do any better in this area with open source than they do with closed.
The problem with your theory is that if it were true the companies would first make their low-ball offer to the developer with the most experience hoping to get a bargain, but in practice this doesn't happen.
Look at the number of leaders or managers vs. the number of developers. Clearly the majority of young developers aren't going to "grow up" to be leaders because there isn't room for them.
The handwriting is on the wall - being a developer isn't a viable long-term career. When you're thirty start to plan your new career so you'll be ready before the trap-door opens.
I don't get all this talk about COBOL with respect to developers in their 40's or 50's. Most developers in that age group worked on PCs or embedded systems, not mainframes.
"Any comments by you have to be taken in context of all of your shill astro-turfesque previous comments made over the years you have been on this site."
No, they actually don't have to be. I wouldn't judge your current post in the context of past postings even if you weren't hiding behind the AC identity.
I used Joe Sixpack in the title, so I made it very clear that I wasn't talking about people who build sophisticated web sites. Most users haven't even created a simple HTML page and never will.
I'm responding to the claim that ordinary users can better help find bugs with open source. I didn't claim that nobody can help better with the source.
"The boomers need to retire and pass the baton to a new generation of computists."
Perhaps I can pass this along at the next boomer geek meeting.
Seriously, geeks in my age group have a lot of diversity of opinion and we aren't all thread-happy. As far as retirement goes, I'd Dig it as long as you Cats bring me enough Bread.
You're generally correct, but I see some problems. First the issues of open vs. closed shouldn't be confined to OS's. Second, vulnerabilities are only one class of bugs. Third, looking at applications that have a long history may distort the evaluation.
Slashdot Mirror
I think the cost of getting photoshop to run under wine might be higher than the cost of porting it to Linux directly.
The Linux "API" (if that's the appropriate name) is well documented and understood. On the other hand, you can think of Wine as being an incomplete implementation of Win32 with a higher percentage of unknown bugs than the real thing.
"The desire to find what you're looking for."
The problem is that "what you're looking for" varies from person to person when using the same search terms.
Unfortunately as is the case in closed source, there's no guarantee that a user's bug will be fixed or that a user's feature request will be implemented just because the code is open source. I don't think there's much evidence that users do any better in this area with open source than they do with closed.
You missed my point. Wine isn't what it's supposed to be if you can't run all Win32 apps under it without special code.
Probably because the rate of features being added hasn't slowed down but the rate of processor performance increases has slowed significantly.
The fact that there's any need for Adobe to support Wine says more about Wine than Adobe.
So you stopped programming professionally at 30 but you don't believe older programmers are "pushed out" based on your personal experience?
I've been in the industry for over 20 years and I've never encountered a developer in all that time who hasn't "learned anything new in 20 years".
I think many of the comments are from people in the US (myself included). It may be quite different in Holland.
They won't offer the older developer a job at any price.
Well, I don't think it's really age related, there are mistakes at every age. Look how dogmatic some people can be about Agile methods.
Anyone who uses both criteria A and B is a fool. You'll just end up with the random guy who guessed your number.
The problem with your theory is that if it were true the companies would first make their low-ball offer to the developer with the most experience hoping to get a bargain, but in practice this doesn't happen.
I think it's more accurate to say that programming is a dying art being replaced by software integration.
Look at the number of leaders or managers vs. the number of developers. Clearly the majority of young developers aren't going to "grow up" to be leaders because there isn't room for them.
The handwriting is on the wall - being a developer isn't a viable long-term career. When you're thirty start to plan your new career so you'll be ready before the trap-door opens.
"Therefore, there is no reason for experienced IT workers to continue to have a conventional job."
Things like eating seem to be good reasons to me.
I don't get all this talk about COBOL with respect to developers in their 40's or 50's. Most developers in that age group worked on PCs or embedded systems, not mainframes.
My point is that a majority of users aren't going to find source code helpful in reporting bugs. Do you disagree?
As I've tried to make clear, there are people who would benefit from the source, they're just a minority.
"It's about how your end users can interact with the software engineers."
So these "end users" you speak of have special characteristics such that they can't be referred to as "Ordinary" or "Typical"?
I think it's obvious that I was referring to non-programmers and so were you.
"So your point is that people who never use a particular piece of software aren't much help in fixing bugs?"
Nope.
"Any comments by you have to be taken in context of all of your shill astro-turfesque previous comments made over the years you have been on this site."
No, they actually don't have to be. I wouldn't judge your current post in the context of past postings even if you weren't hiding behind the AC identity.
I used Joe Sixpack in the title, so I made it very clear that I wasn't talking about people who build sophisticated web sites. Most users haven't even created a simple HTML page and never will.
I'm responding to the claim that ordinary users can better help find bugs with open source. I didn't claim that nobody can help better with the source.
"The boomers need to retire and pass the baton to a new generation of computists."
Perhaps I can pass this along at the next boomer geek meeting.
Seriously, geeks in my age group have a lot of diversity of opinion and we aren't all thread-happy. As far as retirement goes, I'd Dig it as long as you Cats bring me enough Bread.
You're generally correct, but I see some problems. First the issues of open vs. closed shouldn't be confined to OS's. Second, vulnerabilities are only one class of bugs. Third, looking at applications that have a long history may distort the evaluation.