sbahri

it's good editor, but settings it take time 😂

GitHub - esmuellert/codediff.nvim: A Neovim plugin that provides VSCode-style diff rendering with two-tier highlighting (line + character level) in side-by-side and inline layouts, using VSCode's algo... A Neovim plugin that provides VSCode-style diff rendering with two-tier highlighting (line + character level) in side-by-side and inline layouts, using VSCode's algorithm implemented in C. - es...

I use this plugin: github.com/esmuellert/c... for diff, the UI almost the same as VScode

interesting. i never hit with that issue yet. but it look like the best implementation i can think, jsont and caqti style projection hurt when writing many fields, applicative more readable

I stole the idea from jsont, and make our own to be inspectable. I modify the object construction to applicative syntax, which is suprisingly fit in free applicative: github.com/syaiful6/tap...

haha, how is going with your Emacs? This is neovim, the LSP integration suprisingly good here

yes, this one is written so I can get bidirectional encoding <-> decoding, plus we want to inspect this schema into JSON Schema standard, which later taken by our OpenApi generator.

Arguably the most expressive way to describe sum types to any wiring format in #OCaml. You get bidirectional JSON codecs without ppx.

trying out #OCaml effect handlers for a web application today, it work like charm. 😍 what the advantage using this? it work like a dependency injection, since you can interpret differently in tests

that feeling when you work on old abandoned side project

I finally released v1.0.0 of a ppx that enforces the rules of hooks for reason-react

- exhaustive deps in useEffect/useMemo/useCallback
- order of hooks (hooks at the toplevel/not conditionally)

github.com/ml-in-barce...

OxCaml unboxed and stack allocation are 2 features I want it available in main compiler. 😍 the performance gain sound cool

Hahaha. I agree. Haskell philoshophy have been avoid success at all costs

I decided to start new year with simplifying Tapak API, not much changed but I am happy with this changes.

When I switch to neovim, I was slow and not productive at all. 😂 Eventually my head get used. Hope that happen to you as well

Tapak now support extracting parameters from cookie and it reflected in the derived OpenAPI schema

it proof that our GADT based router that provides type safety does not require a performance trade-off. 😃

Completed the rewrite of our type-level router, moving away from linear pattern matching to trie based lookup. I noticed it provides 1.5M to 3.1M reqs/sec perf depending on capture complexity. #OCaml

I genuinely wanted to click those links.😂

simplifying our route handler so it does not always take Request.t as the last argument, feels more natural to write.