skysight-inc/HackerNews huggingface dataset:
I've work in all kind of places as sysadmin (or now devops) since the beginning of the century.

Have seen what you call old-school maybe, the VMware era, Xen, colocated infra ,owned infra, ... The Cloud(s)... and finally docker (and later kubernetes), in those years.

Now I can say I happily switched job 3 years ago, to a place that never entered the virtualization, neither the containers vogue.

On a team of 3 and half persons (enough to cover one week of on-call each month), we manage our near 500 physical servers (all of them with 2xXeon, between 32 and 256G of ram, 10G networks (in 40G switches/uplinks) and all kind of storage layouts with SATA, SSD and NVME ) in different colocations. Sometimes, with the help of remote hands (mainly for hard disk replacements).

During those 3 years (and before) I have seen lot of drama between my friends, by all kind of issues related to container technologies.

Complexity issues, high availability issues, bugs, maintenance issues, team issues, cross-team issues, management issues, security issues, networking issues, chaos issues, nobody-knows issues, cost issues, operational issues, etc

Yes, you can have all of them with bare metal servers too, indeed, but I look my daily work, and then I talk with friends in pro-container companies, and I feel good.

Nothing stops you to use ansible in bare metal servers, indeed you need to automate everything if you want to be happy: IPMI setup, firmware updates, OS install, service management, operations, monitoring... the most of that you fully automate, the better will be your daily routine.

Also, really important, going "old-school" doesn't free you to have a full stage environment, and a well thought and fault-resistant architecture and good backups.

Regarding your random list:

