“I've learned that when people give you notes on something, when they tell you what's wrong they're usually right, when they tell you how to fix it they're usually wrong” — Bill Hader
@noharmpun no joke. It is a quote from Bill Hader in an interview when talking about script writing, which I'm sure is just a remix of earlier thoughts that he's heard, but I liked the way it was framed and fits my understanding of how to take feedback constructively.
A bit blurry due to using a 2x converter on a very soft 500mm on a cheap tripod with very bad skill, but still very happy with how it came out. #Photography#SutroTower#SanFrancisco#Moon
Sometimes I wish that rustc had a database of small breaking changes that affect only a handful of crates, so that we could on the fly patch them going forward. Things like "we now correctly check for lifetimes in assoc types" can technically be a breaking change that affects a handful of crates, but I want to ensure that building a project from today in 15 years doesn't require a compiler tool chain from today.
I guess this is the windows backwards compatibility approach. #rust#rustlang
"#Rust development is going too fast (because they are stabilizing features I don't care about) and going too slow (because they are not stabilizing features I care about!"
There are only so many #RustLang contributors, hours in a day, days in a year to get to everything now, and some features are reliant on other, less flashy work that needs to happen before they can be even attempted.
But people are putting in a lot of work, the codebase changes so quickly that it is hard to keep up.
Was just getting super pissed that the autofocus on my 28-105 D and D750 wasn't working and was scared it was the the screw motor on the body, but my 35 f2 D and 80-200 f2.8 both work, so maybe the 28-105 needs more torque than what the D750 can provide? It used to work, but I guess for now I'll have to stay with a prime walking around lens on. #Photography#nikon
Request for feedback: how would you change this #Rust compiler error? Can you tell what's going on? What the problem is? Do you get a sense of how you might be able to solve it?
@ekuber I'm not saying it should be disallowed. I'm saying it has bad UI. People get into such situation by accident, are unaware when it happens, and a simple cargo update can add dupes to a no-dupes project without informing the user, and without straightforward ability to undo that.
@ekuber yeah, that's the "it's possible" case that bothers me, because two different versions of one dependency at the same time shouldn't be possible in the first place.
Disallow this, and the entire ecosystem has to adapt, and will adapt.
Allow it, and every project will be susceptible to having that, and endure the side effects...
Proc macros in #Rust are objectively bad in a number of ways (limited to only dealing with tokens/no type system access, hard for newcomers to grasp and write, force a lot of attributes to be written to annotate specific items, etc.) but they exemplify "worse is better" perfectly. They are incredibly powerful and allow people to build amazing abstractions that are in some cases best in class. We want to have something better, but there isn't a pressing need now to rush a replacement. #RustLang
I'm glad that #Rust is now at a stage where there aren't any major missing pieces, almost anything you want to do can be represented, just in round about ways and sharp corners that we can chip away in time. Better than the situation years ago where most people used nightly exclusively because there was missing functionality in stable. We still need a way to have "stable early access" for features close to completion, though. #RustLang
@ekuber They are far better than C macros that have no restrictions on input or output. That’s not to say things can’t be better, but how could this even work? So much type information isn’t available without expanding macros recursively already, then you need to resolve dependencies and compile. You have a chicken or the egg problem then.
My biggest gripe is that proc-macros2 is still necessary and knowing when I have to convert types between that or the extern’d proc_macro types. #rustlang
"Incrementalism isn't enough, so we should do nothing until the revolution" only ensures that nothing changes, ever. It's a fundamentally conservative position because the result is the same as "we should do nothing because the status quo is good".