As honest as it is I can't risk using this anywhere near production if this is the attitude.
eminence32•35m ago
Luckily there's a lot of people who write prototype code, toy projects, and other "non-production" code that can experiment with a new project like this
csoups14•13m ago
I'd rather honestly than false confidence, there's something admirable about being this clear for sure
jdw64•46m ago
Has anyone here tried it?
haellsigh•32m ago
I have tried it.
It feels pretty good to use, but you have to keep in mind that it's very early software.
They currently break the API every other week, and it's still missing a lot of fundamental features.
I have made a few basic web apps with it, and on v0.8.1 it was still missing a lot of reactivity which meant you had to use Javascript to bridge the gap.
jdw64•16m ago
I used it in the early days, and it seems it's still the same. Thank you.
moffers•13m ago
We’re using it to build our web app (https://uncook.xyz) and while it’s a slight departure from my team’s NodeJS background it’s been pretty cool to work with
victorbjorklund•30m ago
Sounds a lot like Liveview in Phoenix.
lolakutty•15m ago
Why bother with rust when you can write it in C and ask an LLM to weed out the memory bugs?
Georgelemental•13m ago
Why bother with asking an LLM to weed out the memory bugs when you can write it in Rust?
lolakutty•11m ago
> when you can write it in Rust..
Because fuck borrow checker..(and the horrible syntax)
Ar-Curunir•10m ago
[delayed]
huijzer•7m ago
If you go that way, why not write LLVM Intermediate Representation? And if you know your server arch anyway, why not write machine code?
I personally like Rust for web applications a lot because you can catch many bugs at compile time instead of during tests or runtime.
hmokiguess•5m ago
Soon we're gonna need a way to catch bugs at prompt time
cube00•1h ago
As honest as it is I can't risk using this anywhere near production if this is the attitude.
eminence32•35m ago
csoups14•13m ago