Highland.js

by callum85 • 11 years ago

132 41 11 years ago

vlucas• 11 years ago

Nice library, but please don't use the underscore variable (_). So many people use Underscore.js and Lodash.js that it makes reading your docs confusing.

choward• 11 years ago

You can name it whatever you want. That's one of the benefits using a module system.

hamburglar2• 11 years ago

So why do we have this trend of using meaningless and ambiguous identifiers, and in particular, why would you do it in example code? I thought that as an industry, we'd moved past the folly of giving things terse and unhelpful identifiers in order to save a few bytes or keystrokes.

random283452• 11 years ago

Just as you wouldn't use multiple libraries that bound a CSS selector function to the $ variable, I don't think you'd use underscore and lodash in the same javascript code. Similarly, highlandjs looks to supplant the underscore idioms with stream semantics, and you wouldn't mix both libraries in the same codebase.

91bananas• 11 years ago

While I can grant that it does seem to solve a lot of the same problems as underscore and lodash, this is just asking for confusion and complication down the road. You shouldn't make a decision that makes things hard for people to deal with in the future if they choose to use your product. There is well established meaning now to $ and _ in js land, pick another identifier.

msane• 11 years ago

Yeah that's basically what his point is. Except you misunderstood to interpret any suggestion that people use underscore and lodash together.

ceedan• 11 years ago

For real. Highland should just use an H.

mynegation2• 11 years ago

Or a Greek capital letter Lambda: Λ

Λ(['1', '2', '3'])

spencera• 11 years ago

That's exactly what I use, var h = require('highland');

slang800• 11 years ago

I agree with not using the underscore character, while Underscore/Lodash are still popular. Personally, I do `H = require('highland')`, whenever I'm using it.

thoughtpalette• 11 years ago

"This site or app is sending too much traffic to rawgit.com. Please contact its owner and ask them to use cdn.rawgit.com instead, which has no traffic limit."

rikkus• 11 years ago

Looks similar to Lazy.js (to my uneducated eyes) and also rx.js. To the author: Why should I use Highland.js instead of either of these?

mattpodwysocki2• 11 years ago

RxJS authoer here. Instead, here are the reasons you may want to consider RxJS instead of Highland https://github.com/Reactive-Extensions/RxJS/blob/master/doc/...

andersriutta• 11 years ago

Highland is a great option, even easier to use than Caolan's previous library Async.js.

Re: Highland vs. RxJS, RxJS operates at a lower level interface [0]. As a plus for RxJS, Reactive Extensions are available for multiple languages, not just JS [1].

[0] https://twitter.com/_ericelliott/status/551814104231723009 [1] https://github.com/Reactive-Extensions/RxJS/blob/master/doc/...

mattpodwysocki2• 11 years ago

RxJS author here. Right, an advantage is if you know the Java, .NET, Python, C++ version, etc, then you know the JavaScript version. That and we try to adhere to an Array#extras style following all of ES2015/ES7 Array methods.

Another advantage is that many frameworks such as Angular 2.0 are shipping with support for Observables, so that's a huge win for users of RxJS that it automatically just works.

lmeyerov• 11 years ago

Yep I'm confused why Highland exists. Maybe if it was a sugar layer over Rx?

akilism• 11 years ago

I love highland one of my go to libraries these days.

Kiro• 11 years ago

So what's the benefit of using streams instead of a normal array?

draven• 11 years ago

Processing data as it becomes available instead of waiting for the whole thing, amongst other things (that's what we do in Scala anyway.)

serve_yay• 11 years ago

If you're just mapping an array to double each element, there is no benefit.

Which is another way of saying that the examples in this doc are not very good, unfortunately.

bstar77• 11 years ago

Very interested as I use Async.js in virtually all of my node projects. I'm liking the idea of a 'toolkit' approach more than Async (which just feel like a monolithic lib), will definitely be trying it out soon.

tericho2• 11 years ago

async.js changed my life, async programming can get out of hand in a hurry.

dopamean• 11 years ago

Is this similar to what transducers do in Clojure? My understanding there is that they allow you to do things like map over core.async channels.

notduncansmith• 11 years ago

According to my understanding of transducers (warning: possibly inaccurate), that's one use-case of transducers. Transducers are a way to let you map over anything, including (but not limited to) channels, streams, etc.

zxcvcxz• 11 years ago

What's the deal with non descriptive titles on HN?

toxicFork• 11 years ago

Yes, I would prefer if they mentioned what it did in a few words instead. Maybe they are aiming to trigger curiosity.

jozzas• 11 years ago

" If you prefer using highland under the name _ like is done in the examples below, you can then simply use:

var _ = highland"

No. No, no, no. Goodness me.

doobiaus• 11 years ago

If it's not a drop in replacement for underscore or lodash, please don't use "_".

epidemian• 11 years ago

I see nothing wrong with using "_". It's just a variable name. The first snippet of code and preceding paragraph are:

If you prefer using highland under the name _ like is done in the examples below, you can then simply use: > var _ = highland

So it's not like you are required to use "_". And if it is a local variable, there is no risk of colliding with Underscore.

Highland.js

Related Stories