Remember, moderators, it's a troll if it's slightly funny and you didn't think of it first:)
Re:It is the Palm killer. Here's why:
on
Pocket PC 2002
·
· Score: 1
So, how does a guy who absolutely hates Windows, and runs Linux on everything, make use of Windows CE development tools? Run them under Wine?
Not to mention that his complaint is completely orthogonal to his platform, since you can run Linux on your iPaQ. Not running Linux on your iPaQ because you couldn't develop for PalmOS for free doesn't make any sense at all; why be spiteful at Linux for Palm's problems?
So either I think you've left out a crucial detail, or your former co-worker was a few sardines short of a tin...
Fair enough, and I'll admit that the interoperation isn't there between the two. Although in most cases the actual office suites will support embedding provided you use a homogenous office suite - all OpenOffice, or all Koffice.
As far as the look, well, I guess it doesn't bother me that much. I imagine you could track down themes for one that would make it look pretty much like the other, although I don't know for sure. It still doesn't mean you can't use the Gimp along with KDE2, though, just that the look may be a little jarring.
``With the virus attacks of late and the numbers of those and how vicious those
attacks have been... it's incumbent on Microsoft, being in the leadership position
we're in, to help drive forward the industry in this area,'' Brian Valentine, senior vice president of the Windows Division
at Microsoft, said in an interview.
I would think that Microsoft would want to get out of their leadership position in enabling virus attacks and making them so painful, but I guess that's why I'm not President of the Windows Division. I don't think the industry wants to be driven too much further down that path, though - alternate web serving platforms are more like where Microsoft is driving their customers.
``We can't just sit back and think about Microsoft,'' said Valentine, who is leading Microsoft's new security task force.
You know you can use GIMP under KDE, and KDE apps under Gnome, right? It's amazing how many people don't. Yes, you need to install both sets of libraries. No, it isn't the end of the world to do so.
Devil's Advocate time: "copyright enforcement" is one of the services that record companies sell to their artists - it's part of the package deal that you get when you sign your soul on the dotted line. True, you essentially gift the song to the record company, and so their enforcement tactics have a lot of self-interest associated with it, but that's the contract.
If artists don't want the RIAA handling enforcement for them, they can always stay independent, and perhaps even encourage P2P networks to carry their tunes. Of course, the RIAA has been very successful about shutting down those P2P networks and destroying this distribution path for independent musicians, but on the other hand the large majority of P2P music sharers were searching for music they'd already heard of, not looking for new music that they might like. So P2P mp3 swapping wasn't necessarily generating a lot of exposure for new independent bands, or at least only marginally more so than just having a band web site. That doesn't make the RIAA any less a bunch of greedy monopolistic bastards, it just means that their victory is a lot less of one than they think.
Well, in some respects technical communication is a little different than just general teamwork.
At my school we did have a generic "communications" class, but it was pretty worthless. It was more about "giving a presentation/talk effectively" rather than "how to work with a team towards an objective". Most colleges do end up teaching teamwork to most people, but only as a side effect of having to work on teams for other direct educational objectives. Which is why people can still come straight out of school and have no idea how to work in a team.
Of course you could get along without teams in the Real World. The point is that management will rarely choose that course, so you're destined to work in a team whether you like the idea or not. Thus, you should learn to work with a team.
One of the previous comments had it exactly right: first you teach the actual concepts of programming, then you teach people to use them in a team. The two skillsets are disjoint and (for most people) equally important.
You're right that teams in college aren't used to decrease the workload per person or to increase the time to market. Teams in college are used to teach people what teams in the real world will be like, and that is a very valuable lesson.
I had a number of team projects in school, but unfortunately most of them did not teach the team skills that I now use at work. Most projects were small (2-3 person) teams, fairly limited in scope, with a clearly-defined direction from the course instructors. These projects were easy to resurrect if one person didn't pull their weight, and usually became mostly the work of the person with the strongest personality on the team.
In contrast, most "real world" teams that I work on are large (up to 10 people), require the direction and many of the major decisions to be decided by the members of the team rather than imposed from outside, and require a lot of finesse to reconcile the opposing viewpoints of the many opinionated people on the team. A lot more of the work goes into deciding how to decide what things will get done, because once you're out of school, the question of how to do things is mostly a known factor (based on corporate-provided development process and the abilities of the developers). The workload of this larger team is enough that one person couldn't carry it alone (well, without putting in 100-hour weeks, which was fun when you were 20 but maybe not now) and even if one person had the ability to do so, the rest of the team wouldn't take kindly to being left out of the loop.
I did have one class that focused on large-team development and real-world problems like this, and I probably learned the most from it as I did from any course (thanks Prof. Mowle!). But looking back, we probably should have had several courses like that, and in fact most of the last year of school should have been focused on team-driven development projects like that. Colleges are kidding themselves if they think they can grade students on their separate work, when in real life they'll spend the majority of their time building on the work of others. Grading on team projects can be done reliably - for example, we had weekly status reports for each developer to make sure that you were keeping involved, part of your grade was based on your peers' estimation of how useful you were to the team, and the remainder of your grade came from the "management" (instructor's) view of how much you had contributed. Which seems to mirror my real world job pretty reliably, come to think of it.
Bingo. The RIAA really are the last of the old-school monopolies - they haven't realized that once you consider their product as just plain bits, Microsoft has a vested interest in charging for bits, and can certainly take over their disorganized empire with ease.
But if Microsoft doesn't want you to compete with them, they won't let you. So you'd trade the control of a giant, faceless, but ultimately somewhat representationally controlled government for the control of a giant, faceless, and entirely greed-oriented company? I thought most people wanted to move out of the company town...
After two program crashed and relaunched, Ramos moved to a laptop PC and attempted to show Reader 2.0's new ability to provide external links, as to
dictionaries other than Microsoft's own Encarta. However, the program chose that moment to crash again.
...
Perhaps most ominously for Microsoft and its plans for securing media rights,
one questioner stated that Reader 2.0 had already been hacked, opening up Reader-format e-books for copying to more than the allowed four locations.
Ramos denied that Reader had been cracked.
Ironically, by that point most of the audience had left, possibly to attend a panel discussion about the Digital Millennium Copyright Act.
[an error occurred while processing this directive]
That last part worked right in with the overall theme of "crashing, and then crashing again".:) But just imagine the Microsoft Reader error message:
[an error occurred while reading this book. Please close and open the book, then resume the Microsoft Reading eXPerience!]
At least in some cases, the tracks are WMA. So even this level of so-called fair use is not available for non-Windows users. I don't know if the guy being interviewed above is part of the WMA-using company or not.
It's kind of a big, black, analog LaserDisc. But with a mechanical rather than an optical readout. Sometimes they come with a little spotted dog I think...
Good point, and I agree that we're all affected when a worm runs rampant. But no matter how well we create an atmosphere of respect for other people's machines, there will always be that one guy who writes a worm out of boredom, terrorism, or just didn't expect it to get out of hand (the Robert Morris excuse IIRC). So products still have some responsibility to withstand attacks, just the same way that cars have to have some ability to withstand 80 MPH drunk drivers, even though those sorts of collisions aren't really expected operation. No matter how much we criminalize the worm writers, we still have to have a defense and we still should expect that our computer products are at least adequately defended.
Hmmm, perhaps it depends on your connection to the 'net - I don't recall any "Internet is broken" problems at my workplace. Lots of internal panic mails from IT, but nothing affecting the local *nix network or access out through the proxies.
My interpretation of the original post was that it was an internal problem, though - since they mentioned taking down the network in an effort to fix things, which wouldn't have affected the external attack rate but would have decreased the internal infection rate. I suspect it wouldn't take a bevy of admins all kinds of overtime just to block nimda DOS-like effects from the 'net. At least I hope it wouldn't:)
Since the Nimda scanning is supposed to be somewhat random, I can't imagine that blocking would be particularly effective. Maybe you could block remote infected servers that are either massive enough or else have poor random number generators, so that they tend to hit you more often, but I can't imagine this would make much of a dent.
Slashdot Mirror
Remember, moderators, it's a troll if it's slightly funny and you didn't think of it first :)
So, how does a guy who absolutely hates Windows, and runs Linux on everything, make use of Windows CE development tools? Run them under Wine?
Not to mention that his complaint is completely orthogonal to his platform, since you can run Linux on your iPaQ. Not running Linux on your iPaQ because you couldn't develop for PalmOS for free doesn't make any sense at all; why be spiteful at Linux for Palm's problems?
So either I think you've left out a crucial detail, or your former co-worker was a few sardines short of a tin...
Fair enough, and I'll admit that the interoperation isn't there between the two. Although in most cases the actual office suites will support embedding provided you use a homogenous office suite - all OpenOffice, or all Koffice.
As far as the look, well, I guess it doesn't bother me that much. I imagine you could track down themes for one that would make it look pretty much like the other, although I don't know for sure. It still doesn't mean you can't use the Gimp along with KDE2, though, just that the look may be a little jarring.
I would think that Microsoft would want to get out of their leadership position in enabling virus attacks and making them so painful, but I guess that's why I'm not President of the Windows Division. I don't think the industry wants to be driven too much further down that path, though - alternate web serving platforms are more like where Microsoft is driving their customers.
Well, that will be a first.
You know you can use GIMP under KDE, and KDE apps under Gnome, right? It's amazing how many people don't. Yes, you need to install both sets of libraries. No, it isn't the end of the world to do so.
Devil's Advocate time: "copyright enforcement" is one of the services that record companies sell to their artists - it's part of the package deal that you get when you sign your soul on the dotted line. True, you essentially gift the song to the record company, and so their enforcement tactics have a lot of self-interest associated with it, but that's the contract.
If artists don't want the RIAA handling enforcement for them, they can always stay independent, and perhaps even encourage P2P networks to carry their tunes. Of course, the RIAA has been very successful about shutting down those P2P networks and destroying this distribution path for independent musicians, but on the other hand the large majority of P2P music sharers were searching for music they'd already heard of, not looking for new music that they might like. So P2P mp3 swapping wasn't necessarily generating a lot of exposure for new independent bands, or at least only marginally more so than just having a band web site. That doesn't make the RIAA any less a bunch of greedy monopolistic bastards, it just means that their victory is a lot less of one than they think.
Well, in some respects technical communication is a little different than just general teamwork.
At my school we did have a generic "communications" class, but it was pretty worthless. It was more about "giving a presentation/talk effectively" rather than "how to work with a team towards an objective". Most colleges do end up teaching teamwork to most people, but only as a side effect of having to work on teams for other direct educational objectives. Which is why people can still come straight out of school and have no idea how to work in a team.
Of course you could get along without teams in the Real World. The point is that management will rarely choose that course, so you're destined to work in a team whether you like the idea or not. Thus, you should learn to work with a team.
One of the previous comments had it exactly right: first you teach the actual concepts of programming, then you teach people to use them in a team. The two skillsets are disjoint and (for most people) equally important.
You're right that teams in college aren't used to decrease the workload per person or to increase the time to market. Teams in college are used to teach people what teams in the real world will be like, and that is a very valuable lesson.
I had a number of team projects in school, but unfortunately most of them did not teach the team skills that I now use at work. Most projects were small (2-3 person) teams, fairly limited in scope, with a clearly-defined direction from the course instructors. These projects were easy to resurrect if one person didn't pull their weight, and usually became mostly the work of the person with the strongest personality on the team.
In contrast, most "real world" teams that I work on are large (up to 10 people), require the direction and many of the major decisions to be decided by the members of the team rather than imposed from outside, and require a lot of finesse to reconcile the opposing viewpoints of the many opinionated people on the team. A lot more of the work goes into deciding how to decide what things will get done, because once you're out of school, the question of how to do things is mostly a known factor (based on corporate-provided development process and the abilities of the developers). The workload of this larger team is enough that one person couldn't carry it alone (well, without putting in 100-hour weeks, which was fun when you were 20 but maybe not now) and even if one person had the ability to do so, the rest of the team wouldn't take kindly to being left out of the loop.
I did have one class that focused on large-team development and real-world problems like this, and I probably learned the most from it as I did from any course (thanks Prof. Mowle!). But looking back, we probably should have had several courses like that, and in fact most of the last year of school should have been focused on team-driven development projects like that. Colleges are kidding themselves if they think they can grade students on their separate work, when in real life they'll spend the majority of their time building on the work of others. Grading on team projects can be done reliably - for example, we had weekly status reports for each developer to make sure that you were keeping involved, part of your grade was based on your peers' estimation of how useful you were to the team, and the remainder of your grade came from the "management" (instructor's) view of how much you had contributed. Which seems to mirror my real world job pretty reliably, come to think of it.
Sure, but since it's published it's no longer patentable.
Have you considered the possibility that you may just be multiple people sharing a consciousness?
Bingo. The RIAA really are the last of the old-school monopolies - they haven't realized that once you consider their product as just plain bits, Microsoft has a vested interest in charging for bits, and can certainly take over their disorganized empire with ease.
Well, until you upgrade to Microsoft Microphone XP with new DRM Management...
Or maybe just the complete works of Thomas Dolby, but that's all right with some of us :)
Science!
http://slashdot.org/comments.pl?sid=22063&cid=2364 556
Thank you, and please read the article before posting duplicates next time :)
Just because I'm paranoid, Mr. Troll, doesn't mean they're not out to get me :)
From reading the story, same as the rest of us...
I couldn't have summed it up better myself. Although I don't know if #6 has actually been verified to have occurred :)
But if Microsoft doesn't want you to compete with them, they won't let you. So you'd trade the control of a giant, faceless, but ultimately somewhat representationally controlled government for the control of a giant, faceless, and entirely greed-oriented company? I thought most people wanted to move out of the company town...
That last part worked right in with the overall theme of "crashing, and then crashing again". :) But just imagine the Microsoft Reader error message:
See this article: http://news.cnet.com/news/0-1005-201-7320279-0.htm l
At least in some cases, the tracks are WMA. So even this level of so-called fair use is not available for non-Windows users. I don't know if the guy being interviewed above is part of the WMA-using company or not.
It's kind of a big, black, analog LaserDisc. But with a mechanical rather than an optical readout. Sometimes they come with a little spotted dog I think...
Good point, and I agree that we're all affected when a worm runs rampant. But no matter how well we create an atmosphere of respect for other people's machines, there will always be that one guy who writes a worm out of boredom, terrorism, or just didn't expect it to get out of hand (the Robert Morris excuse IIRC). So products still have some responsibility to withstand attacks, just the same way that cars have to have some ability to withstand 80 MPH drunk drivers, even though those sorts of collisions aren't really expected operation. No matter how much we criminalize the worm writers, we still have to have a defense and we still should expect that our computer products are at least adequately defended.
As the saying goes: "HP-UX and AIX are dead, as soon as someone finds a hole deep enough to bury the remains."
Hmmm, perhaps it depends on your connection to the 'net - I don't recall any "Internet is broken" problems at my workplace. Lots of internal panic mails from IT, but nothing affecting the local *nix network or access out through the proxies.
My interpretation of the original post was that it was an internal problem, though - since they mentioned taking down the network in an effort to fix things, which wouldn't have affected the external attack rate but would have decreased the internal infection rate. I suspect it wouldn't take a bevy of admins all kinds of overtime just to block nimda DOS-like effects from the 'net. At least I hope it wouldn't :)
Since the Nimda scanning is supposed to be somewhat random, I can't imagine that blocking would be particularly effective. Maybe you could block remote infected servers that are either massive enough or else have poor random number generators, so that they tend to hit you more often, but I can't imagine this would make much of a dent.