I think it's funny that HDI doesn't have a tooltip hover, but the other 4 spelled-out headings do.
427 karma · joined May 10, 2013
I'm going to try your recipe.
From http://data.consilium.europa.eu/doc/document/ST-5419-2016-IN...
Article 83:
Section 4:
> Infringments of the following provisions shall, in acccordance with paragraph 2, be subject to administrative fines up to 10 000 000 EUR, or in the case of an undertaking, up to 2% of the total worldwide annual turnover of the preceding financial year, whichever is higher:
Section 5:
> Infringements of the following provisions shall, in accordance with paragraph 2, be subject to administrative fines up to 20 000 000 EUR, or in the case of an undertaking, up to 4% of the total worldwide annual turnover of the preceding financial year, whichever is higher:
- The first item added has rank "m"
- If I want to add an item before that, it's m-a/2 (somewhere around "f")
- If I want to put something between "b" and "c" that's "bm"
- The database can sort it just fine.
> We have shown that, within the boundaries of our corpus, there are no significant differences in aggregate between pre-prints and their corresponding final published versions. In addition, the vast majority of pre-prints (90% - 95%) are published by the open access pre-print service first and later by a commercial publisher. Given the fact of flat or even shrinking library, college, and university budgets, our findings provide empirical indicators that should inform discussions about commercial publishers’ value proposition in scholarly communication and have the potential to influence higher education and academic and research libraries’ economic decisions regarding access to scholarly publications.
As I've never even paid attention to the sending address of GitHub merge notifications, perhaps the principle is: "If someone notices that your email came from noreply@ then you shouldn't use noreply@"
(And, no, you don't seem critical -- more like thoughtful)
I'm writing from the perspective of a customer. As a customer, I don't care how your email queues work. I do care that you sent me an email and forbid me from replying to it. It chafes. And you want my money?
From the perspective of a company, I can sympathize. I've been directed to create noreply-sending mailers in the course of my job. In every case, it would have been better sent from support@, but because of understandable but dumb reasons (bureaucratic laziness; not-my-problem-itis), it's way easier just to turn on the mailing hose and forget replies. So that's what we did.
I've also worked on handling bounces of both email replies and (cringe) faxes. Yes, handling bounces can be annoying, but to create a good customer experience I think it's worth the cost.
Avg Energy Impact:
- 14.08 Google Chrome
- 3.01 Docker (for Mac)
- 2.55 Sublime Text
- 2.04 Slack
- 2.03 Terminal
- 0.28 Mail
- 0.20 My Electron app (which hasn't been open all day, so this number is definitely wrong)
Some of those surprise me.
Those who complain about Electron being a hog are right. But it's not like there's nothing that can be done about it. I'm sure there are optimizations that could be made to reduce resource usage. Firefox recently improved memory usage. With enough demand, I'm sure Chrome could, too.
> we're almost leaving the 90's and entering the 00's.
Because I feel the opposite: computers were first terminals attached to mainframes, then in the 90s the pendulum swung to personal computers free from the mainframe. In the 00s we swung back to the "cloud" (terminals dependent on the central computer) and LHTML feels like the pendulum swinging back to computers being able to run without the mainframe/cloud.