Definitely. But to be fair, we should make floating point operations like we make house-building operations, because the return values both have floors and ceilings.
You may recall from last week the news item concerning FunnyJunk's extortion...
Charles Carreon has filed suit in California court against Slashdot, alleging that an article appearing on the site defamed him by characterizing his lawsuit agains The Oatmeal as "extortion."
When reached for comment, Carreon stated, "They like to hide behind this claim that their content is all user-generated, but that certainly doesn't obviate their responsibility to... oh, fuck."
While the Dunning-Kruger effect may be thought of as related to the Peter Principle, I think Dunning-Kruger is more apt in describing this case.
While the Peter Principle is the observation that in hierarchical organizations, individuals tend to be promoted to the level of their own incompetence, Dunning-Kruger relates more broadly to the pattern that the less competent one is, the more likely one is to over-assess one's own level of knowledge or skill.
So what you're saying is that you rely on your own set of utilities developed in C, instead of using the tried-and-true, often secure and in some cases with more than one decade in deployment (as in -stable-) shell commands? And this is your counter-argument to why "rubyists" don't understand security?
No, that would be stupid. And we could do that in pure Ruby. The point of writing C extensions is to link the libraries and gain access to the function calls that the shell commands themselves invoke.
This was a system created by Rubyists. They don't understand security because that's a "low-level detail" they can't be arsed to learn.
Rubyists pay attention to low-level details. This is why we write C extensions rather than executing shell commands from web applications, which is asinine.
"Rails developers" are rarely Rubyists, properly speaking. This is one of the issues plaguing the Rails community. It could be worse, though. Rails developers can become Rubyists. In the PHP community, given that the preferred development methodology seems to be having two cats copulate on a keyboard, I don't hold much hope.
Not always... for our Rails (and Sinatra) projects, we use nginx as the frontend/static asset server to a (pool of) Ruby-based application servers (mostly Unicorn). There's no Apache anywhere in the mix, and that has greatly reduced my migraines. Perhaps in some situation it makes sense to have nginx as a cache engine or load balancer for Apache, but in my world, nginx usually replaces Apache, rather than supplementing it.
1) Hell yes, it's easier to configure than Apache. Has most of the plugins you could want from Apache, whilst being much more lightweight.
2) I'll echo the other comment here, YOU HAVE THE SOURCE CODE. Worry about backdoors in IIS from the U.S. Gov't., nginx has way more eyes on it.
3) You eventually figured out the pronunciation. Most of the people I know that use GNU/Linux and LaTeX ca't pronounce GNU or LaTeX, but they work great so they get used. What's the problem?
And you should absolutely do something about this. Unless GPL infringement is met with at least the threat of legal action, it will continue unchecked.
It is still PHP though so it won't force all your dev team to write better code as much as RoR will.
I sincerely hope this isn't being listed as a plus for using Cake. If "language/framework/methodology n forces me to write better code!" is ever heard as a complaint, the source of said complaint is in the wrong field.
That being said, Ruby and/or Rails doesn't force anyone to write better code. I have seen some crawling horrors perpetrated in Ruby that have kept me up nights. They do facilitate the writing of better code quite nicely. Whereas PHP doesn't do anybody any favors. Ever. PHP WTFs are generally of the "never sleep again" variety. The Cthulhu of WTFs.
If you have Ruby people on your team, use Rails (or Sinatra/Padrino if you need less magic). I say this only because the Rubyists are going to spend more time flogging any other language into behaving more like Ruby than on actual domain problems.
On the other hand, if you choose a PHP or Python-based framework, one of them might come up with a really handy gem that lets you generate PHP or Python code from Ruby, and you could blog about it.
Not even trying to start a flame war, I'm a Rubyist, I work with Rubyists, and this post is intended as Ha Ha Only Serious based on my experience.
Have you ever used zenmap (formerly nmapfe)? This is how a LOT of *nix GUIs work. They wrap a command-line utility, use the GUI to compose the argv, execute, and pipe the output to a buffer in the GUI itself, with the option to export that buffer to a file.
Slashdot Mirror
"Reports of my decline have been greatly exaggerated."
-- UNIX
Definitely. But to be fair, we should make floating point operations like we make house-building operations, because the return values both have floors and ceilings.
Obligatory:
Hey girl, the only way you're gonna keep my stack from overflowing is if you dereference my pointer.
I remember when we called this sort of thing "cowboy coding."
Now I feel so old, I'm imagining there were actual cowboys.
You may recall from last week the news item concerning FunnyJunk's extortion ...
Charles Carreon has filed suit in California court against Slashdot, alleging that an article appearing on the site defamed him by characterizing his lawsuit agains The Oatmeal as "extortion."
When reached for comment, Carreon stated, "They like to hide behind this claim that their content is all user-generated, but that certainly doesn't obviate their responsibility to... oh, fuck."
While the Dunning-Kruger effect may be thought of as related to the Peter Principle, I think Dunning-Kruger is more apt in describing this case.
While the Peter Principle is the observation that in hierarchical organizations, individuals tend to be promoted to the level of their own incompetence, Dunning-Kruger relates more broadly to the pattern that the less competent one is, the more likely one is to over-assess one's own level of knowledge or skill.
Sounds like Carreon to me.
Not that I would ever nitpick on /.
Neither can being an "Internet lawyer" with absolutely no understanding of the Streisand Effect.
I liked the one that was 'HideYourKids,HideYourWifi'.
Ironically, it was broadcasting hits SSID.
It's an extension to Ruby, written in C.
Often it's a "wrapper," in that it wraps a C function call. Either way, much safer (and far less idiotic) than shell invocations.
Nowadays we're using FFI more, though.
Fat models, skinny controllers, dumb views...
Oh, wait, are we not talking about code all of a sudden? Okay, in that case, dumb, skinny models, and no fat chicks.
In fact, forget I was here.
So what you're saying is that you rely on your own set of utilities developed in C, instead of using the tried-and-true, often secure and in some cases with more than one decade in deployment (as in -stable-) shell commands? And this is your counter-argument to why "rubyists" don't understand security?
No, that would be stupid. And we could do that in pure Ruby. The point of writing C extensions is to link the libraries and gain access to the function calls that the shell commands themselves invoke.
Are you even a programmer?
Maybe if ponies were the incentive offered, this would be a viable startup idea.
This was a system created by Rubyists. They don't understand security because that's a "low-level detail" they can't be arsed to learn.
Rubyists pay attention to low-level details. This is why we write C extensions rather than executing shell commands from web applications, which is asinine.
"Rails developers" are rarely Rubyists, properly speaking. This is one of the issues plaguing the Rails community. It could be worse, though. Rails developers can become Rubyists. In the PHP community, given that the preferred development methodology seems to be having two cats copulate on a keyboard, I don't hold much hope.
We're co-workers? Wow!
It's a small internet after all.
Unless SOPA/PIPA ever become law, in which case, goodbye Slashdot.
I'm so glad my router's SSID is 'serious business'. Because apparently that's what the internet is.
Not always... for our Rails (and Sinatra) projects, we use nginx as the frontend/static asset server to a (pool of) Ruby-based application servers (mostly Unicorn). There's no Apache anywhere in the mix, and that has greatly reduced my migraines. Perhaps in some situation it makes sense to have nginx as a cache engine or load balancer for Apache, but in my world, nginx usually replaces Apache, rather than supplementing it.
Amen, brother.
1) Hell yes, it's easier to configure than Apache. Has most of the plugins you could want from Apache, whilst being much more lightweight.
2) I'll echo the other comment here, YOU HAVE THE SOURCE CODE. Worry about backdoors in IIS from the U.S. Gov't., nginx has way more eyes on it.
3) You eventually figured out the pronunciation. Most of the people I know that use GNU/Linux and LaTeX ca't pronounce GNU or LaTeX, but they work great so they get used. What's the problem?
And you should absolutely do something about this. Unless GPL infringement is met with at least the threat of legal action, it will continue unchecked.
...the Software Freedom Law Center
They exist specifically for evaluating and defending against this sort of infringement. They're experts, and their services are generally free.
You know, way back when /. was awesome, this wouldn't have even been a debate. God damn, I miss the late '90's.
It is still PHP though so it won't force all your dev team to write better code as much as RoR will.
I sincerely hope this isn't being listed as a plus for using Cake. If "language/framework/methodology n forces me to write better code!" is ever heard as a complaint, the source of said complaint is in the wrong field.
That being said, Ruby and/or Rails doesn't force anyone to write better code. I have seen some crawling horrors perpetrated in Ruby that have kept me up nights. They do facilitate the writing of better code quite nicely. Whereas PHP doesn't do anybody any favors. Ever. PHP WTFs are generally of the "never sleep again" variety. The Cthulhu of WTFs.
If you have Ruby people on your team, use Rails (or Sinatra/Padrino if you need less magic). I say this only because the Rubyists are going to spend more time flogging any other language into behaving more like Ruby than on actual domain problems.
On the other hand, if you choose a PHP or Python-based framework, one of them might come up with a really handy gem that lets you generate PHP or Python code from Ruby, and you could blog about it.
Not even trying to start a flame war, I'm a Rubyist, I work with Rubyists, and this post is intended as Ha Ha Only Serious based on my experience.
Have you ever used zenmap (formerly nmapfe)? This is how a LOT of *nix GUIs work. They wrap a command-line utility, use the GUI to compose the argv, execute, and pipe the output to a buffer in the GUI itself, with the option to export that buffer to a file.
It's simple, brilliant, and elegant.