oboe

By the way, my friend, the amazing oboe player, years later ended up selling her oboe in disgust and never played again.

The obvious conclusion is to use fewer but larger requests, which is why Oboe is so attractive.

And then tons of the little helpers in oboe could easily be their own components and useable by others.

If an oboe studio has 10 students, that's essentially 10 hours a week in lessons alone.

Interesting sound, a bit of a cross between a oboe and harpsichord with an air of church organ about it.

Makes writing libraries like oboe even easier because all of the little stuff is packaged up for you already, like emitter[2].

I'd guess the oboe as the next least popular, but that's probably just because of the joke.

It was all too easy for me to adjust the tuning of any particular note on my oboe, unfortunately usually in the wrong direction.

What's the difference between an oboe and a bassoon?

You request this from oboe('/myapp/things.json') My question: why not modify the backend to accept a request like `/myapp/foods.json` and let the backend compose the json you need & send only that?

It would be really nice to have the same streaming interface (with EventEmitters) as Node, but you I can just shim that on top of Oboe I guess.

Those are numbers for a small school; at larger universities an English professor might lecture to 300 students a week in 10 hours, but that oboe professor is still seeing just 10 students.

In the overwhelming majority usecase, this oboe.js thing is not going to be a "plug it in, automatically webscale" type of optimization.

Imagine arguing against the merits of the organ by saying "It gives up the expressiveness of the Oboe/Flute with no tangible benefit beyond being able to play more notes at once." Keyboard music is meaningful in different way.

I've been to a large "job fair" kind of event, except for there being no jobs, given by a very large university's college of Fine Arts--I went with a friend that was already a freelance musician at the professional symphony level who was going back to work on a graduate degree in oboe.

But what tech interviewers really do is interview a bassoon player, grill her on obscure points in jazz theory on paper, allow her to strum on "air guitar" but never actually letting her pick up an instrument, and in the unlikely event she passes, will later place her as an oboe player in an orchestra, figuring, close enough.

Oboe.js is marginally slower for messages that load very quickly but for most real-world cases reacting to i/o sooner beats fussing about CPU usage.

Oboe runs fine in Node but I want to make the code a bit more standards-y.