carllerche

7 ms·

31.
by carllerche 2y ago
I doubt it. Eating healthy is already cheap and easy (rice & legumes as a base, fresh or frozen veggies based on what is cheapest at the time). It just doesn’t taste as good and gets boring fast.
32.
by carllerche 2y ago
I respect that some prefer just to use SQL, but that isn't where most stand. Also, instead of a reactionary "all ORMs are trash," where ORM probably means different things to different people, maybe you could provide some val
33.
by carllerche 2y ago
It happens in the US with how fed, state taxes interact with social security and Medicare (income capped)
34.
by carllerche 2y ago
The easy solution is to tax vacancy at a rate that makes this strategy not profitable.
35.
by carllerche 3y ago
IMO corporate ownership isn't bad as corporations rent housing to individuals who can't afford mortgages. Let's say corporations are 100% banned from the housing market. 85% of Americans cannot qualify for a mortgage, where w
36.
by carllerche 3y ago
Good thing this would have no impact on home values. Hedge funds getting involved is a symptom, not a cause. Hedge funds buy properties *because* home values go up due to limited supply. The only thing that can lower housing prices is a dra
37.
by carllerche 3y ago
The issue here is that, after M110, there is little the police can do to prevent *public* usage of hard drugs like fentanyl. Drug addicts will be smoking fent in front of a K-5 school and all the police can do is fine them. There is more en
38.
by carllerche 4y ago
It isn't a question of backwards compatibility, it is just way easier to iterate / evolve in a crate than it is in stdlib. For example, Tokio has the concept of "unstable" features, which have stronger stability guaran
39.
by carllerche 4y ago
Can you elaborate on "heavy weight"? Tokio lets you opt-in to only what you need via feature flags. This lets you use a small subset of the lines of code & transitive deps.
40.
by carllerche 5y ago
Here is the PR: https://github.com/rust-lang/futures-rs/pull/2551 Yield = wake the `waker_ref`. Avoiding the yield would be clone().wake(). That said, "poll immediately" isn't actually a thing
41.
by carllerche 5y ago
It wouldn’t be too hard. The trickiest bit would be putting together a consistent API.
42.
by carllerche 5y ago
It wouldn’t be too hard to tell it apart. A yield is defined as the task waking itself vs something else waking it. The yield methods already do this.
43.
by carllerche 5y ago
I don't think it is an issue w/ the pre-emption code. I believe FuturesUnordered is just doing the wrong thing: not respecting yields.
44.
by carllerche 5y ago
IMO FuturesUnordered should stop executing futures when it sees a "yield". An explicit yield signals control should be returned to the runtime. FuturesUnordered does not respect this.
45.
by carllerche 5y ago
Tokio author here. Generally speaking, I recommend strongly against using FuturesUnordered unless you know all the pitfalls. We are working on an alternative utility that should hopefully avoid the issues described here and others: https:&
46.
by carllerche 5y ago
Would love a real GUI but we have no design talent and stuck with something simpler.
47.
by carllerche 5y ago
It does not have a hard dependency to Tokio. Any runtime can use tracing to emit the necessary instrumentation to work with Tokio Console.
48.
by carllerche 5y ago
We would love a web view but don’t have any ability to design or much experience with building web apps, so we stuck with a terminal UI.
49.
by carllerche 5y ago
Yeah, it is decoupled from Tokio. Tokio emits instrumentation via the `tracing` crate. Tokio Console just listens to the tracing events. Any runtime that emits the same events can be used with Tokio Console. This is the tracking issue: htt
50.
by carllerche 5y ago
Not too many now. What it really needs is real usage to find any potential limitations.
51.
by carllerche 5y ago
Dumping to a file for later analysis is on the roadmap.
52.
by carllerche 5y ago
It is fairly subtle and mostly an implementation detail. In Rust, the concept of "polling tasks" was very exposed before the async/await keywords were introduced, so the lingo kind of stuck. There is an argument that we sho
53.
by carllerche 5y ago
The current release of `tracing` includes the predecessor of valuable ( https://docs.rs/tracing-core/latest/tracing_core/span/struct... ). Valuable extracts this functionality and improves on it, but hasn&
54.
by carllerche 5y ago
Also, thanks for the thought re: digit precision. I am tracking it here: https://github.com/tokio-rs/console/issues/224
55.
by carllerche 5y ago
This first release is geared primarily towards local debugging. That said, it is designed to be able to enable / disable instrumentation at runtime and it will be able to support connecting to a process in production, enable the instru
56.
by carllerche 5y ago
I'll answer the polling question. The Tokio runtime (and async rust in general) works a bit differently than other async runtimes like node. With node, callbacks are provided and executed when an OS event is received. With Tokio, there
57.
by carllerche 5y ago
Exactly, this is the first release of Tokio Console. We will keep adding functionality over time, which will help inform the APIs in Tokio to better provide the necessary instrumentation. I expect the new APIs like the task builder will sta
58.
by carllerche 5y ago
Interesting, could you elaborate on what you mean by "shared mutable state"? In the parse_line example (first one in the post), what state is shared and with whom is it shared?
59.
by carllerche 5y ago
I believe it would be possible to implement using an edition in a way that any *old* code is compatible with new code. Regarding implicitness, a lot in Rust already is implicit (e.g. type inference). Good implicitness only feels weird at fi
60.
A New AWS SDK for Rust(aws.amazon.com)
219 points by carllerche 5y ago|61 comments

More ›