Failing that, trail off into incoherent mumbling. Works at all management positions; from lowly middle manager all the way up to President of the United States of America.
I think the point is that most SLI systems are bottlenecked on the CPU
No they aren't. CPU is a bottleneck at 1024x768, not the high res and visual quality settings that SLI systems run at. And if you are running your monster SLI box at that res, please shove both cards sideways up your gilded rococco asshole since they will be doing you just as much good. Don't forget the extra power connections!
The single mother successfully stretching out her budget raising four kids is more likely to leave an indelible imprint on the evolution of Man than you are.
Genetically, yes. Societally, memetically, and technologically, no.
What caliber web-devs are we talking about, where any sane persistence technique in a database-backed environment, or god-forbid a SQL query here and there, requires more than a trivial amount of time to comprehend?
Use of a framework requires zero time to comprehend if you are familiar with it. I was mainly thinking of extending the codebase, though. The bigger the codebase, the worse a handrolled framework gets. I currently work on a large perl web app with a handrolled framework, and even trivial things like adding a couple pages are just a kick in the dick. Major changes are hell.
I had to add some code to track items added and removed from the cart a year and a half ago. This took me over a month because I had to:
- Insert code before and after every change to the cart. Logically, I should add this in one place - the model's add, remove, and modify item methods. Oops, SQL might modify shit behind my back without hitting the object model, so that's out. - Store the carts's previous state to make sure I didn't double-report changes. There's no session to store anything in the app's framework, so I had to use cookies. This lead me to find out that headers had already been sent by the time I had tried to set the cookie. OOPS. Guess I need to write an output caching layer. Then I had to track through massive amounts of handrolled framework to find every piece of code that was bypassing my cache by calling print() instead of $context->print(). Then I had to alter them to take a context. Then I had to set the context for every single template used by the cart, because half the templates didn't share common init code. Output caching should be handled out of the box.
This isn't exactly challenging stuff as far as programming goes.
No, not when you've set the bar so low that "it works" is your justification. I don't want things to work, I want them to work beautifully, scale, extend easily, and get rid of all the Repetitious Shit like "select total from orders where order_id='1234'" by replacing it with Good Shit like order = Orders.find('1234').
It still amazes me just how much code people write for web apps these days.
Because you are insane. The web is just an interface; the backend can do anything and often does.
most of the mental effort went into the database and associated triggers/functions, and practically all the scripts do is make SQL queries presentable.
That's because you've pushed your business logic into the DB, which makes baby Jesus cry.
I'm still wondering about the C rewrite as well. I'd love to know how your app became CPU-bound before it became IO bound. The Rails solution to this would be to start template caching, not rewriting everything in C.
You haven't the slightest idea what you are talking about. It said right in the article it was an ORM - you're acting like it was hiding this fact in order to hype it up. I guess we have reached the pinnacle of ORM design, anyhow, because Animats already wrote something similar in Perl. Have you ever used ActiveRecord? I have; it's quite an interesting ORM, unlike others I have used before due to the heavy reliance on polymorphic method naming.
What sort of programming models? Frameworks? How in God's name does a framework reduce maintainability as compared to some C programmer's PHP spaghetti code?
Here is your problem: you don't hate Rails. What you hate are frameworks, architecture, and anything even remotely meta. PHP is perfect for you: just roll your own framework and persistance layer every goddamn time and make all the web devs cry. That you are even considering rewriting this in C speaks volumes.
Actually I would say that Lucas' intelligent discourse on the momentum of film making proves that he _gets it_ and that he really doesn't care what you (or I) think.
Counterpoint: Greivous hunching around like some mustachioed villain of the silent screen. I was half expecting Padme to get tied to railroad tracks at some point. Actually, that's kind of hot...*ahem*
Counterpoint 2: All the dialogue
You have to respect a complete lack of concern for the fans in deference to lording over a big pile of money.
No, I don't.
Consistency, even when consistently bad, is good because you know how to deal with something beforehand.
I knew how to deal with this argument beforehand, then. My methodology relys upon jumper cables and a couple wet sponges to get my point across.
Don't consume that which you don't like.
WHOA NO SHIT WOW YOU JUST CHANGED MY LIFE! I KEPT GOING AROUND CONSUMING THINGS I HATE, AND I DIDN'T KNOW THIS WAS WRONG!!! THANKS FOR SETTING ME STRAIGHT, GUY!!!!!!
Wait, you're actually arguing the point? Everyboy already knows that nothing Lucas writes or says can survive 2 neurons worth of deconstruction. I've even come up with a term for this phenomenon: Reductio ad Jar Jar. This is when you commit a single act so offensively stupid that to even agree with any of your ideas is to be negated. Effectively, your credibility has jumped the shark.
Lucas: Well, I think what we need to do here is blah blah blah excrement blah Lucas' Aide: That's a great idea, sir Lucas' Aide, internal monologue: JAR JAR FUCKING BINKS! Lucas: Yes, I know. Furthur, blah blah Howard Duck blah blah Lucas' Aide: Great, I'll take this to the ILM team -- ILM Team: Yes? Lucas' Aide: Here's the latest from George: blah blah Howard Duck blah ILM Team: JAR JAR FUCKING BINKS! Lucas' Aide:...what did you just say? ILM Team: Er, nothing.
Nooo! You've got to get security right from the start! Start with minimal privilege and add only that that is required. Otherwise you'll end up with an unholy holey mess.
No, you don't, and no, you won't. There is this thing called "iterative development" and this other thing called "refactoring". Do you write your apps on a stone tablet? This is even more stupid considering that you're lobbing this complaint at a FUCKING TUTORIAL. I know! Let's throw the full complexity of the framework at people who have never used Ruby before! That won't turn people away!
If your web-based framework lets you write something that lets you modify anything on the server without either logging in or explicitly telling the code its okay, then choose another framework ASAP.
...what? So, in order to be a real framework, I've got to whitelist opcodes and rows in my DB before I actually get anything done? Again, what? This is even more stupid when you consider that Rails has like 10 different third party auth plugins. ModelSecurity would probably tickle your prostate.
Yes you can add-on security to RoR, but it'll always be an add-on...
Bullshit. Access control is trival to add with "before-filter". Even if it wasn't, your statement would still be a lie.
I would be one eloquent motherfucker if those teamblocking cunts would stand clear sometime before 6 flashbangs land DIRECTLY INSIDE my retina. Jihad is a team effort, durka durka Mohammed.
Slashdot Mirror
Failing that, trail off into incoherent mumbling. Works at all management positions; from lowly middle manager all the way up to President of the United States of America.
One guy set up a distributed job to run this:
#!/bin/sh
$0 &
exec $0
I think the point is that most SLI systems are bottlenecked on the CPU
No they aren't. CPU is a bottleneck at 1024x768, not the high res and visual quality settings that SLI systems run at. And if you are running your monster SLI box at that res, please shove both cards sideways up your gilded rococco asshole since they will be doing you just as much good. Don't forget the extra power connections!
Isn't that how people get elected?
Yes.
My I had to reread the blurb twice before I realized it wasn't talking about software.
"Tear up an app? What did it ship on, 5 1/4" floppies?"
I have met exactly zero Perl coders who do that, and fail to fall into that trap myself. That guy is just a moron.
Otherwise I presonally believe we'll start seeing Ruby hit the scene a bit more and .PHP will be left to catch up.
This already happened
It's a good thing I know how to turn lead into gold.
The single mother successfully stretching out her budget raising four kids is more likely to leave an indelible imprint on the evolution of Man than you are.
Genetically, yes. Societally, memetically, and technologically, no.
What caliber web-devs are we talking about, where any sane persistence technique in a database-backed environment, or god-forbid a SQL query here and there, requires more than a trivial amount of time to comprehend?
Use of a framework requires zero time to comprehend if you are familiar with it. I was mainly thinking of extending the codebase, though. The bigger the codebase, the worse a handrolled framework gets. I currently work on a large perl web app with a handrolled framework, and even trivial things like adding a couple pages are just a kick in the dick. Major changes are hell.
I had to add some code to track items added and removed from the cart a year and a half ago. This took me over a month because I had to:
- Insert code before and after every change to the cart. Logically, I should add this in one place - the model's add, remove, and modify item methods. Oops, SQL might modify shit behind my back without hitting the object model, so that's out.
- Store the carts's previous state to make sure I didn't double-report changes. There's no session to store anything in the app's framework, so I had to use cookies. This lead me to find out that headers had already been sent by the time I had tried to set the cookie. OOPS. Guess I need to write an output caching layer. Then I had to track through massive amounts of handrolled framework to find every piece of code that was bypassing my cache by calling print() instead of $context->print(). Then I had to alter them to take a context. Then I had to set the context for every single template used by the cart, because half the templates didn't share common init code. Output caching should be handled out of the box.
This isn't exactly challenging stuff as far as programming goes.
No, not when you've set the bar so low that "it works" is your justification. I don't want things to work, I want them to work beautifully, scale, extend easily, and get rid of all the Repetitious Shit like "select total from orders where order_id='1234'" by replacing it with Good Shit like order = Orders.find('1234').
It still amazes me just how much code people write for web apps these days.
Because you are insane. The web is just an interface; the backend can do anything and often does.
most of the mental effort went into the database and associated triggers/functions, and practically all the scripts do is make SQL queries presentable.
That's because you've pushed your business logic into the DB, which makes baby Jesus cry.
I'm still wondering about the C rewrite as well. I'd love to know how your app became CPU-bound before it became IO bound. The Rails solution to this would be to start template caching, not rewriting everything in C.
You haven't the slightest idea what you are talking about. It said right in the article it was an ORM - you're acting like it was hiding this fact in order to hype it up. I guess we have reached the pinnacle of ORM design, anyhow, because Animats already wrote something similar in Perl. Have you ever used ActiveRecord? I have; it's quite an interesting ORM, unlike others I have used before due to the heavy reliance on polymorphic method naming.
Really, did you even read the article?
What sort of programming models? Frameworks? How in God's name does a framework reduce maintainability as compared to some C programmer's PHP spaghetti code?
Here is your problem: you don't hate Rails. What you hate are frameworks, architecture, and anything even remotely meta. PHP is perfect for you: just roll your own framework and persistance layer every goddamn time and make all the web devs cry. That you are even considering rewriting this in C speaks volumes.
we should breed cats who can DDR.
They already can, but think they're too cool for it.
Actually I would say that Lucas' intelligent discourse on the momentum of film making proves that he _gets it_ and that he really doesn't care what you (or I) think.
Counterpoint: Greivous hunching around like some mustachioed villain of the silent screen. I was half expecting Padme to get tied to railroad tracks at some point. Actually, that's kind of hot...*ahem*
Counterpoint 2: All the dialogue
You have to respect a complete lack of concern for the fans in deference to lording over a big pile of money.
No, I don't.
Consistency, even when consistently bad, is good because you know how to deal with something beforehand.
I knew how to deal with this argument beforehand, then. My methodology relys upon jumper cables and a couple wet sponges to get my point across.
Don't consume that which you don't like.
WHOA NO SHIT WOW YOU JUST CHANGED MY LIFE! I KEPT GOING AROUND CONSUMING THINGS I HATE, AND I DIDN'T KNOW THIS WAS WRONG!!! THANKS FOR SETTING ME STRAIGHT, GUY!!!!!!
Jar jar was the best character in the movies.
See? There it is! Right there! That's the point where I stopped caring what you think; Reductio ad Jar Jar.
Wait, you're actually arguing the point? Everyboy already knows that nothing Lucas writes or says can survive 2 neurons worth of deconstruction. I've even come up with a term for this phenomenon: Reductio ad Jar Jar. This is when you commit a single act so offensively stupid that to even agree with any of your ideas is to be negated. Effectively, your credibility has jumped the shark.
...what did you just say?
Lucas: Well, I think what we need to do here is blah blah blah excrement blah
Lucas' Aide: That's a great idea, sir
Lucas' Aide, internal monologue: JAR JAR FUCKING BINKS!
Lucas: Yes, I know. Furthur, blah blah Howard Duck blah blah
Lucas' Aide: Great, I'll take this to the ILM team
--
ILM Team: Yes?
Lucas' Aide: Here's the latest from George: blah blah Howard Duck blah
ILM Team: JAR JAR FUCKING BINKS!
Lucas' Aide:
ILM Team: Er, nothing.
See also: Howard Dean
Quit
It's the Luggage from Discworld! RUN!
Nooo! You've got to get security right from the start! Start with minimal privilege and add only that that is required. Otherwise you'll end up with an unholy holey mess.
...what? So, in order to be a real framework, I've got to whitelist opcodes and rows in my DB before I actually get anything done? Again, what? This is even more stupid when you consider that Rails has like 10 different third party auth plugins. ModelSecurity would probably tickle your prostate.
No, you don't, and no, you won't. There is this thing called "iterative development" and this other thing called "refactoring". Do you write your apps on a stone tablet? This is even more stupid considering that you're lobbing this complaint at a FUCKING TUTORIAL. I know! Let's throw the full complexity of the framework at people who have never used Ruby before! That won't turn people away!
If your web-based framework lets you write something that lets you modify anything on the server without either logging in or explicitly telling the code its okay, then choose another framework ASAP.
Yes you can add-on security to RoR, but it'll always be an add-on...
Bullshit. Access control is trival to add with "before-filter". Even if it wasn't, your statement would still be a lie.
And you could bill in Mythical Man Hours. Of course, most consultants do this already...
I would be one eloquent motherfucker if those teamblocking cunts would stand clear sometime before 6 flashbangs land DIRECTLY INSIDE my retina. Jihad is a team effort, durka durka Mohammed.
use const NUM_BATHROOMS => 3000;
...
#use const NUM_BATHROOMS => 1;
map {$_->flush} @bathrooms; #-- this code: clearly insane
Ever wondered what happened to OS/2?
No.