151 karma · joined April 21, 2023
But what matters is that it was all memory safe and had no data races.
Irony is that it's most useful for hobby projects. In production I'd not use it.
Can you tell more about what is your freelance work about?
Implementing AI solutions for companies?
And how do you get freelance clients?
I bet more money was spent on the tokens than the mathematicians.
There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies and the other way is to make it so complicated that there are no obvious deficiencies.
— C.A.R. Hoare, The 1980 ACM Turing Award LectureEveryone ^H^H^H^H everyone's clanker is building the same things.
2. They may intend the parts of it to be reused on workers?
To get rid of this issue, go must add a level of indirection or track aliasing at compile time; the tradeoff Go made here is perfectly reasonable.
Even though macros can do this, it's not intuitive to expect this kind of JSX soup in rust. It's difficult to reason about than a function call. Something like flutter where widgets are ordinary function calls is far better.
Plus the macros add to the compile time tax.
This is another exhibit that rust is full of web programmers from React JS world (the above is exactly like JSX), all about aesthetics than practicality and predictability these days, pulling what should be a system language into incompatible directions.
Long live zig for trying engineering directions rust couldn't. But we need a rust killer with memory safety which gatekeeps web programmers and slop peddlers.
In any case railers are screwed (or railed, if I may). Either use the upstream which DHH is going to slopify and slowly kill, or use these forks by left-fascists who might happily sabotage you for perceived wrongthink in future.