3.5.10 is going to be released in August. How does that equate to disappearing?
Listen, I'm running KDE 4.0 on Kubuntu (alongside 3.5) and I don't think there's anything seriously wrong with it. That was surprising to me given all the "unusable FUD" I've been reading about the last 6 months.
The WIFI switch on my backup Acer laptop (Aspire 5610) miraculously started to work when I updated to KUbuntu 8.04 a few weeks ago. Shove it to the left, a little (bright red) LED goes on and a few seconds later the wireless networks show up under the KNetworkManager icon in the taskbar. It even connects too, imagine that. So I guess there is hope, even for these awful switches.
The mass of such an anti-hydrogen particle must be pretty low. As such, it could perhaps be influenced by the container it's flying through, some unknown property, the previous of the next particle in the series, etc. I think there is always room for doubt in these experiments.
Mmm, suppose I have an old piece of open source software that is no longer supported. I *still* could hire someone to figure out the problem, contact one of the original developers, etc. These options are typically not available in closed source software and are hardly theoretical.
In fact I know companies that keep their own validated copies of popular open source software pieces and maintain those themselves. Only the fixes they like go in. More and more companies are learning to work with open source and are learning to see the possibilities.
Personally I have seen entire companies being swallowed up by the likes of Computer Associates (Platinum for example) only for the (closed source) software never to be seen again a year after. The impact for companies (like the one I worked for that used Platinum) is not to be underestimated.
However you want to put it: the risk is simply lower with open source.
I actually RTFA and this device is obviously not remarkable because of the storage size. It's remarkable because of the transfer speed and the number of transactions/operations per second. I can see how this device can be considered dirt cheap by people that are looking for a solution in that last area.
Isn't that from the Blake's 7 episode where the liberator is being consumed by some sort of fungus? That must have been one of the cooler episodes. Hope it makes it into the remake: http://www.theregister.co.uk/2008/04/24/blakes_seven/
Obviously I have to disagree. Google and the host of thin client applications that are available to users on the desktop are changing the game, slowly but certainly. You can't simply draw a technical line between thin and fat clients. People value and use both types of applications.
The changeover to open source happening on the desktop seems slow, and with the market monopoly of Microsoft that slowness is to be expected. However, I think that there are clear signs that things are changing. One of the key differences in 10 years is IMHO exactly the fact that an application doesn't really have to run on your desktop as a fat client, but can live happily inside your browser.
Another evolution is that cross platform development is becoming easier all the time, even on the desktop and that more and more development is being done on Linux machines (such as myself on my laptop). That makes me very hopeful for the future.
Google ring a bell? (large MySQL user, GWT,...) Youtube, flickr et all? I have a theory that these companies probably wouldn't have been created if it weren't for open source software. It simply would have been too expensive to do so.
By the way, those articles are one big rant without too much proof.
You know, Digital Restrictions Management is not about hardware, nor software, not even content. It's about restricting users to do exactly what the content providing industry wants you to do by allowing you to see what they want you to see and to let you listen to what they want you to listen to. There ought to be a law against it.
In conclusion, as far as I'm concerned : the entire industry.
In the line of work I'm usually in, data warehousing, we have large data loading jobs that want to load say 100M rows of data. For one thing, you usually can't do that in one transaction. To get over that problem you slam commits in between. You basically don't care if the commits work immediately or not. What you care about is whether or not the 100M rows of data end up in the target table.
As such, the question then becomes: when am I going to be certain that the data is written to disk? Obviously not when I do the commit. Is everything synchronized when I close the connection? Is there some "sync" command I can issue like in the "sync ; sync ; sync ; reboot" days on Linux?
I could imagine this being useful during one-off big-*ssed database loads, but other than that, I have to go with stoolpigeon : use with caution.
Oh, now it's a user error, right? Blaming it on the users is so 1980 "mate".
That type-ahead "feature" is probably the most annoying type-ahead I've ever come in contact with. Sure, it's fine if you have one or two files around. If not, it's a nightmare. I pray every time that type-ahead is disabled. You see, for some reason it works in some situations and doesn't in others. I don't have time to look in the code to see why it wouldn't work in some situations.
The main problem with it is that you don't know when it will auto-complete and when it will not. Suppose you want to go to/usr/lib, right? For me, it's probably faster to type/usr/lib and be done with it, but if I did, I would end up with/usr/sr/lib or some other bastardized variation of the real filename. (remember: you can't tell when it's enabled or not!) Also, it's not proposing an option, it enforcing an option. That means I have to wait for it to pop up the only possible option after each character I type... really... carefully. I don't know how many options there are, so in a lot of cases it's a lot slower than just typing in the frigging filename.
Aaaaaarghhh!!!!!!!!!!! Time to call my shrink again, thanks a lot.
I wish it was as simple as running away from it. I use Eclipse and SWT for Java development. Because Eclipse uses SWT and SWT uses GTK+ to bind to, that piss poor dialog trolls all over the place in many, many SWT based applications. The trick with FF is nice (and I applied it immediately on my Kubuntu box) but there are unfortunately other apps out there...
Man, how do I hate that dialog. I'm getting all worked up just thinking about it. Shees.
My pet peeve: you type in a filename, say "foo-bar.txt" and you hit enter. ANY sane dialog would close and accept this as being the same as hitting the OK button. Well, in 95% of the cases it doesn't. In 5% of the cases (when you browsed around or something, can't figure it out exactly) it actually closes and accepts the filename.
That dialog has "amateurs" written all over it. Here's some advice Gnome fan-boys: get that dialog right before you do anything else. It matters.
Not only that, but IMHO the numbers are meaningless to Linux itself. Linux got started with only a few people. Now that it has millions of users and thousands upon thousands of people contribute to the various distributions, critical mass has been reached. The reasons why people use Linux and/or contribute to it probably vary a lot. However, I'm sure marketing or perceived market share has little to do with it.
Sometimes you just have to roll the dice. You will probably take a lot of heat for it. There will be bugs, there will be criticism and Anonymous Cowards spouting vitriol on Slashdot. That's just the way things go.
In a year from now, nobody will remember all that and I'm sure everyone will blow smoke up your ass for how well things have turned out to be and how visionary you were. Keep up the good work Aaron.
Slashdot Mirror
Eminem is dead, he's locked in my basement! (Ha-ha!)
It's open source. You should not ask : "what can KDE do for me?" You should ask: "What can I do for KDE".
Obviously, in your case, that's less than nothing.
3.5.10 is going to be released in August. How does that equate to disappearing?
Listen, I'm running KDE 4.0 on Kubuntu (alongside 3.5) and I don't think there's anything seriously wrong with it. That was surprising to me given all the "unusable FUD" I've been reading about the last 6 months.
...
5. Handles codepages very well
6. Supports Unicode
7. Handles codepages very well
8. Supports Unicode
9. Handles codepages very well
and did I mention this one?
10. Supports Unicode
Thank you for the kind reminder to use "were" in stead of "where". That being said, I don't think anything was wrong with the spelling itself.
Kittens and bunnies were not mentioned I believe.
Intel 3945 abg /var/log/messages:
If you hit the switch you get a line in
iwl3945: Radio Frequency Kill Switch is On: Kill switch must be turned off for wireless networking to work.
HTH,
Matt
The WIFI switch on my backup Acer laptop (Aspire 5610) miraculously started to work when I updated to KUbuntu 8.04 a few weeks ago.
Shove it to the left, a little (bright red) LED goes on and a few seconds later the wireless networks show up under the KNetworkManager icon in the taskbar.
It even connects too, imagine that. So I guess there is hope, even for these awful switches.
The mass of such an anti-hydrogen particle must be pretty low. As such, it could perhaps be influenced by the container it's flying through, some unknown property, the previous of the next particle in the series, etc.
I think there is always room for doubt in these experiments.
Mmm, suppose I have an old piece of open source software that is no longer supported.
I *still* could hire someone to figure out the problem, contact one of the original developers, etc.
These options are typically not available in closed source software and are hardly theoretical.
In fact I know companies that keep their own validated copies of popular open source software pieces and maintain those themselves.
Only the fixes they like go in. More and more companies are learning to work with open source and are learning to see the possibilities.
Personally I have seen entire companies being swallowed up by the likes of Computer Associates (Platinum for example) only for the (closed source) software never to be seen again a year after.
The impact for companies (like the one I worked for that used Platinum) is not to be underestimated.
However you want to put it: the risk is simply lower with open source.
I actually RTFA and this device is obviously not remarkable because of the storage size. It's remarkable because of the transfer speed and the number of transactions/operations per second.
I can see how this device can be considered dirt cheap by people that are looking for a solution in that last area.
Look at it this way: if the slashdot crowd had any say in it, he would have been gone long ago :-)
Isn't that from the Blake's 7 episode where the liberator is being consumed by some sort of fungus?
That must have been one of the cooler episodes.
Hope it makes it into the remake: http://www.theregister.co.uk/2008/04/24/blakes_seven/
No, it's because Java is a strongly typed language and as such suitable for enterprise work.
Obviously I have to disagree. Google and the host of thin client applications that are available to users on the desktop are changing the game, slowly but certainly. You can't simply draw a technical line between thin and fat clients. People value and use both types of applications.
The changeover to open source happening on the desktop seems slow, and with the market monopoly of Microsoft that slowness is to be expected. However, I think that there are clear signs that things are changing. One of the key differences in 10 years is IMHO exactly the fact that an application doesn't really have to run on your desktop as a fat client, but can live happily inside your browser.
Another evolution is that cross platform development is becoming easier all the time, even on the desktop and that more and more development is being done on Linux machines (such as myself on my laptop). That makes me very hopeful for the future.
Matt
Google ring a bell? (large MySQL user, GWT, ...)
Youtube, flickr et all? I have a theory that these companies probably wouldn't have been created if it weren't for open source software.
It simply would have been too expensive to do so.
A lot of end-users indeed.
What makes it more reasonable?
The fact that everyone in the same geographical area does it together I guess.
IBM seems to be doing just fine it seems.
By the way, those articles are one big rant without too much proof.
You know, Digital Restrictions Management is not about hardware, nor software, not even content. It's about restricting users to do exactly what the content providing industry wants you to do by allowing you to see what they want you to see and to let you listen to what they want you to listen to. There ought to be a law against it.
In conclusion, as far as I'm concerned : the entire industry.
In the line of work I'm usually in, data warehousing, we have large data loading jobs that want to load say 100M rows of data.
For one thing, you usually can't do that in one transaction. To get over that problem you slam commits in between.
You basically don't care if the commits work immediately or not. What you care about is whether or not the 100M rows of data end up in the target table.
As such, the question then becomes: when am I going to be certain that the data is written to disk? Obviously not when I do the commit. Is everything synchronized when I close the connection?
Is there some "sync" command I can issue like in the "sync ; sync ; sync ; reboot" days on Linux?
I could imagine this being useful during one-off big-*ssed database loads, but other than that, I have to go with stoolpigeon : use with caution.
Matt
Oh, now it's a user error, right? Blaming it on the users is so 1980 "mate".
/usr/lib, right? /usr/lib and be done with it, but if I did, I would end up with /usr/sr/lib or some other bastardized variation of the real filename. (remember: you can't tell when it's enabled or not!)
That type-ahead "feature" is probably the most annoying type-ahead I've ever come in contact with.
Sure, it's fine if you have one or two files around. If not, it's a nightmare. I pray every time that type-ahead is disabled.
You see, for some reason it works in some situations and doesn't in others. I don't have time to look in the code to see why it wouldn't work in some situations.
The main problem with it is that you don't know when it will auto-complete and when it will not. Suppose you want to go to
For me, it's probably faster to type
Also, it's not proposing an option, it enforcing an option. That means I have to wait for it to pop up the only possible option after each character I type... really... carefully. I don't know how many options there are, so in a lot of cases it's a lot slower than just typing in the frigging filename.
Aaaaaarghhh!!!!!!!!!!! Time to call my shrink again, thanks a lot.
Matt
I wish it was as simple as running away from it.
I use Eclipse and SWT for Java development. Because Eclipse uses SWT and SWT uses GTK+ to bind to, that piss poor dialog trolls all over the place in many, many SWT based applications.
The trick with FF is nice (and I applied it immediately on my Kubuntu box) but there are unfortunately other apps out there...
Man, how do I hate that dialog. I'm getting all worked up just thinking about it. Shees.
My pet peeve: you type in a filename, say "foo-bar.txt" and you hit enter. ANY sane dialog would close and accept this as being the same as hitting the OK button.
Well, in 95% of the cases it doesn't. In 5% of the cases (when you browsed around or something, can't figure it out exactly) it actually closes and accepts the filename.
That dialog has "amateurs" written all over it. Here's some advice Gnome fan-boys: get that dialog right before you do anything else. It matters.
Matt
Not only that, but IMHO the numbers are meaningless to Linux itself.
Linux got started with only a few people. Now that it has millions of users and thousands upon thousands of people contribute to the various distributions, critical mass has been reached.
The reasons why people use Linux and/or contribute to it probably vary a lot. However, I'm sure marketing or perceived market share has little to do with it.
To prockcore's defense, the topic of today is Unix on the desktop. "GUI layers" have everything to do with that.
Sometimes you just have to roll the dice. You will probably take a lot of heat for it. There will be bugs, there will be criticism and Anonymous Cowards spouting vitriol on Slashdot. That's just the way things go.
In a year from now, nobody will remember all that and I'm sure everyone will blow smoke up your ass for how well things have turned out to be and how visionary you were. Keep up the good work Aaron.
Matt