Argorak

16 ms·

91.
by Argorak 7y ago
You're pretty much correct, there is a tradeoff here. There's reasons why many high-performance systems like databases are mixed systems.
92.
by Argorak 7y ago
0-cost abstraction was summarised by Stroustrup as: > What you don’t use, you don’t pay for. And further: What you do use, you couldn’t hand code any better. In that mind-set, it is completely okay that `sync_read` and `async_read.await`
93.
by Argorak 7y ago
Note that the implementation of the runtime itself is subject to change. It's currently an unbounded threadpool. https://github.com/async-rs/async-std/pulls?utf8=%E2%9C%93&q...
94.
by Argorak 7y ago
Project member here. It exports stdlib types (like io::Error) where appropriate so that libraries working with these can stay compatible, so `no_std` is not really an option. The underlying library (async-task) is essentially core + liballo
95.
Announcing `async-std` beta, an async port of the Rust standard library(async.rs)
6 points by Argorak 7y ago|0 comments
96.
by Argorak 7y ago
The LLVM got covered as part of ARM switching their toolchain to clang. (FWIW, I'm part of Ferrous Systems)
97.
Status of Rust-Analyzer: Achievements and Open Collective(ferrous-systems.com)
5 points by Argorak 7y ago|0 comments
98.
by Argorak 7y ago
I have talked to a couple of AdaCore folks personally and the competition is friendly, because Rust brings movement into the space. We also respect Ada a ton and fundamentally believe that clients having actual choice improves all products.
99.
by Argorak 7y ago
Unsafe code is a really hot subject in the Rust project already and there's tons of research work around that done by Ralf: https://www.ralfj.de/blog/categories/research.html . He's also building Rust too
100.
by Argorak 7y ago
We'd be super interested in talking and giving feedback on the draft! If you are interested, feel free to get in touch somewhere, preferably on sealed-rust@ferrous-systems.com?
101.
by Argorak 7y ago
It isn't sudden, there's a lot of verification work for Rust already going on, e.g. the Rust Belt Project. I don't see how delaying would help in the long run. (Full disclosure: I'm MD at Ferrous Systems)
102.
Building a lock free continuous ring buffer in Rust(ferrous-systems.com)
200 points by Argorak 7y ago|109 comments
103.
by Argorak 8y ago
That would better be covered by unlimited sick leave. Which, for example, Germany has. Sick leave is covered to some extend (70% up to 30 days, fully afterwards) by the health insurance. There's a clear separation between sick leave an
104.
by Argorak 8y ago
Matrix is terrible in as it is purely focused on building a protocol. Everything else is underserved. People are into Chats because of the clients.
105.
by Argorak 8y ago
Slack is free for users in FOSS communities. So they beat IRCCloud by 5$. Why would people with a question pay those to get into your community? I hate Slack for open communities as much as the next person, but IRC or fixes on top of it are
106.
by Argorak 8y ago
ES 2 was followed by ES 5.
107.
by Argorak 8y ago
The plugin already has paid features in the sense that the debugging support only works in CLion. That seems like a likely future path to me.
108.
by Argorak 8y ago
The author of the plugin works at JetBrains and works on it on his day job.
109.
by Argorak 9y ago
Taking a trait object by reference is a pretty common pattern. Box<Trait> is so pervasive because it's currently the easiest way to get type erasure in return position.
110.
Rust Lifetimes for the Uninitialised(asquera.de)
2 points by Argorak 9y ago|0 comments
111.
Parcel v1.5.0 Released: Source Maps, WebAssembly, Rust, and More(medium.com)
3 points by Argorak 9y ago|0 comments
112.
Getting started with Rust on the command line(asquera.de)
5 points by Argorak 9y ago|0 comments
113.
by Argorak 9y ago
qznc puts that better then I do. It saves you from data races, but not from race conditions. Cell and RefCell are both not Sync (that means they can't be used from multiple threads) for a reason. RefCell does, however, allow borrow che
114.
by Argorak 9y ago
Rust only saves you from simple races, not more complex ones. That's quite a lot already. Most importantly, though, it preserves _memory safety_ in concurrent situations, so your stuff won't randomly crash, but properly panic. It&
115.
by Argorak 9y ago
Founder of RustFest here. First of all: RustFest is unaffiliated with Rust, the project. We are in touch, but we run our own ship. I _am_ member of the Rust community team, but my function within RustFest is not that one. Currently, I am th
116.
Show HN: Full Rust course material under CC license
5 points by Argorak 9y ago|0 comments
117.
by Argorak 10y ago
If that were the case, much of the community-driven work going towards - for example - specific embedded targets wouldn't happen. What is the case is that one of the major users of Rust is Servo, which definitely runs into more problem
118.
Lambda Island – Screencast Series about ClojureScript and Clojure(lambdaisland.com)
2 points by Argorak 10y ago|0 comments
119.
by Argorak 10y ago
There's a lot of stuff in Rust that makes such types manageable. Also, such types should always be expressed as: struct MyFancySharedThing<T> { thing: Rc<RefCell<T>> } Rc and RefCell are implementation details and
120.
by Argorak 10y ago
You need an Apple Developer Cert. Here's the relevant tracking issue for the same problem in Rust. https://github.com/rust-lang/rust/issues/27694

More ›