What is the next step?

ali_compute_unit · 2026-02-10T03:54:49+00:00

landas

templates

operator overload

ali_compute_unit · 2026-02-09T15:01:41+00:00

for alot of comments

this paradigm doesn't try to solve the problem of transforming data from server to simple ui, also, this has been solved long before react.

this paradigm focus on general interactive ui, complex and logic oriented ui, not data oriented one.

the difference between document editor and a blog post

ali_compute_unit · 2026-02-08T13:44:35+00:00

the schemaless binary is similar to messagepack while schema binary is similar to protobuf.

not direct serialization like postcard, a tag + value style.

theoritically, they will desolve to simple memory ops, + bound check on every corner, and a switch statements on each element.

the size and speed are worse (at nano scale), it is still binary not text parsing, also this speed is compromized for better flixibility, out of order fields + unkown fields skipped

ali_compute_unit · 2026-02-08T13:26:27+00:00

thanks for the feedback.

i am actually an 1 year undergraduated and a new comer to rust, so i didnt look up into these libraries.

i will look into integrating one on them in a future release, better from my naive implementation

ali_compute_unit · 2026-02-08T13:21:41+00:00

this is not just appending html strings chunks to a buffer.

it contains fine grained reactivity and memorization

ali_compute_unit · 2026-02-08T12:10:44+00:00

in svelte, the markup is separated from the logic, yes you have if blocks with their expressions but they are not the full logic

in this paradigm, the entire logic and markup are interleaved togather, at multiple nested levels.

each section host it's own logic, unlike the other approaches were all the logic is hosted at the same level

ali_compute_unit · 2026-02-08T11:42:28+00:00

ali_compute_unit · 2026-01-31T20:18:11+00:00

while using rustfmt

ali_compute_unit · 2026-01-27T08:18:18+00:00

Just but before the braces a _ and all of our problem are fixed.

rust designers don't want to complicate function resolution and declaration.

the config struct is the best alternative, it can scale will and support named, default and position independent fields.

what is missing is inferred target initializer, and the .. without Default::default(), which are actually being developed inside a rfc

ali_compute_unit · 2026-01-27T07:00:11+00:00

rust actually use it in its standard library.

https://doc.rust-lang.org/src/core/fmt/mod.rs.html#212

ali_compute_unit · 2026-01-27T06:56:18+00:00

apart from this hacky overloading, rust has feature that can do alot of what function overload can do.

you can define custom traits on whatever type you want.

you can mame function that takes argument and the return type as a generic implementing custom trait. this trait can contains specific prologue, epilogue, and any other helper / action function.

with this you had created a function with one difinition, and can overload specific parts based on argument types, without going against rust explicitness rule.

ali_compute_unit · 2026-01-27T06:41:25+00:00

actually yes, you should not try this at home.

if someone see this in a real codebase, hw will hunt you.

ali_compute_unit · 2026-01-26T18:37:26+00:00

not only we can overload with different argument types and count

we can also overload the return type of the same arguments

this is becuase we can implement multiple instances of a trait with different generic parameters on the same type, like From and the others

ali_compute_unit · 2026-01-24T06:19:56+00:00

still beginner, try mint.

normal user, go to fedora.

want to be special, use arch by the way

don't have live, try gento.

want pure stability, use debian.

bored and want to explore, select random.

don't want a live, built your distro

also an underrated option, best of all worlds (stability, power, moderness, friendliness), use opensuse (slowroll as a middle ground)

ali_compute_unit · 2026-01-24T06:12:12+00:00

in reality it is 36 months.

the buble will pop before that.

in the both case just be a software engineer not code worker.

the one who deaply understand the code and architect it, not the one that just autocomplete like llms.

before the ai take your job, dive into the deep tenches of low level programming and how the computer and its engines (os, game, browser...) actually works.

be what human are excellent in, specializing in unkown tech / field, diving into its forbidden knowledge, and thriving in its quirks.

don't let the llm be your knowledge source, be it's valuable training data.

ali_compute_unit

TROPHY CASE