> Must build an image before deploying and it takes time, so deploys are slow (of course we use CI to do it, it's not manual).

Maybe going "quick and dirty" will release you of this, but doing things well, no mater if it's container or bare metal, won't.

I need to build packages (or ansible roles), test the change effects, pass tests and CI, the same (it's not mandatory, but it's convenient)

> If I need quick hot fix RIGHT NOW, I can't just log in, change couple of lines and restart, must go through full deploy cycle.

True, but we're in the same point... "old-school" is not the same than "quick and dirty". You can change containers in a quick and dirty way too if you want (and your company allows that).

> Must remember that launched containers do not close when ssh breaks connection and they can easily linger for a couple of weeks

Well each platform has their own issues to deal with. In bare metal you could have to deal with compatibility and degradation (or even breakage) issues for example.

I think, a good balance between all this could be: develop "quick and dirty" and freely, release via CI, deploy properly. No mater the platform.

If developers don't have agile environments, and they need to commit, wait for build, wait for CI, review the results etc for every and each line of code they want to try... I get what you mean, it's a pain.
Or take worker control of a business run by vampires.

Your vision of a better world is miopic.
We have a custom in-house Concourse CI setup that most of our developers hate, built by a consulting firm that no longer has much interaction with the company. One of things it does it run an entire new container to run `shfmt`, a linting tool.

Our new CI happens to use containers, but:

- We aren't managing the containers ourselves, because we're an arts platform not a cloud infrastructure provider.

- We don't spawn new instances to run a (expletive) linting tool.
Interesting, I never got hit by those I think.

The biggest issue I had was with the macro import and visibility changes in the 2018 edition.

That broke quite a lot and was rather painful.
> This would be a great chance for Microsoft / GitHub to swoop in and maintain one of the more invaluable resources on the internet

No, it wouldn't! I don't want yet another corp running MDN who might have their own agendas, or will be just as susceptible to reorgs and layoffs.

It would be great if Microsoft, Google, and Apple funded Mozilla to maintain and improve MDN. I like the idea of a "neutral" third party looking after MDN.
Depends what you want to achive. With wire transfers there's usually (always?) info about amount and last few digits of the account you're transfering money to on your 2FA provider.
So much IT is relatively easy in the singular.

It's the plural that teases out the differences between the pets and the cattle.

And maybe that's the point of this thread: scalability.
Well, with a spam viagra site, I think the point is keeping it up.

On topic, it's crazy how willing some people are to defraud their investors.
Yes. My work takes me to the research on conspiracy theories (I am creating a database) and I actually read through these because these responses are part of how conspiracy theories function in a culture. eg https://doi.org/10.1177/1745691618774270
Learning (Software)
I just published "Learning (software)"
About my approach to learning..
Hope you like it and benefit from my thoughts.
Learn to code or anything else and enjoy yourself
Local environment specifically isn't fully containerized in my project. DB and similar things (elasticsearch, message queue) locally are inside containers, but the code itself is not. I worked on a project before where I had to have it containerized and it was a slow mess. I'd rather spend a couple more hours on setting up local dev environment for every new hire than deal with code in Docker locally.

In production we have it done the other way - PostgreSQL and Elasticsearch are run directly, but code is in containers.
File access in Docker for Mac is a known issue. Best solution is to mitigate using docker-sync or similar.
That's essentially my problem with the open source.

I was an open source apologist some time ago, but since I quit full-time job
and started to freelance/working on my own personal projects I began to
realize, that I as an independent developer can't actually profit from it.
In fact, it takes a lot of my time to contribute to something and I get nothing
in return.

From my perspective:

* Behind every popular open source project there is a company (typically big),
which pays core team salary to maintain open source project.
Community is typically do work for free. The bigger the project, the better
for the company public image.

* Open source projects end up to be designed by committee, which inevitably
turns projects to bloatware, which are hard to maintain and hard to use.

* Increase in technology turn-over. Projects become hyped and die faster that

* Competition is becoming more difficult. Why to try to make another deployment
manager if there's Kubernetes?

* En-masse community memebers get nothing from contrubuting to projects while
doing a lot of work for free. One may argue that in return they get polished
product, but in reality that's far from true.
Decent Eng Grad School grades are not that hard to get. It's not 'exhausting' to have to take 'Electrodynamics, Orbital Mechanics, or Geophysics' I wish I would have paid more attention in Project Management class, I did not respect how important it was going to be until later in life, for example.

See how stupid that sounds
Which means the throughput per tunnel is more expensive, right? A tunnel with a half diameter will have a quarter the throughput (i.e. the ratio of circle diameter to area). Which is why TBM tech develops towards bigger machines, not smaller ones.
Micropayments are proven to work but everyone seems to hates micropayments. Software is good when regularly updated but everyone hates on subscriptions, claiming to be OK with one time payment but that business model got almost wiped out because people actually don’t like to pay one the (sustainable) one time fee too.

Pay with your data and liberties business model seems to be the darling of the masses.

Cult of free is actually just that and Mozilla is also part of it as it is making its revenue from Google.
The paper says "Reddit’s lassez faire approach
to sanctioning demonstrates an ethos of lawlessness; when lawlessness is framed as ‘free speech,’ moderation is seen as censorship".

You may not agree with this sentence, but it is definitely not calling free speech "lawlessness".
That just ugly. I'd just go with something like this: http://experiments.wemakesites.net/css3-treeview.html
My own experience as a Software Engineer in Switzerland:

- A lot of companies are ok with 80% (most often that means 4 days of full time work). Some aren't, but especially towards more experienced roles, it's not out of the ordinary at all.

- 40h is actually somewhat rarer. I've been interviewing recently and lots of smaller companies think it's a point of pride to have 45h or 43h weeks. When you point out to them that this 12.5% rise in hours should also come with a 12.5% pay rise, they are baffled how you would come to that conclusion.

- 4wk vacation is the mandatory minimum. 5wk is nice and often available.
Keep making stuff like these, this habit will be the biggest force multiplier in your life. I wish I had started so early. All the best.
> and nothing would compile without the nightly toolchain

That has changed a lot over the past 1-2 years. Many popular crates have matured a lot and work just fine on stable.

Not all, and Rust is still evolving, but things are much more stable now.
I should wait for the next parts, but I fear the author ignores our very important point of view: we are bayesian machines working with limited information under conditions of bounded rationality.

Lack of proof that Vitamin D supplementation is necessary is irrelevant. We don't work on proofs. If I were to describe our standard, it would a balance of "might it help?" and "might it hurt?". Currently, and I think taking the next parts in consideration as well, I think the answers will be very much in favor of supplementation - with caveats I'm actually very eager to read about.
This method only works because the boxes have the same number of balls. To calculate probabilities by counting outcomes you have to start with outcomes that all have equal probabilities.
My startup would have gone bankrupt a couple of years ago if we would use something as expensive as Heroku. Or AWS.
> lease don't tell me you've never encountered post-install errors with Windows and Mac software.

Sorry to say, but I have to raise my hand here.

The only post-installation issues I ever had on Mac and Windows were related to drivers, not applications.

Plus since like a decade or so, I rarely "install" software on Windows anyway, because all the tools I use come as a "portable" version, which is just a ZIP archive.

In an Apple-like fashion, these "just work" after unpacking to an arbitrary location (e.g. a USB-stick or SD-card)...

What am I doing wrong here? ¯\_(ツ)_/¯
How would the NSA do anything about COVID or any illness for that matter?
News on Belarus? Not clickbaity enough
Maybe that’s why c level employees should be compensated on reaching certain targets, rather than getting at least a million a year. Because, if you are the captain of a schip, you should drown with it if it capsized.
I live in Scotland and we are at 19, 126 confirmed infections with 2,491 deaths.

That gives us a fatality rate of about 13%

It seems from other countries that a 13% fatality rate is far too high. Is it reasonable to think the fatality rate is really around 1% in Scotland, therefore we've probably had closer to 250k cases?

Or could we have been unlucky that the majority of people who contracted covid in Scotland were in the vulnerable group and so 13% fatality rate could be reasonable?
Amazing how unintelligent all of the engineers replying in this thread are... It is objectively true that having all planes in the air flying the same exact path is idiotic. Ditto for fast pods on the ground. Plus take all of the downsides of not having an atmosphere. Plus take all of the downsides of someone being able to shoot a $10 bullet anywhere along the side of this and you have a shock wave traveling the speed of sound that will destroy any pods within about a mile of the hole (and all of the others if they don't have an intelligent emergency braking system).

This whole thing is a joke and anyone who thinks Elon isn't an actor has their head so far up their ass they have no place commenting on the web concerning "space travel" or any related topics.
Your suggestion is to take this high interest loan to take a long position in a high risk high yield speculative investment in other cryto... wut? This is like telling people to buy cryto with their credit card....
> Is it a damage if you damage damaging thing?

When in doubt - yes. It's the same reasoning forbidding you from shooting criminals in the street, you'd just open up mob justice.

Of course, this is a pretty clear cut case and you might argue that this is an emergency (as people are clearly in danger of being scammed unless you act right now), but overall this is a very blurry line.
I have heard this "Paradox of tolerance" mantra many times. And in my opinion it is the doorway to a totalitarian society, which is perfectly demonstrated to us by cancel culture excesses. It is basically a terrorist tactic, scaring people into making them keep their mouths shut.

If you claim to be 'tolerant', but do not tolerate those who aren't, you are not really tolerant. Period. What a truly tolerant person should do with those who aren't, is to find ways to persuade them to change their ways. It is not impossible. Civil rights movements in 1960s or suffrage movement achieved success not by scaring 'white racists' or 'male supremacists' into submission, but by persuading a sufficient number of them that segregation or discrimination based on sex is bad.
> interrupting a blocked write would remain a tricky problem.

Would it? I believe kill(pid, SIGTERM) interrupts it all right. Or do you want to do this without terminating the program? But then we are back to square one: the programs have to handle failed writes somehow. How? "Abort, Retry, Ignore"? And then again, most of this stuff happens deep inside libraries, and every library makes different choices in handling such errors, and when you combine them in a single program, you end up with a mess. As always.
The are finally doing the helicopter money. Some have a better income from not working than they had when they were working.

https://en.wikipedia.org/wiki/Helicopter_money
Yes, dynos are containers; their use of containers predates Docker.
I would gladly pay for MDN access. Mozilla has done a wonderful work with that, it's a goto place for any kind of web related documentation (and I'm probably not the only one).
This where anti-trust kicks in, that you don't allow companies to leverage a monopoly/duopoly position in one market to destroy competition in another. Particularly if they give products away for free to destroy the existing competition or as a lead in to their existing profit-making product.
Context: rigged elections in Belarus (European country the size of Portugal/Greece/Sweden, bigger than Libya and Lebanon), massive protests, hundreds of people arrested, dozens disappeared.

Clashes with police in multiple municipalities. Several factories and plants on strike or planning to go on strike. Multiple accounts of torture and physical abuse of those arrested or detained.
I mean, why should the general public have information about their divorce at all?
I would love to leave a comment in that page but sadly they decided to use Disqus. My issue is not even that it is proprietary (which is a big issue) or that it sells your data (which is again a big issue) but rather that it does not let me log-in.

Along with Firefox, Thunderbird, Rust, and Servo, MDN was one of the best projects from Mozilla, it is sad that they decided to fire people that worked on it.
Is there an article on this?
I agree this inflation story isn’t the story we should focus on. We should be doing everything to get our numbers under 1 new case per 100k people per day. We’re still having a 9/11 event every three days by death count.
Vitiligo Miracle Review, Legit or a Scam?
Are you a C programmer threatened by the emergence of a C competitor? I have nothing to gain by "promoting" Rust as I'm not a Rust dev. You have commented a lot in these threads to complain about Rust.

If I'm right remember that both your self worth and your employability are ultimately not tied to C. Programmers switching programming languages are not life long miners that have to turn overnight into lawyers. You start building something with Rust and you should be operational quite quickly, most of your skills transfer over.
Containers are indeed cumbersome but what's even more cumbersome is software that work on your laptop, pass the tests, and fail in production for whatever reason such as a different software version of a dependency.

So I rather deal with containers. However never do kubernetes, it has nice features but it's not worth it for small and medium companies.
> As a software dev, my personal experience of "professional linux distro packagers" is people literally removing random lines of code of my software until it builds

That's sad. But fortunately, not all packagers are like this. As a software dev too, I have a great experience with packagers from various distributions. When they have an issue (either build or runtime) they tell me about it and we discuss a patch together that I include in my next release.

> My subjective experience from the software I use is that stuff like AppImage made straight by the dev is generally much more stable and works much better than whatever chtonian hack a debian packager decided to apply.

Sure it works if you are in the most common case (Linux on x86_64), but it has some downsides:

* It only supports CPU architectures the dev can build for

* It only supports operating systems the dev can build for

* The dev needs to publish an update every time there is a vulnerability in a bundled dependency (assuming they are even watching for vulnerabilities)
In the end everything is backed by our ability to kill each other. Bitcoin as well, because equipment needs to be somewhere and it must be protected. However, it's bogus because more can be created at a whim, as we've seen in the last months.
> Software distribution hasn't caused problems in windows since XP.

The windows way of installing software (download random .exe or .msi files from random websites on the internet) has been a problem for every non tech-savy people and the people helping them manage their computer forever.

Every modern OS comes with its own package manager nowadays for a good reason.
I am the author, and will be here for a few hours in case there are any questions.

(proof: https://keybase.io/byronbates)
"We love dirty laundry."--Don Henly
This mixes up several entirely different terms:

- warez: piracy (or copyright infringement if not on the sea)

- open source: cares about user's rights, not price.

- "4 free": freeware. Does not care about rights, only price.

Relatedly, you are very much encouraged to sell free software https://www.gnu.org/philosophy/selling.en.html and free speech does not mean cellphone contracts with voice for $0/month.
Why should we care about arguments in a random HN discussion? We should care about arguments from people who have done substantial work.

Totals grouped by language (dominant language first):

python: 578880 (54.33%)
ansic: 475310 (44.61%)
sh: 4073 (0.38%)
cpp: 3847 (0.36%)
asm: 1486 (0.14%)
objc: 761 (0.07%)
lisp: 502 (0.05%)
pascal: 353 (0.03%)
xml: 308 (0.03%)
csh: 21 (0.00%)

Most of pure Python is in the stdlib.
> by requesting donations from inside Firefox...

Donations are a bad idea. Companies can't make donations (usually). But they can buy software licenses.

They should sell something. Not sure what, though.
Mozilla brought in $450M last year because Google wanted to be the search engine on its free software. You can give software away and make money in other ways. Plenty of software companies do it and it's a perfectly valid business model. Small company does not "lose", and $450M is not small
It's the worst model, and is not in any way, shape or form sustainable. This works for a very small number of prominent devs. For everybody else it means poverty: https://staltz.com/software-below-the-poverty-line.html
Danfo.js: Pandas-like library built on top of Tensorflow.js
Why don’t interviewers at tech companies just don’t follow these rules while grading candidates?
Mission creep has been a fundamental Mozilla flaw for too long.

And are they a corporate, a charity, or a corporate non-profit? Charities very often pay substantially lower salaries, the tradeoff being you feel you contribute to a greater good. That's how I thought of them, but the wage bill doesn't match up.
> What does that mean in practice though?

It means the idea isn't necessarily wholly impractical. That's not nothing.

I imagine superoptimisers scale extremely poorly, but that's a different question. I imagine they're best suited to bit-twiddling problems rather than, say, figuring out the best assembly code to implement a parallel Timsort.

I have to admit ignorance here though, I know almost nothing about superoptimisers.
Good luck with feeding a family on recognition.
In GNU/Linux it's the GNU part that supplies the C ABI. The GNU compiler collection provides it, and the GNU libc uses it talk with the Linux kernel, usually through traps appropriate to the CPU. The LLVM toolchain (and other alternatives, like ICC) conform to this de facto standard. The GNU devs designed their ABI long before Linux came along and it is mostly inherited from even older OSes like BSD and SVr4 and developed refined and adapted over decades by a common community of interests.

If you're going to criticise GNU/Linux for not providing a Rust ABI, make sure you're aiming at the GNU part. The Linux part doesn't care.
Its almost as if one free thing in one category doesnt observe the same laws as another free thing in another category.
CCL:

Totals grouped by language (dominant language first):

lisp: 336793 (84.60%)
asm: 30410 (7.64%)
ansic: 29862 (7.50%)
sh: 718 (0.18%)
objc: 299 (0.08%)
java: 7 (0.00%)

> Lisp is a memory-safe language with automatic memory management, which removes all of the aforementioned classes of attacks that are available in C.

Yeah, right.
I doubt you would get worse than the current management team.
The most important software is the least visible. See OpenSSL. If you have individual developers doing crowdfunding, the most visible ones - the ones making GUI applications everyone uses - win, and all the critical infrastructure gets neglected because it is boring and 99% of people never think about it.
We use DigitalOcean's loadbalancer product, we've also tried Cloudflare's for pure HTTP loadbalancing. We also use a single Redis instance for job queues. We use Graphite and Grafana for monitoring system metrics (running a Bitnami Graphite/Grafana instance on AWS because we had credits) And for the rest I guess just keeping the services simple? When we do need to scale up and add a new web server or task runner, it takes about an hour of my day.

One thing I realised with going bare-VM is that most services today are insanely stable. MySQL almost never crashes, Redis definitely almost never crashes, Rails/Passenger/Nginx never have any issues. The things that do happen is disks filling up, application bugs causing issues, or actual VM downtime, which is rare but happens when you have 30 VMs. With Docker or K8s it added a super complex layer that is in development and has issues.

The 4 months we ran our web servers on K8s, I spent at least 1 month debugging issues that ended at an existing open ticket on Github.