1- installed a root kit on my In-laws machine through a Neil Diamond CD
The rootkit I can tolerate; we all have the occasional judgment lapse, right? But making your in-laws buy Neil Diamond... that, well, some things you just can't condone.
Now look at what you've done. Confusing the MySQL fanbois with performance figures for PostgreSQL not even closely resembling their world-view. How will this end...? The horror!
Imagine if I started throwing out numbers for selects with bitmap scans - their little heads would explode.:-)
Seriously, "PostgreSQL is slow" is about as current as "Slowaris" and the "17 minutes to copy a file" Mac troll. None of them have been true for years, if they ever were.
... because counting out 500 question marks to figure out why the hell your parameters don't match up is MUCH more fun than being paged at 3AM because the entire production database was wiped out.
In the Python DB-API, SQL strings look like:
select foo from bar where baz=%(baz)s
You create a dictionary (hash table) with a key "baz", pass that dict to the database along with your query, and it fills in the blanks. Your job as the programmer is to make sure that dict has all the keys in it to complete the query; it doesn't matter which order you assign them or if you don't use them all.
In fact, a very common case is to create on dict with all the values you'll need to execute a whole list of queries, and just keep passing the same dict rather than redoing it each time:
# I know this example is lame. sqlparams = { 'zipcode': '12345', 'lastname': 'smith' } cursor.execute('insert into customers (lastname) values (%(lastname)s)', sqlparams) cursor.execute('insert into locations (zipcode) values (%(zipcode)s)', sqlparams) cursor.execute('insert into shipments (lastname, zipcode) values (%(lastname)s, %(zipcode)s)', sqlparams)
It's about as easy as you can possibly make it and has no disadvantages that I've ever encountered. So, I'd take the position that it's better to protect the server and forget about old ideas like positional parameters. There are extremely programmer-friendly solutions to this problem if you know where to look.
There is also obviously the danger that some people might want to take this drug for cognitive boosting effects which would not be a good thing if it was not highly tested before hand.
Especially since it's "usually used to treat insomnia" (summary). There's not much use for an IQ of 180 if you're asleep.
There is no way in hell postgres can come close to 35k inserts/s.
You're wrong. My company has a huge legacy FoxPro database, but for performance reasons we copy most of its tables to PostgreSQL as an hourly cron job. One of those tables is just over 7 million rows and I can copy it into PostgreSQL is slightly less than 5 minutes. 7071473 rows in 287 seconds yields 24639 inserts/s, and this is on a production server answering other queries at the same time.
PostgreSQL 8.1.3, FreeBSD 6.1-STABLE, single Xeon, 3GB of RAM, one SCSI-320 drive, very little performance tuning. If we can hit 25K on that box, I have no doubt he can sustain 35K on beefier hardware.
When the telecommuter's NYC company gets a new bill from their ISP raising rates on their VPN, the company calls the Consumer Affairs department, the cops, the Attorney General, or some other government office, or their lawyer does.
You mean to tell me that where you live, if you change the price you charge for your services then you can expect to hear from Consumer Affairs, the cops, the AG, and other government offices?
I think I've identified the disconnect between our logic: You've been living around lawyers and politicians far too long for your own good.
The truth is that upstate many high-quality jobs *are* moving to other states due to high taxation, usually in areas where the loss of such jobs can further cripple an already devastated local economy.
The scary part is that many of the upstate residents think their taxes are perfectly reasonable. My father-in-law thinks it's awful that I have to pay for garbage pickup, since the city of Buffalo provides his for free. Never mind that he's paying twice the taxes on half the house that I am; that extra $2500 a year will go a long, long way toward covering a $20/month trash bill.
I never really understood this complaint. I live in the midwest. If I do some remote work for a client in New York, how do they expect to collect New York income tax from me? Do they have any legal recourse whatsoever to try to collect?
What if my local employer opens a branch office in NYC. Do I owe NY taxes then, even though I don't work there? What if I do some remote administration for that office? What if they're connected via VPN and I occasionally browse fileservers on their LAN? At what point do I cross the line where they mistakenly think I should pay them something?
I'm glad to see this legislation go through, even though I think it's incredibly stupid that there's a need for it.
Apparently the Australian date for the DS Lite is June 1st, which is very odd as that's before the US release.
You Aussies always forget about the conversion rate; June 1st for you is mid-September for us. And don't get me started about how you always have your seasons backwards.
Good point, but then wouldn't we have the problem of trying to get everyone to suppy a wap._____.___?
If a company can't be bothered to spend 30 seconds to configure wap.example.com, they almost certainly won't go out of the way to register example.mobi.
No, because it's Yet Another Stupid ICANN't Proposition that almost nobody wants except for the people who'd like to sell names in that space.
File it next to ".museum" (handy for the 50 or so people using it) and ".jobs" (for companies who don't want job seekers to look at their real website), preferably in the big circular file next to your desk. I swear, it's amazing the lengths that ICANN't will go to in order to feel relevant and useful.
The most painful thing I do often is display apps running on remote machines with a slow link. Spend 5 minutes waiting for kmail to render, switch to another desktop, switch back, and wait another 5 minutes for it to re-render.
Does the functionality exist right now to fully buffer that window so that it doesn't have to completely redraw each time? It seems like the Composite extension would solve that problem, but it doesn't seem to be fully ready for production yet.
Since they managed to piss off almost everyone in the F/OSS community, the Changelog for XFree 4.6.0 has a lot of stuff like:
3.5.2. XFree86 core server and modules
Port of SBUS drivers to SunOS variants. This also allows for multihead using a mix of SBUS and PCI devices.
3.6.11. twm
Allow environment variables to be used in menu names.
3.6.10. xclock
Use the Xaw tooltip to display the date in xclock.
I mean, they make Debian/stable look like the very model of cutting-edge experimentation. You won't get any fancy XGL stuff, but if you need enhanced support for your Sun IPX running twm, xclock and xbiff - well, then, they're your go-to guys.
I'd like to say I wish them luck, but I don't really. They spent years doing their darnedest to alienate their talent pool and end users alike, and it wouldn't hurt my feelings to see that dog laid to rest.
When I was in Gamestop last week, the sales rep told me he had received many more people asking if they could reserve the PS3 than the Wii. Not only that, he claimed that a bunch of people were willing to put up the $600 now (plus some kickbacks to him) if they could get one promised the day it comes out.
If he wasn't lying, there's apparently a strong calling for it, at least in my neighborhood.
An alternate explanation: the would-be PS3 buyers want to profit off a likely shortage. I mean, wouldn't you like to have had a couple of 360s listed on eBay on premier day? I don't recall any huge Nintendo shortages in the recent past, so maybe people expect to be able to amble in to their local store on premier day and pick up a Wii for MSRP.
Was it really necessary to use gratuitous cussing on the front page? Hey, I did my time in the Navy: I promise you nothing I could see here is worse than what I heard on ship. But that seemed like a total non sequitur in this instance. Since neither a speaker nor a print source were being quoted, why put it there?
Zope calls a method named "customerlist" in the same directory (for our purposes here) and gets a list of dictionaries (Perl: hash tables) as results. Then, it loops across that list. For each row, it writes out a tr tag (without the "tal:" stuff), replaces the string "Jim" inside the first td tag with the value of the "firstname" key from that row, does the same for the "lastname" key, and closes the tr. If your method returns one row, Zope writes one row. If it returns 1,000, Zope writes 1,000.
But the beauty is that the marked up template is still valid HTML that can be edited in Dreamweaver or whatever it is your web design guys like. They can do whatever they want to it, as long as they leave the "tal:" stuff alone. Then you, the programmer, write the "customerlist" method that pulls from a database, fetches from an Active Directory server, parses out of an email - whatever you think is appropriate. You don't care how the web guys write the HTML, and they don't care how you write the code.
The real magic, though, is that any page on the site can call your "customerlist" method and mangle the output as it sees fit. If someone decides they want to see lastname come first, they just write the HTML; you don't touch a line of your code. Similarly, if you replace your MS-SQL backend with PostgreSQL, your web team doesn't even need to know. They just use the results without caring where they came from.
If you can't see why this is code reuse nirvana, you don't have a very good imagination. In theory, this works great. In practice, it's even better.
I'd agree with you - had I not been replying to a mailserver administrator with instructions on how people in that job can fight spam. I even said that they weren't really intended for "moron users" (your sentiment, not mine), but end users weren't relevant to the topic anyway.
Slashdot Mirror
The rootkit I can tolerate; we all have the occasional judgment lapse, right? But making your in-laws buy Neil Diamond... that, well, some things you just can't condone.
While that may be true, they're claiming to ship later this year. It's almost June - when are these mythical drivers going start to materialize?
Imagine if I started throwing out numbers for selects with bitmap scans - their little heads would explode. :-)
Seriously, "PostgreSQL is slow" is about as current as "Slowaris" and the "17 minutes to copy a file" Mac troll. None of them have been true for years, if they ever were.
In the Python DB-API, SQL strings look like:
You create a dictionary (hash table) with a key "baz", pass that dict to the database along with your query, and it fills in the blanks. Your job as the programmer is to make sure that dict has all the keys in it to complete the query; it doesn't matter which order you assign them or if you don't use them all.
In fact, a very common case is to create on dict with all the values you'll need to execute a whole list of queries, and just keep passing the same dict rather than redoing it each time:
It's about as easy as you can possibly make it and has no disadvantages that I've ever encountered. So, I'd take the position that it's better to protect the server and forget about old ideas like positional parameters. There are extremely programmer-friendly solutions to this problem if you know where to look.
Our brain is umami and sweet at the same time? Maybe zombies are just looking for low-calorie Oriental fare.
Especially since it's "usually used to treat insomnia" (summary). There's not much use for an IQ of 180 if you're asleep.
You're wrong. My company has a huge legacy FoxPro database, but for performance reasons we copy most of its tables to PostgreSQL as an hourly cron job. One of those tables is just over 7 million rows and I can copy it into PostgreSQL is slightly less than 5 minutes. 7071473 rows in 287 seconds yields 24639 inserts/s, and this is on a production server answering other queries at the same time.
PostgreSQL 8.1.3, FreeBSD 6.1-STABLE, single Xeon, 3GB of RAM, one SCSI-320 drive, very little performance tuning. If we can hit 25K on that box, I have no doubt he can sustain 35K on beefier hardware.
You mean to tell me that where you live, if you change the price you charge for your services then you can expect to hear from Consumer Affairs, the cops, the AG, and other government offices?
I think I've identified the disconnect between our logic: You've been living around lawyers and politicians far too long for your own good.
The scary part is that many of the upstate residents think their taxes are perfectly reasonable. My father-in-law thinks it's awful that I have to pay for garbage pickup, since the city of Buffalo provides his for free. Never mind that he's paying twice the taxes on half the house that I am; that extra $2500 a year will go a long, long way toward covering a $20/month trash bill.
The taxes from the NYC-based ISP.
Should it ever come up, remind me to get a local judgement against Bloomberg for some fictional fee.
As far as how your "locale" is determined - that's up to your employer.
OK, then. Is there any incentive for your employer to list you as a NY employee?
What if my local employer opens a branch office in NYC. Do I owe NY taxes then, even though I don't work there? What if I do some remote administration for that office? What if they're connected via VPN and I occasionally browse fileservers on their LAN? At what point do I cross the line where they mistakenly think I should pay them something?
I'm glad to see this legislation go through, even though I think it's incredibly stupid that there's a need for it.
You Aussies always forget about the conversion rate; June 1st for you is mid-September for us. And don't get me started about how you always have your seasons backwards.
If a company can't be bothered to spend 30 seconds to configure wap.example.com, they almost certainly won't go out of the way to register example.mobi.
No, because it's Yet Another Stupid ICANN't Proposition that almost nobody wants except for the people who'd like to sell names in that space.
File it next to ".museum" (handy for the 50 or so people using it) and ".jobs" (for companies who don't want job seekers to look at their real website), preferably in the big circular file next to your desk. I swear, it's amazing the lengths that ICANN't will go to in order to feel relevant and useful.
Does the functionality exist right now to fully buffer that window so that it doesn't have to completely redraw each time? It seems like the Composite extension would solve that problem, but it doesn't seem to be fully ready for production yet.
My understanding is that 7.x is identical to 6.9.x right now except for changes to the built system.
I mean, they make Debian/stable look like the very model of cutting-edge experimentation. You won't get any fancy XGL stuff, but if you need enhanced support for your Sun IPX running twm, xclock and xbiff - well, then, they're your go-to guys.
I'd like to say I wish them luck, but I don't really. They spent years doing their darnedest to alienate their talent pool and end users alike, and it wouldn't hurt my feelings to see that dog laid to rest.
Not necessarily.
If he wasn't lying, there's apparently a strong calling for it, at least in my neighborhood.
An alternate explanation: the would-be PS3 buyers want to profit off a likely shortage. I mean, wouldn't you like to have had a couple of 360s listed on eBay on premier day? I don't recall any huge Nintendo shortages in the recent past, so maybe people expect to be able to amble in to their local store on premier day and pick up a Wii for MSRP.
Was it really necessary to use gratuitous cussing on the front page? Hey, I did my time in the Navy: I promise you nothing I could see here is worse than what I heard on ship. But that seemed like a total non sequitur in this instance. Since neither a speaker nor a print source were being quoted, why put it there?
So install the AnkhSVN plugin to Visual Studio and demonstrate that the salesperson was lying through their teeth.
Please explain what's ingenious about taking an action based on user input.
No, really. Go ahead.
In general, I disagree. Zope use a page template language that works like this:
First, you write plain HTML:
Let your design guys work on it until it looks pretty. Then you embed template code into the HTML:
Zope calls a method named "customerlist" in the same directory (for our purposes here) and gets a list of dictionaries (Perl: hash tables) as results. Then, it loops across that list. For each row, it writes out a tr tag (without the "tal:" stuff), replaces the string "Jim" inside the first td tag with the value of the "firstname" key from that row, does the same for the "lastname" key, and closes the tr. If your method returns one row, Zope writes one row. If it returns 1,000, Zope writes 1,000.
But the beauty is that the marked up template is still valid HTML that can be edited in Dreamweaver or whatever it is your web design guys like. They can do whatever they want to it, as long as they leave the "tal:" stuff alone. Then you, the programmer, write the "customerlist" method that pulls from a database, fetches from an Active Directory server, parses out of an email - whatever you think is appropriate. You don't care how the web guys write the HTML, and they don't care how you write the code.
The real magic, though, is that any page on the site can call your "customerlist" method and mangle the output as it sees fit. If someone decides they want to see lastname come first, they just write the HTML; you don't touch a line of your code. Similarly, if you replace your MS-SQL backend with PostgreSQL, your web team doesn't even need to know. They just use the results without caring where they came from.
If you can't see why this is code reuse nirvana, you don't have a very good imagination. In theory, this works great. In practice, it's even better.
I'd agree with you - had I not been replying to a mailserver administrator with instructions on how people in that job can fight spam. I even said that they weren't really intended for "moron users" (your sentiment, not mine), but end users weren't relevant to the topic anyway.