Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
> This appears to be related to a behaviour that ProtonMail has of dropping all plaintext email if any mime-encoded parts exist.
https://github.com/ProtonMail/proton-bridge/issues/26#issuec...
I'm actually more shocked knowing that they drop plain text if there is a mime-encoded part (e.g. HTML). Just verified that all mails imported from GMail and all newer mails I received in PM only have the HTML part now, while GMail shows both HTML and plain text parts in message source. Great, now if I want to use a text-only client to read those mails in the future, I won't be able to.
Now I honestly wonder, how did they think this is something okay to mess up? Is there just no usable email hosting service for someone that want their mails not touched and also stored securely? Like, this is not even going to save storage space for PM - I'm paying for my storage.
Python formatter Black: https://github.com/psf/black
> By using Black, you agree to cede control over minutiae of hand-formatting. In return, Black gives you speed, determinism, and freedom from pycodestyle nagging about formatting. You will save time and mental energy for more important matters.
Prettier also came to mind, and I'm usually pretty happy with the "it's formatted this way, deal with it" approach - but I also would like the tool to behave predictably with updates. Prettier had some changes in 2.5 related to multi-line-classnames (namely, forbidding them), which in turn made it unusable for projects with tailwind usage, as it now forces extremely long classnames in some cases. (Especially for elements that have styling based on a breakpoint and a darkmode variant, you're hitting >120 chars easily).
I know that you can go for descriptive classnames and "@apply", but I was still miffed about a change like this in an already existing tool, with a lot of community pushback and no compromise in sight.
(Here's a relevant discussion, but keep in mind that multi-line-classes worked at some point and now just don't: https://github.com/tailwindlabs/tailwindcss/discussions/7763)
So for prettier, it wasn't just "format your code our way or else" - which is a good approach for a formatter, see also gofmt - it was "your current set up doesn't work anymore, tough luck".
Related posts
- How to setup Black and pre-commit in python for auto text-formatting on commit
- Let's meet Black: Python Code Formatting
- Show HN: Visualize the Entropy of a Codebase with a 3D Force-Directed Graph
- Introducing Flask-Muck: How To Build a Comprehensive Flask REST API in 5 Minutes
- Auto-formater for Android (Kotlin)