Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Fast-Nop22379265dWith idiomatic LISP, the issue is that people usually take its name too literally. Every shit is shoved into lists, and you never know whether you have a tuple or a list or even code.
With idiomatic C, you'd have a tuple in a struct, a list in an array, and you'd (usually) not hand over executable code at all.
That's another thing with LISP, self modifying code. It's how people thought AI would be like. Turned out it wasn't - all that came out of that was an unmaintainable mess.
Oh and that you can redefine the whole language in LISP is also a weakness and not a strength because it means that every fucking project is de facto in another language. The only kind of devs who like that is people working on one-off stuff that nobody will ever touch again after them.
Root58068265dThe only thing I like about implicit returns is that it shortens already tiny functions by a little bit.
Used outside of that niche it just irritates or infuriates me. Especially when there are implicit returns at multiple indent levels throughout the function. That practice should burn along with its practitioners.