Um, $2000 per year isn't much. I spend more than that on just bandwidth. $2000 to guarantee that all the mail coming out of my server wasn't spam would be worthwhile.
Problem is, this idea isn't worth $2000, because it doesn't guarantee that. It's DOMAIN based, when it needs to be server based. Otherwise, I gotta pay $2000 per DOMAIN? That's $100,000 per server!
Since when was selling quality products at a fair price to a market with money to spend and a desire to buy them considered "defying the odds?"
If you asked me, I'd say it was Dell and all the other companies selling dirt cheap with no margin who were defying the odds. Apple's just succeeding in a sheisty market with a classical business plan: make a good product, market it efficiently, pump some of the proceeds back into r & d.
What's with all this "Joe Sixpack" bashing on slashdot? Don't you fuckers drink beer like the rest of us?
Anyhow, the reason most people don't switch around their formats is that the gains usually don't outweigh the effort. If you like sitting in front of your computer, chatting on IRC while reencoding music or ripping DVDs or something, you're going to do it even for a slight quality gain. If you want to live your life away from the multimedia hub (hence why you bought a portable audio player in the first place), you'll use whatever format fits the most music and keep stuff in its original format.
I know that since I stopped worshipping my tiny god, I've been more interested ubiquity than quality. Back in college, I burned most of my CPU cycles moving video or audio from one format to another. No longer.
1) PDA memory is slowww. And switching tracks was slowww. The interfaces were slowww. Copying to the memory card, even over USB 2.0, was so slowww I coudn't take it! Copying 30 gig to the iPod took less than ten minutes.
2) PDAs are hard to control one handed or while in motion. I kept screwing it up while running at the gym. Plus I looked stupid, tapping at a pda in a leather case with a plastic stick while running in a circle.
3) PDAs aren't very rugged. I dropped it a lot and would cringe every time. The iPod isn't much better, but there are a number of shock absorbing "skins" that really make it nice. Furthermore, sweating on the PDA can cause it to not work right. The iPod, being nearly seamless, is unaffected by sweat.
4) The PDA sound was awful...besides being hard to control, volume wise, there were noticable problems with the sound. And it wasn't loud enough. And the headset plugged in to a really inconvenient place. Mostly, it felt "tacked on."
Guy sees some giant man railin' a porn star, he thinks "damn, she's getting it good. look at the size of that thing! this guy's a sexual demon."
Girl sees the same scene and thinks, "wow, I'll bet that really hurts. he's pushing right into her bladder, and there's hardly any contact with the clitoris at all."
Of course, if they made porn for women, it'd be 45 minutes of foreplay followed by the man taking the garbage to the curb.
saving user's time, preventing bugs, and integration
God bless you, man. If we had one guy duking it out in academia with those goals in mind for every five guys trying to build a better mousetrap simulator, we'd have software that didn't suck.
Me, I'm just a code monkey trying to get my time in before my brain crashes and I have to switch careers (which is in 2008, given conventional wisdom)
So wait -- the outsourcing trend is creating a demand for foreign students to get good education -- and they're not getting it here because of the DHS -- and people STILL plan to vote for Bush?
Just to play devil's advocate for a second...a lot of people who work in software and are genuinely talented don't understand working directories, networking or compilers. You don't have to. In fact, if you were to learn every nuance of every aspect of computing before you could start writing software, you'd be a fairly crummy programmer when compared to somebody who just learned what he had to.
I know an AWFUL lot about SQL, but I find I don't write as succinct and usable statements as some of the neophyte SQL people I work with. I have had a hatred of cursors and unions, so i try not to use them, but cursors are often easier to understand and thus easier to maintain.
My point is, a senior programmer doesn't have to know what a working directory is, or how to remove one in an arbitrary operating system. She just needs to know how to find out, and to retain the knowledge once she gets it. Seems like she has that down pat.
Typical attitude. "Oh, liberal arts, that'll be useful."
Well, I have a degree in a fairly specific liberal arts field. And I've worked consistantly as a programmer for five years. Most of my CS friends do not work in the field anymore. They either burnt out or never got a chance to burn in the first place.
Part of the reason for my continued employment is that liberal arts degree. Before I took my first rhetoric class, I didn't understand the importance of politics, networking, attitude or even how to work in groups. Most of the CS courses I took were exercises in elitism...generally, one or two students would do the assignment while the others made the TA do it for them, or devised ways to cheat. A lot of people dreamed of making a lot of money and getting great internships with arms manufacturers, etc, or of getting in with some video game studio and just playing for the rest of their lives.
There was very little really useful work going on. I mean, half of everything was in Pascal. They taught C++ like C and never explained the importance of streams. There was a class in building a web page at 300!
I had planned on transferring into that department, but I said fuck it. I took more rhetoric, and as electives, differential equations and network programming. The rest of it I gleamed from Oreilly books (which are just wonderful).
And you know? My writing skills are better than most programmers. Even if my other plans fall through, I could always write a really bitchin' primer on visual inheritance. Which at my school would be used in doctoral classes.
That's crap, man. I was "low income" when I was in college, making under 11k per year and paying for school at the same time. I never got a loyalty card to my local Wegmans' and was still able to feed myself just fine.
Over the course of a shopping trip, you MIGHT save pretty heavily with one of these cards. But usually on name brand items. Quite often, the generic and store brand items are less expensive or at least within 10% of the sale price. I'd buy the 99 cent Tonys pizza instead of the two for $3 loyalty card special on Stauffers.
I put together a solid DDoS exploit for Windows using XNA, it will affect XBOX and Windows Mobile devices?
I dunno. If you build an exploit for the JVM or the STL, does it affect everything written in Java, everything written in C? A library is not the same as an application or a service, and a framework is nothing more than an organized set of libraries. Sure, a bug in a fundamental library could be disasterous, but that can be said of ANY set of libraries, from DirectX to TCP/IP. But obviously, a SINGLE implementation is a lot easier to test and secure than three of them.
.NET has yet to establish itself anywhere useful except as an architecture for Web Development.
Wow, I guess the past two years I've spent writing Windows Forms and Mobile applications in.NET were pretty pathetic considering it's not established and apparently highly broken. Maybe we should return the money from all the orders we've received for our software suite, and ask our satisfied customers to stop using it immediately. I'm sure they'll be much happier using their old VB6 and Delphi apps.</sarcasm>
.NET is a great tool for windows app development. It's nearly drummed the Java advocacy right out of me. In fact, the only area I don't like the system in web development, and only because I had a few bad experiences with webforms.
Well, if you put $3m into a game only to find a year later that you've got little beyond an engine and a premise that's overdone in the marketplace, and you'll need $10m and two years more before you could make enough back selling the game to cover costs, then you save $7m and a lot of uncertainty by cancelling the project and getting to work on some better use for that time & money.
Remember, the most important part of editing is knowing what to keep and what to throw away. If you just released every POS you put any effort into regardless of whether it was worthwhile or bug free...well, you'd be ValuSoft.
Well, it depends. Do you purport to be a moral and logical person? Do you believe in the protection of personal freedoms?
If so, then even if you don't KNOW or LIKE the victim, you should still support punishment of the criminal. Otherwise, you're encouraging elitism. Or do you want to live in a world where crimes against the unpopular are cheered and go unpunished?
I lived in a similar world called "Middle School," and I wouldn't want to go back.
This is just rambling. That.NET "compiler hole" was patched, sometime before the first service release and well before.NET 2003. Furthermore, those articles are fairly sensational..."there is no just add water approach to security?" No, but using a managed language *IS* a just add water approach to avoiding buffer overflows. If there's a bug in a brand new compiler, it's a lot easier to fix than, well, every quicky C program ever written.
In fact, picking C# as the new language of choice over C is one of the things that could really change the perception most people have of MS' products.
And please. I work in software. I have seen first hand that no patch will ever solve every problem every time without need for tweaking. This isn't true of Linux (even great systems like emerge occasioinally need a kick in the pants if you're seriously hacking away or even just installing packages in wierd places), so why should Microsoft -- who have roughly 20 times the install base to worry about -- be expected to perform miracles? Hell, our company occasionally spends weeks on an update patch, performing hands-ons with customers. Nowadays, 99% of the time, Microsoft's patches consist of clicking on a link and waiting. And you know, that's almost a miracle...in fact, it's almost as good as Software Update on my mac.
.NET is not "fading away." It's not "mucked up by schizophrenic marketing." The marketing you're talking about SEEMS schizophrenic, because basing everything on a technology like a CLI and a framework means your technology touches everything.
It's just a set of tools for writing software. And it's a very convenient tool for writing really robust software relatively quickly. Meaning that, while a lot of development had yet to shift completely to the.NET CLI, more and more applications every day are going there.
For us niche and small market developers, it's a godsend, bridging the gap between the ubiquity of Java and the speed and usability of native windows APIs. And thanks to Mono,.NET apps will eventually gain the benefit of being cross platform.
And as for MS being insecure...well, those products "hit in the last 6 months" were all patched prior to the outbreak. Look it up, if you want to be informed. The difficulty there is an uninformed public and/or lazy IT staff. If you don't apply your OpenSSL patches, your Linux or BSD system will be pretty insecure, too.
Actually, domain registrars are getting paid to be a responsible party keeping people from squatting on domains they have no rights to and enforcing correct contact information.
They're just not doing it very well, because they make so LITTLE money off each domain it doesn't pay to do so. And who demanded $10 domain names?
Slashdot Mirror
Um, $2000 per year isn't much. I spend more than that on just bandwidth. $2000 to guarantee that all the mail coming out of my server wasn't spam would be worthwhile.
Problem is, this idea isn't worth $2000, because it doesn't guarantee that. It's DOMAIN based, when it needs to be server based. Otherwise, I gotta pay $2000 per DOMAIN? That's $100,000 per server!
Since when was selling quality products at a fair price to a market with money to spend and a desire to buy them considered "defying the odds?"
If you asked me, I'd say it was Dell and all the other companies selling dirt cheap with no margin who were defying the odds. Apple's just succeeding in a sheisty market with a classical business plan: make a good product, market it efficiently, pump some of the proceeds back into r & d.
What's with all this "Joe Sixpack" bashing on slashdot? Don't you fuckers drink beer like the rest of us?
Anyhow, the reason most people don't switch around their formats is that the gains usually don't outweigh the effort. If you like sitting in front of your computer, chatting on IRC while reencoding music or ripping DVDs or something, you're going to do it even for a slight quality gain. If you want to live your life away from the multimedia hub (hence why you bought a portable audio player in the first place), you'll use whatever format fits the most music and keep stuff in its original format.
I know that since I stopped worshipping my tiny god, I've been more interested ubiquity than quality. Back in college, I burned most of my CPU cycles moving video or audio from one format to another. No longer.
I had a multimedia PDA before I got my iPod.
I sold it because:
1) PDA memory is slowww. And switching tracks was slowww. The interfaces were slowww. Copying to the memory card, even over USB 2.0, was so slowww I coudn't take it! Copying 30 gig to the iPod took less than ten minutes.
2) PDAs are hard to control one handed or while in motion. I kept screwing it up while running at the gym. Plus I looked stupid, tapping at a pda in a leather case with a plastic stick while running in a circle.
3) PDAs aren't very rugged. I dropped it a lot and would cringe every time. The iPod isn't much better, but there are a number of shock absorbing "skins" that really make it nice. Furthermore, sweating on the PDA can cause it to not work right. The iPod, being nearly seamless, is unaffected by sweat.
4) The PDA sound was awful...besides being hard to control, volume wise, there were noticable problems with the sound. And it wasn't loud enough. And the headset plugged in to a really inconvenient place. Mostly, it felt "tacked on."
Same is true with porno.
Guy sees some giant man railin' a porn star, he thinks "damn, she's getting it good. look at the size of that thing! this guy's a sexual demon."
Girl sees the same scene and thinks, "wow, I'll bet that really hurts. he's pushing right into her bladder, and there's hardly any contact with the clitoris at all."
Of course, if they made porn for women, it'd be 45 minutes of foreplay followed by the man taking the garbage to the curb.
That's a crass way of putting it.
Ideally, you should dazzle them with brilliance and baffle them with bullshit.
saving user's time, preventing bugs, and integration
God bless you, man. If we had one guy duking it out in academia with those goals in mind for every five guys trying to build a better mousetrap simulator, we'd have software that didn't suck.
Me, I'm just a code monkey trying to get my time in before my brain crashes and I have to switch careers (which is in 2008, given conventional wisdom)
So wait -- the outsourcing trend is creating a demand for foreign students to get good education -- and they're not getting it here because of the DHS -- and people STILL plan to vote for Bush?
Just to play devil's advocate for a second...a lot of people who work in software and are genuinely talented don't understand working directories, networking or compilers. You don't have to. In fact, if you were to learn every nuance of every aspect of computing before you could start writing software, you'd be a fairly crummy programmer when compared to somebody who just learned what he had to.
I know an AWFUL lot about SQL, but I find I don't write as succinct and usable statements as some of the neophyte SQL people I work with. I have had a hatred of cursors and unions, so i try not to use them, but cursors are often easier to understand and thus easier to maintain.
My point is, a senior programmer doesn't have to know what a working directory is, or how to remove one in an arbitrary operating system. She just needs to know how to find out, and to retain the knowledge once she gets it. Seems like she has that down pat.
Hooray!
Computing needs more people who refer to those who have difficulty with software as tards.
After all, it's these elite few who give us the breathtaking inscruitable syntax seen in Perl, Lisp and Haskell. I salute you!
Typical attitude. "Oh, liberal arts, that'll be useful."
Well, I have a degree in a fairly specific liberal arts field. And I've worked consistantly as a programmer for five years. Most of my CS friends do not work in the field anymore. They either burnt out or never got a chance to burn in the first place.
Part of the reason for my continued employment is that liberal arts degree. Before I took my first rhetoric class, I didn't understand the importance of politics, networking, attitude or even how to work in groups. Most of the CS courses I took were exercises in elitism...generally, one or two students would do the assignment while the others made the TA do it for them, or devised ways to cheat. A lot of people dreamed of making a lot of money and getting great internships with arms manufacturers, etc, or of getting in with some video game studio and just playing for the rest of their lives.
There was very little really useful work going on. I mean, half of everything was in Pascal. They taught C++ like C and never explained the importance of streams. There was a class in building a web page at 300!
I had planned on transferring into that department, but I said fuck it. I took more rhetoric, and as electives, differential equations and network programming. The rest of it I gleamed from Oreilly books (which are just wonderful).
And you know? My writing skills are better than most programmers. Even if my other plans fall through, I could always write a really bitchin' primer on visual inheritance. Which at my school would be used in doctoral classes.
That's crap, man. I was "low income" when I was in college, making under 11k per year and paying for school at the same time. I never got a loyalty card to my local Wegmans' and was still able to feed myself just fine.
Over the course of a shopping trip, you MIGHT save pretty heavily with one of these cards. But usually on name brand items. Quite often, the generic and store brand items are less expensive or at least within 10% of the sale price. I'd buy the 99 cent Tonys pizza instead of the two for $3 loyalty card special on Stauffers.
I put together a solid DDoS exploit for Windows using XNA, it will affect XBOX and Windows Mobile devices?
.NET has yet to establish itself anywhere useful except as an architecture for Web Development.
.NET were pretty pathetic considering it's not established and apparently highly broken. Maybe we should return the money from all the orders we've received for our software suite, and ask our satisfied customers to stop using it immediately. I'm sure they'll be much happier using their old VB6 and Delphi apps.</sarcasm>
I dunno. If you build an exploit for the JVM or the STL, does it affect everything written in Java, everything written in C? A library is not the same as an application or a service, and a framework is nothing more than an organized set of libraries. Sure, a bug in a fundamental library could be disasterous, but that can be said of ANY set of libraries, from DirectX to TCP/IP. But obviously, a SINGLE implementation is a lot easier to test and secure than three of them.
Wow, I guess the past two years I've spent writing Windows Forms and Mobile applications in
.NET is a great tool for windows app development. It's nearly drummed the Java advocacy right out of me. In fact, the only area I don't like the system in web development, and only because I had a few bad experiences with webforms.
So was KOTOR, and it's great on the PC. I hear good things about Halo's PC port, not to mention GTA3 and Vice City.
One example does not prove anything other than that Deus Ex 2 was a lazy port.
Well, if you put $3m into a game only to find a year later that you've got little beyond an engine and a premise that's overdone in the marketplace, and you'll need $10m and two years more before you could make enough back selling the game to cover costs, then you save $7m and a lot of uncertainty by cancelling the project and getting to work on some better use for that time & money.
Remember, the most important part of editing is knowing what to keep and what to throw away. If you just released every POS you put any effort into regardless of whether it was worthwhile or bug free...well, you'd be ValuSoft.
Well, it depends. Do you purport to be a moral and logical person? Do you believe in the protection of personal freedoms?
If so, then even if you don't KNOW or LIKE the victim, you should still support punishment of the criminal. Otherwise, you're encouraging elitism. Or do you want to live in a world where crimes against the unpopular are cheered and go unpunished?
I lived in a similar world called "Middle School," and I wouldn't want to go back.
This is just rambling. That .NET "compiler hole" was patched, sometime before the first service release and well before .NET 2003. Furthermore, those articles are fairly sensational..."there is no just add water approach to security?" No, but using a managed language *IS* a just add water approach to avoiding buffer overflows. If there's a bug in a brand new compiler, it's a lot easier to fix than, well, every quicky C program ever written.
In fact, picking C# as the new language of choice over C is one of the things that could really change the perception most people have of MS' products.
And please. I work in software. I have seen first hand that no patch will ever solve every problem every time without need for tweaking. This isn't true of Linux (even great systems like emerge occasioinally need a kick in the pants if you're seriously hacking away or even just installing packages in wierd places), so why should Microsoft -- who have roughly 20 times the install base to worry about -- be expected to perform miracles? Hell, our company occasionally spends weeks on an update patch, performing hands-ons with customers. Nowadays, 99% of the time, Microsoft's patches consist of clicking on a link and waiting. And you know, that's almost a miracle...in fact, it's almost as good as Software Update on my mac.
Don't forget Ebay's single login for ebay AND paypal.
Or Apple's single login for their website AND itunes (you can also use your AOL login).
.NET is not "fading away." It's not "mucked up by schizophrenic marketing." The marketing you're talking about SEEMS schizophrenic, because basing everything on a technology like a CLI and a framework means your technology touches everything.
.NET CLI, more and more applications every day are going there.
.NET apps will eventually gain the benefit of being cross platform.
It's just a set of tools for writing software. And it's a very convenient tool for writing really robust software relatively quickly. Meaning that, while a lot of development had yet to shift completely to the
For us niche and small market developers, it's a godsend, bridging the gap between the ubiquity of Java and the speed and usability of native windows APIs. And thanks to Mono,
And as for MS being insecure...well, those products "hit in the last 6 months" were all patched prior to the outbreak. Look it up, if you want to be informed. The difficulty there is an uninformed public and/or lazy IT staff. If you don't apply your OpenSSL patches, your Linux or BSD system will be pretty insecure, too.
I needed to open a Passport account to get content on my Verizon phone.
Once I did, it opened the doors to tons of content I didn't give a shit about. I just wanted to delete all the useless bookmarks they shove in there.
So...your proposed spam solution is an MX record???
What's your solution to pop up ads...the off switch?
Dude, if steps 1, 2 and 3 make money, you don't need an intermediary "???" step to attain Profit.
/., but I understand it's pretty big elsewhere.
We call this alternate model "Business." It's not so popular on
+1, .Insightful
That's an excellent theory you have. Eugenics as an anti spam tool.
Actually, domain registrars are getting paid to be a responsible party keeping people from squatting on domains they have no rights to and enforcing correct contact information.
They're just not doing it very well, because they make so LITTLE money off each domain it doesn't pay to do so. And who demanded $10 domain names?