Good job at taking things out of context. And as any UX designer will tell you, it doesn't matter if it *is* faster if it doesn't *feel* faster.
Exactly. And this is where 7 wins. It "FEELS" extremely quick, because it responds to user input better. If you need to take a minor throughput hit for that, so be it. Most people multitask these days anyway - some fractional of a percentage point difference in throughput loss means jack shit if you can actually use the computer while its doing stuff in the background...
I've been running the RC since it came out, no way I'm going back to XP or Vista for Windows stuff.
Benchmarks might not indicate it to be fastest, but it sure FEELS fast in general use.
This is one thing benchmarks unfortunately do not show, but is where Windows 7 (and FreeBSD as well) excel - responsiveness.
On a modern multitasking machine, I (for one) don't care so much if a task takes a little longer to complete in the background so long as I can carry on working in the foreground.
7 Multitasks better than any previous Windows OS bar none, and I think this is why it "feels" faster. It responds to user input a lot better.
Re:Per-desktop activities assignments
on
KDE 4.3 Released
·
· Score: 1, Interesting
Of course, then you try to do something like, oh I dunno, run a 3d game and it craps out because you cant run compiz and openGL apps at the same time.
Or couldn't (no doubt someone will correct me if I'm wrong now) - haven't tried running Compiz/beryll/whatever for a while now because I just don't see the point...
But, point being - you can (and have been able to since release) run 3d shit on vista (or OS/X for that matter) by pointing, clicking and drooling... for the most part it "just works"
So, in 6 months, in going from the KDE 4.2 that was widely lauded as "the KDE4 for end users" or "what KDE4 should have been", they've squashed over 10,000 bugs?
Wait, what?
What actual advantages are there to KDE3.5 for "getting shit done"? Really, I want to know...
I've briefly checked out KDE4.0, 4.1 and 4.2, and immediately been turned off (as a long time KDE user since before 1.0). Its as if they got rid of all the developers who had a clue and replaced them with Javascript web flunkies.
It just feels "wrong", unfamiliar and awkward to use - for no good reason that I can discern (why the fuck do i need a "plasmoid" to store folders in, what the fuck is wrong with my desktop - just for starters?)... and thats coming from someone who loved KDE 2.0 through 3.5 and was looking forward to further development down the same path...
Its not a "vaccine" in the traditional sense, but the end result is the same. before this, the only way to not get malaria was to keep taking the drugs. Which, as I mentioned, have undesirable long term side effects (basically, take them too long and they make you batshit crazy).
... I mention this as someone who travels internationally, occasionally to African nations - so I've had all the vaccines for shit they can prevent that way (typhoid, yellow fever, rabies, etc, etc) - malaria isn't one of them.
If you feed any OS shit hardware and/or shit drivers, it will die.
I've stuck with Intel motherboards, intel CPUs and Nvidia video for the past 6 years, and the only blue screen i have seen in that time (on my desktop, don't get me started on the BIOS and driver issues on my P.O.S. Dell E6400 under Vista) was due to faulty RAM.
But again, blue screens on the E6400 are Dell's fault. As proven by them coming and going with various BIOS and driver updates.
Most of windows is probably written in C/C++ or C# by now, so I'd say its pretty portable that way anyway. All the major APIs have been recently re-written recently, and moving to a new architecture would allow them to drop a lot of legacy x86 shit... I'd hazard a guess that Microsoft has Windows running on various other platforms in some way internally already. They'd be stupid not to.
... whether or not you agree with the method of delivery or not, this is good news. Thus far there has been no *vaccine* for malaria, merely drugs to take while you're exposed to the risk of catching it. Unfortunately, at least one of these has undesirable long term side-effects...
At the end of the day, that point is irrelevant. If people can not be easily sourced to maintain it, it is unmaintainable. OR, alternatively; you are stuck as the sole maintainer for the life of the product. Some may call that job security. I call it a pain in the arse; maintenance is boring, playing with new stuff is where it's at.
A *good* coder will ensure that the code is sufficiently documented so that it is easier to follow.
Not saying you do. However, whatever processing power mixing uses, could be diverted to other purposes. Besides, simple mixing channels these days isn't all there is to audio - you've got positional 3d audio, effects processing (pitch bending, reverb, etc), etc that takes a fair bit more.
But yes, of course - like any specialised hardware, it will eventually be replaced by quick busses and the main cpu.
They took a lot of it out of the kernel, and also re-wrote it to be multi-channel (per-app) aware.
Given that an SB-Live for example is now about 10+ years old, Vista is not designed for 10 year old PCs, and a compatible sound card is all of about $20 - I don't see the big problem.
Yes, yes you need to buy a new sound card. if you want to cry about it, complain to Creative.
Blame creative. Besides, as a former sb-live on linux user, i went through many many months of having no audio output without totally rooting around with different versions of ALSA because the linux driver blindly decided to use digital output, and who the fuck cares about anyone on analogue.
Solution to the problem? Go back to an old inferior card? Wait?
At least with the windows box your solution is to fork out $20 on an audigy...
similar to how Greenland was upon a time was warm enough to be farm land.
uh, when?
greenland was named by an outcast viking (i.e., well before the industrial age) who called it that to get people to come with him to settle it. they died, basically because the only food they could obtain was fish; they couldn't grow anything and shipments from the motherland were not reliably forthcoming.
In the days of phones using proper email, why the fuck use MMS? Seriously, I've had MMS on every phone bar the iphone in the past 6-7 years, and you know how many times I used it?
And please, none of this subjective vague "It does it better it just does". Especially considering that having to jailbreak your phone to get it running the apps that Apple haven't approved hardly constitutes "just working".
As an iphone user of about a year, this is exactly why it is an awesome device. If you haven't used one for any real amount of time, its not surprising that you just don't "get it".
Does it have faults? Yes. but what it does, it does extremely well. I jailbroke my iphone to see what the big deal with running apps apple hasn't allowed was. You know what I found?
90% of them are shitware, and the remaining 10% have about 5 minutes of novelty value. About the only things I missed when running on 2.2 firmware were universal search (in 3.0) and tethering (also in 3.0). Cut/paste - sure its nice, and in 3.0, but I can't say I missed it. No keyboard? Sure, its a drawback, but its also one less thing to break. The iphones we've deployed have been surprisingly durable, and I believe its a large part due to having zero moving parts, zero latches, covers (for removable batteries, memory cards), etc.
I went back to a non-jailbroken firmware simply because there was no value to me in what wasn't available as a certified app from the app store.
If you're running an iphone and actually using it, $99 is not much to pay to have a legit development environment and ability to upload apps to it - it will pale in comparison to your plan's data fees, handset repayment, etc.
Setting affinity made no difference. There is a community patch to resolve the issue though. It ran just fine with my Q6600 on Vista 64 beforehand anyway... got it running on 7 last night. Runs fine:)
Slashdot Mirror
Exactly. And this is where 7 wins. It "FEELS" extremely quick, because it responds to user input better. If you need to take a minor throughput hit for that, so be it. Most people multitask these days anyway - some fractional of a percentage point difference in throughput loss means jack shit if you can actually use the computer while its doing stuff in the background...
I've been running the RC since it came out, no way I'm going back to XP or Vista for Windows stuff.
This is one thing benchmarks unfortunately do not show, but is where Windows 7 (and FreeBSD as well) excel - responsiveness.
On a modern multitasking machine, I (for one) don't care so much if a task takes a little longer to complete in the background so long as I can carry on working in the foreground.
7 Multitasks better than any previous Windows OS bar none, and I think this is why it "feels" faster. It responds to user input a lot better.
Or couldn't (no doubt someone will correct me if I'm wrong now) - haven't tried running Compiz/beryll/whatever for a while now because I just don't see the point...
But, point being - you can (and have been able to since release) run 3d shit on vista (or OS/X for that matter) by pointing, clicking and drooling... for the most part it "just works"
Wait, what?
What actual advantages are there to KDE3.5 for "getting shit done"? Really, I want to know...
I've briefly checked out KDE4.0, 4.1 and 4.2, and immediately been turned off (as a long time KDE user since before 1.0). Its as if they got rid of all the developers who had a clue and replaced them with Javascript web flunkies.
It just feels "wrong", unfamiliar and awkward to use - for no good reason that I can discern (why the fuck do i need a "plasmoid" to store folders in, what the fuck is wrong with my desktop - just for starters?)... and thats coming from someone who loved KDE 2.0 through 3.5 and was looking forward to further development down the same path...
Exactly. OS/X is just an updated (majorly, but still) variant of NextStep, which ran on Intel since 1991 or so.
I've stuck with Intel motherboards, intel CPUs and Nvidia video for the past 6 years, and the only blue screen i have seen in that time (on my desktop, don't get me started on the BIOS and driver issues on my P.O.S. Dell E6400 under Vista) was due to faulty RAM.
But again, blue screens on the E6400 are Dell's fault. As proven by them coming and going with various BIOS and driver updates.
Most of windows is probably written in C/C++ or C# by now, so I'd say its pretty portable that way anyway. All the major APIs have been recently re-written recently, and moving to a new architecture would allow them to drop a lot of legacy x86 shit... I'd hazard a guess that Microsoft has Windows running on various other platforms in some way internally already. They'd be stupid not to.
... whether or not you agree with the method of delivery or not, this is good news. Thus far there has been no *vaccine* for malaria, merely drugs to take while you're exposed to the risk of catching it. Unfortunately, at least one of these has undesirable long term side-effects...
cheers for the clarification. as i said, just getting started, but from what i've seen, i like :)
In any case, the "project evil" stuff for BSD allows use of NDIS windows drivers via a wrapper.
Any more misinformed bullshit about BSD to post up?
Any idea how much that rises to when you strip out the drivers? Or is that only counting the kernel core, not hardware drivers?
A *good* coder will ensure that the code is sufficiently documented so that it is easier to follow.
For values of everyone that exclude apple and many of the top machines in the netcraft uptime surveys...
But yes, of course - like any specialised hardware, it will eventually be replaced by quick busses and the main cpu.
They've modelled him on Vigor
For an example, see Dtrace... :D
eg, Browser has an image open to display, drag drop = new object in the other app, cloned from the image object in the source app...
At least, thats my understanding of how it would work, I'm just starting out in Objective-C./cocoa...
Given that an SB-Live for example is now about 10+ years old, Vista is not designed for 10 year old PCs, and a compatible sound card is all of about $20 - I don't see the big problem.
Yes, yes you need to buy a new sound card. if you want to cry about it, complain to Creative.
Solution to the problem? Go back to an old inferior card? Wait?
At least with the windows box your solution is to fork out $20 on an audigy...
uh, when?
greenland was named by an outcast viking (i.e., well before the industrial age) who called it that to get people to come with him to settle it. they died, basically because the only food they could obtain was fish; they couldn't grow anything and shipments from the motherland were not reliably forthcoming.
Its a waste of resources they could have diverted elsewhere.
Once.
As an iphone user of about a year, this is exactly why it is an awesome device. If you haven't used one for any real amount of time, its not surprising that you just don't "get it".
Does it have faults? Yes. but what it does, it does extremely well. I jailbroke my iphone to see what the big deal with running apps apple hasn't allowed was. You know what I found?
90% of them are shitware, and the remaining 10% have about 5 minutes of novelty value. About the only things I missed when running on 2.2 firmware were universal search (in 3.0) and tethering (also in 3.0). Cut/paste - sure its nice, and in 3.0, but I can't say I missed it. No keyboard? Sure, its a drawback, but its also one less thing to break. The iphones we've deployed have been surprisingly durable, and I believe its a large part due to having zero moving parts, zero latches, covers (for removable batteries, memory cards), etc.
I went back to a non-jailbroken firmware simply because there was no value to me in what wasn't available as a certified app from the app store.
If you're running an iphone and actually using it, $99 is not much to pay to have a legit development environment and ability to upload apps to it - it will pale in comparison to your plan's data fees, handset repayment, etc.
Setting affinity made no difference. There is a community patch to resolve the issue though. It ran just fine with my Q6600 on Vista 64 beforehand anyway... got it running on 7 last night. Runs fine :)