bitstream
generator
Our great sponsors
bitstream | generator | |
---|---|---|
4 | 5 | |
86 | 4 | |
- | - | |
6.8 | 7.7 | |
3 months ago | 6 months ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bitstream
-
Coroutines in JavaScript for Web Components
I use generators to handle performant asynchronous bitstream parsing. Using promises is far too slow: https://github.com/astronautlabs/bitstream
-
Why Would Anyone Need JavaScript Generator Functions?
I used generators to increase the performance of bitstream parsing by several orders of magnitude over using a promise based system
https://github.com/astronautlabs/bitstream#generators
- bitsream - Utilities for packing/unpacking fields in a bitstream in typescript
- Show HN: A powerful bitstream library for TypeScript
generator
-
Ramda: A practical functional library for JavaScript programmers
I find straight forward, dedicated combinators much more readable and practical to use ie. for iterables (context where it makes a lot of sense) [0] example [1], runtime assertions (through refutations, which are much faster than combinators over assertions) [2], parser combinators for smallish grammars [3] etc.
In many cases vanilla/imperative js is more readable and terse, no need to bring functional fanaticism everywhere, just in places where it gives true benefits and in form that can be understood by peers.
Functional code can be beautiful and can also be unreadable/undebugable. Same with imperative code. It's great in js/ts you can pick approach where the problem is expressed more naturally and mix it at will.
[0] https://github.com/preludejs/generator
[1] https://observablehq.com/@mirek/project-euler
[2] https://github.com/preludejs/refute
[3] https://github.com/preludejs/parser
- Why Would Anyone Need JavaScript Generator Functions?
-
A pipe operator for JavaScript: introduction and use cases
You can type it, take a look at pipe and pipe1 in [0].
[0] https://github.com/preludejs/generator/tree/master/src
- Parser Combinators in Haskell
-
Loopless Code
Loops are great if your programming languages supports iterables/iterators/generators (also async generators) like in js/ts for example.
Especially generator-to-generator combinators ie. [0] give you terse, transducer expressiveness over computation on finite/infinite streams, arrays, etc. (all iterables). It's easy to compose them, jump into for loops if needed for arbitrary yielding (ie. yielding multiple items sometimes, skipping some, halting etc). `continue`, `break`, nesting, yield, yield from, normal code in for loops is very intuitive and terse creating pleasant, understandable code.
[0] https://github.com/preludejs/generator
What are some alternatives?
netlist-to-vhdl - Netlist and Verilog Haskell Package
angstrom - Parser combinators built for speed and memory efficiency
transfermyti.me - Web-based tool for transferring data between time tracking tools.
assert-combinators - Functional assertion combinators.
async-generator - Async generator module.
ppipe - pipes values through functions, an alternative to using the proposed pipe operator ( |> ) for ES
testkube-dashboard - Dashboard for viewing real-time TestKube results
notion-sdk-js - Official Notion JavaScript Client
IxJS - The Interactive Extensions for JavaScript
trealla-js - Trealla Prolog for the web