I’m not a huge fan of Warp, but I would love for any other terminal to copy its text editor-style input field.
It’s so much nicer for 90% of my terminal usage (long multi-line commands, etc.) And when you do need TUI behavior that 10% of the time, just toggle it off.
VPC endpoints in general should be free and enabled by default. That you need to pay extra to reach AWS' own API endpoints from your VPC feels egregious.
Just offloading the analysis to the phone is extremely funny. It also seems like a pretty obvious solution, so I wonder if it was delayed by legal analysis and they only just decided it was likely to hold up in court.
As a recent Linux (and Wayland) switcher, I love this behavior. It has always felt insane to me that macOS will just let some random auto-updater steal focus and eat your keystrokes while trying to work on something.
I like Nix but I think the current model of reinventing a new set of declarative configuration settings for each package is fundamentally misguided and will not scale in the long term (look at the number of program-specific options in Home Manager for example).
The nice thing about container-based systems is that all the existing documentation for configuring a given program continues to apply as expected. Of course the tricky part is figuring out how to compose them together.
I don’t know what you mean by this, unless there’s a personal reason.
LGA has a free shuttle bus from the subway, JFK and EWR have AirTrains connected to the subway, and SFO has a direct BART connection.
I use public transit exclusively to get to all of those airports.
My guess would be that this is in support of the preview hover feature. For a while now, you can watch an entire video just by hovering over it, complete with captions, scrubbing and audio. This wouldn't be very useful if the thumbnails were still tiny like in the past. Personally, I like this feature and don't often need to look at tons of thumbnails at once, but to each their own.
Abandoning traditional constructors and all their strange special-cased rules in favor of regular old class methods that return Self was one of Rust’s best design decisions, I think. Super easy to reason about. Glad to see similar techniques being advocated for other languages.
Gross. The slow intrusion of ads into more and more places might raise revenue a little bit, but tarnishes Apple's brand image. Apple News is already a revolting app, only somewhat saved by the fact that Google News is even worse.
I've already decided that my personal line in the sand is when they replace the scenic screensavers on Apple TV with ads, something they're already toeing the line with in the newly added Peanuts screensavers. At that point Apple has lost the plot and I want nothing to do with their products anymore.
Wow, I really, really like this! A couple points of feedback (based on testing out Japanese -> English translation):
- It took me a second to find auto-pause. Maybe some of those things in the settings menu could be more accessible, similar to how Spotify puts shuffle/repeat icons near the play button.
- I would really like the arrow keys to move back and forth between auto-pause points.
- Regarding auto-pause, it seems to clip off a little early, maybe consider extending the duration or adding a little bit of overlap?
- When clicking to define a word, "Define in Context" is a nice feature to have but is maybe a little slow (and possibly expensive on your end?) to have as a default. I think just opening a static dictionary lookup by default would be nice. With Japanese, I am able to work around this with the Yomitan browser extension though.
- I probably wouldn't use the spoken translation feature, but when I tried it, the voice sounded very robotic considering the high standards for AI-generated voices these days. Though I imagine a better voice might be a cost barrier.
Please don't take this as harsh criticism, just some initial impressions. Overall I really like the idea and will likely continue to use it for listening practice.
Using #[from] in a thiserror enum is an antipattern, IMO. I kind of wish it wasn't included at all because it leads people to this design pattern where errors are just propagated upwards without any type differentiation or additional context.
You can absolutely have two different enum variants from the same source type. It would look something like:
#[derive(Debug, Error)]
pub(crate) enum MyErrorType {
#[error("failed to create staging directory at {}", path.display())]
CreateStagingDirectory{
source: std::io::Error,
path: std::path::PathBuf,
},
#[error("failed to copy files to staging directory")]
CopyFiles{
source: std::io::Error,
}
}
This does mean that you need to manually specify which error variant you are returning rather than just using ?:
but I would argue that that is the entire point of defining a specific error type. If you don't care about the context and only that an io::Error occurred, then just return that directly or use a type-erased error.
No. Screen Time (their parental controls implementation) is easily circumventable, includes a “One More Minute” feature that can’t be disabled, doesn’t sync properly, manages to crash Safari in mysterious ways… I could go on.
It’s disastrous, like an intern-level project that was shipped and never improved upon. And these are the only parental controls APIs available, so competing apps aren’t even possible, they ultimately just serve as alternate frontends for Screen Time.
Venvs are so clunky and probably the biggest stumbling block for beginners.
There was a proposal for a directory-based node_modules analogue which was unfortunately rejected.
I think that would have been the single biggest improvement to the Python onboarding experience ever.