Comment Re:Name revealed (Score 1) 890
Unless SOPA/PIPA ever become law, in which case, goodbye Slashdot.
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
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.
Excel is extremely powerful
Sure, but certainly not more powerful than exporting to CSV and doing your calculations in Perl or Ruby.
GUI tools are great for people who never learned to use the CLI. But once you know how to use it, there's no need to submit to the bondage and discipline of a GUI.
At the duty-free shop on your way out of the country. Unfortunately, it's not available to U.S. citizens.
Don't worry, the GOP is completely fine with murder-neutrality laws. But net neutrality, that's a crime against Jeebus and Adam Smith!
Obvious troll is obvious
"When the going gets tough, the tough get empirical." -- Jon Carroll