jeremychone

8 ms·

31.
by jeremychone 4y ago
Nice one. Never knew about this story. I was still at the Mozilla CSS story.
32.
by jeremychone 4y ago
Railway is very promising. It makes total sense to write those CLI in Rust. We have rewritten our CLI to Rust, and the runtime reliability, performance, and developer productivity paid off.
33.
by jeremychone 4y ago
This is a very informative article with some excellent points. Indeed, having worked a little in the UI toolkit realm, I agree that a different UI Component model is warranted for an efficient Rust UI toolkit. Perhaps some of Bevy "ECS
34.
by jeremychone 4y ago
After a couple of years of coding Rust, I found the error system, including the ?, well thought out. It is explicit and clear that the error is or maps to the function return error. The only thing is that Rust rightfully uses the ? to retur
35.
by jeremychone 4y ago
I would differ that Rust would not be a better choice than Rust. Seeing Rust as a system programming language only is missing the bigger picture (IMO).
36.
by jeremychone 4y ago
Well, we are doing just that, building a new venture with Rust because we think it is transformative in our field. Will post our findings in a year or so.
37.
by jeremychone 4y ago
It might be good to decouple the work coding environment vs. the coding activity itself. Secure the income stream by doing what is expected of you, and use your personal creativity on side projects with a potentially new language (e.g., Rus
38.
by jeremychone 4y ago
That is a very good way to look at it. Now, I am not a C++ dev, but how much effort would it be for a team to pick up C++ 20 if they only had worked with was C++ 11?
39.
by jeremychone 4y ago
I think Axum has the potential to be the top web framework. Not too high, not too low, very well designed and complete, and well maintained with healthy momentum. It has become our web framework for web services and web app backend. Not sur
40.
by jeremychone 4y ago
I recommend Axum. 1) Not too high, not too low. 2) Very well componentized (e.g., Tower for middleware) 3) Very well modelized and complete (e.g., middleware, extractor, req/res extension, fallback, req/res mappers, simple and fle
41.
by jeremychone 4y ago
A little more explicit than the "Rust’s Ugly Syntax"
42.
Ten Reasons Not to Use Rust (The Whole Truth)(youtube.com)
5 points by jeremychone 4y ago|1 comments
43.
by jeremychone 4y ago
That is a nice blog post. We have moved from Warp to Axum as well. It's not too high, not too low, and very well componentized. Also, it has good momentum, and its commits "cadence" looks healthy so far.
44.
by jeremychone 4y ago
The "rewrite-it in Rust" is not for all projects, obviously, but for some, it might be a smart move. Time will tell.
45.
by jeremychone 4y ago
It's interesting. The same post was on the Rust Reddit a few days ago, and almost everybody got the point of the article, which is the opposite of what we could infer from the title alone. Many have a good laugh as well. But somehow, o
46.
by jeremychone 4y ago
I had the same initial opinion about the '.' Vs. ':' for module separation. Why add weight to make this distinction? However, after over a year of coding Rust every day, I now really appreciate the distinction. It's
47.
by jeremychone 4y ago
Code aesthetic appreciation is a temporal matter. Something that looks ugly initially might feel natural and sound later. This happened a lot to me while learning Rust. Rust has to be learned, true, but once the initial learning phase is do
48.
by jeremychone 4y ago
Coding in Rust is definitely addicting.
49.
by jeremychone 4y ago
Here is a bevy video tutorial I did: https://youtu.be/j7qHwb7geIM Source on GitHub.
50.
by jeremychone 4y ago
Been using recut and it is amazing. The fact that this was rewritten in Rust and Tauri is impressive, and I think a very smart move. Once you know Rust, you tend (at least I do) to be very productive. Looking forward to new recut features.
51.
by jeremychone 4y ago
That’s the point of Tauri. UI is html/css/js, and the backend logic is Rust.
52.
by jeremychone 4y ago
Yes, and as you can see, things are not that trivial. At the high level, you can approach it in two ways. - WebView to localhost would be the first solution but is inherently not secure (or needs lot of work to make it so, and still) - Anot
53.
by jeremychone 4y ago
What do you mean "native messaging API?" Tauri offers a very elegant, secure, and effective way for the WebView JS environment to communicate with the Rust backend. It's not a trivial task to do this effectively and securely,
54.
by jeremychone 4y ago
Tauri is very well designed, from an app model to its component parts (wry, tao). In short, it’s a platform that allows writing Rust as the backend and use of the OS webview. So light and fast. I think and hope that many new desktop apps, e
55.
by jeremychone 5y ago
I think you have a good point, Rust might be too much for them (at least for now).
56.
by jeremychone 5y ago
I am not a Go developer, I just looked at it from afar, but I understand that the GoRoutine was the cornerstone of high concurrency performance. In Rust, you have the async/await/future model. You can combine with MPSC (multiple p
57.
by jeremychone 5y ago
cool stuff. I need to learn Solana one of these days. Still confused with the whole thing.
58.
by jeremychone 5y ago
Here are some random points, but you have more context at the end, so make the decision that fells right to you. - I heard a lot of npm dependencies nightmare, but somehow, we do not hit that much. Once in a while (a couple of months at mos
59.
by jeremychone 5y ago
I would say definitely yes. While Rust asks the developer to worry about things they don't in other "memory managed" languages, its ergonomic and expressiveness add to the productivity. Once you get used to Rust, it becomes a
60.
by jeremychone 5y ago
Actually, once you get used to Rust, what you “loose” on one side of the productivity (ownership/lifetime/dispatch) you gain on the other side with the ergonomics (enum, matches, expression, …). So our experience, is that at the e

More ›