acoliver

pfth as if I'd use Gemini.

side-eye "anyone can read the code" -- usually the first words of someone who writes unreadable code. perl -e'$_=q/dk|jk`%fdk%w`da%qm`%fja`/;s/./chr(ord($&)^5)/seg;print'

Oh nice. Man I hate filling out all that stuff. And getting the LLM to do it without freestyling and hallucinating is a pain. Kinda wish it were an MCP so I can shove it in my CLI or maybe the hooks for git...

Not exactly. It is my (the author)'s blog and frequently we stick extra content in there. Also the DISQUS comments on Infoworld are notoriously problematic.

First off, if you're writing granny's addressbook it doesn't matter what you use. RDBMS, NoSQL, filesystem, it will work, who cares. I assume that this is at scale. It is a perspective of bill rates I guess :-) Not many grannies hire me to write addressbook apps :-)

Secondly, prototyping your straight JQuery/HTML to MongoDB or Couchbase 2.0 is SIMPLER than to the RDBMS where you must do XML transform first.

Search in RDBMS with ORs and LIKEs is hard and not a good idea for the RDBMS or your middle tier or your user (reduced capabilities with more complexity).

Storing images in the DB vs say a clustered FS makes everything from replication to performance to scalability. Get a few TB of BLOBs and tell me this is a good idea.

I (the author) familiar with functional languages, have implemented a compiler for a small one and such. However, for every day applications that are non-algorithmic attempts to express them using functional constructs have often been a strain. I've been watching projects go late due to this. There are many things, however, that I find much clearer to express in terms of functional programming constructs. But nominal business apps which show a GUI and CRUD from one location to the next or do a fairly simple data transform with a bit of boolean logic? Not so much.

The formatting is a result of the copy-editing process. The code excerpts were all from the beginner tutorials linked from the sites or wikipedia.