skysight-inc/HackerNews huggingface dataset:
Could you talk more about this? Anecdotally I've found american diets to not be fiber rich and full of fried foods, resulting in less solid BMs, but maybe you have more information?

edit: any explanation for downvotes?
Killing me softly: Graceful shutdowns in Clojure
I had this problem too when my team first adopted docker, but you can use a conventional debugger if you run your container interactively (with -i.)
>Even Google's own Pixel devices do not support this. The image quality from CameraX API is not ass good as the stock camera. And there is no support for Night Sight. I do not get this.

From the comment 2 months ago
https://www.youtube.com/watch?v=QYkTXJ2TuiA&lc=UgwBlx_R3eL4k...
You have to clean a bathroom? That explains some things.
Wow. I’ve never seen a top loader with a horizontal spin axis. Until now I never even contemplated it could be different. I wonder what other stuff is like that.
They don't look like counterweights to me. Why are they always at the same level as the booth?
Fossilized insect discovered not in amber, but in opal
> I have no idea how they were kept from rusting immediately.

Rust isn't a huge problem because the environment is very dry. Salt doesn't cause rust, it just makes it worse.
https://www.mbg.codes/

Built with Gatsby, MDX and Theme UI. Yes, overkill!
Of course you should consider performance when you start a project - if your language, framework or core design is slow it seems unlikely you'll be able to do much to improve it later. You need to at least think about it.

But I don't think "Premature optimization" is synonymous with "performance". Optimizing or perfecting every detail of a feature that might still go through significant changes over time seems risky and wasteful.
Simplifying Social Login for Your Web Applications
There isn't a vaccine for either SARS or MERS, in part because they don't happen very often. In the case of SARS, that one outbreak was it so far, while in MERS we've seen a grand total of about 1500 people infected worldwide, although the disease is still circulating.
You can't cheat physics. If you dump X gal of water from Y height it will have Z kinetic energy minus efficiency losses. We've greatly improved the efficiency of the water dumping mechanism over the years but a high end low flow toilet of today is still nothing compared to a high end toilet of decades past. That said, there's a lot of crappy old toilets out there that don't flush any better than a modern low flow toilet and take 5+gal to do it.

Source: Moved into a house that was once owned by wealthy people. The upstairs toilet was clearly top of the line circa 1940s and is awesome. The downstairs toilet was clearly subject to some serious compromises for packaging reasons and is nothing special.
You never know what kind of idiocy you'll get into with renters. The kinds of things that people think they can put down drains is endlessly astonishing.

I had one guy who kept putting kitty litter down the toilet, even after I started charging him to get it snaked out.

Another one that I have seen too often is people dumping paint down the drains...
Performance has a variety of contextual meanings. Market performance would be an example. When talking about execution performance, we're usually talking about speed/smoothness, under the assumption that a program is already correct and complete. If we overload this to include basic correctness, we would need another term to capture these other qualities.
I use this on all of my systems. It's great and supports unlocking disks with full disk encryption.

https://github.com/slashbeast/better-initramfs
Better link, article is (2018)

https://www.nationalgeographic.com/news/2018/02/trapped-atom...

Also, modals that lock the page should be forbidden.
Performance takes time and intention. It needs to be planned for _like it's a feature_ or it won't get worked on. Usually this means working with business analysts to communicate to your customer that performance needs to be thought of like a feature -- AKA given its own time and effort and space.
If the author had said, "Performance & functionality over beauty" it would have made more sense.
It says it ships with "Raspbian with a real-time patch", whatever that implies.
The earliest use of the term in the DSM is "Attention Deficit Disorder (with and without Hyperactivity)". You're clearly working from your own colloquial definitions and applying the contents of a single blog post to an anecdotal data point of your hyperactive friend.
A great pivot success story – Ben Jabbawy and Privy [audio]
There seems to be a misunderstanding regarding what Continuous Delivery (CD) is, as well as what is all required.

CD doesn't necessarily refer to Deployment of Delivered artifacts. Instead, once code is merged back into your release branch (sometimes master branch, sometimes tag, sometimes an actual release branch), it should be made available to be launched to production. This doesn't mean more testing isn't required and it doesn't mean that humans are not involved. Continuous Deployment is the process of releasing software to production automatically.

If you did in fact mean Continuous Deployment then you do not need 100% integration test coverage or anything of that nature. Typically, the process might work by releasing a canary deploy which receives a fraction of the traffic going to production. In the unlikely event a breaking change has silently made it through your other tests, it should likely be caught when it is deployed as a canary. If in the extremely unlikely scenario it makes it through both then the existing pipeline you have can be used to "roll-forward" a fix automatically instead of via the human process that is much more likely to fail.

