hooray! I will give some or all of those a shot.:D
Re:If you want to watch your WMV now in linux...
on
Jon Bringing WMV9 to Linux
·
· Score: 2, Informative
Except that Xine's UI is annoying and it somehow never plays movies loud enough. I much prefer VLC for playing my movies.
I'll agree with most other posters here in saluting DVD Jon; the guy is a machine!
ugh. bittorrent is for big files. HTML pages are not big files. There are other, better solutions for HTTP, like HTTP proxies and coral. Bittorrent is the wrong hammer to be using for the http screw.
stop using RPM. Debian has a central repository. Most non-RPM systems do as well. I recommend installing apt on any RPM system and using that to manage source lists and package control. It still uses RPMs, but it takes care of most of the dependency problems for you.
pretty much every single item listed in the changelist is going to make me a very, very happy gimper. Shortcut editing, improved copy/paste, new input controls, previews, improved cropping, ico files... It's going to be a very very nice package.
For everyone whining about it not being as "good" as photoshop, quit bitching and go use photoshop. Gimp is not a photoshop clone. It is an independent application and stands just fine on its own merits.
> If it isn't, it's your fault, 'cause you make the stuff.
There's many good analogies above about why that is the wrong attitude. Here's another one: If someone gets a speeding ticket, they don't blame Ford for letting their car go too fast. It's their own fault for not using their equipment properly. Wifi falls under the same laws as the rest of the public spectrum; if these rich idiots don't secure their connection, If we're going to pass new legislation about this, it should be a fine for anyone leaving their WAP accidentally unsecured. (note that I said accidentally)
> First one to make it secure makes a billion dollars.
No, security is not a consumer priority, as evidenced by the popularity of Microsoft products. There is possibly a small niche market for selling secure devices, but you're not going to make billions off of it. Like everything else in computer security, companies are only going to address security when forced to.
that's pretty much the definition of 'public domain'. Except with public domain, you get no say at all about what is done with your code later, so if you don't want it to be used by someone else under license, too bad for you, you should have used a real license of your own. Legally, either anyone can do whatever they want with it including relicensing, or you need to use a license which lets you retain some rights over the work.
If that's what you meant, then you may as well call it public domain.
Many legitimate corporate IT teams do it because they CTO has declared it to be a windows-only shop. MSexchange is popular in the not-so-technical corporate world.
If your system asks the sending *server*, this is redundant, as you already know the sending server sent it, by definition.
If your system asks the domain that the mail is supposedly from, then you may as well be using SPF, as it saves on network traffic and gets you the same answer.
They're actually just 'rolling out' the craft on august 5th, which I believe means it's finished, not that they're going to actually launch it that day.
How do you figure that eye candy is a usability problem? Apple researches these things. The dock is good because it visually shows you what apps you're running, with a nice big icon and great feedback on mouseover. The genie (swooshy) effect is good because it shows where your window goes/comes from when you minimize, instead of having it just disappear. OSX is far more 'spatial' than Gnome 2.6, but OSX has done it in a subtle way that doesn't break users' current expectations.
More eye candy that turns out to not be useless: actual transparency lets you keep track of what is behind/under your current window, which means you don't have to rearrange windows as often.
Also, my KDE3.2 desktop is far closer to OSX right now than it is to windows. Check out ksmoothdock.
Er, I have to say that the high tech job market in Edmonton is fairly shitty. There's jobs, but there's also massive competition for it. There are *way* too many techies for the number of jobs here. While Edmonton is cheap to live in, and is a great city all round, that's not very useful if you're unemployed.
Re:Scalability and Maintainability go hand in hand
on
On PHP and Scaling
·
· Score: 1
PHP only becomes unmaintainable if you don't know what you're doing, or if you don't plan well at the onset.
In the Real World, you rarely get to write the web app yourself; instead, you get to add features/clean up/fix the web app that the Other Guy wrote. The Other Guy invariably doesn't know what he's doing, nor did he plan well at the beginning. Knowing this is the case, I would much rather he were using an environment that forces some amount of good design on him, since that will save me time and frustration. Being allowed to write bad code is great for learning a language, but horrible for actual development.
I like most of perl. I like parts of PHP. I love HTML::Mason, I love PEAR classes. Scalability and maintainability come from using existing extensions to do the heavy lifting instead of rewriting the wheel every time, a lesson that most web programmers have yet to learn. Discipline is still required, but if your environment lets you immediately get down to making the thing work, you won't be as tempted to toss in ugly hacks.
Slashdot Mirror
hooray! I will give some or all of those a shot. :D
Except that Xine's UI is annoying and it somehow never plays movies loud enough. I much prefer VLC for playing my movies. I'll agree with most other posters here in saluting DVD Jon; the guy is a machine!
ugh. bittorrent is for big files. HTML pages are not big files. There are other, better solutions for HTTP, like HTTP proxies and coral. Bittorrent is the wrong hammer to be using for the http screw.
stop using RPM. Debian has a central repository. Most non-RPM systems do as well. I recommend installing apt on any RPM system and using that to manage source lists and package control. It still uses RPMs, but it takes care of most of the dependency problems for you.
pretty much every single item listed in the changelist is going to make me a very, very happy gimper. Shortcut editing, improved copy/paste, new input controls, previews, improved cropping, ico files... It's going to be a very very nice package.
For everyone whining about it not being as "good" as photoshop, quit bitching and go use photoshop. Gimp is not a photoshop clone. It is an independent application and stands just fine on its own merits.
therefore, all 7/11s are women! brilliant!
what's a "newspaper"?
Are you saying you agree with him or giving a suggestion?
Could *have*, or "Could've". Not "could of".
Yes, and big brother is starting to lose.
> If it isn't, it's your fault, 'cause you make the stuff.
There's many good analogies above about why that is the wrong attitude. Here's another one: If someone gets a speeding ticket, they don't blame Ford for letting their car go too fast. It's their own fault for not using their equipment properly. Wifi falls under the same laws as the rest of the public spectrum; if these rich idiots don't secure their connection, If we're going to pass new legislation about this, it should be a fine for anyone leaving their WAP accidentally unsecured. (note that I said accidentally)
> First one to make it secure makes a billion dollars.
No, security is not a consumer priority, as evidenced by the popularity of Microsoft products. There is possibly a small niche market for selling secure devices, but you're not going to make billions off of it. Like everything else in computer security, companies are only going to address security when forced to.
that's pretty much the definition of 'public domain'. Except with public domain, you get no say at all about what is done with your code later, so if you don't want it to be used by someone else under license, too bad for you, you should have used a real license of your own. Legally, either anyone can do whatever they want with it including relicensing, or you need to use a license which lets you retain some rights over the work. If that's what you meant, then you may as well call it public domain.
Many legitimate corporate IT teams do it because they CTO has declared it to be a windows-only shop. MSexchange is popular in the not-so-technical corporate world.
keep an eye on backports.org if you're using debian stable.
If your system asks the sending *server*, this is redundant, as you already know the sending server sent it, by definition.
If your system asks the domain that the mail is supposedly from, then you may as well be using SPF, as it saves on network traffic and gets you the same answer.
The point of SPF is not to whitelist servers that have it. Instead, the purpose is to not trust (and possibly blacklist) servers that don't.
Availability is not the same as use, or affordability.
PCAnywhere for linux is called X11. It's been around for years and years, this is just KDE taking advantage of a protocol to speed that up.
Meanwhile, the rest of the world would go ahead and use it while laughing at the poor backwards americans.
But they still can't find it on a map.
They're actually just 'rolling out' the craft on august 5th, which I believe means it's finished, not that they're going to actually launch it that day.
It's a *balloon*. If the first stage fails, odds are good they can float back to earth, drinking beers and being mellow all the way.
Also, it's 'eh', not 'ay'.
How do you figure that eye candy is a usability problem? Apple researches these things. The dock is good because it visually shows you what apps you're running, with a nice big icon and great feedback on mouseover. The genie (swooshy) effect is good because it shows where your window goes/comes from when you minimize, instead of having it just disappear. OSX is far more 'spatial' than Gnome 2.6, but OSX has done it in a subtle way that doesn't break users' current expectations.
More eye candy that turns out to not be useless: actual transparency lets you keep track of what is behind/under your current window, which means you don't have to rearrange windows as often.
Also, my KDE3.2 desktop is far closer to OSX right now than it is to windows. Check out ksmoothdock.
Er, I have to say that the high tech job market in Edmonton is fairly shitty. There's jobs, but there's also massive competition for it. There are *way* too many techies for the number of jobs here. While Edmonton is cheap to live in, and is a great city all round, that's not very useful if you're unemployed.
In the Real World, you rarely get to write the web app yourself; instead, you get to add features/clean up/fix the web app that the Other Guy wrote. The Other Guy invariably doesn't know what he's doing, nor did he plan well at the beginning. Knowing this is the case, I would much rather he were using an environment that forces some amount of good design on him, since that will save me time and frustration. Being allowed to write bad code is great for learning a language, but horrible for actual development.
I like most of perl. I like parts of PHP. I love HTML::Mason, I love PEAR classes. Scalability and maintainability come from using existing extensions to do the heavy lifting instead of rewriting the wheel every time, a lesson that most web programmers have yet to learn. Discipline is still required, but if your environment lets you immediately get down to making the thing work, you won't be as tempted to toss in ugly hacks.