That makes little sense, as the DirectX filters are usable on Windows NT. The filters came out with IE 5.5. This means that the alpha-blending group must either suffered political pressure, or were just overlooking this solution when it came to real support in IE 5.5. They could (probably) easily switched the PNG handler to DirectX rather than whatever it is now without the end user really noticing or caring.
That being said, I'd like to hear their excuse for not supporint <object> properly;)
First off, I know all about the drama surrounding IE's PNG support. Secondly, I think those that gripe about it to Microsoft pretty much gripe in vain (at least for now). Thirdly, at least on my work computer, IE uses Quicktime to render PNG files. This leads me to conclude that we, the concerned few should ask Apple to make Quicktime for Windows support PNG's alpha channels. As we do this, we can ask Apple to add support for this APNG format too.
To some degree yes. If I use an API that starts out insecure as long as I continue to still use that API, the provider can still fix the problems with that API so I don't have to re-invent the wheel. There are of course, some caveats, but poor implementations shouldn't prevent the usage of useful tools.
Wow, this is amazing to see that groups/companies are finally tackling the issue of finding files on your computer. It seems so simple, yet Apple, Microsoft, and now KDE are all making "search" their next big feature. Who's willing to stick their neck out and venture a guess as to the next en vogue feature will be? If Apple has any say, it'll be accessibility, but I'm gonna say blogging-in-a-box will be the next fashionable thing to do.
So you have a choice, be practical and don't use the camera with Linux, or be shackled with the responsibility of maintaining a module across any kernel version you may ever come across.
Ain't freedom grand? As with most things in life, freedom is only available to the elite few that possess enough understanding to be free in the first place. I understand that I'm free to fork the source, but if I lack the knowledge necessary to hack on the kernel what good is it to me to fork?
Reinventing the wheel for every project is a form of laziness too--you're too damn lazy to learn about existing APIs. Tools exist for a purpose, and people too lazy/prejudiced/"good" to use them should shut up, imho;)
Simple, double-sided tape. Since your keyboard and mouse are now one item, you shouldn't need to have your hands on anything else. The next version is promising to have a handy little nose scratcher attachement as well, so when your hands are effectively glued to this device, you can still scratch yourself. Scratching your crotch with a controller still isn't testing very well, except amongst a surprisingly high percentage of female testers...
It's funny that people claim this is a strength of Open Source, but when someone forks a spec, flames reign supreme. Can anyone explain why this is? I'd really like to know how forking and introducing proprietary featurs is okay for some projects, but on other projects it's not.
Seriously consider the differences between say, Microsoft forking HTML, and GNU forking ANSI C. I know that the Linux kernel can pretty much only be compiled by gcc since the kernel depends on gcc proprietary extensions, yet feel outraged that a company dare to do the same to a (wildly) popular markup language.
The problem is this: Ford doesn't have a stake in the future of your vehicle other than selling you a new one. (maybe if you had a service agreement like an extended warranty, but anyway)
Apple is protecting themselves from the bad press that will surely ensue when they release the next update of the iPod software that removes the rm mod, not solely because they don't like it, but because they don't support it (nor should they).
As long as Apple has some responsibility to keep providing software for their hardware (firmware updates), they have a say in how people use their hardware (though they may be ignored by the individual). Individuals that would proverbially hack their xbox here aren't the concern--it's the masses that are the concern.
I really dug season 1, but season 2 was a little too goofy. On the other hand, i'll probably pick this up just to support them, cuz I really dig the artform.
I suppose in the end the wallet has the final say.
You might think twice if you can't instantaneously pull a knife on someone. Just like you watch what you say when you know you're not anonymous, you behave differently when something takes a few seconds longer.
There are a lot of problems with that way of thinking. First off, it tends to reek of "newer equals better" syndrome. Recent technology addresses the issues of today, just as older tech addresses the issues of yesterday. Building on older tech address the issues of yesterday and today (even if it suffers from being kludgy). There are going to be bugs that newer tech introduces, whereas older tech has bugs that are understood, sometimes even fixed.
While this may not seem to be a big deal to some, when you start risking people's lives you begin to see why dependable technology is better than newer stuff. Even if the newer stuff makes gold from lead, it's safer to stick with the older, familiar tools of the trade.
In short, complete re-thinks should rarely, if ever, happen, especially in regards to areas which risk human lives.
That won't be any problem, as we all know that killbots have a preset kill limit. All we'll have to do is send wave after wave after wave of our own men against them and we'll eventually prevail.
Re:My Win desktop already runs *nix code...
on
Unix To Beef Up Longhorn
·
· Score: 4, Insightful
I know you're making a point here, but it's pretty rare for the most part to take a random package off the net and have./configure; make all install; work at all. I don't know how many packages have had little bugs that cause compile problems in FreeBSD or OSX or any other non-Linux system that wasn't properly tested.
It's a very nice sidebar. You can find it here.
Basically, you bookmark your rss feeds in a specific folder, and Sage reads from that folder. I don't know if it can "discover" new feeds or not. (my guess is no, but i'll probably be corrected here if need be)
Slashdot Mirror
That makes little sense, as the DirectX filters are usable on Windows NT. The filters came out with IE 5.5. This means that the alpha-blending group must either suffered political pressure, or were just overlooking this solution when it came to real support in IE 5.5. They could (probably) easily switched the PNG handler to DirectX rather than whatever it is now without the end user really noticing or caring.
;)
That being said, I'd like to hear their excuse for not supporint <object> properly
First off, I know all about the drama surrounding IE's PNG support. Secondly, I think those that gripe about it to Microsoft pretty much gripe in vain (at least for now). Thirdly, at least on my work computer, IE uses Quicktime to render PNG files. This leads me to conclude that we, the concerned few should ask Apple to make Quicktime for Windows support PNG's alpha channels. As we do this, we can ask Apple to add support for this APNG format too.
To some degree yes. If I use an API that starts out insecure as long as I continue to still use that API, the provider can still fix the problems with that API so I don't have to re-invent the wheel. There are of course, some caveats, but poor implementations shouldn't prevent the usage of useful tools.
Wow, this is amazing to see that groups/companies are finally tackling the issue of finding files on your computer. It seems so simple, yet Apple, Microsoft, and now KDE are all making "search" their next big feature. Who's willing to stick their neck out and venture a guess as to the next en vogue feature will be? If Apple has any say, it'll be accessibility, but I'm gonna say blogging-in-a-box will be the next fashionable thing to do.
So you have a choice, be practical and don't use the camera with Linux, or be shackled with the responsibility of maintaining a module across any kernel version you may ever come across.
Ain't freedom grand? As with most things in life, freedom is only available to the elite few that possess enough understanding to be free in the first place. I understand that I'm free to fork the source, but if I lack the knowledge necessary to hack on the kernel what good is it to me to fork?
Reinventing the wheel for every project is a form of laziness too--you're too damn lazy to learn about existing APIs. Tools exist for a purpose, and people too lazy/prejudiced/"good" to use them should shut up, imho ;)
Simple, double-sided tape. Since your keyboard and mouse are now one item, you shouldn't need to have your hands on anything else. The next version is promising to have a handy little nose scratcher attachement as well, so when your hands are effectively glued to this device, you can still scratch yourself. Scratching your crotch with a controller still isn't testing very well, except amongst a surprisingly high percentage of female testers...
|<3rry
use the <
HTML Entities are your friend, or else a powerful enemy bent on global domination. I forget which
Also, preview is a friend
It's funny that people claim this is a strength of Open Source, but when someone forks a spec, flames reign supreme. Can anyone explain why this is? I'd really like to know how forking and introducing proprietary featurs is okay for some projects, but on other projects it's not.
Seriously consider the differences between say, Microsoft forking HTML, and GNU forking ANSI C. I know that the Linux kernel can pretty much only be compiled by gcc since the kernel depends on gcc proprietary extensions, yet feel outraged that a company dare to do the same to a (wildly) popular markup language.
The problem is this: Ford doesn't have a stake in the future of your vehicle other than selling you a new one. (maybe if you had a service agreement like an extended warranty, but anyway)
Apple is protecting themselves from the bad press that will surely ensue when they release the next update of the iPod software that removes the rm mod, not solely because they don't like it, but because they don't support it (nor should they).
As long as Apple has some responsibility to keep providing software for their hardware (firmware updates), they have a say in how people use their hardware (though they may be ignored by the individual). Individuals that would proverbially hack their xbox here aren't the concern--it's the masses that are the concern.
While you make some great points, I must point out that some open source project don't even try to be small , do-one-thing-well programs.
Free software doesn't necessitate programs or projects being small. Just look at the freaking kernel. The strength in free software is flexibility.
it's XSLT. XML Stylesheet Language Transformations.
I remember it as x-slut. Transforming data into xml used to make me feel like a whore before I started using XSLT.
I really dug season 1, but season 2 was a little too goofy. On the other hand, i'll probably pick this up just to support them, cuz I really dig the artform.
I suppose in the end the wallet has the final say.
You might think twice if you can't instantaneously pull a knife on someone. Just like you watch what you say when you know you're not anonymous, you behave differently when something takes a few seconds longer.
There are a lot of problems with that way of thinking. First off, it tends to reek of "newer equals better" syndrome. Recent technology addresses the issues of today, just as older tech addresses the issues of yesterday. Building on older tech address the issues of yesterday and today (even if it suffers from being kludgy). There are going to be bugs that newer tech introduces, whereas older tech has bugs that are understood, sometimes even fixed.
While this may not seem to be a big deal to some, when you start risking people's lives you begin to see why dependable technology is better than newer stuff. Even if the newer stuff makes gold from lead, it's safer to stick with the older, familiar tools of the trade.
In short, complete re-thinks should rarely, if ever, happen, especially in regards to areas which risk human lives.
That won't be any problem, as we all know that killbots have a preset kill limit. All we'll have to do is send wave after wave after wave of our own men against them and we'll eventually prevail.
I know you're making a point here, but it's pretty rare for the most part to take a random package off the net and have ./configure; make all install; work at all. I don't know how many packages have had little bugs that cause compile problems in FreeBSD or OSX or any other non-Linux system that wasn't properly tested.
It's a very nice sidebar. You can find it here. Basically, you bookmark your rss feeds in a specific folder, and Sage reads from that folder. I don't know if it can "discover" new feeds or not. (my guess is no, but i'll probably be corrected here if need be)
Didn't Ducktales come out for the GBC?
as original as your spelling of "sequel"
The final boss was always such a pain in the ass until I read a tip on gamefaqs that allows you to finish him off relatively unharmed.
I wonder if that bug's been fixed link Enix fixed some cheating bugs in their dragon warrior games that were re-released?
use ipv6, of course.
It's not like cars won't eventually get their own ip anyway, so let's do it now.
Wow. You may want to visit a doctor at some point if you're spending that much time in the bathroom :)
If you're on Windows with an NTFS partition, look for the utility linkd.exe. I've found it to be most useful.