This is really bizarrely popular. I think it's nifty and all, but it has been on literally every news program I've listened to today, from fairly conservative morning talk hosts to All Things Considered. It's popped up on a good chunk of the blogs I've viewed... it's freaking everywhere!
And at the same time, most science stories get squat. (The T. Rex story died out when reporters found out that they weren't cloning dinosaur armies). What the hell?
Programmatic widgets have been part of KDE since the beginning; it was one of the early differences. There are now fancy KDE styles that do gleams when you hover over buttons, window frames that have lava lamp like "liquid" sloshing in them, etc.
X Extensions are fairly new, so the only ones that KDE supports right now are the older ones (that spawned the x.org split). Transparency and the like are done - you can right click on a window and set the transparency with a slider. Of course, you have to have an X that supports it, but reread the first five words of this paragraph before you complain about that.
The newer X features being added are only supported by brand spanking new software, so I'm absolutely sure that in the next several months things will pop up on kde-apps, and if the quality, stability and portability[1] is good enough, it will be added to KDE CVS. Err, KDE Subversion.
[1] Remember that KDE's aim is to be a "Unix Desktop", not a "Linux with X.org/XFree86 Desktop". It runs on all manner of X on all manner of Unix. That means SUSE Linux 9.2, but also SCO with a third party X, OSX with X Windows, etc. Thus eyecandy and extra X features are always optional and fallback gracefully.
If he is correct, then this is the same as running a centrifuge for five minutes and then turning it off and letting it sit overnight versus setting it to turn off in five minutes and then leaving the lab for the night.
Who cares if he turned off the charger after a certain time or if it automatically shut off after a certain time?
It's one/a. I thought about that, and it still boils down to "your account is unresponsive, but you can fix it". Perhaps a new intervening level of "it only affects the one account and/or session, not other accounts and/or sessions" would be good.
Thinking about it after my post, I came up with the following criteria for this test on OSes:
Fail - The OS grinds to a halt and after waiting five minutes, there is no recourse other than cutting power and rebooting.
Pass (one/a) - The OS grinds, but the user can navigate to a feature (console, Control-ESC in KDE, etc) that allows the user to quickly kill the offending process(es).
Pass (one/b) - The OS grinds or not, but regardless automatically kills the offending process. I consider this to be a worse level than the following.
Pass (two) - The OS grinds and automatically offers the user a method to kill the offending process(es). (KDE had something like that at one point. It may still). Sometimes you may want to let it run.
Pass (three) - The OS does not grind and upon approaching resource limits, offers the user an option to shut down the process or let it run.
And finally...
Pass (four) - The OS does not grind and upon approaching resource limits, offers the user an option to increase limits, potentially by moving the process to another machine or allocating more systems to the process. Presumably the migration would be automatic (and transparent) if the resource limits were higher than the local machine.
Obviously, "user" may be a combination of user and admin in certain cases (multi-user machine, accessing other machines off a local cluster, etc).
Under SUSE 9.1 on a 2.8 Ghz laptop, that spikes the load average well past 300 with no problem. X becomes fairly unresponsive (move mouse, wait, arrow leaps), but a console is not so bad. It reaps quite quickly when killed.
I went through the books at Borders as I do every couple months. The "Advanced..." and "Professional..." tend to cover things like how to use the GD image system or how classes work. In other words, very basic language stuff. Many of the "Professional..." with PHP and MySQL cover basic "How to use SQL" topics.
If there's something regarding SQL, I want how to validate serialized objects in a Oracle database, not how to use CREATE TABLE to make a MySQL pricelist. And I really don't care so much about that - I'd rather have something about managing projects with a QA cycle that uses the PHP error logging system. That by itself would help the Dev/QA cycle, but we don't have the budget in time to toss a developer on building an in-house solution. In other words, I want a book about how to deal with real "I use this to put food on my table and pay people" issues.
Quite a bit of game flavor is helped by the "make it up as you go" nature of most games. For my current GURPS Firefly game, we're using this map. It contains the very basic outline of the planet, and could be wrong (after all, the ASA only cares about taxpayers, and settlers spring up anywhere).
Not mapping out towns allows the players to search for creative people and things that would make sense to find, and not be constrained by what I thought up a few weeks earlier. It also allows for wonderful things like incorporating in-references to events and ideas that happened *after* the map was made.
Get off yer low horse fer chreissake. So you're a BEGINNING PROGRAMMER who probably is trying to learn to programme.
Meanwhile, for people who use PHP for a living, there are no books out there. There are dozens of "Learn PHP" books on the shelf at my local Borders (I was literally looking through them *yesterday*), but none for advanced development issues or project management.
Poor you. You have what you need. Damn him for lamenting his lack.
I still maintain that you're not running Wine on the PPC, but rather an emulated layer in between. I will note freely that you can claim it is semantics, but by that logic, Windows itself runs on PPC (try telling Microsoft that).
By that logic, Apple ProDOS and Magic Window run on x86. Which isn't quite true... unless you emulate a 6502 on top of the x86.
Way back in this thread, I said that there are solutions involving Wine, but Wine by itself can't run Windows apps on a PPC. I still maintain that to be true.
(I could also pick at your calling something a "solution" and then saying "most win32 programs do not run at all". But putty is a pretty good example that at least one substantial app is able to run).
The emulation in that setup is qemu. For all intents and purposes, you are running Wine on an Intel processor. A virtual one, to be sure, but you are not running Wine on a PPC.
Nifty trick, though (and a very good example of *nix style "small apps that do their job well and can be chained together"). How well does it perform with more complicated and/or demanding applications?
The profanity is simply unnecessary. I am making an informed statement, but could certainly be wrong. An aggravated emotional response is not required.
That said, a screen shot demonstrates very little in terms of specifics. What software were you using? Wine? A different piece of software based on Wine? Or a different emulator altogether? If it was Wine, was it a copy of putty.exe compiled for x86 Windows?
No. There are side projects and spinoffs, but the project named "Wine" does not run binaries compiled for Windows. You can compile Wine for PPC, and it still cannot run binaries compiled for Windows - they are targeted for x86, and Wine does not translate opcodes.
Okay, for the pedantics in the audience, "Wine does not run apps on a PPC system that were compiled for Windows (which runs in Intel)". Which means that Wine does not work for the poster's stated purpose.
Also for the pedantics: some of the other applications that I mentioned that *do* run Windows binaries on PPC use Wine. But Wine itself can't run a Windows binary, compiled for Windows, on a PPC system.
You can, however, compile Windows apps for PPC against the winelibs - assuming you have the source code for the Windows app.
Which is to say, unless you are king of theoretical phrasing and stretching the definition, it doesn't work.
Wine does not work on a non-intel system. It doesn't handle different opcodes, only a different API. There are solutions for running Windows on PPC, both closed and open source, but Wine is not one of them.
Absolutely. That's why he uses KDE. But he's been using KDE on Linux for a long time. What does changing the hardware have to do with his desktop environment? He's still running the same OS and software...
Hey, I never said it made sense. That's why I said "currently frowned upon".
Personally, I consider a site that returns a special page to search indexers (stripped of navigation words, added context keywords) to be a *good* thing.
That said, I recognize the validity of the opposing view - that it can be abused and/or that the indexing app should see exactly what a user would see.
It's the fact that the title is different when a search engine views it versus when a person views it. Feeding different information to a search engine (with more keywords) is currently frowned upon, as people have abused it.
Check the *title* of the two links. One has a comma separated list of keywords.
See, this is why I think they should have NCIS spin off SFCIS (Star Fleet Criminal Investigative Service) and CSI: Vulcan (Grissom would fit right in... and Adrian Monk on Vulcan would be amusing).
Incidently, there has already been a Star Trek crime "series" that is quite nice. Book, of course... the first (and so far only) is "The Case of the Colonist's Corpse: A Sam Cogley Mystery". Pretty good read; I'd like to see more published (the cover and title hint that more may be planned).
Of course, with the recent success of Harry Potter and Lord of the Rings, I'm surprised there isn't a high fantasy series in the works.
Plus a few more superhero attempts.
It's endlessly debated. I've tried to take an honest look at the statistics and come away with the simple understanding that on certain issues, especially those with such emotionally involved sites, the statistics are useless, as each side has their own equally compelling, completely opposed, and thus utterly useless statistics.
So, in such cases, I reduce it to the basic "what would I do" and "what would I want". I've lived in urban areas where I could hear the automatic weapon fire as I grilled out on my patios. The weapons are already out there to be turned on me, and the people who have them are happy to pull the trigger. I have no love nor hate of guns; I don't own a handgun, and the rifles I have date to when I was a Boy Scout and was target shooting. I am cognizant of the real personal risks associated with them - if you have a gun, you have the chance of accidents happening.
That's the background for how I think. My conclusions are not written in stone, but I think that gun ownership makes a society more safe at both a personal level and allows for a physical empowerment of the people - the ultimate (meaning final) level of democracy.
That said, the fact that there is question about the issue is *exactly* what I mean - they should not be outlawed when there is such a debate over their positive aspects. Rights should be inherent in the people, and selectively removed minimally as possible. There are some fairly clear ones - you shouldn't have the right to walk down the street and drag a random person off and cut their throat. But removing the right to run a certain type of application (versus removing the right to copy somebody's recent work without their permission) is very questionable.
Slashdot Mirror
--
Evan
And at the same time, most science stories get squat. (The T. Rex story died out when reporters found out that they weren't cloning dinosaur armies). What the hell?
--
Evan
Eyecandy
--
Evan
Programmatic widgets have been part of KDE since the beginning; it was one of the early differences. There are now fancy KDE styles that do gleams when you hover over buttons, window frames that have lava lamp like "liquid" sloshing in them, etc.
X Extensions are fairly new, so the only ones that KDE supports right now are the older ones (that spawned the x.org split). Transparency and the like are done - you can right click on a window and set the transparency with a slider. Of course, you have to have an X that supports it, but reread the first five words of this paragraph before you complain about that.
The newer X features being added are only supported by brand spanking new software, so I'm absolutely sure that in the next several months things will pop up on kde-apps, and if the quality, stability and portability[1] is good enough, it will be added to KDE CVS. Err, KDE Subversion.
[1] Remember that KDE's aim is to be a "Unix Desktop", not a "Linux with X.org/XFree86 Desktop". It runs on all manner of X on all manner of Unix. That means SUSE Linux 9.2, but also SCO with a third party X, OSX with X Windows, etc. Thus eyecandy and extra X features are always optional and fallback gracefully.
--
Evan
--
Evan
Who cares if he turned off the charger after a certain time or if it automatically shut off after a certain time?
--
Evan "Note the 'if he is correct' part"
--
Evan
Fail - The OS grinds to a halt and after waiting five minutes, there is no recourse other than cutting power and rebooting.
Pass (one/a) - The OS grinds, but the user can navigate to a feature (console, Control-ESC in KDE, etc) that allows the user to quickly kill the offending process(es).
Pass (one/b) - The OS grinds or not, but regardless automatically kills the offending process. I consider this to be a worse level than the following.
Pass (two) - The OS grinds and automatically offers the user a method to kill the offending process(es). (KDE had something like that at one point. It may still). Sometimes you may want to let it run.
Pass (three) - The OS does not grind and upon approaching resource limits, offers the user an option to shut down the process or let it run.
And finally...
Pass (four) - The OS does not grind and upon approaching resource limits, offers the user an option to increase limits, potentially by moving the process to another machine or allocating more systems to the process. Presumably the migration would be automatic (and transparent) if the resource limits were higher than the local machine.
Obviously, "user" may be a combination of user and admin in certain cases (multi-user machine, accessing other machines off a local cluster, etc).
--
Evan
It's also a good way to turn on the cooling fan.
--
Evan
If there's something regarding SQL, I want how to validate serialized objects in a Oracle database, not how to use CREATE TABLE to make a MySQL pricelist. And I really don't care so much about that - I'd rather have something about managing projects with a QA cycle that uses the PHP error logging system. That by itself would help the Dev/QA cycle, but we don't have the budget in time to toss a developer on building an in-house solution. In other words, I want a book about how to deal with real "I use this to put food on my table and pay people" issues.
--
Evan
Not mapping out towns allows the players to search for creative people and things that would make sense to find, and not be constrained by what I thought up a few weeks earlier. It also allows for wonderful things like incorporating in-references to events and ideas that happened *after* the map was made.
--
Evan
Meanwhile, for people who use PHP for a living, there are no books out there. There are dozens of "Learn PHP" books on the shelf at my local Borders (I was literally looking through them *yesterday*), but none for advanced development issues or project management.
Poor you. You have what you need. Damn him for lamenting his lack.
--
Evan
They are all hot topics, just like Gitmo... and all have nothing whatsoever to do with the PATRIOT Act... just like Gitmo.
So... how do you feel about late term abortions?
--
Evan
--
Evan "Maybe I missed a new editor popping up, darn 'reading by RSS' habit"
By that logic, Apple ProDOS and Magic Window run on x86. Which isn't quite true... unless you emulate a 6502 on top of the x86.
Way back in this thread, I said that there are solutions involving Wine, but Wine by itself can't run Windows apps on a PPC. I still maintain that to be true.
(I could also pick at your calling something a "solution" and then saying "most win32 programs do not run at all". But putty is a pretty good example that at least one substantial app is able to run).
--
Evan
Nifty trick, though (and a very good example of *nix style "small apps that do their job well and can be chained together"). How well does it perform with more complicated and/or demanding applications?
--
Evan
That said, a screen shot demonstrates very little in terms of specifics. What software were you using? Wine? A different piece of software based on Wine? Or a different emulator altogether? If it was Wine, was it a copy of putty.exe compiled for x86 Windows?
--
Evan
--
Evan
Also for the pedantics: some of the other applications that I mentioned that *do* run Windows binaries on PPC use Wine. But Wine itself can't run a Windows binary, compiled for Windows, on a PPC system.
You can, however, compile Windows apps for PPC against the winelibs - assuming you have the source code for the Windows app.
Which is to say, unless you are king of theoretical phrasing and stretching the definition, it doesn't work.
--
Evan
--
Evan
--
Evan
Personally, I consider a site that returns a special page to search indexers (stripped of navigation words, added context keywords) to be a *good* thing.
That said, I recognize the validity of the opposing view - that it can be abused and/or that the indexing app should see exactly what a user would see.
--
Evan
Check the *title* of the two links. One has a comma separated list of keywords.
--
Evan
Incidently, there has already been a Star Trek crime "series" that is quite nice. Book, of course... the first (and so far only) is "The Case of the Colonist's Corpse: A Sam Cogley Mystery". Pretty good read; I'd like to see more published (the cover and title hint that more may be planned).
Of course, with the recent success of Harry Potter and Lord of the Rings, I'm surprised there isn't a high fantasy series in the works. Plus a few more superhero attempts.
--
Evan
So, in such cases, I reduce it to the basic "what would I do" and "what would I want". I've lived in urban areas where I could hear the automatic weapon fire as I grilled out on my patios. The weapons are already out there to be turned on me, and the people who have them are happy to pull the trigger. I have no love nor hate of guns; I don't own a handgun, and the rifles I have date to when I was a Boy Scout and was target shooting. I am cognizant of the real personal risks associated with them - if you have a gun, you have the chance of accidents happening.
That's the background for how I think. My conclusions are not written in stone, but I think that gun ownership makes a society more safe at both a personal level and allows for a physical empowerment of the people - the ultimate (meaning final) level of democracy.
That said, the fact that there is question about the issue is *exactly* what I mean - they should not be outlawed when there is such a debate over their positive aspects. Rights should be inherent in the people, and selectively removed minimally as possible. There are some fairly clear ones - you shouldn't have the right to walk down the street and drag a random person off and cut their throat. But removing the right to run a certain type of application (versus removing the right to copy somebody's recent work without their permission) is very questionable.
--
Evan