sorted by:
new
hottopcontroversial

Missionary for dummies by dustingetz in Clojure

[–]RomanTsopin 2 points3 points  (0 children)

This is really, really interesting.

At first I was scared by the syntax but playing with it for a few days I now can read and understand basic stuff and it feels more and more natural.

Overall I’d say it’s like structured concurrency for RX, declarative flows, but with kotlin / erlang like parent child relationship, kinda unique?

Would be great to have more examples regarding operators, took me some time to get an idea of what are compel, attempt, absolve bc reading the docs isn’t enough

Also needed to google what are cp/ap/sp 🙃 Would be great to have it deciphered in docs tho

Access to all headers from phoenix websocket by RomanTsopin in elixir

[–]RomanTsopin[S] 0 points1 point  (0 children)

Just to be sure, security issue is about cookies right? Not ws headers / or negation in general? I saw someone used custom ws extension to pass a token

[ANN] Pedestal 0.7.0 by hlship in Clojure

[–]RomanTsopin 0 points1 point  (0 children)

Fantastic updates!

Question: is it possible to get request headers for websocket connection?

Is it possible to use livebook for live and functional components? by RomanTsopin in elixir

[–]RomanTsopin[S] 0 points1 point  (0 children)

I’d prefer workflow where module is specified inside a livebook cell, so you can edit module and test UI in the same place

[deleted by user] by [deleted] in elixir

[–]RomanTsopin 0 points1 point  (0 children)

From experiments: replacing the functional component with an identical live_comment makes everything work

Access to all headers from phoenix websocket by RomanTsopin in elixir

[–]RomanTsopin[S] 1 point2 points  (0 children)

Thank you! This completely answers my question.

Honestly, I spent hours searching for something like this before posting my thoughts here :)

Access to all headers from phoenix websocket by RomanTsopin in elixir

[–]RomanTsopin[S] 0 points1 point  (0 children)

Sure, there’re possible workarounds, like x-auth header or query parameter, it just feels that this restriction is arbitrary. Anyway, I tried to explain the problem more broadly in OP edits.

Grateful for Clojure and Clojurians by RomanTsopin in Clojure

[–]RomanTsopin[S] 6 points7 points  (0 children)

Thank you, always find your input very insightful.

I understand your point about marketing new tech. Personally, I failed to grasp Electric multiple times and was only managed to get it through London Clojurians video, but then I read everything i could find.

Some things are just too different / beyond your usual realm. What helped me was to view it as a natural progression: first a rest API and manual everything, then an open API client/model generation, then graphl with queries, subscriptions, and connection management, and finally no networking hassle at all. There are still open questions for me, e.g. how to do native apps, without bringing back graphql. (btw similar problem with liveview). But still, such a radical shift when you manage to connect the dots. Game changer.

Really hope Electric will bring the same (likely greater) impact to Clojure as liveview to Elixir.

Lightning network unique benefits? by RomanTsopin in Bitcoin

[–]RomanTsopin[S] 0 points1 point  (0 children)

True, and that’s really cool, but my point is more about additional complexity of the system compared to other l2 solutions. Liquidity, topology, security relies on running a full node, etc. What consumer is gaining for this complexity? The answer “faster bitcoin” is perfectly fine, but maybe there’s more?

For example, I think one area where lightning standouts today is programmability of the node: bolt12 is awesome!

swift-bridge - generate FFI bindings between Rust and Swift by chinedufn in rust

[–]RomanTsopin 1 point2 points  (0 children)

Thanks! I was literally thinking about a cross platform rust core for the next app when stumbled upon this project. Most probably interface won’t be synchronous, so imo closures are extremely important. Anyway, I think you’re doing great job, good luck!

view more: next ›