linqbox VS arktype

Positioning the Ark parser as a unified string syntax for runtime types (to me at least) makes the rationales and justifications for string parsing much more apparent and focused, much more so than just saying "hey, here's a library to write your types with strings just because". It also services as a prototypal implementation of what JS types "could" look like one day (if only we could drop the `scope` and `type` and just write the types naturally in JavaScript), I took a similar approach with https://github.com/sinclairzx81/linqbox many years ago.

Well, I wrote this ... https://github.com/sinclairzx81/linqbox, an actual LINQ syntax mostly for cartesian products (because cartesians with lambda are quite awkward after all)

One shouldn't need to look OData query syntax. For a C# client querying an OData endpoint, one simply need only write LINQ. A problem that exists in current fashionable languages is they do not support anything resembling LINQ. (Although some options exist for Elixir (Ecto) and Rust (implemented via proceedural macro). As for JavaScript....I have tried https://github.com/sinclairzx81/linqbox

If you ask me, TypeScript is a legitimate successor to C#. The only stuff missing in TypeScript is LINQ (as you mentioned) which is why I wrote this, and System.Reflection which is why I wrote this.

Thanks for the response. Here's a fun library I wrote https://github.com/sinclairzx81/linqbox

I primarily rely on that approach to benchmark ArkType's types.

I was one of the most outspoken supporters of this initiative until I started working on ArkType. That may sound oddly self-serving, and it would be naive to claim objectivity after having invested so much into my own solution to this problem. However, I don't think that's the primary reason I changed my mind.

Since it's not explicitly listed there, I feel I should shout out David Blass and his incredibly cool ArkType project: https://github.com/arktypeio/arktype

He sometimes (used to?) streams himself working on twitch and it's a really comfy place to hang out: https://www.twitch.tv/arktypeio

ArkType is a runtime validation library that can infer TypeScript definitions one-to-one and reuse them as highly-optimized validators for your data.

Could also try ArkType if you haven't seen it.

How would you say the functional chaining style overall compares to a parsed syntax like ArkType?

I'm working on a library called ArkType maybe of interest to you.

If you're interested in the possibilities of this kind of stuff in TypeScript, you should check out ArkType.

Have you tried ArkType?