proposal-pipeline-operator VS Gigablast

I wish the pipeline operator hadn't stalled; it's been stuck in stage 2 for four years now:

https://github.com/tc39/proposal-pipeline-operator

We might be able to cross one more language off your wishlist soon, Javascript is on the way to getting a pipeline operator, the proposal is currently at Stage 2

https://github.com/tc39/proposal-pipeline-operator

I'm very excited for it.

This article merely scratches the surface of what the pipeline operator can offer; continued exploration into its capabilities and best practices is essential as the JavaScript ecosystem evolves. For further reading, consult the TC39 Pipeline Operator Proposal and the official ECMAScript documentation for in-depth specifications and updates regarding the implementation of new JavaScript features.

It made it to Stage 2, which is some traction: https://github.com/tc39/proposal-pipeline-operator

It has been "stuck" at Stage 2 for a while, though.

References: Pipeline Operator

https://peps.python.org/pep-0584/ is the PEP for merging dictionaries; sadly, it barely mentions pipes as a consideration.

To be fair, the notion that pipes are lower-priority than other syntax needs is not exclusive to Python: in the JS world, discussion in https://github.com/tc39/proposal-pipeline-operator and specifically https://github.com/tc39/proposal-pipeline-operator/wiki/Bike... has been going on since 2018, with things like Tuple Literals taking precedence.

On the Python side, though, at least you can build your own pipes! You can define various helper classes that have, say, an `__rrshift__` method, to let you do the following with full type-checking support:

load_iterable_from_db() >> to_dict_by("id") >> tee(logger) >> call_(dict.values) >> to_dataframe

(With great apologies to FP folks who see a bind operator, and C++ folks who have seen enough operator overloading for a lifetime!)

Not necessarily something you want to use unless you want to confuse your team, but quite useful for fluent code in notebooks!

> The reluctancy to introduce new syntax too quickly (looking at you, TC39 and Babel) makes go an almost maintenance free language.

Could you provide some examples of this? From knowledge of the pipeline operator proposal[0], moving fast and breaking things isn't always a priority.

[0]: https://github.com/tc39/proposal-pipeline-operator/commit/da...

The pipeline operator proposal, which is currently in Stage 2, introduces a new operator |> that allows developers to chain multiple function calls together in a more readable and concise way. Together with the pipeline operator, the placeholder operator % is being introduced which will hold the previous function’s value. It should enhance the readability and maintainability of code, especially when performing a series of operations on a value.

Current Status: You'd have to check the TC39 proposals repository or the official proposal text for the most recent status. As of my last update, it had not yet reached Stage 4 (final stage) of the TC39 process, which means it wasn't part of the ECMAScript specification yet.

Gigablast - A search engine whose source code is available on Github. TMK, it doesn't depend on any existing indexes either and uses its own crawler. Would be what I'd recommend to everyone but they recently collaborated with a company that has a questionable past to create a privacy focused search engine. A company that was behind the hostile takeover of Freenode IRC.

Any new open-source search option is good, but I also wish more attention was given to prior open projects like GigaBlast[0]/KBlast[1] crawlers, etc.

It hasn't escaped the wider world that quality open-source search is desirable, and it's hard to think what this new EU project brings to the table that isn't already available if others want to contribute to existing efforts. I wish the EU project the best of luck of course!

[0] https://github.com/gigablast/open-source-search-engine

[1] https://github.com/fossabot/kblast

Gigablast Source Apache-2.0

You could look at the source code for Gigablast. https://github.com/gigablast/open-source-search-engine