This may seem like a lot to you, but you are front-loading quite a bit of work and a mature pipeline is much less error prone than manual deploys.
The DIN rail idea is very neat. I've seen a few projects of mounting regular Pi's in server racks but DIN is a much more compact form factor. Wonder how long until someone makes a regular Pi to Din kit.
A LOT of people just don't understand how to use a plunger.
The author here seems to be missing the basic point of the phrase. Others have correctly noted that performance is a feature, but even with that taken for granted, it is not often apparent what the constraints of the full system are until they've been built. You may try and guess, but you're more likely to guess wrong than right. Look at OSes, ISAs, DBs, etc. All of those have been rewritten numerous times not because the originals paid no attention to what performance would be like, but rather because they did not know how to improve performance until they had something they could test.
Python Community Interview with Kelly and Sean of Teaching Python
This is pretty much why I've settled on the idea of buying a small flat.

I've lived in most different types of place now (rurally, in the suburbs, in inner city suburbs, in the middle of metro areas) etc and the idea of having to decorate a massive house is something I really can't be bothered with. If I had children I'd want enough space for them, sure, but that's about it.

It's not even about the cost but just the mental overhead of it all, cleaning, all the stuff you accumulate, etc.
Is a specialized MIP solver mandatory, or would using a general SMT solver like Z3 usually be good enough?
Better-initramfs: initramfs supporting SSH, lvm, luks, raid, uswsusp and more
A very simple version of this: I used to find that my macbook was randomly going to sleep all the time when I was working with it. Eventually realized that it was because I was using my ipad pro right next to it, with its very strong magnets for the smart keyboard---and magnetic sensors are also how the macbook tells the screen is closed. Could probably put one to sleep by just waving a sufficiently strong magnet in front of it...
Coronavirus 2020-NCoV
But we are using other, more precise terms already, no? Speed, fast, slow.
> If we create general AI and it ends up valuing personal freedom as much as we do...

Those are two absolutely gargantuan “if”s.

I’d like to see more discussion about whether it’s appropriate to project the idiosyncrasies of our imperfect, competitively-evolved biological brains— like resentment and anger— onto hypothetical thinking machines.
I disagree. Performance is almost always an implicit goal. People don't state it very often because it's so obvious. Why wants slow software?

But more importantly this article is a rebuttal to people saying "we can optimise performance at the end". They aren't saying "We never intended for it to be fast and we aren't going to bother trying to do that." they're saying that performance is a goal. Look at the examples he screenshotted. Nobody says "dude, performance isn't a goal of this project; you just have to live with it being slow".
See e.g., https://www.medievalists.net/2013/04/did-people-in-the-middl..., which describes the many bathing habits of the Middle Ages that contradicts the original article's claims, including this anecdote:

> The Dutch philosopher Erasmus, writing in 1526, notes the fall of the public bathhouse. “Twenty-five years ago, nothing was more fashionable in Brabant than the public baths,” he remarked. “Today there are none, the new plague has taught us to avoid them.”

That is, water does spread disease, and public baths went out of fashion during the Renaissance, not the Middle Ages.
Why would you renovate your bathroom so often?
I realize everyone here seems focused on the file system, but one of the things stressed by the OpenBSD project is that difficulty in upgrades are the root cause of the biggest problems.

Case in point.
Which seems absolutely crazy to me. I would have expected them to push for them harder than your typical org since such a sweeping change would affect everyone basically the same. Nobody would be immune from raising their prices and the value differential would nudge customers away from fast food.
The toilet and shower being in the same room is the biggest issue. If someone is in the shower and someone needs to go to the toilet that's a problem. The worst is in the morning with homes where more than two people are living.

From what I understand many in the UK, European countries have separate rooms for toilet and bath.
OP was referring to the EU. If it would be about Europe, then the population would be 740 million.
I believe OP is referring to the terrible readability and color contrast, with that background color.
Although the design and expectation is the same in my native Britain as most of the rest of Europe, I've only seen signs like this in France and Germany [1] -- usually in quieter public buildings, like government offices.

[1] https://pbs.twimg.com/media/ChR8ubSW4AEeDcV?format=jpg&name=... from https://twitter.com/hashtag/toilettenb%C3%BCrstenbenutzungsa...
I'd say more like "comfort."

No one wants to hold it while the other person is having a nice relaxing poop.
There are also ways around this by suitable generalizations of MILPs, namely mixed integer comic programs (MICPs), which are about as fast to solve in practice. This generalization allows you to use nonlinear (convex) functions in the objective and in constraints. Coupled with the integrality constraints, almost all nonlinear problems I’ve encountered can be written as MICPs.
I'm not convinced there's much (non-real-time) software where performance places legitimate constraints on deadlines.

I've seen exactly one case before, which was an ancient script running on a mainframe in a bank which took 6 hours to complete overnight. [And, by the way, correctness is still more important in this case!]

