11 ms·
This idea is one of those perennials that makes for interesting discussion yet hasn't been done much with. It's come up on HN a few times (I remember touching o
by gruseom 16y ago
This idea is one of those perennials that makes for interesting discussion yet hasn't been done much with. It's come up on HN a few times (I remember touching on it here: http://news.ycombinator.com/item?id=236704 http://news.ycombinator.com/item?id=236704). The closest thing to it that I've seen get widely adopted is the "fluent interface" or "chaining" style that has caught on in OO over the last few years; particularly, from what I've seen, in Java and JS.
The APL/J/K languages are built around a construct very similar to this, so the OP's reference to APL is apt. You really should check out J or K if you haven't yet. J comes with a marvelous set of tutorials. K comes with nothing. :)
(But K is a work of genius, in my opinion. A pinnacle.)
- barrkel 16y agoThe monadic chaining style of LINQ from the .NET world is also relevant; it's even more pipe-like, in that it's creating a pipeline, rather than modifying the data en masse, one step at a time.
- DannoHung 16y agoIt's pleasant enough for doing computations, but if your C/C++ is not up to snuff, you will find yourself very frustrated trying to integrate it into an existing ecosystem. Additionally, there are some REALLY annoying things you face due to the single threaded nature of the language if you're doing real time systems. But if you go and learn K or Q and you've got good C chops, you can absolutely get a job in Manhattan or Chicago (must be willing to work long hours with little support, build almost all of your own tools, and handle the constant pressure of making everything work perfectly the first time).