skysight-inc/HackerNews huggingface dataset:
It is.

You might have a 10 second build process that does 1 MB of disk IO and it becomes a 100 second build process that does 10 GB of disk IO because you ran it in Docker.

I see people who "know how Docker works" put no care at all in the order of their image builds and end up doing 10-100x more IO than they need to.

Docker is fast compared to the time scale most people deploy servers at but is slow compared to the scale of a healthy software development process particularly if you are not running on a cloud server or are working on a gigabit connection.

If you took the time you spent trying to eliminate entropy from Docker, Kubernetes and such and actually tracked down the entropy that comes in from your environment (like the vandal who set your platform charset to not be "utf-8") you might find you don't have time to check your phone or send your co-workers stupid GIFs on slack waiting for builds.
And yet, the end result is that OP can't advertise on Google if they're using a Google Analytics competitor.

Whether through incompetence or malice, the end result is still the same.
Looks like this might only be an issue with dark-mode. In regular mode the active tab is very visually distinct.

I think this is a more general problem with dark-mode interfaces. Contrast of content is usually easy to achieve (e.g. light text on dark background) but getting contrast between UI elements like tabs is quite difficult.

Apple had a great talk about the design challenges at WWDC 2019. One of the ways they do this is by integrating ambient colours from things like the desktop wallpaper which Firefox doesn't do.
If it works for you don't sweat it.

Docker is fine but if you don't need it then fine (and managing it yourself is usually a pain). But do make sure your systems are up to date (basically your linux distro)
United plans to bring back supersonic air travel
I've concluded this buy looking at some of the makefiles that people are referring to and the way the description of the tool is worded.

Calling makefiles a "single source of truth" for "dev commands" sounds to me like a glorified shell script aggregator. That's not what make is.

All in all I have two issues:

1. The naming of this tool. It's not make specific, you could literally make this tool run anything else and it would still work identically. But in this case it seems to be encouraging misuses of make.

2. The concept described by the tool's documentation that makefiles are "a single source of truth for dev commands".
I live in a neighborhood full of families and the number that actually use their yards for anything other than mowing is minimal. As for my own kids they seemed to have much more fun in the nearby woods than the yards.
It's not really surprising. HN loathes any technology with a ton of hype surrounding it.

14 years in currency trading/quant/FinTech. Regardless of the tech, if you don't own at least some BTC/ETH at this point, I don't know what to tell you.
There's a number of reasons I feel this assumption is valid in most cases:

1) Unless it's a targeted attack it's highly unlikely that a ransomware strain will be designed to target a specific filesystem. Snapshot deletion requires filesystem specific APIs, whereas reading/writing files is just standard libc fare. You would need to maintain different strains of a virus to target an organization running Btrfs vs ZFS vs ReFS, for example. - If the attacker has deep knowledge of your storage stack, and has gained privileged access to it, you've already lost: go to step 4.

2) Separation of privileges. Deleting a snapshot is a privileged command. A ransomware infection that doesn't successfully elevate privileges might be able to encrypt my home directory, which would suck, but it wouldn't have permissions to delete snapshots of my home directory.

3) Virtualization / network storage: snapshots are transparent to virtual guests, a virus inside a guest can't delete snapshots if it's not aware they exist. With network shares and ZFS: you can choose whether or not you want to expose snapshots. If you do expose them: don't grant network clients privileges to delete them.

4) Replication: with any ransomware infection the only real defense is off-site backups. Snapshots makes backups trivial. You can incrementally replicate and restore from them easily (e.g: zfs send/recv.) This alone makes using a CoW filesystem worthwhile in the defense against ransomware. Ransomware will have a hard time deleting snapshots on an air-gapped disk.
Bare metal usually refers to not running in a VM or other actual virtualization tech that boots a nested guest kernel inside the host kernel.
The revisionist practices of the media; they are never wrong.
You don't really need more people than we have currently. We're deplete resources faster than making them.
The bar is really low if the person helps push the narrative.
Just pull yourself up by your bootstraps... oh wait that's physically impossible.
Interesting choice for Stripe to republish this one veering away from their original content run.... I think it's a fairly well known book from back in the day but that's just it, the story it details ends in 1985 so it's really missing a huge chunk of the changes that continued into the 90s and may have lesser known stories. Yes, this is about the foundations, but so much has already been said about the garage-band startups and hippie vibe that gave us Apple etc, so re-issuing this seems kinda meh.
My career specialty is deployment at the 10^5 scale and I'd argue that Python has no business on Production systems. Heck, I'm a former career Rubyist and I'd say the same there too. At a certain point statically linked binaries are going to make several classes of hard problems to solve disappear entirely and is IMO baseline criteria for operating at this level.

