And now, to nobody surprise, time to work again with Angular; all fun and games, until observables join the party.

RXJS IS RETARDED
RXJS DEVS ARE CRIMINALS
RXJS USERS ARE ACCOMPLICES

FUCK YOUR GLORIFIED EVENT EMITTER, FUCK YOUR REACTIVE PROGRAMMING PARADIGM, FUCK YOUR HALF BOTCHED ATTEMPT AT REINVENTING THE OPERATORS I GET FOR FREE FROM ANY LANGUAGE.

YOUR BEST GIFT TO THE WORLD WILL COME THE DIE YOU FINALLLY FUCKING DIE.

This is the literal quickstart, I can't believe an actual professional looked at this shit and was like "YEAH ABSOLUTELY, THE WORLD NEEDS THIS"

@IHateForALiving Git gud ;P no clue what angular uses it for, but it's a lot more performant than the built-in functional parts of JS (map, reduce, etc).

Maybe lookup pipelining to understand what it's for

"HURR DURR IT'S MORE PERFORMANT"

It's not, but I wouldn't care anyway. I'm performing an HTTP request and assigning a few properties here and there; this is NOT what's slowing down my application.

Slowing the entire development process for some hypothetical clock cycles which, even if you did actually get them -and I'm not saying you do-, you'd get exactly 0 benefits in the 99.99% of real world scenarios, because that's now what's clogging your application.

@IHateForALiving It is, strange you need to rx for that, to the point I don't see a benefit other than if it's your style of coding.

I see it as a replacement for [...].map(...).filter(...).reduce(...)

or dealing with websockets

Also since I'm familiar with pipelining it's rather intuitive for me and I work faster with it ¯\_(ツ)_/¯

I can definitely see why would anyone use rxjs for sockets, there's no way in the world I would use rxjs on anything other than this specific scenario you just mentioned.

@IHateForALiving 100% agree

You can't escape it by doing

.pipe(switchMap(async (...) => {

sanity

}))

?

Still it sounds but inane and insane to make it a requirement in a web framework

OKAY I'm never touching angular (just looked up the syntax) 🤮

I may look into it only for websockets.

I've written my own websocket pub/sub thingy but rxjs may make it more comfortable...

But why the fuck are they trying to reinvent map, filter, reduce?

@Ranchonyx map, filter and reduce are all full list traversals (as in each independently does a for loop)

With rxjs it's only a single loop, you're splitting out the bits inside into functions

Created a pastebin for indention; otherwise it's below https://pastebin.com/2BBaWi50

let data = [...]

for (const i = 0; i < data.length; i++) {

data[i] = mapper(data[i])

}

let newData = []

for (const i = 0; i < data.length; i++) {

if (filter(data[i])) {

newData.push(data[i])

}

}

vs

let data = [...]

let newData = []

for (const i = 0; i < data.length; i++) {

const newVal = mapper(data)

if (filter(newVal)) {

newData.push(newVal)

}

}