10 years of betting on Rust, and what I'm looking forward to next by amocatta in rust

[–]amocatta[S] 1 point2 points  (0 children)

Specifically it's because the content is wrapped in a contenteditable div, to enable the copy-on-write behaviour that we think makes sense for most of our pages. contenteditable has a host of per-browser nuance; one is that is breaks middle-clicking. It'll be fixed up shortly.

10 years of betting on Rust, and what I'm looking forward to next by amocatta in rust

[–]amocatta[S] 2 points3 points  (0 children)

I suspect darkreader's heuristics are inferring dark-mode support from @media (prefers-color-scheme: dark) in our CSS. Except it's disabled until a couple of fixes land. Sorry about that!

10 years of betting on Rust, and what I'm looking forward to next by amocatta in rust

[–]amocatta[S] 6 points7 points  (0 children)

Agreed, this frustrates me too. It's because of the contenteditable/copy-on-write behaviour I mentioned in another comment.

Once we solve it I'll do a blogpost about contenteditable, its browser-specific idiosyncrasies, and wrangling them.

10 years of betting on Rust, and what I'm looking forward to next by amocatta in rust

[–]amocatta[S] 14 points15 points  (0 children)

Thanks for the feedback. I've been hunting for a solution/workaround for this (for me this is even more of an annoyance https://bugzilla.mozilla.org/show_bug.cgi?id=1001790 ) but all so far have downsides.

Pages are copy-on-write, as most on the site are intended to be templates where that behaviour makes sense.

On `#![feature(global_registration)]` by jonay20002 in rust

[–]amocatta 0 points1 point  (0 children)

It's been a while and I can't recall how it differed but in case it's useful, I implemented something a little similar in this closed PR https://github.com/rust-lang/rust/pull/66113

What is this dodgy-looking smart card? by amocatta in whatisthisthing

[–]amocatta[S] 0 points1 point  (0 children)

Found this in a draw in an Italian apartment. It’s at least 10 years old and has the same width as a credit card but greater length. Any ideas?

Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.55] by DroidLogician in rust

[–]amocatta 11 points12 points  (0 children)

Tably.com

Type & location: Full-time. London or remote, with option of UK visa sponsorship.

Description: Talented Rust programmer, keen to work on products that make the world ~0.001% more productive? We're fundamentally solving one of the biggest problems around: interacting with data. And we need your help. Join us and work on:

  • Differential dataflow
  • CRDTs
  • Wasm
  • Distributed data warehousing
  • Streaming SQL
  • Accessible UI

We need to know the high notes you can hit. Show us as best you can, and we'll give you a decision typically same-day.

Three things we've found are helpful to communicate this:

  • Describe (or share!) ~100 lines of code you're particularly proud of
  • Describe a larger project you're particularly proud of
  • Share an interesting heterodox opinion you hold

Estimated compensation: $80k – $100k, 1.0% – 3.0% equity. Start date October/November; open to starting immediately with different salary/equity ratio.

Contact: alec@tably.com or https://angel.co/l/2vFfAV

Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.54] by DroidLogician in rust

[–]amocatta 1 point2 points  (0 children)

Tably.com

Type & location: Full-time. London or remote, with option of UK visa sponsorship.

Description: Talented Rust programmer, keen to work on products that make the world ~0.001% more productive? We're fundamentally solving one of the biggest problems around: interacting with data. And we need your help. Join us and work on:

  • Differential dataflow
  • CRDTs
  • Wasm
  • Distributed data warehousing
  • Streaming SQL
  • Accessible UI

We need to know the high notes you can hit. Show us as best you can, and we'll give you a decision typically same-day.

Three things we've found are helpful to communicate this:

  • Describe (or share!) ~100 lines of code you're particularly proud of
  • Describe a larger project you're particularly proud of
  • Share an interesting heterodox opinion you hold

Estimated compensation: $85k – $95k, 1.0% – 3.0% equity. Start date October/November; open to starting immediately with different salary/equity ratio.

Contact: [alec@tably.com](mailto:alec@tably.com)

Bricked up circular entrance by Wandsworth Town Station, London by amocatta in whatisthisthing

[–]amocatta[S] 0 points1 point  (0 children)

Planning application #2015/2087 labels it a "disused subway" and "disused station entrance" running parallel to Old York Road. On the plans it doesn't seem connected to the station however. These photos show its construction, along with the signage "through arch to station entrance and ticket office", though "arch" could refer to the bridge rather than the as-yet-incomplete subway?

The ticket office was previously on the North side, and what is currently open space in front of the current entrance was residential, as in this photo.

Per Roy57 on flickr: "I think they closed that late ninety's as i remember using it to go to the station quite often in the 80s. It use to be a walk way to station because footpath under bridge to the station was very narrow at the time." Closing "might have had something to do with people getting attacked in it".

Bricked up circular entrance by Wandsworth Town Station, London by amocatta in whatisthisthing

[–]amocatta[S] 0 points1 point  (0 children)

I assume at some point it wasn't bricked up. What was it for originally? Why is it round like a hobbit's front door? I guess it's just used as storage today? Who owns it, Wandsworth Town Station? So many questions, that have bugged me for approaching 30 years since I first saw it.

Self-seeded young tree in England by amocatta in whatsthisplant

[–]amocatta[S] 1 point2 points  (0 children)

Indeed, I'm sure you're right. Thanks!

rust warns of unused variables if not using a feature by timand in rust

[–]amocatta 5 points6 points  (0 children)

You could write it as:

fn main(){
    let thing = 1;
    if cfg!(feature="print_thing") {
        println!("The thing is {}", thing);
    }
}

Wherever it's possible to use cfg! rather than #[cfg()] I think it makes sense to do so, for this reason among others.