Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Dagonfly
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
Dagonfly
27d ago
Plenty of high refresh gaming monitors out there that use HDMI 2.1 or DP1.4 with DSC. DSC is just the "card up the sleeve" for DP1.4, you can push it all the way to 4K 240hz HDR. So there is little incentive to switch to DP2.1 for
2.
▲
by
Dagonfly
1mo ago
Oh yeah, I've read about all your blog post on this topic :) To dump some ideas on you: I think one missing piece might be that FnOnce() -> impl Future should implement IntoFuture. Async runtimes would then use IntoFuture in their A
3.
▲
by
Dagonfly
1mo ago
Sure, thats one reason why IntoFuture and Future exist. Imo, in hindsight this is also main mistake in aysnc Rust: The whole async system should be build around IntoFuture rather than Future (async fn should return impl IntoFuture). That wa
4.
▲
by
Dagonfly
1mo ago
Here is an example of the problem: https://play.rust-lang.org/?version=stable&mode=debug&editio... Imagine if MyTrait comes from core/std. Adding an opt-out bound like ?Sized (or ?Move) is a breaking change for
5.
▲
by
Dagonfly
1mo ago
The compat issue has always been associated types on std traits. For example, should Iterator::Item be Move or ?Move If you leave it as Move, you can't create any iterators over !Move types. If you change it to ?Move, then functions us
6.
▲
by
Dagonfly
1mo ago
Passing ownership to another thread is not the same as forgetting/leaking. The point of !Forget is ensuring that once the owner goes out of scope the destructor must be guaranteed to run. An infinite loop is not a problem, cause the ne
7.
▲
by
Dagonfly
1mo ago
> the point of Pin is to wrap types that CAN move. I would highlight that there are many cases where you CAN move an object safely until a certain operation requires the object to "stay put" in place. Pin allows for that by tyi
8.
▲
by
Dagonfly
2mo ago
> some of the dirtiest electricity generation in the entire world In Europe. Still cleaner than the US, China, India, Japan, and the world avg: https://ourworldindata.org/grapher/carbon-intensity-electric... Coal an
9.
▲
by
Dagonfly
4mo ago
It's the one thing I miss from Swift when I'm using literally any other language. Interal and external parameter names. I would love for Rust to adopt: fn foo(namedParam internalName: bool) { // use internalName here
10.
▲
by
Dagonfly
4mo ago
Just to be clear: There is an official notice of the EU commission making this legal argument: https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:52... > Consequently, in the case of portable batter
11.
▲
by
Dagonfly
5mo ago
You are right that intraday went even more negative than day-ahead. But I disagree about the rest of your comment. A spread between day-ahead and intraday does not imply additional redispatch. Only some of it might have been countertrading
12.
▲
by
Dagonfly
5mo ago
So many questionable comments in here. Negative prices have no effect on grid stability. It just means that the day-ahead market was cleared below 0, i.e. for every consumer (buyer) there is a producer (seller) selling at this price. The ma
13.
▲
by
Dagonfly
9mo ago
Well it relates to this sentence: > You can use any credential manager you choose. Which I would be careful with. I can use any authenticator that the RP accepts . I could totally see a future where banks only allow certain authenticato
14.
▲
by
Dagonfly
9mo ago
Quoting your comments on github [0] >> There is no passkey certification process > This is currently being defined and is almost complete. >> no signed stamp of approval from on high > see above. Once certification and att
15.
▲
by
Dagonfly
9mo ago
For DP adoption it's too late. They should push for USB4 / Thunderbolt 4 instead. We are in the phase where about every new laptop has USB4. Connecting your laptop/phone to a TV might be a selling point. I'd love that fo
16.
▲
by
Dagonfly
9mo ago
Yes, HDCP is seperate from HDMI and DP. The source and the sink need a HDCP-licence. Both devices have embbed keys that get exchanged to estabish a encrypted channel. Without the licence you can't get the required key material. AFAIK,
17.
▲
by
Dagonfly
11mo ago
All of those are i586 or i686 though right? AMD Geode LX is the only i586 CPU produced in the last 15 years. Everything else is at least i686 and Rust has perfectly adequate i686 support. Is there any major distro left with pre i686 suppor
18.
▲
by
Dagonfly
11mo ago
That's a really subtle version of the deadlock described in withoutboats FuturesUnordered post [0] When using “intra-task” concurrency, you really have to ensure that none of the futures are starving. Spawning task should probably be t
19.
▲
by
Dagonfly
11mo ago
I recently had to do maintenance on an old WPF app and bring it to .NET9. I feel like at some point we are gonna complete the cycle and have MVVM/MVC binding engines in frontend dev. There is barely any difference left between createCo
20.
▲
by
Dagonfly
1y ago
I'm also surprised how often the preemptive vs. cooperative angle gets ignored in favor of the stackful vs stackless debate. If you choose a non-preemptive system, you naturally need yield points for cooperation. Those can either be ex
21.
▲
by
Dagonfly
1y ago
That's true. Though, for my example, the storage location of the array metadata/fat pointer is not relevant. In Rust you can hold references directly into the buffer backing the array (`&v[0]`). My Java knowledge is quite rust
22.
▲
by
Dagonfly
1y ago
> ArrayList is a wrapper around an array, and so adding entries will not move the ArrayList object, just the (wrapped) private array. That's also how Vec works in Rust. Vec is just (buf_ptr, capacity, len) where capacity is the allo
23.
▲
by
Dagonfly
1y ago
You could pose the same argument against any form of warranty. Why provide/require any warrant for anything if the company might go bankrupt? Yeah, then it gets messy. That's what the legal system and insolvency procedures are for
24.
▲
by
Dagonfly
1y ago
The initiative is not even asking you to provide the full functionality of your online-components. All you should have is a "reasonable effort" EOL plan that allows customers to continue using the parts that can work without the d
25.
▲
by
Dagonfly
1y ago
Assume your cycle detection D(TM, i) always outputs 1 when TM(i) doesn't halt (TM is the encoding of a turing machine and i is the input to TM). Otherwise, if TM(i) halts, D does NOT halt. [1] We can construct a new turing machine F(TM
26.
▲
by
Dagonfly
1y ago
> I'm curious how high up Guandong or Shanghai would be for example Surprisingly far down: https://en.wikipedia.org/wiki/List_of_first-level_administra... California, Texas, England, New York, Guangdong, Jiangs
27.
▲
by
Dagonfly
1y ago
Just in case you haven't read it, I can recommend this excerpt from "They Thought They Were Free." [1] It describes this exact feeling of "maybe I'm just being dramatic" during the rise of the Nazis. [1] https
28.
▲
by
Dagonfly
2y ago
I've never gotten this to work on an ISO-keyboard (chunky enter key). It opens "Help" in every single app, even Apple's like Finder or Safari. I've tried GB, German, US-International, and my default EurKey layout. N
29.
▲
by
Dagonfly
2y ago
As most of the kernel is in C, they probably need a raw pointer quite regularly to pass it into existing C APIs. Just like `Box::into_raw`, this method shouldn't be used in pure Rust code. It's only available for C FFI.
30.
▲
by
Dagonfly
2y ago
Nitpick: There are actually a handful Rust drivers in-tree, e.g. https://github.com/torvalds/linux/blob/master/drivers/net/ph... Though, I think all of them are direct ports of existing drivers
More ›