All of my criteria? None. That's my point. There is no technology that doesn't deserve its share of criticism.
(Actually, asking people what their preferred tools' most important drawbacks are is generally a good litmus test for their competence. If they can't tell you what the pitfalls are and how to work around them, or why they don't affect the task at hand, watch out.)
Simply, some tools are a better match than others for any given task.
For instance, I think that PHP makes for a good, simple and effective templating language.
But of course, there's a world of difference between 'HTML templating' and 'development, deployment and ongoing maintenance of a Web site or set of sites.'
And no, I'm not going to tell you what I personally favor for the tasks in question in this thread. That's not the point. What matters is not the tools I favor, but WHY I favor them. It is important that you figure out for yourself what makes for a suitable tool, from your own experience, because that's how you'll know how to make the best use of that tool, and what to watch for.
The next, much trickier step, is to figure out where your own blind spots are, and learn to take them into account when making your choices. (Mine, for instance, tend to involve underestimating the importance of community support -- a point where PHP, incidentally, scores high.)
I hope I'm not sounding too patronizing here (I'm not very good at finding the right tone in online forums). I'm no better than any other computer dude who's had to deal with a wide set of technologies and their respective fans. But I learnt what I did thanks to other people sharing their experience, and I can only hope that, by sharing my views on what I think really matters at heart, I can help others broaden their own experience. The first step toward learning, after all, is recognizing that there's stuff you need to learn.
Your comment pisses me off, but there's something I want to say all the same: I think you are, essentially, right. Whatever one's woes with PHP might be, they don't justify trolling and unsubstantiated mouthing off. Besides, "toy language" is a purely inflammatory statement that doesn't even have any factual content.
However.
However, the implicit underlying assumption I think I perceive in your comment -- that PHP criticism must be trolling -- annoys me a lot. Please allow me to expand on this.
You see, one constant characteristic of the Internet in general is the noise. Look here on Slashdot: do you read all the comments on any given story?
The noise is a bigger problem than you'd think. The noise means that it's hard to get heard. It means that to be heard, unless you're a remarkable writer (which I, and most people, aren't), you have to exaggerate your message. "PHP is a toy language" is one such exaggeration; and perhaps even actually worthy of being modded up if followed with factual information to support it. And much likelier to catch a moderator's attention with its use of strong language.
Which you would, undoubtedly, consider a troll all the same, wouldn't you?
As you can probably guess by now, I have crates of such information against PHP. (In my defense, I do try hard to gather evidence against my own tools of choice as well, for two reasons. One, being aware of their own idiosyncrasies allows me to work better with them. Two, it's a simple matter of intellectual honesty.)
The vagaries of life have landed me into a managerial-ish position in a small company that develops and hosts large-scale PHP websites. My responsibility here is twofold: ensuring that the sites work, and ensuring that they keep working.
I didn't know PHP before joining this company; I had a generally positive opinion of it beforehand, from reading Slashdot. So I got to discover it through that new role.
Let us just say, to put it mildly, that my opinion of PHP has quickly become very poor.
I think that managing a language's design and development is one of those jobs that's freaking damn hard. It takes a LOT of experience, critical thinking, introspection, knowing to prioritize issues, knowing to tap into the decades of experience in language design to understand what works and what doesn't, why, and in what context. And different people with different backgrounds and objectives are more or less successful with it.
And I don't feel the people behind PHP -- I'm sorry, guys, I don't know how to put it nicely... -- are doing the best possible job of it.
More precisely, my primary issue with PHP is its culture as a project. Cultures are inherently difficult to describe, but if I had to put it in a few words, I'd call it the "Works for me" culture.
Simply put, the sort of attitude that PHP seems to encourage -- by which I mean, the shortest-path-to-arrival approach to doing most things in PHP -- work fine for the developper producing the code, but are formally broken in a way that WILL come back to bite the ass of whomever poor dude is in charge of keeping the thing working.
For instance: I understand PHP uses a function based on the tolower() C call to make method calls case insensitive, and leaves it at it. It works for them, doesn't it? Except that in the real world, it breaks. Deploying PHP sites on servers that use a Turkish locale yields blank pages. The workaround is to never use that particular locale. Easy, isn't it? No, it isn't: PHP's gettext functions for dynamic translation require the locale to be set appropriately (unlike that of other languages). And I have my Turkish clients on the phone a lot.
Until recently, before the introduction of PDO, the canonical native way of addressing databases was to use PHP functions named after the database itself (mysql_*, etc, making the process of migrating databases, or creating a site that may have to be deployed client-side on varying database backends, an utte
Funny indeed! You may however want to note that the Qt-based Krita painting program does actually implement a good number of those things that GIMP has been missing for years: CMYK, layer groups, displacement layers. AND an interface that all fits in one window (although you can also make it work like GIMP if you want, your choice). Even though Krita has a LOT less developpers than the GIMP. I know the history of GTK+ full well, and I like its newest themes and widget styles a hell of a lot, but if at this point it has become a programming liability... History be damned: DITCH IT. Seriously.
Okay... If this was detected in a quasar, and, as I understand it, quasars are insanely far away, with the implication that what we see of them happened insanely long ago... Is it possible that, as I think I once read here on Slashdot, some cosmological constants may really be variables that shift very slowly as the universe ages, and that MECOs were thus possible then, but no longer are?
Just askin', and my apologies if this is a stoopid question.
I believe PyQt will let you render widgets into an OpenGL context without complaint. OpenGL is but one of the rendering backends that it supports. At any rate, you might want to ask on the PyQt mailing-list; people there are exceedingly competent. Hope this helps, and have fun!
Funny you should mention it...
on
Married In Oblivion
·
· Score: 4, Interesting
In Morrowind, you could actually get yourself a girlfriend, and as close to married as you'll get in that game. After meeting and befriending her, then doing a few personal things for her, she ends up giving you the key to her house in Pelagiad, which becomes yours for all intents and purposes. As far as I can remember, there's only one bed in that house, but so long as you don't mind catgirls that shouldn't be an issue.:)
Please excuse me if I'm asking something stupid, but does this relate with the Heim theory? I recently a very interesting paper about its possible use in space propulsion, but I can't tell if this article is about the same thing, not being much of a physicist.:)
I was pleasantly surprised to see KDE developpers rally to GNOME's cause, or at least, advocate the use of GNOME for those for whom it works, regardless of their own opinion. Both DEs are there to stay and the sooner people accept this, the sooner we can build a strong integration layer and move on toward world domination. (Which is why the GNOME people really should get rid of Ximian and its DE fundamentalists if they want to make any progress, by the way -- at least until Ximian gets out of their corporate-love funk and re-learn the OSS virtues of collaboration...)
First of all, I'd say you might be overestimating how much news outlets care for their reputations against bribing, because there are many, many ways to bribe, and whether some qualify as actual bribing is entirely subjective. Does peddling to the Slashdot mindset to get a news about your product on the frontpage count as bribing? Should it? What I mean here is, people can and will easily rationalize a bribe into something more acceptable. That's people for you, you know.
Secondly, companies take a much bigger risk trying to bribe a large array of individuals than another company. A news outlet can't easily make noises about having refused one particular bribe without the implication that they might have accepted others in the past being raised. While an individual has nothing to lose in making a lot of noise about the bribe attempt. All it takes is a few honest people among the targetted crowd. Those exist, too.
Otherwise, you do have a point about individuals being cheaper. Hell, many will be bought by pride alone, especially where technical choices are concerned.
Hello, meet the KDE Free Qt Foundation, founded in 1998 exactly to prevent this kind of problem. In case Trolltech ownership changes and tries to snatch Qt from under our feet, Qt goes BSD-license by contractual agreement.
This being said, much as I like Qt from an engineering point of view, and have appreciated my contacts with the Trolls so far, I don't know what to make of that IPO. This might be a good time to sit back and watch and wait.
Actually, you are wrong. What they put in milk is not vitamin D, but its precursor. Your body still needs sunlight to process that precursor into vitamin D (which is why the very name of vitamin D is a bit of a misnomer, actually).
Why don't they put the real thing in milk, then? Because vitamin D is pretty darn expensive, while its precursor is cheap enough, and it's not like people can tell the difference anyway.
Linux _desperately_ needs to have a working, easy to use RAD environment.
I think that the KDevelop IDE already allows for true RAD in Python and Ruby (with an embedded GUI designer that ties into the editor functions), but if you want a VB workalike without the VB idiosyncrasies, give Gambas a go. It's about to reach 1.0, and seems to work really darn well, from what testing I've subjected it to.
No link per se. I just tried it with Konqueror 3.3.1's own user agent -- I just have to make GMail 'sign in anyway' -- and it worked. There are still a few glitches here and there, note, but it does work. It may be you'll have to authorize redirections (Settings > Web behavior > Allow automated reloading/redirecting), if you turned that off.
Here are the CVS logs of the fixes, dating from early October. As you can see, the fixes have indeed been backported to the 3.3 branch.
Also, I think there -is- a hack to load ActiveX's in Konqueror; I read about it ages ago, and I don't remember much about it, except that it actually seemed to work, but I just wouldn't think of it if I were you, frankly.:)
GMail has been working with Konqueror for a little while. As of version 3.3.1, I believe. You still have to either spoof your user agent, or force GMail to accept Konqueror, though, I believe.
What would be wrong with simply developing any specific package management system?
Portage is great, alright -- in particular, the possibility to pick your own choice of dependencies (like, ALSA but no OSS, SDL backend but no svgalib...) and have it respected all through the system, is the greatest thing since sliced bread.
And with binary packages, you lose that possibility. Unless you provide as many packages as there are possible choices. Good luck.
Besides, if you mix binary packages from different sources, you also get the problem of programs compiled against different specs/glibc version than the libs they end up linking to on your system. The good old third-party RPM recipe for crash.
It's an old problem, and there still isn't any clear solution in sight. Even in distros with the most painstakingly maintained package repository, like Debian, you'll generally need to recompile software to your own needs (support this or that DB backend that your company requires, add ACL support, etc...).
There are only two paths toward solving this class of issues, to my (non exhaustive -> grain of salt, please) knowledge:
1) Somehow provide an API, perhaps glibc-wise, that will allow to disable the relevant paths of code at runtime if the required library runtime is not available. Yeah, I know about dlopen. No, that's not workable. dlopen needs to be designed around. What we'd need would be something as easily managed as #define _HAVE_SDL, only at runtime. There is no way to ensure its adoption if you don't make it as efficient to use as possible.
2) Agree on a common set of libraries -- think DirectX, only system-wide, not just for games -- and have programs 1) depend on the required version of that LinuX set of libs, and 2) ship with what libs they need that aren't in it. The good thing is, if you define a given LinuX version as, simply, an empty package depending on a set of libraries with precise versions and compilation options, each distro can use its own package management to handle it. This is not without drawbacks, though. How do you handle security updates? (Ebuild-like revisions might work, admittedly...) And, just how BIG would any given LinuX-x.y be?
We may never see a smoothly working universal Linux dependency management system, I realize. Still, it's good that there are still possibilities to think of. Perhaps, someday...
My main gripe with other window managers is the inability to set the "Initial Workspace" (virtual desktop) per application.
My main gripe with Slashdoters is they don't look up data to validate their opinions.:)
In KWin, any window setting can be saved on a per application basis -- and that includes which virtual desktop it starts on. And I agree it's extremely useful. Some of my apps I want on all the desktops automatically, some I want borderless and always under the other windows (to keep an eye on logs for instance), etc. One of the little things you just can't live without once you've started using it.
This being said, WMaker still kicks serious loads of ass, and it's cool to see it keep improving steadily.
I tested the spoof vulnerability in Konqueror 3.3.1 (the latest).
When displaying the popup, it 1) switched back to the tab that owns it, and 2) the popup clearly contained the server name "secunia.com".
I was about to call this unhealthy sensationalism, but I haven't checked out older versions. Can anyone confirm the vulnerability in 3.3.0 and older? Thanks.
I think you may not be getting the exact point of this contest.
The thing is that many, many people have velleities of writing novels. Only, it remains a "one day" thing, as in, "one day, I'll write a novel..."
What this contest does is simply provide 1) a community of people suffering the same woes as you at the same time, for mutual encouragement, and 2) a hard deadline.
That's *it*.
It's not about writing something good. The F.A.Q. explicitely states that in one little month, all you'll have time to write is, likely, crap. No time far background checks. No time for procrastinating, hesitating between plot twists. No time for complexity. And it's okay. It's not about writing anything worth publishing. It's about starting to write, and then keeping writing until it's done.
It is really cool that you could write and publish something out of your own will. This contest is for those who haven't been able to. Yet.
And maybe those who pass the finish line will take the rest of the year to polish their work, and have it published. Some have.
Once you have an actual novel under your belt, no matter how bad, writing another, maybe better one, feels a lot more doable.
And while your comment is all in all not wrong, don't let your own admirable experience misjudge the purpose of this contest. Most people simply don't feel able to produce novel-sized writing. After trying this, they will know they can. And it makes a world of difference.
I am having the exact same joe-jobbing problem, and it seems I'm not the only one. Do you still have the scripts used to post the bounces to the support form of the spamvertised websites? I think many of us would be vastly grateful for them. Thanks.
Slashdot Mirror
All of my criteria? None. That's my point. There is no technology that doesn't deserve its share of criticism.
(Actually, asking people what their preferred tools' most important drawbacks are is generally a good litmus test for their competence. If they can't tell you what the pitfalls are and how to work around them, or why they don't affect the task at hand, watch out.)
Simply, some tools are a better match than others for any given task.
For instance, I think that PHP makes for a good, simple and effective templating language.
But of course, there's a world of difference between 'HTML templating' and 'development, deployment and ongoing maintenance of a Web site or set of sites.'
And no, I'm not going to tell you what I personally favor for the tasks in question in this thread. That's not the point. What matters is not the tools I favor, but WHY I favor them. It is important that you figure out for yourself what makes for a suitable tool, from your own experience, because that's how you'll know how to make the best use of that tool, and what to watch for.
The next, much trickier step, is to figure out where your own blind spots are, and learn to take them into account when making your choices. (Mine, for instance, tend to involve underestimating the importance of community support -- a point where PHP, incidentally, scores high.)
I hope I'm not sounding too patronizing here (I'm not very good at finding the right tone in online forums). I'm no better than any other computer dude who's had to deal with a wide set of technologies and their respective fans. But I learnt what I did thanks to other people sharing their experience, and I can only hope that, by sharing my views on what I think really matters at heart, I can help others broaden their own experience. The first step toward learning, after all, is recognizing that there's stuff you need to learn.
Urbanradar,
Your comment pisses me off, but there's something I want to say all the same: I think you are, essentially, right. Whatever one's woes with PHP might be, they don't justify trolling and unsubstantiated mouthing off. Besides, "toy language" is a purely inflammatory statement that doesn't even have any factual content.
However.
However, the implicit underlying assumption I think I perceive in your comment -- that PHP criticism must be trolling -- annoys me a lot. Please allow me to expand on this.
You see, one constant characteristic of the Internet in general is the noise. Look here on Slashdot: do you read all the comments on any given story?
The noise is a bigger problem than you'd think. The noise means that it's hard to get heard. It means that to be heard, unless you're a remarkable writer (which I, and most people, aren't), you have to exaggerate your message. "PHP is a toy language" is one such exaggeration; and perhaps even actually worthy of being modded up if followed with factual information to support it. And much likelier to catch a moderator's attention with its use of strong language.
Which you would, undoubtedly, consider a troll all the same, wouldn't you?
As you can probably guess by now, I have crates of such information against PHP. (In my defense, I do try hard to gather evidence against my own tools of choice as well, for two reasons. One, being aware of their own idiosyncrasies allows me to work better with them. Two, it's a simple matter of intellectual honesty.)
The vagaries of life have landed me into a managerial-ish position in a small company that develops and hosts large-scale PHP websites. My responsibility here is twofold: ensuring that the sites work, and ensuring that they keep working.
I didn't know PHP before joining this company; I had a generally positive opinion of it beforehand, from reading Slashdot. So I got to discover it through that new role.
Let us just say, to put it mildly, that my opinion of PHP has quickly become very poor.
I think that managing a language's design and development is one of those jobs that's freaking damn hard. It takes a LOT of experience, critical thinking, introspection, knowing to prioritize issues, knowing to tap into the decades of experience in language design to understand what works and what doesn't, why, and in what context. And different people with different backgrounds and objectives are more or less successful with it.
And I don't feel the people behind PHP -- I'm sorry, guys, I don't know how to put it nicely... -- are doing the best possible job of it.
More precisely, my primary issue with PHP is its culture as a project. Cultures are inherently difficult to describe, but if I had to put it in a few words, I'd call it the "Works for me" culture.
Simply put, the sort of attitude that PHP seems to encourage -- by which I mean, the shortest-path-to-arrival approach to doing most things in PHP -- work fine for the developper producing the code, but are formally broken in a way that WILL come back to bite the ass of whomever poor dude is in charge of keeping the thing working.
For instance: I understand PHP uses a function based on the tolower() C call to make method calls case insensitive, and leaves it at it. It works for them, doesn't it? Except that in the real world, it breaks. Deploying PHP sites on servers that use a Turkish locale yields blank pages. The workaround is to never use that particular locale. Easy, isn't it? No, it isn't: PHP's gettext functions for dynamic translation require the locale to be set appropriately (unlike that of other languages). And I have my Turkish clients on the phone a lot.
Until recently, before the introduction of PDO, the canonical native way of addressing databases was to use PHP functions named after the database itself (mysql_*, etc, making the process of migrating databases, or creating a site that may have to be deployed client-side on varying database backends, an utte
Ask and you shall receive. Warning, they are a LOT more addictive that they seem. :)
Funny indeed!
You may however want to note that the Qt-based Krita painting program does actually implement a good number of those things that GIMP has been missing for years: CMYK, layer groups, displacement layers. AND an interface that all fits in one window (although you can also make it work like GIMP if you want, your choice). Even though Krita has a LOT less developpers than the GIMP.
I know the history of GTK+ full well, and I like its newest themes and widget styles a hell of a lot, but if at this point it has become a programming liability... History be damned: DITCH IT. Seriously.
Okay... If this was detected in a quasar, and, as I understand it, quasars are insanely far away, with the implication that what we see of them happened insanely long ago... Is it possible that, as I think I once read here on Slashdot, some cosmological constants may really be variables that shift very slowly as the universe ages, and that MECOs were thus possible then, but no longer are?
Just askin', and my apologies if this is a stoopid question.
I believe PyQt will let you render widgets into an OpenGL context without complaint. OpenGL is but one of the rendering backends that it supports. At any rate, you might want to ask on the PyQt mailing-list; people there are exceedingly competent.
Hope this helps, and have fun!
In Morrowind, you could actually get yourself a girlfriend, and as close to married as you'll get in that game. After meeting and befriending her, then doing a few personal things for her, she ends up giving you the key to her house in Pelagiad, which becomes yours for all intents and purposes. As far as I can remember, there's only one bed in that house, but so long as you don't mind catgirls that shouldn't be an issue. :)
Okay, thank you for the interesting replies! :)
Please excuse me if I'm asking something stupid, but does this relate with the Heim theory? I recently a very interesting paper about its possible use in space propulsion, but I can't tell if this article is about the same thing, not being much of a physicist. :)
I was pleasantly surprised to see KDE developpers rally to GNOME's cause, or at least, advocate the use of GNOME for those for whom it works, regardless of their own opinion. Both DEs are there to stay and the sooner people accept this, the sooner we can build a strong integration layer and move on toward world domination. (Which is why the GNOME people really should get rid of Ximian and its DE fundamentalists if they want to make any progress, by the way -- at least until Ximian gets out of their corporate-love funk and re-learn the OSS virtues of collaboration...)
I think that you are right and you are wrong.
First of all, I'd say you might be overestimating how much news outlets care for their reputations against bribing, because there are many, many ways to bribe, and whether some qualify as actual bribing is entirely subjective. Does peddling to the Slashdot mindset to get a news about your product on the frontpage count as bribing? Should it? What I mean here is, people can and will easily rationalize a bribe into something more acceptable. That's people for you, you know.
Secondly, companies take a much bigger risk trying to bribe a large array of individuals than another company. A news outlet can't easily make noises about having refused one particular bribe without the implication that they might have accepted others in the past being raised. While an individual has nothing to lose in making a lot of noise about the bribe attempt. All it takes is a few honest people among the targetted crowd. Those exist, too.
Otherwise, you do have a point about individuals being cheaper. Hell, many will be bought by pride alone, especially where technical choices are concerned.
Hello, meet the KDE Free Qt Foundation, founded in 1998 exactly to prevent this kind of problem. In case Trolltech ownership changes and tries to snatch Qt from under our feet, Qt goes BSD-license by contractual agreement.
This being said, much as I like Qt from an engineering point of view, and have appreciated my contacts with the Trolls so far, I don't know what to make of that IPO. This might be a good time to sit back and watch and wait.
Actually, you are wrong. What they put in milk is not vitamin D, but its precursor. Your body still needs sunlight to process that precursor into vitamin D (which is why the very name of vitamin D is a bit of a misnomer, actually).
Why don't they put the real thing in milk, then? Because vitamin D is pretty darn expensive, while its precursor is cheap enough, and it's not like people can tell the difference anyway.
1) Open the minicli window in KDE (Alt+F2)
:)
2) Type in 'wp <term to look up>'
3) Prof-- err, Kencyclopedia!
You're welcome.
Linux _desperately_ needs to have a working, easy to use RAD environment.
I think that the KDevelop IDE already allows for true RAD in Python and Ruby (with an embedded GUI designer that ties into the editor functions), but if you want a VB workalike without the VB idiosyncrasies, give Gambas a go. It's about to reach 1.0, and seems to work really darn well, from what testing I've subjected it to.
Voulez-vous Cauchy avec moi? ;)
No link per se. I just tried it with Konqueror 3.3.1's own user agent -- I just have to make GMail 'sign in anyway' -- and it worked. There are still a few glitches here and there, note, but it does work. It may be you'll have to authorize redirections (Settings > Web behavior > Allow automated reloading/redirecting), if you turned that off.
:)
Here are the CVS logs of the fixes, dating from early October. As you can see, the fixes have indeed been backported to the 3.3 branch.
Also, I think there -is- a hack to load ActiveX's in Konqueror; I read about it ages ago, and I don't remember much about it, except that it actually seemed to work, but I just wouldn't think of it if I were you, frankly.
GMail has been working with Konqueror for a little while. As of version 3.3.1, I believe. You still have to either spoof your user agent, or force GMail to accept Konqueror, though, I believe.
Let me rephrase your question:
What would be wrong with simply developing any specific package management system?
Portage is great, alright -- in particular, the possibility to pick your own choice of dependencies (like, ALSA but no OSS, SDL backend but no svgalib...) and have it respected all through the system, is the greatest thing since sliced bread.
And with binary packages, you lose that possibility. Unless you provide as many packages as there are possible choices. Good luck.
Besides, if you mix binary packages from different sources, you also get the problem of programs compiled against different specs/glibc version than the libs they end up linking to on your system. The good old third-party RPM recipe for crash.
It's an old problem, and there still isn't any clear solution in sight. Even in distros with the most painstakingly maintained package repository, like Debian, you'll generally need to recompile software to your own needs (support this or that DB backend that your company requires, add ACL support, etc...).
There are only two paths toward solving this class of issues, to my (non exhaustive -> grain of salt, please) knowledge:
1) Somehow provide an API, perhaps glibc-wise, that will allow to disable the relevant paths of code at runtime if the required library runtime is not available. Yeah, I know about dlopen. No, that's not workable. dlopen needs to be designed around. What we'd need would be something as easily managed as #define _HAVE_SDL, only at runtime. There is no way to ensure its adoption if you don't make it as efficient to use as possible.
2) Agree on a common set of libraries -- think DirectX, only system-wide, not just for games -- and have programs 1) depend on the required version of that LinuX set of libs, and 2) ship with what libs they need that aren't in it. The good thing is, if you define a given LinuX version as, simply, an empty package depending on a set of libraries with precise versions and compilation options, each distro can use its own package management to handle it. This is not without drawbacks, though. How do you handle security updates? (Ebuild-like revisions might work, admittedly...) And, just how BIG would any given LinuX-x.y be?
We may never see a smoothly working universal Linux dependency management system, I realize. Still, it's good that there are still possibilities to think of. Perhaps, someday...
My main gripe with other window managers is the inability to set the "Initial Workspace" (virtual desktop) per application.
:)
My main gripe with Slashdoters is they don't look up data to validate their opinions.
In KWin, any window setting can be saved on a per application basis -- and that includes which virtual desktop it starts on. And I agree it's extremely useful. Some of my apps I want on all the desktops automatically, some I want borderless and always under the other windows (to keep an eye on logs for instance), etc. One of the little things you just can't live without once you've started using it.
This being said, WMaker still kicks serious loads of ass, and it's cool to see it keep improving steadily.
I tested the spoof vulnerability in Konqueror 3.3.1 (the latest).
When displaying the popup, it 1) switched back to the tab that owns it, and 2) the popup clearly contained the server name "secunia.com".
I was about to call this unhealthy sensationalism, but I haven't checked out older versions. Can anyone confirm the vulnerability in 3.3.0 and older? Thanks.
So that you can import a generic function that goes, for example, parse_stuff(some_string, flags) and then tack it onto a local class:And instances of that class can now call mystring.parse(self, someflags) and it just works, magically.
This is especially godsent for writing decent wrappers for C libraries.
But I agree that it remains an idiosyncrasy of the language, even if it happens to be a powerful one.
I think you may not be getting the exact point of this contest.
The thing is that many, many people have velleities of writing novels. Only, it remains a "one day" thing, as in, "one day, I'll write a novel..."
What this contest does is simply provide 1) a community of people suffering the same woes as you at the same time, for mutual encouragement, and 2) a hard deadline.
That's *it*.
It's not about writing something good. The F.A.Q. explicitely states that in one little month, all you'll have time to write is, likely, crap. No time far background checks. No time for procrastinating, hesitating between plot twists. No time for complexity. And it's okay. It's not about writing anything worth publishing. It's about starting to write, and then keeping writing until it's done.
It is really cool that you could write and publish something out of your own will. This contest is for those who haven't been able to. Yet.
And maybe those who pass the finish line will take the rest of the year to polish their work, and have it published. Some have.
Once you have an actual novel under your belt, no matter how bad, writing another, maybe better one, feels a lot more doable.
And while your comment is all in all not wrong, don't let your own admirable experience misjudge the purpose of this contest. Most people simply don't feel able to produce novel-sized writing. After trying this, they will know they can. And it makes a world of difference.
Here's what you can tell them:
"Firefox is what you get when people get together for the purpose to write the best possible software, rather than to make money."
This usually conveys the message pretty well, I found.
I am having the exact same joe-jobbing problem, and it seems I'm not the only one. Do you still have the scripts used to post the bounces to the support form of the spamvertised websites? I think many of us would be vastly grateful for them. Thanks.