HN user

zuzun

686 karma
Posts0
Comments177
View on HN
No posts found.

They perform several model runs with slightly different configurations and then compare the predictions to a reference period, currently 1991-2020. When they say "above average", most model runs fell in the upper tercile of the reference period and the probability is derived from the fraction.

Up in the Old Hotel by Joseph Mitchell. I finished it yesterday.

It's a collection of articles the author wrote for The New Yorker around the middle of the last century. The stories are portraits of weird, eccentric people and peculiar places in and around New York. Mitchell describes his subjects with dignity, without putting them on a pedestal.

The author is a very good writer and his stories are enjoyable, but only after I had read the book to the last page, I understood what makes this book so great. The stories tell you as much about the author as they tell you about the protagonists. I started the book to get a glimpse of the old New York and finished the book with a great curiosity about the author himself.

WeatherKit 4 years ago

They still publish all their data free of charge and are required to do so by law. For weather forecast, they dump all parameters of their recent model runs.

So I guess I'm saying that you can already build such a system yourself quite trivially...

My rule of thumb is that once I start writing imperative LaTeX with loops and stuff, I'm almost always on the wrong path. Now, I might be missing some important corner cases, but by skimming through the blog post, I feel like the author's solution is too complicated. For example, I don't get why this requires auxiliary files.

I would create a counter for the affiliations, let the \affiliation command define macros that contain the name of the affiliation and the value of the counter and then append the output to two different helper macros, one for authors and one for affiliations, whose contents I dump in \maketitle.

Memory safety is optional in Rust. It might not be obvious at the moment, because Rust is written by enthusiasts who enjoy fighting with the compiler until their code compiles, but once developers will be forced to use it on their jobs with tight deadlines, unsafe becomes the pass-the-borrow-checker cheat code.

The GDPR is a sensible legislation and no amount of FUD can change that. If you can't explain what you are doing with personal data, you shouldn't be allowed to handle it.

You are also confusing legislation with rulings. GDPR says your business interests cannot outweigh my rights. That's it. Now courts find that leaking my IP address to third countries is something that harms me more than it does your business good. I can live with that.

The problem is that the designers of small icons already work with pixel-snapping and for complex graphics, dumb quantization will look and compress no worse. If you want to work on path optimization, improve Inkscape's path simplification, because why bother with the alignment of a control point that isn't necessary in the first place!?

I don't see what's fundamentally wrong with EV certificates, as long as the certificate authorities do the proper verification. The certificates contain more than just the business name, so I think the criticism should be directed towards browsers that hide the relevant information behind 5 clicks.

You can get the web fonts below 20 KB each if you subset them. You can also check if they are present on the system with `local()` before `url()` in the font-face declaration. You could also give the Apple system fonts a higher priority than Inter, because Inter and San Francisco are pretty similar.