I don't believe you've ever worked in IT. As on-site support, you have only marginally more debugging ability than the support that comes with the OS.
If there's a software problem, IT generally needs to come up with a workaround long before the vendor will deal with it. Having the ability to personally look at the problem, solve it, and throw off a patch for consideration is far superior, since the delay in getting to the vendor's support is usually not worth the time you could've just spent finding a work-around.
To be fair, a work around is probably also less work than a fix, but FOSS means that there are circumstances in which an IT department working with proprietary software would just sweep it under the rug instead fixes the problem once and for all. With proprietary software, you need a really good reason not to sweep it under the rug and get on with your day.
In the short term, sure. But in the long term, you're fine, because BitTorrent was originally engineered as a closed-source application with an open protocol. There are a variety of clients, and you only have interface issues. Yes, I prefer open source, but I think uTorrent is a good example of precisely why it's data communication that's important and not the software doing it.
That said, have you found a good uTorrent replacement? I'm still looking. At the moment I just use transmission, which is suboptimal.
All the user cares about is data. If I can switch from your mail app to my mail app without losing my data, the system is open. However, if the developer has the choice of whatever mail format it wants, it's unlikely that I can transfer my data without issue. Thus, choice for the developer does not equal choice for the user.
I think that may be your problem. I have a desktop with an FX 5600 OC. No, it won't be running anything made in the past 3 years, but it has functioned without complaint for over 5 years now.
Ok, that's not entirely true. When I've had it under load for 5+ hours in the summer my machine will sometimes spontaneously reboot. But I'm frankly amazed it lasts more than 2.
Apple ditched their old OS for BSD because it was a piece of shit. They release the source because if you don't release your proprietary modifications, it only serves to suggest that you're hiding what a disgusting mess your hacks are. That's different from open-sourcing your piece of shit because everyone already uses it.
You don't want to imply that your product is for nerds. That's why T-Mobile's Android phone is just marketed as "T-Mobile 3G, now with Google!"
Linux is increasingly behind the scenes everywhere, because it works well and requires no licensing costs. Google OS is likely to make it mainstream, because that's a name people trust. Linux is a server OS. But only if you call it Linux.
How many admins are on this database, how large is it, and what does it do? Just because the new server is better and stronger and runs the latest and greatest doesn't mean that one guy can easily do the entire migration. My business just got done with a database migration that took 2 years, and this was transitioning from one product to another, both of which were offered by the same company.
Budgeted money for a new system does not automatically equate to budgeted money for an actual migration.
TFS implied that they had wiki-like access to each others' mail, so this scenario is indeed "less bad" from a privacy perspective than unfettered access to in-progress communication. What if I'm ordering something and someone else sees the tracking number, sees when it's delivered, and surreptitiously intercepts the shipment? It takes a lot longer to search a back catalog for something good, and someone is a lot less likely to do such a thing on impulse. (Odds are, these were not incredibly tech savvy nor evil people that got the email.)
It's a colloquialism. Deal with it. Contrary to popular belief, abstract, proper grammar has nothing to do with content or literary value. Now, there are awkward constructions, and there are incorrect usages, but this is a pretty standard colloquialism that in no way obscures the meaning of the text.
This wasn't IT's fault, but in my university CS department, there was a period of about three months during which we had passwordless logon to our department course Wiki, which provided the option to use Perl in place of Wikicode as the source for a page. Said Perl ran with the webserver's username on the server.
As far as I know, nothing bad came of it. The seniors just enjoyed not needing to bother with passwords. (To be clear, we repeatedly notified the professor responsible for the Wiki, who repeatedly said he'd take care of it. After a couple weeks, it just kind of became normal.)
It's more like saying show me 3 guys that own an SUV and I'll show you 3 guys who can't afford a hybrid car. They're different engines, for different tasks.
They might be hoping to position Windows CE for that space. It is, after all, what it's designed for.
Which would actually be pretty nice. ARM would no longer be completely a second class citizen, which can only ease porting in general for those of us using Linux.
And this is what happens to people who serve big photos to Slashdot:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@itrunsonlinux.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request. Apache/2 Server at eeepc.itrunsonlinux.com Port 80
Slashdot Mirror
I don't believe you've ever worked in IT. As on-site support, you have only marginally more debugging ability than the support that comes with the OS.
If there's a software problem, IT generally needs to come up with a workaround long before the vendor will deal with it. Having the ability to personally look at the problem, solve it, and throw off a patch for consideration is far superior, since the delay in getting to the vendor's support is usually not worth the time you could've just spent finding a work-around.
To be fair, a work around is probably also less work than a fix, but FOSS means that there are circumstances in which an IT department working with proprietary software would just sweep it under the rug instead fixes the problem once and for all. With proprietary software, you need a really good reason not to sweep it under the rug and get on with your day.
>The last major vulnerability in this was due to a stupid, stupid flaw in the implementation.
You know as well as the rest of us that there's always a less obvious flaw behind the obviously stupid one.
In the short term, sure. But in the long term, you're fine, because BitTorrent was originally engineered as a closed-source application with an open protocol. There are a variety of clients, and you only have interface issues. Yes, I prefer open source, but I think uTorrent is a good example of precisely why it's data communication that's important and not the software doing it.
That said, have you found a good uTorrent replacement? I'm still looking. At the moment I just use transmission, which is suboptimal.
All the user cares about is data. If I can switch from your mail app to my mail app without losing my data, the system is open. However, if the developer has the choice of whatever mail format it wants, it's unlikely that I can transfer my data without issue. Thus, choice for the developer does not equal choice for the user.
Or Chrome, or Safari, or even Firefox 2 on Windows
>laptop
I think that may be your problem. I have a desktop with an FX 5600 OC. No, it won't be running anything made in the past 3 years, but it has functioned without complaint for over 5 years now.
Ok, that's not entirely true. When I've had it under load for 5+ hours in the summer my machine will sometimes spontaneously reboot. But I'm frankly amazed it lasts more than 2.
Unless ATI's drivers stabilize, Nvidia will always have a market in the high-end gaming market.
He said sub $1000 dollars. That's three times the cost of a a netbook.
And really, what he's asking for is entirely possible if you string together two netbook cpus + a low power high yield graphics card.
And well, we already have StarCraft, so the first is not a request.
The Apple fanboys are out in force, and dear god do they have modpoints.
Apple ditched their old OS for BSD because it was a piece of shit. They release the source because if you don't release your proprietary modifications, it only serves to suggest that you're hiding what a disgusting mess your hacks are. That's different from open-sourcing your piece of shit because everyone already uses it.
You don't want to imply that your product is for nerds. That's why T-Mobile's Android phone is just marketed as "T-Mobile 3G, now with Google!"
Linux is increasingly behind the scenes everywhere, because it works well and requires no licensing costs. Google OS is likely to make it mainstream, because that's a name people trust. Linux is a server OS. But only if you call it Linux.
Actually, it's a lot easier than you think, it's just hard to get them to do anything.
Source or it doesn't work.
How many admins are on this database, how large is it, and what does it do? Just because the new server is better and stronger and runs the latest and greatest doesn't mean that one guy can easily do the entire migration. My business just got done with a database migration that took 2 years, and this was transitioning from one product to another, both of which were offered by the same company.
Budgeted money for a new system does not automatically equate to budgeted money for an actual migration.
Took me a minute to realize you weren't talking about her barrier toward dealing with your inadequacies.
TFS implied that they had wiki-like access to each others' mail, so this scenario is indeed "less bad" from a privacy perspective than unfettered access to in-progress communication. What if I'm ordering something and someone else sees the tracking number, sees when it's delivered, and surreptitiously intercepts the shipment? It takes a lot longer to search a back catalog for something good, and someone is a lot less likely to do such a thing on impulse. (Odds are, these were not incredibly tech savvy nor evil people that got the email.)
It's a colloquialism. Deal with it. Contrary to popular belief, abstract, proper grammar has nothing to do with content or literary value. Now, there are awkward constructions, and there are incorrect usages, but this is a pretty standard colloquialism that in no way obscures the meaning of the text.
50 is 7410 in computer years.
(Assuming the universe began in 4000 B.C.)
Or lack thereof.
This wasn't IT's fault, but in my university CS department, there was a period of about three months during which we had passwordless logon to our department course Wiki, which provided the option to use Perl in place of Wikicode as the source for a page. Said Perl ran with the webserver's username on the server.
As far as I know, nothing bad came of it. The seniors just enjoyed not needing to bother with passwords. (To be clear, we repeatedly notified the professor responsible for the Wiki, who repeatedly said he'd take care of it. After a couple weeks, it just kind of became normal.)
Coincidentally, that's exactly why Microsoft has the least secure operating system on the planet.
50000 LoCs
Humans are also afraid of dead human. The interesting thing here is that bugs have a universal death scent.
However, bugs evolve very quickly, and I imagine that some will develop an immunity to this fairly quickly if we do any sort of widespread deployment.
It's more like saying show me 3 guys that own an SUV and I'll show you 3 guys who can't afford a hybrid car. They're different engines, for different tasks.
They might be hoping to position Windows CE for that space. It is, after all, what it's designed for.
Which would actually be pretty nice. ARM would no longer be completely a second class citizen, which can only ease porting in general for those of us using Linux.
And this is what happens to people who serve big photos to Slashdot: