@bkuhn
To be fair, to this European who's lived in a welfare state for the first 4 decades of his life rather than the church of capital that the US is,

We already do that.
@dotmavriq

@argv_minus_one
That today's models are built in expensive data centres does not imply the same for all future models. Tech gets better, not worse, so eventually we'll do it on affordable hardware, Moore's law or not.

Also, free software lives on collaboration. Build a BOINC app to build a free model, wouldn't take as much time as that.
@Feral_3D @bkuhn @twipped @cwebber @copiesofcopies

@NanoRaptor
So I use filesystem snapshots to deal with the first, and a bacula-based backup that writes (encrypted) to AWS storage gateway for the second.

@NanoRaptor
You need multiple types of backup, too.

One of for the 'oh shit I deleted that file but I actually still need it' situation. The ideal setup for that is that it happens automatically multiple times per day and is low friction to restore from.

One for the 'I lost everything' situation (fire, theft, ransomware, etc). For that you need off site backups that are not connected to your main infra. This conflicts with the requirements for the other type.

@cwebber
No, that would be free software.

Open source is a strategem to make free software not as unappealing to for-profit organisations as it otherwise would have been.

I guess that worked too well.
@futzle

@VeroniqueB99
Eh.

Assuming 70 BPM, which Wikipedia suggests is the average for the human heart,

70 beats per minute times 60 minutes per hour times 24 hours per day times 365.25 days per year times 85 years = 3.129.462.000 beats in 85 years.

That's all I know 🤷
@hyc

@hyc
(About 3 billion of them, if you make it into your 80s)
@VeroniqueB99

@stroobl
Dat is boekhoudkundig dan ook moeilijk om te corrigeren.

Voor een foute factuur kan je een creditnota uitschrijven.

Voor een foute creditnota kan je eventueel terug een factuur uitschrijven, maar een factuur zonder geleverde diensten of goederen uitschrijven zorgt voor allerlei alarmbellen.
@peturdainn @wannes

TIL: in rxvt-unicode, holding meta ("alt") while middle-clicking copies from the CLIPBOARD buffer rather than from PRIMARY, which is awesome!

@rauschma
Dutch

IOW, having part of your language that can't be dynamically linked doesn't mean that's true for all of it, nor that there is no benefit at all.

I don't know though about rust to have a meaningful discussion about its ability to benefit from dynamic linking but if it relies on code generation to a large extent then yes obviously it becomes complicated.
@hrw @kornel

@kornel
Oh, I see now what you mean.

Yes, if you want to do any type of code generation, be that C++ templating, C preprocessor macros, or eval-type stuff in scripting languages, you can't do dynamic libraries for those parts of your language. In C++, the STL is typically header-only for that reason, but C++ still has a substantial standard library that is dynamic.
@hrw

@kornel
C++ actually does support dynamic linking. On POSIX systems it does this by encoding the argument types into the symbol name. Not sure how it works on Windows but most of Windows is C++ and it does have DLLs so clearly it's possible.

Dynamic linking is really just mmap() plus a lookup table of symbol name to compiled code. It's not rocket science and absolutely not C specific, but it does require a reasonably stable ABI to make it work.
@hrw

@jpmens
Ohhhh, so you are a vulnerability researcher then? Awesome.
@shaft

@HerveRenault
That will create a lot more reflections though
@sundogplanets

@harld
Dus er zijn vier categorieën voor het kleinste continent maar heel Afrika wordt wel op één pot nat gegooid.

Zuid-Afrika is niet het zelfde als pakweg Zimbabwe. 🤷

@BalooUriza
My guess is that's why @corbet called them "CVE numbers" and not "security vulnerabilities"...
@corbet

@veronica
It's not just Debian though, these are all upstream CVEs...