Does Class::Std really have problems under mod_perl? Is that under Apache 2 or 1.3.x? That would be too bad. Class::Std really does address so much of what Perl 5 doesn't do for encapsulation. It looks, probably not coincidentally, that some of its thinking is reflected in Perl 6 design (like painless creation of accessor methods).
Are there other ways of accomplishing the same thing using inside-out objects without Class::Std? I'm not easily guessing exactly where the problem lies - though I suppose the overriding of some stuff in UNIVSERAL might do it?
AC says: "You have it exactly backwards. Farming, right out of the gate, is a more reliable way of getting food. If it wasn't, it never would have caught on, and we'd all still be out in the jungle trying to throw pointed sticks at wild boars."
Be careful. If farming's more reliable at preventing, say, a whole tribe from extinction and increasing its overall size, farming passes evolutionary muster. That doesn't mean life isn't, overall, shorter and nastier for most of the individuals in it. They might be able, for example, to feed more children - indeed, need them - to keep this whole farming pyramid scheme going. But with diseases and a social structure that demands stratification - chiefs to count grain, soldiers to steal grain from other tribes and repel invaders - you might need those extra little hands to weed and feed chickens so you don't all starve.
So, yes, farming had to yield some benefits immediately, but benefiting the gene pool as a whole could still mean overall suckage (shorter, nastier lives) for the majority of individuals in the system.
I thought that the most interesting idea in Guns, Germs & Steel was the suggestion that writing was primarily an invention designed to steal from the farmer class. In fact, if you look at the main things social conservatives of all religions are "for", it amounts to supporting this stone age social structure. Have lots of kids, be fearful of your lord, keep the young folks locked up until they can be indoctrinated in the system, don't question any of this or we'll knock the shit out of you. Actually, large parts of the world still work this way.
I wouldn't say your average 3rd world farmer is better off than a stone age hunter-gatherer. But I am.
Yeah, now those programmers have to go back to writing monolithic incomprehensible procedures stuck inside java classes and/or PHP programs loaded with thousands of "echo" statements and no encapsulation of anything, anywhere, ever.
I have never observed sucky programming to vary its frequency by language.
Actually, backwards compatiblity with Perl 5 is a key design feature. But looking at how Perl6 handles class members, accessors, methods, arguments, overloading, inheritance, etc, etc, it's clear that there's a lot to be excited about. It just makes programming easier and more powerful, without (like Java) swallowing the OO koolaid so uncritically that simple things are made hard because "classes good, operators bad".
Python is a nice language, but it suffers actively from design features that simply try to be unlike Perl - strip the "line noise" out, force tab indenting and what do you get? Opaque variables, hungarian notation, inconvenient editing, programming in widescreen. Whatever.
Yes, the word "fuck" was invented in 1958. Before then, no one ever swore. Not even at public executions or gang rapes during routine sacking by mercenaries. The world was such an innocent place back then.
Duh. People were not more sensitive. The smaller percentage of literate people (than today) were also more likely to be aristocratic types who had never seen bullshit, much less said it or shoveled it. So sensitive that they got all flush and dizzy just looking at something so racy as the legs of a piano.
for the past 6 years or so, i've switched browsers fairly regularly, say every 6 months or so. i've given the gnome contingent - what is it? galeon? epiphany? day late? whatever - short shrift, but i think with good reason (mozilla/firefox is usually the better solution).
personally, i find browsers trade the lead as "best" every so often. that's a Good Thing. but surprisingly, a number of things have remained fairly constant
Mozilla/Firefox is slow. particularly, it's kind of unresponsive when tabs are opening pages in the background. it's not terribly fast in any sense, but it has always done a good job of looking nice and installing decent fonts and rendering popular websites well. It's a memory hog.
Konqueror has been the opposite of the Mozilla camp. It's speedy-feeling, sometimes looks awkward or renders pages oddly, is definitely behind on javascript support, occasionally has suffered due to KDE-related constrictions on it's UI. But overall, it's agile, not slow, responsive, and good enough that i use it for daily browsing.
The gnome entry - galeon/ephiphany - is a slimmed down mozilla/firefox, but not in a good way. it's just minimal.
Opera has always been the fastest of the bunch by far. It's not Open Source. I've had to write scripts to translate my bookmarks out when switching back to another. So free-as-in-beer is a step up. Given that they make their cash off small platform use, i think that's good enough. It will remain in my repertoire. It taught the other browsers that faking identity is useful. The screen real estate given to adware was a big problem for me. No more.
Decently programmed websites do fine across the board. It's been a couple years since major websites look really bad on one or the other (excluding stupid ideas like the motley fool div popup). Shitty websites just suck; if they only look good on IE, they are like retail stores that punch every tenth customer in the face (inexcusably stupid).
Other notes: on FreeBSD, both Moz/FF do well with the linux flash plugin, and even Konqueror isn't hard to use these days. I hate flash but sometimes i need to see it.
WiMax looks like a good technology - but don't expect to usefully deploy it yrself unless you can afford the mucho bux0r to license the bands. And if you can't, expect vicious competition and/or poor results.
This will mostly be useful to folks in broadband-poor areas, period.
No, storing mail in a database is still stupid. Backups are now unnecessarily complicated. You have to write your own mail server rather than scaling up an existing one. Etc. But by all means, continue wanking.
You got that right. I have nothing against manipulating data files, personally. I used windowmaker for quite a long time. Still do when I'm running on battery power, sometimes. And even windowmaker had a decent graphical menu editor many years ago.
But meanwhile, KDE has added an automated menu updating tool that seems to find all my graphical programs, whether they are Gnome-ish or KDE or just plain old X, plus adds a number of terminal programs (e.g. lynx), and adds nice icons for them all.
Not really having used Gnome in years, I might be missing something, but... Recent Gnome additions also include a tool that looks a lot like KWallet.
As it stands... but this is a public beta. Google has so far shown - via gmail - that they will open things up, given time to do technical assurance. They could have a major SPIM problem if they aren't careful.
So I'm willing to be patient, not least because this could be the not-so-very-thin wedge in opening IM against proprietary systems. It could mean the usefullness - finally - of having myname@mydomain.dom for IM. So user@your-own-domain might finally become useful.
And if it doesn't turn out that way - if they lock up the protocol against open participation, in the end, I'll be among the first in line to call "betrayal".
But so far - third party clients work. GAIM works. Even though it isn't on their "clients" page, Kopete does work - with no nothing extra.
I'm willing to grant them time to figure out the anti-spim issues before going totally open on s2s. For now, the no-jabber-spim phenom is probably that no one thinks it worthwhile to bother. But if Google enters the game, signed certs for SSL-based s2s could - and probably should - become the norm. The next test would be: can the SSL cert-granting mechanisms live up to real attack pressure by spammers - not that this will be tested severely while zombie-sent email spam is profitable.
Well if you take a look a the geographic distribution of, say, pork in the highway bill - the Republicans win by 10,000 miles. They're building hundred million dollar bridges to nowhere for Alaska's Republican congress-cretin, and they are closing every army base north of the Mason-Dixon line.
Yes, back in 1937 the balance was the other way, and it probably stayed that way until, say, the early Reagan administration. It's tipped pretty hard since then, with both Reagan and Dubya presiding over record deficits. Dubya in particular, with Republican control of both houses, has no damn excuse.
So don't tell me "Republicans are the party of fiscal responsibility". That lie is a stinking corpse.
Don't get me started on what they've done for national security.
I have had a child with severe medical problems. Do you think I'd switch to VOIP or whatever? No freakin way. I have not one, but two "no electrical" telephones, because - what happens if she had a problem during a power outage? It's one of those circumstances where the reliability standards forced by monopoly status had a positive effect.
Still - if the power goes out, my GAS stove is useless. A relative just bought an "antique" plain old gas stove with no electronics. What does it do? It works. Why did they buy it? The circuit board on their 12 year old stove died, and of course the replacement part cost almost as much as a new stove.
Companies who make consumer devices have got to stop expecting best cases and start expecting worst cases. They've got to make devices that degrade gracefully, when possible.
ID has more problems than that. For one thing, this Intelligent Designer must be incredibly complex to be able to create such complexity - flawed or not - as we see in the Earth's creatures.
Surely, this Intelligent Designer didn't come from nowhere. This intelligent designer is so overwhelmingly complex, it must have been created by a super-creator, a sort of Intelligent-Designer Designer. And I.D^N = reductio ad absurdum.
It's a little premature to make these conclusions. Why don't you try using it and see what happens?
I know, I know, a venerable and reliable flamewar is about to die a cold, hell-frozen death. Don't worry - the MacTel is out there and I'll be surprised if it doesn't yield some new hunk of flamebait.
Of course they watered down the BSD license! It was getting used so much they were bound to run out if they didn't. You'll see; one day you'll be using the GPL, the next, you'll need twice as much to get high.
Uh duh. I checked/usr/src/COPYRIGHT and it looks like it's still full strength. Just not intended for internal use.
I think you make a good point about developing nations. Especially China and India, where there's enough intellectual capital and drive and interest for homegrown solutions (i.e. "our department's Linux install") to work. And China and India are maybe 35% of the world's population. Especially true in China, where native piracy and WTO acceptance will force their hand towards free software.
I also agree that the Apple move to Intel may be driven as much by developing markets as the chipmaker realities.
Mason rocks. It's got the "scripting language in a web page thing" which can be great, especially if you modularize your code so not too much is happening inside the Mason code. On the other hand, it's quite easy to write spaghetti of code and HTML, so PHP programmers should like it too.
Mason also has good control over execution phases - you can do things "once", "first", etc. Arguments are named (not positional), can be made optional, or given defaults - and this is easier than you can imagine (if you don't know why this is a good thing, you haven't done very much programming). You can also pass a Mason "component" formatting from the "outside" and let the "inside" take care of other logic. It makes caching things (like, say, a list of articles pulled from a database) as easy as it can possibly be (even worse than not pooling DB connections is not caching results when you can). It generally pushes you in the direction of good solutions.
But having used PHP, JSP, Perl with other templating systems, I prefer Mason by far. Mason uses Perl - no mini-languages here - and gives you access to the huge amount of stuff on CPAN - PEAR isn't there yet and won't be soon (and Java never will be).
careful with that analogy. as far as i know, in many places just carrying lock picks around for no obvious reason carries a presumption of criminal intent. professional locksmiths are, as far as i know, registered with authorities in most locations.
care to register that BitTorrent client with the feds?
regardless, if you look into this a little further, (like, actually read the linked article), you'll see that few, if any, of the projects are really netbsd-specific. for one thing, considering the amount of cross-fertilization between the BSDs these days, that would be unlikely. but "wide character support in curses" is hardly parochial.
And, some dummy previous poster was all "what's the google summer of code" and stuff, but there's links at the bottom of the article. whateva.
Its only a problem if they thumb their nose at the namespace thing and just blithely add tags in the "default". THEN they'll have pissed off a number of people. You mean "when", right? Or are you implying Longhorn might never be released?
Seriously, though, one can't criticize them for leaving open the the possibility of eXtending the eXtensible Markup Language. Not yet, anyway.
Slashdot Mirror
Have a nice day!
Are there other ways of accomplishing the same thing using inside-out objects without Class::Std? I'm not easily guessing exactly where the problem lies - though I suppose the overriding of some stuff in UNIVSERAL might do it?
Be careful. If farming's more reliable at preventing, say, a whole tribe from extinction and increasing its overall size, farming passes evolutionary muster. That doesn't mean life isn't, overall, shorter and nastier for most of the individuals in it. They might be able, for example, to feed more children - indeed, need them - to keep this whole farming pyramid scheme going. But with diseases and a social structure that demands stratification - chiefs to count grain, soldiers to steal grain from other tribes and repel invaders - you might need those extra little hands to weed and feed chickens so you don't all starve.
So, yes, farming had to yield some benefits immediately, but benefiting the gene pool as a whole could still mean overall suckage (shorter, nastier lives) for the majority of individuals in the system.
I thought that the most interesting idea in Guns, Germs & Steel was the suggestion that writing was primarily an invention designed to steal from the farmer class. In fact, if you look at the main things social conservatives of all religions are "for", it amounts to supporting this stone age social structure. Have lots of kids, be fearful of your lord, keep the young folks locked up until they can be indoctrinated in the system, don't question any of this or we'll knock the shit out of you. Actually, large parts of the world still work this way.
I wouldn't say your average 3rd world farmer is better off than a stone age hunter-gatherer. But I am.
I have never observed sucky programming to vary its frequency by language.
Python is a nice language, but it suffers actively from design features that simply try to be unlike Perl - strip the "line noise" out, force tab indenting and what do you get? Opaque variables, hungarian notation, inconvenient editing, programming in widescreen. Whatever.
Duh. People were not more sensitive. The smaller percentage of literate people (than today) were also more likely to be aristocratic types who had never seen bullshit, much less said it or shoveled it. So sensitive that they got all flush and dizzy just looking at something so racy as the legs of a piano.
Everyone else swore like motherfucking crazy.
for the past 6 years or so, i've switched browsers fairly regularly, say every 6 months or so. i've given the gnome contingent - what is it? galeon? epiphany? day late? whatever - short shrift, but i think with good reason (mozilla/firefox is usually the better solution).
personally, i find browsers trade the lead as "best" every so often. that's a Good Thing. but surprisingly, a number of things have remained fairly constant
- Mozilla/Firefox is slow. particularly, it's kind of unresponsive when tabs are opening pages in the background. it's not terribly fast in any sense, but it has always done a good job of looking nice and installing decent fonts and rendering popular websites well. It's a memory hog.
- Konqueror has been the opposite of the Mozilla camp. It's speedy-feeling, sometimes looks awkward or renders pages oddly, is definitely behind on javascript support, occasionally has suffered due to KDE-related constrictions on it's UI. But overall, it's agile, not slow, responsive, and good enough that i use it for daily browsing.
- The gnome entry - galeon/ephiphany - is a slimmed down mozilla/firefox, but not in a good way. it's just minimal.
- Opera has always been the fastest of the bunch by far. It's not Open Source. I've had to write scripts to translate my bookmarks out when switching back to another. So free-as-in-beer is a step up. Given that they make their cash off small platform use, i think that's good enough. It will remain in my repertoire. It taught the other browsers that faking identity is useful. The screen real estate given to adware was a big problem for me. No more.
Decently programmed websites do fine across the board. It's been a couple years since major websites look really bad on one or the other (excluding stupid ideas like the motley fool div popup). Shitty websites just suck; if they only look good on IE, they are like retail stores that punch every tenth customer in the face (inexcusably stupid).Other notes: on FreeBSD, both Moz/FF do well with the linux flash plugin, and even Konqueror isn't hard to use these days. I hate flash but sometimes i need to see it.
Long live choice.
WiMax looks like a good technology - but don't expect to usefully deploy it yrself unless you can afford the mucho bux0r to license the bands. And if you can't, expect vicious competition and/or poor results.
This will mostly be useful to folks in broadband-poor areas, period.
Beware impostors! I have at least one, by handle
Well, when you've made the filesystem obsolete, you just let us know.
You know, there are mail clients that index mailboxes. You know, parse, break out key data into little pieces, put it away in a little database file.
And anyone designing a mail system for 1,000,000 users who actually lets 100MB messages through needs to be put down like a foamy dog.
But go ahead, design a system for 1,000,000 users of Pine. That makes sense.
No, storing mail in a database is still stupid. Backups are now unnecessarily complicated. You have to write your own mail server rather than scaling up an existing one. Etc. But by all means, continue wanking.
You got that right. I have nothing against manipulating data files, personally. I used windowmaker for quite a long time. Still do when I'm running on battery power, sometimes. And even windowmaker had a decent graphical menu editor many years ago.
But meanwhile, KDE has added an automated menu updating tool that seems to find all my graphical programs, whether they are Gnome-ish or KDE or just plain old X, plus adds a number of terminal programs (e.g. lynx), and adds nice icons for them all.
Not really having used Gnome in years, I might be missing something, but... Recent Gnome additions also include a tool that looks a lot like KWallet.
Catch up much?
So I'm willing to be patient, not least because this could be the not-so-very-thin wedge in opening IM against proprietary systems. It could mean the usefullness - finally - of having myname@mydomain.dom for IM. So user@your-own-domain might finally become useful.
And if it doesn't turn out that way - if they lock up the protocol against open participation, in the end, I'll be among the first in line to call "betrayal".
But so far - third party clients work. GAIM works. Even though it isn't on their "clients" page, Kopete does work - with no nothing extra.
I'm willing to grant them time to figure out the anti-spim issues before going totally open on s2s. For now, the no-jabber-spim phenom is probably that no one thinks it worthwhile to bother. But if Google enters the game, signed certs for SSL-based s2s could - and probably should - become the norm. The next test would be: can the SSL cert-granting mechanisms live up to real attack pressure by spammers - not that this will be tested severely while zombie-sent email spam is profitable.
LA is not a city. It's an extremely large set of suburbs without a city to anchor them. There is, technically, a downtown, but no one ever goes there.
Well if you take a look a the geographic distribution of, say, pork in the highway bill - the Republicans win by 10,000 miles. They're building hundred million dollar bridges to nowhere for Alaska's Republican congress-cretin, and they are closing every army base north of the Mason-Dixon line.
Yes, back in 1937 the balance was the other way, and it probably stayed that way until, say, the early Reagan administration. It's tipped pretty hard since then, with both Reagan and Dubya presiding over record deficits. Dubya in particular, with Republican control of both houses, has no damn excuse.
So don't tell me "Republicans are the party of fiscal responsibility". That lie is a stinking corpse.
Don't get me started on what they've done for national security.
I have had a child with severe medical problems. Do you think I'd switch to VOIP or whatever? No freakin way. I have not one, but two "no electrical" telephones, because - what happens if she had a problem during a power outage? It's one of those circumstances where the reliability standards forced by monopoly status had a positive effect. Still - if the power goes out, my GAS stove is useless. A relative just bought an "antique" plain old gas stove with no electronics. What does it do? It works. Why did they buy it? The circuit board on their 12 year old stove died, and of course the replacement part cost almost as much as a new stove. Companies who make consumer devices have got to stop expecting best cases and start expecting worst cases. They've got to make devices that degrade gracefully, when possible.
ID has more problems than that. For one thing, this Intelligent Designer must be incredibly complex to be able to create such complexity - flawed or not - as we see in the Earth's creatures.
Surely, this Intelligent Designer didn't come from nowhere. This intelligent designer is so overwhelmingly complex, it must have been created by a super-creator, a sort of Intelligent-Designer Designer. And I.D^N = reductio ad absurdum.
It's a little premature to make these conclusions. Why don't you try using it and see what happens?
I know, I know, a venerable and reliable flamewar is about to die a cold, hell-frozen death. Don't worry - the MacTel is out there and I'll be surprised if it doesn't yield some new hunk of flamebait.
Uh duh. I checked /usr/src/COPYRIGHT and it looks like it's still full strength. Just not intended for internal use.
Will I see pictures of Natalie Portman?
I also agree that the Apple move to Intel may be driven as much by developing markets as the chipmaker realities.
Don't forget the BSDs in the server room, either.
Mason rocks. It's got the "scripting language in a web page thing" which can be great, especially if you modularize your code so not too much is happening inside the Mason code. On the other hand, it's quite easy to write spaghetti of code and HTML, so PHP programmers should like it too.
Mason also has good control over execution phases - you can do things "once", "first", etc. Arguments are named (not positional), can be made optional, or given defaults - and this is easier than you can imagine (if you don't know why this is a good thing, you haven't done very much programming). You can also pass a Mason "component" formatting from the "outside" and let the "inside" take care of other logic. It makes caching things (like, say, a list of articles pulled from a database) as easy as it can possibly be (even worse than not pooling DB connections is not caching results when you can). It generally pushes you in the direction of good solutions.
Check this article on Catalyst, too.
But having used PHP, JSP, Perl with other templating systems, I prefer Mason by far. Mason uses Perl - no mini-languages here - and gives you access to the huge amount of stuff on CPAN - PEAR isn't there yet and won't be soon (and Java never will be).
careful with that analogy. as far as i know, in many places just carrying lock picks around for no obvious reason carries a presumption of criminal intent. professional locksmiths are, as far as i know, registered with authorities in most locations.
care to register that BitTorrent client with the feds?
regardless, if you look into this a little further, (like, actually read the linked article), you'll see that few, if any, of the projects are really netbsd-specific. for one thing, considering the amount of cross-fertilization between the BSDs these days, that would be unlikely. but "wide character support in curses" is hardly parochial.
And, some dummy previous poster was all "what's the google summer of code" and stuff, but there's links at the bottom of the article. whateva.
Its only a problem if they thumb their nose at the namespace thing and just blithely add tags in the "default". THEN they'll have pissed off a number of people. You mean "when", right? Or are you implying Longhorn might never be released? Seriously, though, one can't criticize them for leaving open the the possibility of eXtending the eXtensible Markup Language. Not yet, anyway.