3 ms·
I don't know; is there not some point where we can just declare something to be terrible? I looked at what he wrote about Angular's 2 templating, and then I lo
by bshimmin 10y ago
I don't know; is there not some point where we can just declare something to be terrible?
I looked at what he wrote about Angular's 2 templating, and then I looked at the bits in the documentation about "pipes" (https://angular.io/docs/ts/latest/guide/pipes.html https://angular.io/docs/ts/latest/guide/pipes.html), and it really does look terrible - confusing terminology (is this really a pipe in the sense that most people would understand?), confusing syntax (the colons to separate arguments), and generally impenetrable without a trip to the documentation.
- agos 10y agoI don't know, the concept has been around for a long time in Angular 1 under a different name (filters) and it's pretty handy.
- onion2k 10y agoThe pipe operator isn't really an Angular thing. It comes from Unix[1] and it was first implemented in 1973[2]. [1] https://en.wikipedia.org/wiki/Vertical_bar#Pipe https://en.wikipedia.org/wiki/Vertical_bar#Pipe [2] https://en.wikipedia.org/wiki/Pipeline_(Unix) https://en.wikipedia.org/wiki/Pipeline_(Unix)
- bshimmin 10y agoYes, of course I know this - I'm sure many people know this. What Angular 2 calls a "pipe", though, doesn't refer really to the piping of the data (though of course it also uses a vertical bar), but the actual thing that's receiving/processing the data. Their previous name of "filter" was probably better, except for use-cases where there was no filtering being done.