cjg

22 ms·

181.
Why is capitalizing the first letter of a string so convoluted in Rust?(stackoverflow.com)
39 points by cjg 5y ago|14 comments
182.
by cjg 5y ago
Most people are happy to teach themselves the basics through some reading of https://doc.rust-lang.org/book/ then a mixture of pairing, code walkthroughs and short presentations. We will also run a training course next
183.
by cjg 5y ago
>> you’re slower than a dev team working in a traditional language (java, go, python, …) If anything my experience is that it's quite productive to work in Rust. For example, compared to Python (which you mention) we catch bugs e
184.
by cjg 5y ago
A couple of reasons: 1. We like the thread-safety properties that Rust offers 2. We don't have any Go experience Does Go offer similar guarantees for concurrency?
185.
by cjg 5y ago
We initially used it on a small project that had the requirement that the chances of a crash / failure should be very low because it would be used as a remote control process for a wider system. We had good success there and so the com
186.
by cjg 5y ago
We've been using Actix. We evaluated several frameworks and liked the model that Actix has and also its relative maturity (for example documentation / examples). It has been pretty straightforward to work with - including doing th
187.
by cjg 5y ago
I have been involved in training several "junior" devs in Rust and I would say that it's more about their ability as a developer rather than them being junior. Developers who could get by professionally in Python, but were no
188.
by cjg 5y ago
I'd be interested in hearing what you think is a problem in async Rust.
189.
by cjg 5y ago
In my experience, Rust code is relatively easy to read, even by developers with no Rust experience. Of course, you can write hard to read code. But that's not typically what comes out of a process of writing production software. That&#
190.
by cjg 5y ago
We are using Rust for backend web development and other things. For us, the safety is the critical reason to choose Rust - particularly the thread-safety. Also the relatively small memory footprint compared to something like Java. Performan
191.
Safe Systems Programming in Rust(cacm.acm.org)
1 points by cjg 5y ago|0 comments
192.
A Practical Wait-Free Simulation for Lock-Free Data Structures [pdf](people.scs.carleton.ca)
1 points by cjg 5y ago|0 comments
193.
by cjg 5y ago
This is what BitMessage tried to solve, but it looks a bit unloved right now.
194.
Predictive test selection: A more efficient way to ensure reliability of code(engineering.fb.com)
1 points by cjg 5y ago|0 comments
195.
Gravity is a double copy of other forces(quantamagazine.org)
324 points by cjg 5y ago|205 comments
196.
Fast, Fun, Omniscient Debugging(pernos.co)
2 points by cjg 5y ago|0 comments
197.
by cjg 6y ago
I had a similar experience searching for "rust hashmap" - expecting to get some links to the standard docs.
198.
by cjg 6y ago
Well, you can use https://docs.rs/async-std/1.9.0/async_std/task/fn.spawn_bloc... But this is partly the reason why libraries might be more inclined to support async rather than blocking calls.
199.
by cjg 6y ago
Rust async doesn't quite solve the cancellation problem either. Sure, you can stop polling the future at any time, but that doesn't mean that you left the system state consistent. Careful thought is needed on every call to await i
200.
by cjg 6y ago
It's easy to convert an async function into a blocking one. For example, you could use https://docs.rs/async-std/1.9.0/async_std/task/fn.block_on.h... So just use the async functions from the librar
201.
by cjg 6y ago
I think that's too strong. You could have two executors with no problem. What might cause issues is if code running on one executor needed close interaction with the other - such as running a task on the other executor. Most of the tim
202.
by cjg 6y ago
Unfortunately if enough people have been looking at Bose QC-35s then there's no reason why that couldn't be a fact about your cohort.
203.
by cjg 6y ago
The contract is mostly there so that it's clear what each party is trusting the other to do. Enforcing a contract is often not worthwhile.
204.
by cjg 6y ago
The idea is that they group you with N other similar people where N is large enough to anonymise you enough to stop the worst complaints but small enough that advertisers still find it useful. Some sort of principal component analysis to de
205.
by cjg 6y ago
Must have been this: https://www.stairwaytohell.com/music/Frak.mp3
206.
by cjg 6y ago
That sounds very familiar! There was essentially no security on those Econet networks. If you had a copy of the executable that could read and write the memory of a remote computer, you were good to go. I remember I had a print-out of a hex
207.
Beware the Spider Economy(linkedin.com)
3 points by cjg 6y ago|0 comments
208.
by cjg 6y ago
We give up on automated program analysis far too easily - even for "Turing complete" languages. To be truly Turing complete requires infinite memory. That clearly doesn't hold for any current programming language. Mathematica
209.
by cjg 6y ago
Sounds like something you could 3D print.
210.
by cjg 6y ago
Or work 7 years and then retire. https://www.mrmoneymustache.com/

More ›