BEAM at least has some compelling features working in its favor that make it worth exploring operationally, but also it doesn't really operate at that very large scale. It's well-adapted for smaller scale systems.
Company leaders really live in a bubble compared to the working stiff cranking out code. They often have no understanding of working conditions, and are instead focused on products and customers. A common inclination when facing internal criticism (if that's encouraged at all) is to dismiss or minimize the importance. Yet when a supposedly neutral 3rd party reveals a different perspective, the leaders are given permission to make changes.
>One driver and two to take payments etc.

What the heck?
Yes, Boston is far too large of a city to be classified as a "College Town".

And the GP commenter asked a completely valid question. The answer is clearly that most families with remote working parents and most mature couples that can remote work are not likely to prioritize a college town as a place to enjoy their years or raise a family.

Young single people who remote work seem to be the target of these efforts. And that is great because there are an increasing number of them.

This could help stimulate the socialization and dating scene for young single adults as well. Instead of relying on moving where the jobs are and doing online dating with random strangers.

Time will tell.
Not only are there students in college towns, but there are a large number of highly educated faculty, administrators, and support staff in college towns. If you know the right places to go, the intellectual and artistic lives of adults in college towns can be very high level.

Also, Boston is full of colleges and universities, but has so, so, so much more. It’s all easily avoided if you care to.
We do it right now, though we run Node instead of Go. For us it's not 'copy a binary', but 'copy and untar', but it's still very simple.

One downside that we find surprizing is that way too many Ops people are more familiar or comfortable in cloud or Kubernetes environments these days. We find it hard to find local talent who are willing to deal with bare metal hardware.

Because of that we plan to migrate to k8s at some point later this year. I'm neither support nor oppose it, to be honest. Introducing an extra Docker build step is annoying, but the idea of adding a few hundreds of Yaml lines to get monitoring, log aggregation, tracing, etc. sounds really nice, too.
> I see people who "know how Docker works" put no care at all in the order of their image builds and end up doing 10-100x more IO than they need to.

I don't want to go into no-true-scotsman territory here, but this really is a literal contradiction.
What explains the pervasive malaria that used to be in this country then?
What you're describing is a real type of person, and one that should be avoided, but that's probably not what's fueling this statistic. Large portions of the population did not suddenly become lazy and lose all ambition. They're not engaged with the economy because they're losing the ability to engage. This is a global phenomenon, and it's getting worse and worse as tech makes most of the population increasingly irrelevant in the job market. We are rapidly approaching a situation with only two end states: Some kind of intense wellfare state, or riots and brutal chaos. Forget South Africa, the US is full of 30-and-unders who are perfectly capable and willing to engage, but can't because there's no place for them. No good jobs, rent and home prices are through the roof, college prices are through the roof and don't buy a good career anymore anyway. And on and on.

The problem isn't that young people are lazy. It's that they're being left behind. And if something isn't done about it soon, society is going to start to crumble. In some ways, it already has.
Just to expand.

Container technology run your software just as it was a standard process.

There are no performance implications in running code inside or outside the container.

Here be careful, that on MacOS docker is implemented as a virtual machine. In such case there could be somehow serious performance implications. Especially around IO.
Leaked Walmart memo reveals competitive threats
Changing your Google password will never log you out of Slack
Maybe some Slack admin needs to read this before something bad happens to them.

We have Slack setup with Google Workspace SSO (not SAML), meaning everyone has to log in with his @TLD.com address.

One of my colleagues quit the company, and we kept his Google account, but changed his password. On Slack, we didn't disable his account, as I incorrectly assumed that he'd be logged out pretty quickly.

Turns out, when you change your Google account password, you can stay logged in on all your slack sessions, indefinitely (unless you set a session limit in the admin console).

So this person has been logging in from his Android phone for the last 9 months and been able to read everything happening in our internal Slack workspace.

The only solution I got from the Slack support rep, is that you can follow this obscure procedure to log everyone out: https://slack.com/help/articles/214613347-Sign-out-of-Slack#sign-out-of-all-sessions

This is 100% our fault, but maybe this can be a good lesson not to trust SSO to log you out.
> LA, my hometown is full of people who simply don't want to do anything. They have a nasty tendency to introduce chaos, and not appreciate anything done for them.

What other info do you have to share about them? Do they have anything else in common?
yeah, I forgot to include unicode but I actually think they should have completed the print() and integer division change migration (without a major version bump, with import futures) and then done a major version bump (to 3) specifically for Unicode. And I agree- utf-8 has clearly established itself as the preferred encoding.
This is the feature firefox needs to be in the default browser. All these tweaks to the top tab thingy is just a band-aid on the fire.
Scientists should never be afraid to speak to truth and speak their mind. Whether it’s a lab leak, gender, or climate change, scientific fact should be immune to political comfort.
These days people most frequently seem to mean "without a hypervisor" when they say bare-metal. In this case I guess it's "without containers", which isn't far off. Since it's not a formally defined term I'm happy as long as it's clear what the question means, and this one is explained clearly enough imo.
I like your reasoning. My question is: do you think that is why the mainstream media completely rejected the idea of lab leaked virus?
Because we're talking about research of biological weapons of mass destruction.
I see a lot of unrest coming up as AI replaces workers. The elites can keep the poors down for a while but eventually as we see all through history, they revolt. I suppose given better AI and drones the elites can eventually make AI robots to keep the rabble in line maybe(?) as tech gets better though, kind of like T1000s under the control of the Elon Musks and Peter Thiels of their time.
And all towns
I will reply the same way I did to another comment:

I like your reasoning. My question is: do you think that is why the mainstream media completely rejected the idea of lab leaked virus?
>Consider the priors.

There have been two serious epidemics of coronavirus disease in recent history: SARS and MERS. There is overwhelming evidence that both have a natural origin. Indeed, the fear of further crossover events is precisely why there was a lab studying these viruses in Wuhan.

I'm not saying that this wasn't a lab accident. What I'm saying that is that if you were actually "considering the priors" (in the statistical or strictly literal sense), you'd be concluding the exact opposite of what you're saying in this post.
Works but looks differently with less emphasis on the current tab.

I haven’t gotten used to it yet, but oh well.
This hasn't been my experience. Once I let my lawn get quite tall (grass that was maybe 4-5 inches), and I had crazy mosquitoes. When I finally mowed that grass, they came up in swarms. I then learned, and have kept it short since then and voila, no mosquitoes.
I can't find the article, which I read years ago. Some quick googling did turn this up:

https://www.psychologytoday.com/us/blog/do-the-right-thing/2...

Which discusses the fact that the abuse isn't any more prevalent than with school teachers or other denominations.
>Are you really suggesting that the reason 43% of South African youths are unemployed is because they're lazy?

Not at all, it's structural problem. I've seen this in LA as well and it's the number one reason I left. Since I lack the personal capacity to fix LA, I no longer live there.

If anything if you live in a city or a nation where unemployment is rampant , you just need to leave. Not worry about what the government is going to do to fix it.
My only big issue with the redesign is that it no longer shows you at a glance when a background tab is playing audio. You have to mouseover each tab to show the audio icon.
You Live in Apple’s World. Here’s What You Are Missing
Mysterious AWS NLB Timeouts in Kubernetes – N26
I'm using ESR, so this hasn't impacted me yet, but there's a large userChrome.css file that reverts the worst of the changes at:

https://github.com/black7375/Firefox-UI-Fix/

It's well commented enough that you should be able to cherry-pick individual fixes.
Yes. Go static binaries are super useful and simple to deploy. IMPO, this is one of the reasons Go has become so popular.

Docker became popular because it fixed a lot of deployment issues for dynamic scripting languages. And really, Go static binaries and/or Java jars solve that same problem. So there is no need to complicate these deployments with Docker.

I do dockerize some Go binaries to run in ECS/Fargate, but otherwise I see no real need or reason to do so.
Your performance should not noticeably differ (on linux) between docker and just running as an uncontainerized process on the host. There's almost no difference as far as the kernel is concerned; it just tags your process slightly differently (different kernel namespaces and cgroups, but these apply to every process).

Bare metal usually refers to running without hardware or software virtualization (kernels within kernels), and if that were the case (docker on linux does not virtualize) it would be meaningfully faster, but that's not the case here.

The primary benefits you get from Docker may not be immediately apparent, so go for whatever works. Eventually, you'll probably find that it's substantially easier to scale out appropriately and automatically with some sort of orchestration tech, which is nearly all built on containers these days. Don't sweat it til you need it but at the same time, it's easier to learn sooner than when you're knee deep in tech debt for a dozen services.
I am not at all shocked. All this was known and reported over a year ago. Social media companies and the MSM actively censored this information then in the name of squashing fake news. It was called conspiracy theory. What is different now? The only new and shocking revelations are the release of Fauci's emails.
CT is the easiest tax to avoid and FAANG companies can provide states with a wealth of surveillance data. I think it will be the business as usual.
On the international scale almost all things happen by force. They wouldn’t pay anything voluntarily but getting the world united against you means tariffs, limits on exports, etc. it doesn't help that they are already known to lie even to their own people on things like pollution or imprison dissidents.
There's a remarkable tension in this piece between "just trust people to do the right thing" and every "PRs are bad because" bullet point which assumes people are constantly doing the _wrong_ thing...

Also, I loled when I got to this part:

I think that the practice of Continuous Integration [...]
combined with Pair/Mob Programming is likely to yield the
best results.

followed immediately by:

Admittedly, I don’t have huge experience with Pair Programming
That has to do absolute nothing with the shell, that's a Unix convention how commands parse their arguments.
The FT quotes: ‘120,000 a year for bat surveillance’.

Seems negligible as an outsider.
This guy looks like a tool.
Wait but what happened? Did he do something about it after, like contact Sun saying "Stop! You have violated the law!" or whatever? If not, why on earth not?

What's the point of publishing with a copyleft license if you aren't going to do anything when someone literally walks into your office and says "we at Big Corp are selling your work without any attribution?"
A few. J, K and Q come to mind.
What? How? When? What? I don't get the joke.
germany has working poor
> You might have a 10 second build process that does 1 MB of disk IO and it becomes a 100 second build process that does 10 GB of disk IO because you ran it in Docker.

How and why? Unless you use a wrong image ( like Alpine for Python) or your Dockerfile is poorly made and cache doesn't work, nothing should change besides immutability and proper and clean dependencies ( your code won't work because you have some lib installed on your local machine by chance, and fail in prod because the lib doesn't exist or is ot a wrong version).
Sounds like you got outside your bubble (comfort zone) by moving somewhere new. People in Chicago are no better than people in LA or NYC or Mobile.
Cryptocurrency is an alternative to centralized parties that abuse their monopoly positions as payment platforms while non-profit/government sectors are too inept to provide a public payment option.

Here's a case of PayPal closing the account of a user because they used it to fund servers to run TOR nodes:

https://www.eff.org/deeplinks/2021/06/paypal-shuts-down-long...
It would help to clarify some words:

"Bare metal" means that your application is running on the same OS that is also running the raw hardware (metal), aka no virtualization. Containers are not (generally) the same as virtualization.

The analog to bare metal is virtualized, where the hardware your program is seeing is not necessarily the hardware that is running on the actual host machine.

A docker container could ostensibly be considered running on bare metal. A container is really just isolation but the parent OS/kernel is in command. Here is a graphic that illustrates the differences: https://www.sdxcentral.com/wp-content/uploads/2019/05/Contai...

What you are really asking is do you need an abstraction layer or orchestration tool to manage doing this.

The short answer is that no you do not need it at all. If you can DIY this and are happy with it, that is sufficient. For example, a current deployment process for one of my clients (EC2 environment) involves stopping a custom systemd service, pulling the new binary/deps and then starting the systemd service. Really simple with a small instant of downtime, but within this environment that is not a problem.
To finish up the point on performance I link this very interesting answer on so:

https://stackoverflow.com/questions/21889053/what-is-the-run...
Have you considered that maybe you could not recognize the person correctly?
What you're describing sound like normal bugs. Have any of your links been specifically flagged by Customer Support and said to be impermissible?
It is not, and its a sad state of affairs that people believe so.
> Property-based testing requires you to define the condition of success or failure (the "property" you're testing for) too, right?

That property can be "does not crash".

And I'd say this is the structured / language-awareness part: with fuzzing you can't generally build an oracle.

And if you can it's of course trivial: just have a wrapper script check the result against the oracle, and trigger whatever the fuzzer looks for indicating "failure" whether it's a return code or a segfault or…
> in zsh […] setopt NO_CLOBBER

In Bash it’s

set -o noclobber

or

set -C
I like some of it but really wish they would just add a connection graphic to the page so they are actually tabs again.

Also I know some people are mad the menus are too tall.

ProTip don't try to disable the new "proton" menus its all whacky.
My general feeling is that we will see a structural adjustment:

- We will see a total of about 50-100% inflation. This is not necessarily a bad thing, given the amount of debt in the system. People's mortgage, educational debts, and credit card debts will be lightened.

- The dollar will fall in value relative to world currencies. This makes sense since the US no longer has a monopoly on much of anything. There is no business like the US automotive/manufacturing post-WWII, or tech in the eighties and nineties. The US is a superpower mostly out of velocity.

I don't think this necessarily results in a depression, unless we mess up. This could be healthy or unhealthy, depending on the cards we play.

I don't see a world in 30 years where a SWE in the US makes $350K and a SWE in China/India makes $10k, or where unskilled labor in the US makes $40k, and unskilled labor in India/Africa makes $1k.

The key question is how we get the the new world. This could be through an economic collapse in the US, or through pretty healthy changes. I just don't know.

E.g. 50-100% inflation is enough to trigger a spiral to hyperinflation, depending on how we react.
Computer Science Logo Style: Programming Language Implementation (1997)
The housing market in Ithaca, NY (where Cornell is) has become very tight.

One sad thing about university access these days is that so much library content is electronic, and not accessible to the general public, even if they walk into a physical library on campus.
The problem that tabs no longer look like tabs (and that the active one has this weird button look) is not exclusive to dark mode.

In one word: Why?