and undoubtedly plenty of people who excel at FPS but would rather not be bothered by the hacks and cheats and immature behavior that flourishes in so many of the multiplayer venues,
Of course
so confine most of their playtime to the single-player games and/or maps.
Here is where you jump off the deep end. Being good at single player is enough to get you "noob" status online. Nobody who can play at a decent level limits themselves to single player because it would be like Kasparov playing against a 4th grader.
Cheers! This has to be one of the best geek jokes I've seen on Slashdot. My own (recycled from the first article) was that it should be easy to crack the case. Hans never does anything without writing it down first.
I fucking hate a world in which this study has to be done. Here is how much I hate marketing: Last night, at the bar, super hot promoter chick comes over to pass out free vodka. I physically recoiled. Yes, I hate marketing more than I love super hot chicks giving me free vodka.
Oh good, positional arguments. Who decides the order?
Whee, more bashing. The developer decides the order when they call set_primary_keys.
They're not positional in the database...
Yes, they are. A "select * from..." always returns columns in the same default ordering.
The internals of Perl are old. Over the years, they've come to be fairly full-featured and quite speedy... but they're 10 years old. Any piece of software that organically grows for 10 years is going to become a maintenance nightmare, and that's the state of perl right now. Hence it's time for a rewrite.
So, it isn't technologically superior, then. You don't throw superior technology out and replace it with new tech borrowing all sorts of ideas from your competitors.
Lastly, why is any of this stuff an "OOPS"?
The "OOPS" was directed at your statement of Perl's superiority in relation to it being thrown out and rewritten. Obliquely stated, sorry.
If Perl 5 was technologically superior, as the guy I was arguing with stated, nothing would need to be borrowed. I never said or implied that stealing ideas from Haskell is a bad thing - I think quite the opposite. We agree, you're just misinterpreting what I said.
Actually, I once wrote an ActiveX component in perl that talked to a Java server (which I also wrote) via XML diff. The diff itself was also XML. Java was great for the combo of XML processing and heavy networking support that I needed. NIO had just come out, otherwise I would have been forced to use C++.
If you want to talk of language I use daily, I'm more of a Perl guy than anything else. I'd be much happier using Ruby or Python or Haskell or whatever, though, as I am sick of writing $this->{shit} = [qw(oh god the pain)];
Follow the argument. The GP said that Perl was technically superior. I countered with the fact that Perl is doing a huge rewrite and taking a bunch of ideas from Haskell. This is not a slight against Haskell, which I would describe first and foremost as "thought-proviking"; it is, instead, proof against the imagined technological superiority of Perl 5. Perhaps I was not clear: the "OOPS" was meant to be taken against the statement of technological superiority, not the use Haskell.
The only Rails guy I see routinely mouthing off is DHH. Most of his invective (that I've read) is aimed at Java, though, which is a mitigating factor. J2EE is easy to bash because you'll be right most of the time.
I maintain a 35KLOC+ mod_perl web app. Not including the templates. It manages to be more readable than a great deal of the PHP I've come into contact with. I really don't think readability is a strong point for either language, anyhow. Perl's reference semantics are ass, and PHP lends itself to not separating the view from the controller.
As the linked article said, this is an experimental patch + hack.
That blog post was from when the plugin was first released. It has been under active development for months and could easily become part of the standard distro if DHH didn't have such a huge bug up his ass about composite primary keys.
With DBIC, you just do find({key1 => $val1, key2 => $val2}), which is a natural extension of the simple single-key case: find({key1 => $val1}). This all works very well in practice, as opposed to the it-might-work approach of ActiveRecord.
Standard activerecord find:
ModelName.find val1
Composite plugin find:
ModelName.find val1, val2
OH SHIT, THAT TOTALLY DIDN'T FIT INTO THE ORIGINAL DESIGN! Also: the syntax is ten times more elegant than your Perl example.
I'm not saying you shouldn't use ActiveRecord... but I wouldn't use it.
So, you admit to being full of shit and self-contradictory, then?
Bashing? I said it was good. There are some places where Catalyst is better, and some places where it's not as good. In my experience, Catalyst's good points make more complex applications easier (frontend to an HR system is what I've done), whereas Rails full-stack approach is great for CRUD applications. You're allowed to like both, ya know!
Perhaps you could, I don't know, explain why you think Catalyst is better? Rails being full stack does not count as a valid assertion of either superiority or inferiority; all it means is that Rails distributes everything together.
These people (I'm one of them) get upset because their languages are technically better than the alternatives,
Yeah, it's so technically better that gradual extension of the language was stopped in favor of a full redesign and 10 years of labor on a new VM. OOPS. The new language features? Taken from Haskell. The only functional implementation at the moment? Written in Haskell. OOPS.
but "nobody" uses them, and they're shunned for not using PHP. "Perl is so 1996, man, use PHP or Ruby now." Irritating. use Perl;;)
There are still more Perl jobs out there than Python or Ruby. At least we can agree that PHP is a hateful language. Actually, hating PHP is just about the only thing you can get a majority consensus on from programmers across the language spectrum.
Any time I see a Rails vs. Django comparison, which is quite often, half of the Python users have their nose hiked 90 degrees into the air. They're maybe half as bad as the Lisp community (which rates a full centidijkstra in arrogance). I don't represent this as being scientific fact, but it is exactly what I have observed.
I don't think PHP merits being put on the command line, even if it were cleaned up. Instead of mod_perl, you'd just have a grotty Perl dialect without CPAN and, really, Perl itself is already deprecated. I only use it at work because I have to. All my personal projects are done in Ruby or Haskell. I'd probably be using Python, too, if the users I routinely run into on the net weren't such zealots.
PHP's niche in the web ecosystem is as "the stupid, easy to host scripting language". If you forked it like that, you'd basically have mod_perl, and everyone would still be using the original, awful PHP.
Also, if you'd like to access a database with compound primary keys, ActiveRecord won't support that, but Catalyst's ORM (DBIx::Class) supports it fine.
Rails is good for quick apps like a wiki or a blog, but for more complicated internal applications, Catalyst is where it's at.
I am hesitant to try any framework whose partisans routinely bash other frameworks. I'm used to getting this from Python; it's refreshing to see a Perl guy screaming at the wind.
That assumes that there aren't any quirks in the IT departments' design of the company network, systems, or policies, that any quirks are already documented, that the dev's system doesn't have any bugs, and that the dev's testing environment is completely equivalent to the production environment.
This is why we have something called a QA department
Re:It's nice for little things.
on
Rails Recipes
·
· Score: 1
You're annoyed by having to modify 3 files; your opinion does not count. You say compiled code is better, then cite Java, PHP, and.NET, all of which run on a VM; your opinion does not count. You prefer PHP; your opinion does not count, you have no taste, and you're insane.
Slashdot Mirror
Of course
Here is where you jump off the deep end. Being good at single player is enough to get you "noob" status online. Nobody who can play at a decent level limits themselves to single player because it would be like Kasparov playing against a 4th grader.
I saw 75% given as a number by the head dev maybe a week ago. Not quite ready for prime time.
If they were blaming this on anything other than Sarbanes-Oxley or HIPAA, I wouldn't believe them.
Or just warez oracle once onto an 8-way smp
There are lies, damned lies, and software specs.
It's Waldo. Obviously.
Cheers! This has to be one of the best geek jokes I've seen on Slashdot. My own (recycled from the first article) was that it should be easy to crack the case. Hans never does anything without writing it down first.
I fucking hate a world in which this study has to be done. Here is how much I hate marketing: Last night, at the bar, super hot promoter chick comes over to pass out free vodka. I physically recoiled. Yes, I hate marketing more than I love super hot chicks giving me free vodka.
If Perl 5 was technologically superior, as the guy I was arguing with stated, nothing would need to be borrowed. I never said or implied that stealing ideas from Haskell is a bad thing - I think quite the opposite. We agree, you're just misinterpreting what I said.
Actually, I once wrote an ActiveX component in perl that talked to a Java server (which I also wrote) via XML diff. The diff itself was also XML. Java was great for the combo of XML processing and heavy networking support that I needed. NIO had just come out, otherwise I would have been forced to use C++.
If you want to talk of language I use daily, I'm more of a Perl guy than anything else. I'd be much happier using Ruby or Python or Haskell or whatever, though, as I am sick of writing $this->{shit} = [qw(oh god the pain)];
Follow the argument. The GP said that Perl was technically superior. I countered with the fact that Perl is doing a huge rewrite and taking a bunch of ideas from Haskell. This is not a slight against Haskell, which I would describe first and foremost as "thought-proviking"; it is, instead, proof against the imagined technological superiority of Perl 5. Perhaps I was not clear: the "OOPS" was meant to be taken against the statement of technological superiority, not the use Haskell.
-1? Wow, I thought my winning the argument with LOGIC would have negated a troll mod.
The only Rails guy I see routinely mouthing off is DHH. Most of his invective (that I've read) is aimed at Java, though, which is a mitigating factor. J2EE is easy to bash because you'll be right most of the time.
I maintain a 35KLOC+ mod_perl web app. Not including the templates. It manages to be more readable than a great deal of the PHP I've come into contact with. I really don't think readability is a strong point for either language, anyhow. Perl's reference semantics are ass, and PHP lends itself to not separating the view from the controller.
That blog post was from when the plugin was first released. It has been under active development for months and could easily become part of the standard distro if DHH didn't have such a huge bug up his ass about composite primary keys.
Standard activerecord find: Composite plugin find: OH SHIT, THAT TOTALLY DIDN'T FIT INTO THE ORIGINAL DESIGN! Also: the syntax is ten times more elegant than your Perl example.
So, you admit to being full of shit and self-contradictory, then?
Perhaps you could, I don't know, explain why you think Catalyst is better? Rails being full stack does not count as a valid assertion of either superiority or inferiority; all it means is that Rails distributes everything together.
Yeah, it's so technically better that gradual extension of the language was stopped in favor of a full redesign and 10 years of labor on a new VM. OOPS. The new language features? Taken from Haskell. The only functional implementation at the moment? Written in Haskell. OOPS.
There are still more Perl jobs out there than Python or Ruby. At least we can agree that PHP is a hateful language. Actually, hating PHP is just about the only thing you can get a majority consensus on from programmers across the language spectrum.
Any time I see a Rails vs. Django comparison, which is quite often, half of the Python users have their nose hiked 90 degrees into the air. They're maybe half as bad as the Lisp community (which rates a full centidijkstra in arrogance). I don't represent this as being scientific fact, but it is exactly what I have observed.
I don't think PHP merits being put on the command line, even if it were cleaned up. Instead of mod_perl, you'd just have a grotty Perl dialect without CPAN and, really, Perl itself is already deprecated. I only use it at work because I have to. All my personal projects are done in Ruby or Haskell. I'd probably be using Python, too, if the users I routinely run into on the net weren't such zealots.
PHP's niche in the web ecosystem is as "the stupid, easy to host scripting language". If you forked it like that, you'd basically have mod_perl, and everyone would still be using the original, awful PHP.
Bullshit
I am hesitant to try any framework whose partisans routinely bash other frameworks. I'm used to getting this from Python; it's refreshing to see a Perl guy screaming at the wind.
This is why we have something called a QA department
You're annoyed by having to modify 3 files; your opinion does not count. You say compiled code is better, then cite Java, PHP, and .NET, all of which run on a VM; your opinion does not count. You prefer PHP; your opinion does not count, you have no taste, and you're insane.
Yes. A 3000$ MacBook Pro.
...or you can just go into Quicktime's config and disable the startup option. You don't get that same feeling of beating The Man, though.
Actually, I take that back. There's this new robotic police officer we've been working on...