pyre-check VS psst

Internally we use Pyre for Python type checking: https://github.com/facebook/pyre-check

Before type hinting, work had intense rules and linters enforcing docstrings with types. Now, type hints and automatic pyre runs take care of all the heavy lifting.

Python now has an optional type system and if you add one of them such as mypy or pyre to your CI process and you can configure GitHub to refuse the pull request until types are added you can make it somewhat strongly typed.

If you have a preexisting codebase I believe the way you can convert it is to add the types that you know on commits and eventually you will have enough types that adding the missing ones should be easy. For the missing ones Any is a good choice.

https://pyre-check.org and https://github.com/python/mypy are popular.

So to find things in a similar space, you need to look for languages with these sorts of constraints - so things like Sorbet for Ruby or pyright/pyre and you'll see similar and new ideas

Facebook/Instagram uses Pyre which is a typechecker for Python.

I'd be curious if the pyre-check compilation is any faster for you either by removing the inlining optimization flag (the `-Oclassic` here https://github.com/facebook/pyre-check/blame/36243764ab81a82...) or whether there's a way to compile pyre-check to bytecode instead of the native compilation step (which unfortunately it looks like there's no easy way to modify pyre-check's build config to do so).

I must be doing something wrong.

[1] https://github.com/facebook/pyre-check

Some other good alternatives for type checking are Pyright (which is seen in VSCode via Microsofts PyLance plugin) and Pyre.

On the other hand, this Rust-based one called Psst looks awesome and works: https://github.com/jpochyla/psst

Psst but currently very limited in features and have to build yourself.

psst, https://github.com/jpochyla/psst

Would like to add that you can also use clients such as spotify-qt and Spotify TUI to control said "device". There's also Spot and psst that are standalone (librespot not required but no Connect functionality).

You can also take a look at Psst. I use Symphonia for decoding and CPAL or CubeB for output. CubeB is a bit nicer.

There‘s a Spotify client, psst, which has an Async widget (with a Promise state struct) that works very well for loading states etc. That project has a bunch of other tidbits and interesting patterns for Druid, I learned a ton from the code.

Not that I'm in any way suggesting that you have to have to pursue this, but I'd suggest that not having this as a goal is why it hasn't happened. I've seen apps built with Druid (like https://github.com/jpochyla/psst) and they look great. But when I looked into the documentation, I was really struggling to get started. In contrast, libraries like Iced are quite limited in what they can do and are not as architecturally sound as Druid, but seem to have put more effort into the onboarding experience and documentation for beginners (see also: the effort that Rust itself puts into being beginner friendly, and how that has enabled it jump into the mainstream where other similar languages have remained niche).

The Psst spotify player is just awesome.