But 99.999% of the time, your code's performance is not the final word.
Is it really better for money-wise to make frequent renovations if you plan to eventually sell?
I just do most of the work myself and only contract things out directly (hire the tile installer directly, don't use a "remodeling" contractor) to make things affordable.

Obviously there are still expensive parts, but we don't rebuild the entire bathroom every 15 years and we don't have to do that rebuild all at once.
Among developed countries, the US has one of the harshest "justice" systems.

It still has death sentences and the dubious record of an incarceration rate higher than any other country.
UK proposes law for IoT security
Goldman Sachs will no longer do IPOs for companies with all-male boards
NASA 3D Models
Or if they are Trump 10-15 times: https://www.youtube.com/watch?v=VygBCFQVFgM
You're being downvoted, which I think is because you've clearly decided nothing I can say will make any difference to you and your replies seem a bit cranky, but I'm not downvoting you.

Here's another example for you, that just happened today:

On a shared iPad, the iPad was returned with a note saying 'no safari'. I worked out that one student had changed the default Safari search engine to DuckDuckGo. For reasons, the school's ISP blocks DuckDuckGo and visiting it on an iPad just results in a 'connection was lost' message.

The next student needed to visit a website called Kahoot and the URL for this site is kahoot.com. Looking at the history I could see the student had just been typing 'kahoot' in to the URL/search bar over and over again. They also tried typing 'google'. At no point did they try entering the URL nor does it seem they even know how to do anything beyond type search keywords.
This makes me not want to learn elixir. Learning one language and becoming masterful at it is hard enough. There's too many "learn this language, but also this other language and platform"'s in my life (JVM-based work, and anything in the front-end JavaScript world it feels like these days). It just feels like you are telling people "Here, learn this language, but also learn the assembly instruction set for your architecture as well" -- that's not the reason I choose to use higher level language.
I don't think hair is usually included in the faked part. Generally for a convincing result you would use a base video of someone who has at least some semblance to the target (including hair).

It is also possible that hair was disabled to get real-time performance for this (quite impressive) demo.
> There is no such thing as "ethical technology".

Commonly expressed opinion, and for a reason of course.
But I have come to think that rather there is pretty much no such thing as 'morally neutral' technology. Everything lends itself more or less well to different purposes, and can, and often will, interact with an immensely complex society rife with morally loaded choices and actions.
There was an eloquently presented thought experiment I heard many years ago, for which I have unfortunately forgotten the exact context, but I suspect it may be from former US Secretary of Defense, Robert McNamara. (If anyone recognizes this one, I'd be grateful if you refresh my memory)

Play with the thought that someone comes to you and presents you a ground-breaking invention, namely a procedure to manufacture dirt cheap, compact atomic bombs. Nuclear weaponry needs no longer be beyond the means of even the humblest citizen.
Well, that would be a stunning scientific and technological achievement. We should probably give this person the at the very least the Nobel Prize and an annual feast in their honor. Is that what would happen? No, more like it, we'd make sure we have all copies of the schematics and then lock him up in isolation and throw away the key.

It's an extreme case, naturally, but I think it's a neat illustration that there are powers whose properties have a profile which give them a completely predictably huge and horrifying potential for abuse and great difficulty to use for good. And conversely, arguably those which have very readily apparent beneficial uses and would be much harder to use for nefarious purposes, though that direction may be tempered somewhat by the fact that there are many more ways for something to be broken than to be whole.
I'm asking myself the same thing... but I think he is referring to Load Balancing and Logging and maybe Public Key Pinning? Not sure... I'm however sure that Google and Facebook are not the only ones who do Load Balancing and Logging and therefore aren't the only ones who can benefit from CD :)
Dataset Store for Computer Vision
> Why don't people plan for potential disasters? [...] even people who do have more time and money also haven't generally thought through simpler preparations.

I can't speak for everyone, but despite having money and discretionary time, my list of priorities has an event horizon entry called "relax and recharge ready for tomorrow" and very few things below that make much progress.

Should I plan for potential disasters? Sure, it's on my list of priorities, just after 'do a proper cut to increase my abs definition' and 'get to know my neighbours well' and just before 'finish that online Spanish course I started' and 'write down the serial numbers of all my electronic gadgets'

(Of course, I live in the UK. So to me it seems extremely unlikely I'd ever face the kind of disaster where I'd, for example, need 15 litres of drinking water.)
Preprint and not peer reviewed. The WHO had it at 1.4-2.5 a few days ago.

https://www.who.int/news-room/detail/23-01-2020-statement-on...
Incidentally, the Raspberry Pi Compute Module is indeed "rather unknown", which is a shame. It is amazingly useful and lets you design devices without getting into high-complexity PCBs and BGAs. You can place an SO-DIMM socket on a simple 4-layer board (adventurous types might even go with 2 layers if you don't need USB) and build a computing device that would otherwise be out of reach.

Another added bonus is the built-in flash, which is significantly more reliable than the whole SD card setup (for many reasons). Or the two CSI ports (only one is exposed on the standalone RPi board).

All in all, for anything except prototyping, this is a much better solution than a standalone RPi. In my designs, I found it to be a useful and reliable workhorse.
It depends on your definition of "Europe" - the EU is indeed quite a bit smaller than the United States, but the continent of Europe is, as you have noticed, slightly larger in area than the United States.

I can still remember pointing this out to someone on HN who stated that Europe would fit inside Texas.
Hi, I'm a kernel dev on the Revolution Pi team. AMA.
Sounds like data was on one pool with a 3 disk mirror setup and nowhere else. This is 'RAID is not a backup' territory. Much better would have been to duplicate the volumes themselves somewhere else (eg using zfs send/receive to a different host) and ideally the contents of those volumes too.
Shouldn't be America first?
> Well, with DNA, on this planet apparently the first version of life able to reproduce at all significantly was based on DNA, and all versions of life since then, including us, have also been based on DNA. Moreover we got here by small modifications of the DNA.

Are you sure? I remember that life started as RNA not DNA.
If it's regularly taking 2+ flushes you might want to consider changing your diet.
FYI recent discussion here:
https://news.ycombinator.com/item?id=21702424
> The important part of "premature optimisation is the root of all evil" is PREMATURE.

Right -- I think the examples he's arguing against have slightly misunderstood what "premature" means. The quote is supposed to mean, "Don't optimize until you know that optimization is necessary." The people in his examples are interpreting it as, "Don't optimize until your program is feature complete". I doubt Knuth would agree with that principle. If people are raising tickets saying that some feature is slow, then you know optimization is necessary, and it's not premature any more.

That said, as with any proverb, you have to use some common sense. If you know you're going to be doing key-value lookups in a data structure that's going to contain hundreds of thousands of pairs, it's OK to start off with a hash table, rather than starting with flat list + linear search and switching over only after benchmarking.
High performance code can often be an order of magnitude longer and more complex to write than moderately performant code. When you're not even sure what you're building yet, aiming for performance first is a waste of time and a good way to ensure you end up not realising anything at all.

Optimise for what's important for your specific project. Maybe exploring the design space is the priority to start. Maybe releasing before the end of the year is more important.

Not all projects are the same so it's pointless to argue about general rules like this.
Ours has a cleaning cycle we run about once a month that sanitizes the machine. I've been adding a recommended cleaner with it, but I think even that is unneeded.
I think it depends on if your design is conducive to performance or not and this is the cross-purpose here.

If you've architected a bunch of end points that are chatty and jump layers in a weave of a tangled mess or built an app infrastructure that never isolates expensive operations and just arbitrarily inlines them, then you'll struggle to optimise it later.

But if your architecture is relatively sane and your data model apt for the features at hand and those on the horizon then finding hotspots and improving performance many times fold is totally doable later.
Yeah, "force quitting" apps in that way is the only way a user can force-reset the app's case if they it a bug or if the app starts behaving unpredictably.

If you quit an app, open something else, and then come back to it, it should maintain state.
Note that "canary deployment" (I hate the usage of 'deploy' as noun.) is only possible under specific circumstances. You would not want to do that with your database, for instance (aka, "0.5% of your data might now be corrupt or lost) or your development tooling (aka, 0.5% of your deployed code might not do what it should do according to its source code).
Except in the very common case when 2 of those people are children.
My wife and I tend to only rent places that have at least a powder room on top of a primary bathroom for this exact reason. It isn't often we need that dual toilets, but after contracting food poisoning with only a single toilet... we decided never again.

Dual toilets have rescued us twice now from inevitable accidents.
They don't say they're sorry, because they're not. Instead they minimize their actions by: 1) stating how few customers customers were affected, 2) how it's not really their fault because it was a hardware error, 3) it's not really their fault because they had already planned to upgrade the server, 4) it's not really their fault the restore procedure took so long because they had to make backups first, 5) the restore took so long because spinning disks are slow, and they really had no way to know this in advance. And to top it all off they point out they're not contractually obligated to provide working snapshots at all, so really it's the customers who are at fault here.

The take-away here is clear: don't trust Gandi with anything you care about.
In my opinion, the truth is somewhere between what the author is suggesting and what most developers actually do. I recently came across The Fallacy of Premature Optimization on ACM [1], which I think is a much better take on this topic. It clarifies the statement that started this confusion which, in whole, was "We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil" [2].

The key words being "small efficiencies", but you seldom hear that part of the quote.

[1] https://ubiquity.acm.org/article.cfm?id=1513451
[2] Sir Charles Antony Richard Hoare
I've done a lot of continuous deployment to staging and dev, with regular 'releases' to prod. It doesn't need to go straight out to prod every time you push some code.