Contempt Culture (2015)
blog.aurynn.com
blog.aurynn.com
One thing it got right is shared-nothing architecture where a PHP instance effectively spawns for each request and then dies.
I heard it was called "PHP must die architecture", probably as a tongue-in-cheek reference to haters or to a 2000 film with Jet Li.
By 2009 I switched from EJB-ridden Weblogic-posessed Java programming into PHP prigramming, and it was a breath of fresh air. Unfortunately, it paid much less.
Nowadays PHP is in pretty much the same situation as JavaScript: rotten to the core, but great nevertheless if used properly.
Agreed. I have nicknames due to some of the diatribes I've gone on regarding C#/.NET but it's what I do and I am always willing to be challenged.
> JavaScript is really good at this, because they’re trying to help people write better code within JavaScript.
Now now we all get to pick on JS
-----
Also, I just really feel the need to throw out the statement, you can still have contempt out of a 'language', even a 'circle' you know about, for extreme derp.
I.e. if it becomes obvious talking heads are just doing what the salespeople Gartner led them down the path towards due to a magic quadrant and are thing both too big and too small for your org, it's OK to have contempt for that too.
Tools with nice build processes: golang, (free)nginx, beanstalkd, memcached, erlang, elixir, rust, uv, pipx, and pnpm. RPM packages.
Tools with okay build processes: gradle, gcc, clang/LLVM. cmake. DEB packaging. GNU's stuff is more-or-less consistent, but autotools (automake/autoconf/m4) configure scripts are sequential, slow, and pedantically redundant. Haskell is a pain to build from source, because like go, it requires bootstrapping... which is difficult on a new platform; PSA: please don't bootstrap languages without a maintained, functioning, widely-portable, alternative reference implementation.
Tools that need improvement: openssl's configure flags are poorly documented but they're better than they were, ruby and ruby native extensions. conan. A number of Apache's (mostly Java) projects are prone to enterprise overengineering, XML, excessive but outdated features, too many options, and lack of simplicity and sane defaults. JVM (Java and not) apps can be JITed fast, portably, and run securely, but.. there's a complexity management tax and gotchas overhead. Scala footgunned itself going corporate, but Clojure and Kotlin are decent.
I'd agree with the author's point that its blanket use is an anti-strategy but wouldn't go so far as to tell people to "shut up".
In IT very early days, it started out as lite fun joking, but quickly morphed into what we have now.
Plus it is not only in Tech where this occurs. Just look at the various Automobile Communities to see this on steroids
All this is is a form of "My ** is bigger that yours".
PHP is just objectively crap in a way that Python or Rust aren't.
_Someone_ has to develop for Windows, though I'm ever so glad that that someone isn't me. Etc.