> So it's not [Guido's] problem that [Python] sucks.
Were your parents eaten by Python or something? Calm it down a notch! Here's some facts about the projects that I know something about:
sgmllib was built into the Python 2 (which I mention in case you thought it was an external library). It existed solely to be used by the HTMLParser module, and as such it never fully supported SGML, making it useless for its stated purpose. Moreover, it's so absurdly trivial to port to Python 3 that I did it for the feedparser project.
BeautifulSoup relied on HTMLParser, which relied on sgmllib. That could be overcome but the author, Leonard Richardson, doesn't enjoy working on BeautifulSoup:
Beautiful Soup is a hobby that I don't really enjoy and that's similar to the work I do all day. It's competing against other hobbies and committments I have, hobbies and committments that are more enjoyable and significantly different from my day job.
He also notes that BeautifulSoup has been surpassed by other libraries, and recommends using those instead. It's no reflection on Python 3 that a library you used to use is not in active development.
I ported feedparser to Python 3 over the course of a week. It weren't no thang.
> If you're using Python for anything important, start working on your exit strategy.
I'm sorry Python made you cry, but I really do bristle that you hoisted up feedparser to support your sarcasm and hyperbole, particularly since you clearly have no idea what you're talking about in these three instances (and I think GooberToo handily dealt with some of your other points).
No cigar. For whatever advantages it may have, NoSQL's tradeoff is that it's only eventually consistent. You can't update the database and get nationwide replication immediately.
Come to think of it, maybe they're already using a NoSQL database. That'd explain why that guy was added to the no fly list over the Atlantic. He was probably blacklisted well in advance, but the database wasn't updated until he was already on the plane.
OP is correct, people will likely go with whatever is suggested by the government, even given the chance to review and modify it. Dan Ariely points out this effect in the context of organ donor percentages across multiple nations in his TED talk. I also think that Intuit is, though admittedly biased, correct (at least insofar as the company was quoted correctly in the summary).
But what I want to know is, by what metric do you determine the average case? 95% of the time the government's calculations are accurate? 99%? 99.9%? The census.gov Population Clock estimates that there are 308 million people in the United States, and the Bureau of Labor and Statistics currently claims that the employment-population ratio is 58 percent, which I assume translates to about 179 million people who'll be paying income taxes.
If the error rate is 1%, just short of 2 million people will have to correct mistakes in their government-provided taxation proposals. If the error rate is 0.1%, it'll be just shy of 200,000 people.
I agree in principal that taxes could be streamlined, but I would want to see some hard numbers after a trial run before deciding that the government was doing a good job (and I would want to see a comparison with the current error rate, as well as hard numbers on the Intuit-assisted error rate).
The resource isn't "Not Found", it's "Gone". HTTP 404 is inappropriate in this instance.
Likely the best solution will be to ensure that people are notified first. If you're receiving a large number of hits, replace the content with a single RSS item that has a guaranteed-unique guid for every single request (say, based on the request time). This way, with each request, people will receive a "new" item that will display as unread, reminding them to unsubscribe from that particular feed.
After some amount of time, start returning HTTP 410 for all requests.
Re:When I think about the internet in 1996
on
Jurassic Web
·
· Score: 1
Obviously he was referring to Winamp HTML playlists being the first five pages of hits while searching Excite or Dogpile for your favorite artist/song.
I'm really surprised that with all the users they had, they are so quick to say "everything is gone and we're giving up"
Considering how complete and unrecoverable the loss is, they have no idea who their users are. The accounts would have to be recreated from scratch, but who would try? Their users have no reason to ever trust them again. Journalspace would have a difficult time wooing back their original users, and no new user would seriously consider using them.
Bowing out is the only recourse, but I'm glad they're considering releasing their source code.
OpenID works thusly: You tell a site that you are "JimBob" of "random URL".
Wrong. You tell a site "I am in control of random URL". That's it. That's all. OpenID only does authentication, not identification, and its authentication is based solely on control over a particular URL.
So, when are we going to see smart and innovative desktops that dramatically improve user friendliness?
Just as some examples:
As an end-user why can't I extend applications by simply thinking things into existence? i.e. Dragging and dropping Blender into Gaim?
I have 1000s of photographs and I hate metadata. Why can't my computer automatically recognize people's faces and group the photos accordingly? Why can't it analyze the hairstyles and figure out when the photo was taken, and why can't it automatically scan the photos for logos and figure out where the photo was taken?
I have 1000s of mp3s and I hate metadata. Why can't my software use voice recognition to figure out the lyrics and then create a playlist using a Bayesian filter? I can filter spam out of my inbox, I should be able to filter ARTIST UNKNOWN out of my GENRE UNKNOWN playlist!
These are some of the type of things that would make using a computer more like using deep black magic.
Are open source desktop developers so focused on trying to make it "easy" for Windows users to convert they get Microsoft tunnel vision and can't innovate?
It's the year 2007 and I want my computer to be more like the computers in the sci-fi movies I saw in the early 80's.
It's a problem of manpower. My understanding is that there was a sudden and unexpected number of Gnome documentation people who were unable to contribute as they have in the past, which is what prompted this post by Quim Gil calling for help.
> I couldn't figure out, for the life of me, how to access those folders.
The guy appears to not know how to use checkboxes. Look at the dialog he includes in his screenshots: the dialog from Novell includes subscription buttons and checkboxes, while the dialog he was seeing only had checkboxes.
I think both of your outcomes hinge on the assumption that the patent is granted. Besides, do we really need anymore proof that the patent system is seriously b0rked?
The rel attribute is designed to specify a forward relationship with the current document. Google broke that when they proposed 'nofollow' (a nice idea that does not appear to have solved the spam problem except for Google's spidering of blogs). Further, you can't add it to images and paragraphs and everything else this guy is envisioning. The rel attribute is only applicable to a and link tags, and to use it otherwise deviates from the XHTML spec.
Slashdot Mirror
> A good hat dog is as illusive as it is tasty.
That's a fact, but it can be a head cover or food, not both!
> Ah, denial
Cool intro, bro!
> So it's not [Guido's] problem that [Python] sucks.
Were your parents eaten by Python or something? Calm it down a notch! Here's some facts about the projects that I know something about:
BeautifulSoup relied on HTMLParser, which relied on sgmllib. That could be overcome but the author, Leonard Richardson, doesn't enjoy working on BeautifulSoup:
He also notes that BeautifulSoup has been surpassed by other libraries, and recommends using those instead. It's no reflection on Python 3 that a library you used to use is not in active development.
I ported feedparser to Python 3 over the course of a week. It weren't no thang.
> If you're using Python for anything important, start working on your exit strategy.
I'm sorry Python made you cry, but I really do bristle that you hoisted up feedparser to support your sarcasm and hyperbole, particularly since you clearly have no idea what you're talking about in these three instances (and I think GooberToo handily dealt with some of your other points).
OP clearly has an agenda.
> How about checking within seconds of an update?
No cigar. For whatever advantages it may have, NoSQL's tradeoff is that it's only eventually consistent. You can't update the database and get nationwide replication immediately.
Come to think of it, maybe they're already using a NoSQL database. That'd explain why that guy was added to the no fly list over the Atlantic. He was probably blacklisted well in advance, but the database wasn't updated until he was already on the plane.
OP is correct, people will likely go with whatever is suggested by the government, even given the chance to review and modify it. Dan Ariely points out this effect in the context of organ donor percentages across multiple nations in his TED talk. I also think that Intuit is, though admittedly biased, correct (at least insofar as the company was quoted correctly in the summary).
But what I want to know is, by what metric do you determine the average case? 95% of the time the government's calculations are accurate? 99%? 99.9%? The census.gov Population Clock estimates that there are 308 million people in the United States, and the Bureau of Labor and Statistics currently claims that the employment-population ratio is 58 percent, which I assume translates to about 179 million people who'll be paying income taxes.
If the error rate is 1%, just short of 2 million people will have to correct mistakes in their government-provided taxation proposals. If the error rate is 0.1%, it'll be just shy of 200,000 people.
I agree in principal that taxes could be streamlined, but I would want to see some hard numbers after a trial run before deciding that the government was doing a good job (and I would want to see a comparison with the current error rate, as well as hard numbers on the Intuit-assisted error rate).
I agree, it's time to switch to the Unix password entry scheme. No feedback is good feedback!
Intel announced yet another delay for Tukwila, the next generation Itanium
Please tell me that's not an actual product name. (apologies)
The resource isn't "Not Found", it's "Gone". HTTP 404 is inappropriate in this instance.
Likely the best solution will be to ensure that people are notified first. If you're receiving a large number of hits, replace the content with a single RSS item that has a guaranteed-unique guid for every single request (say, based on the request time). This way, with each request, people will receive a "new" item that will display as unread, reminding them to unsubscribe from that particular feed.
After some amount of time, start returning HTTP 410 for all requests.
> force a bunch of stupid "notes" down the show-runner's throat ("Hey, can you bring in a sassy robot?
Hey, Bender made Futurama!
The editors gave a hat tip to Anonymous Coward?!
Obviously he was referring to Winamp HTML playlists being the first five pages of hits while searching Excite or Dogpile for your favorite artist/song.
...and a grammar checker. Its a shame.
Considering how complete and unrecoverable the loss is, they have no idea who their users are. The accounts would have to be recreated from scratch, but who would try? Their users have no reason to ever trust them again. Journalspace would have a difficult time wooing back their original users, and no new user would seriously consider using them.
Bowing out is the only recourse, but I'm glad they're considering releasing their source code.
The Fireman Music's website is actually hosting downloads of their music in Flash video files; you can download them from here:
The Fireman Music download section
I posted this exact quote on my tumblelog back in 2007, but I still laugh out loud every time I read it for the first time.
Wrong. You tell a site "I am in control of random URL". That's it. That's all. OpenID only does authentication, not identification, and its authentication is based solely on control over a particular URL.
I pay for and highly recommend Mailtrust. They've treated me very well.
Of course you can shoot them. You just have to fit the minimum requirements to mount a successful Geek defense.
> Disclaimer: I am not American, so I possibly don't know enough about your constitution.
Don't worry about it. Most of us Americans don't know enough about our constitution either.
Which means that he's right.
So, when are we going to see smart and innovative desktops that dramatically improve user friendliness?
Just as some examples:
These are some of the type of things that would make using a computer more like using deep black magic.
Are open source desktop developers so focused on trying to make it "easy" for Windows users to convert they get Microsoft tunnel vision and can't innovate?
It's the year 2007 and I want my computer to be more like the computers in the sci-fi movies I saw in the early 80's.
> Good thing we've got our priorities straight.
It's a problem of manpower. My understanding is that there was a sudden and unexpected number of Gnome documentation people who were unable to contribute as they have in the past, which is what prompted this post by Quim Gil calling for help.
> I couldn't figure out, for the life of me, how to access those folders.
The guy appears to not know how to use checkboxes. Look at the dialog he includes in his screenshots: the dialog from Novell includes subscription buttons and checkboxes, while the dialog he was seeing only had checkboxes.
> good that the BBC has given equal time to the major alternatives
I use Amiga 4.0 you insensitive clod!
I think both of your outcomes hinge on the assumption that the patent is granted. Besides, do we really need anymore proof that the patent system is seriously b0rked?
The rel attribute is designed to specify a forward relationship with the current document. Google broke that when they proposed 'nofollow' (a nice idea that does not appear to have solved the spam problem except for Google's spidering of blogs). Further, you can't add it to images and paragraphs and everything else this guy is envisioning. The rel attribute is only applicable to a and link tags, and to use it otherwise deviates from the XHTML spec.