Viewing profile — loup-vaillant

It would, but then there’s another dilemma: in a country where there’s a limit to how far into pregnancy you can abort, that pill could easily be used over that limit, and then you…

> No one, whether a doctor or not, should be forced by the state to end the life of any being. I feel you. But that right not to kill, conflicts with the autonomy of women. Which i…

> Pro-choice people "believe" that it isn't. Not all of us I would bet. One can believe the fetus is a human life, and still want to allow the mother ending it. Sure it’s rough, bu…

There are several aspects to this. One is control over women. Another is panic over the idea that other people with darker skin tone might overrun us with their reproductive might;…

> If access is not easy, there needs to be a different solution. Indeed, access must be made easy. Abortion, through a pill or otherwise, should be accessible anywhere, freely, and…

I mean it needs to be made standard because of how bloody useful that is. More people need to be made aware (industry knowledge inertia), and it needs to be usable pretty much ever…

You can kinda do this in C++ too with `std::vector::reserve()`. The thing is if my collection has no known bounds, well, maybe this time it requires 64GB of space? Except RAM is at…

A fourth alternative, in 64-bit systems, is to reserve a stupidly large chunk of memory up front with `mmap()` or equivalent (`malloc()` actually should work about as well). That w…

> malloc/free, not being a language feature, cannot be reasoned about. They’re defined in the standard all the same. Of course they can be reasoned with. The defined parts at least…

> It can be reasoned about, but doing so correctly is very difficult […]. I don’t think this is controversial? It’s actually much easier than 95% of programmers think. The trick is…

Then it needs to be made standard. Without that, or an equivalent solution, garbage collected languages will remain unusable in constrained environments.

First, I’m not familiar with the Go ecosystem. I have never written a single line of Go, and I learned in this thread that there was more than one compiler. Second, please don’t ac…

> In practice, if you were going use Go on a microcontroller you would not use the same compiler as you would use if you writing a web server. Is that a fact? Are you telling me th…

"Just don’t use it" is a valid argument, if it’s clear when you’re using it or not. It’s easy not to use `malloc()`: just don’t call it, and don’t call dependencies that call it. S…

> Most software written today doesn't need to do manual memory management. Need? Not really, not on the desktop (embedded is a different story entirely). But there are still benefi…

Compatibility is a big one. Probably the biggest reason to chose C over Zig or Rust today. But that can be remedied if the new language has a C compilation target.

> I'm sure _someone_ thinks manual memory management is a feature rather than a bug, I reckon mandatory manual memory management is not ideal. But the ability to manage some memory…

> * but if you have accepted the tradeoffs of using dynamic memory allocation then why not GC?* That’s the thing: many do not use dynamic allocation at all. Did you know for instan…

You know, I’m actually tempted right now to do my own "C with ". Except I wouldn’t make the same choices as Stroustrup did. For one, I wouldn’t aim for popularity. I’d want somethi…

> As simple as that, not everyone of us is a Linus. I’m pretty sure Linus could not have written Linux today. Too much hardware to support, too many drivers to write, before it’s r…

> If so, why has it not been done? Because of the 30 million lines problem. Writing a serious OS kernel nowadays is flat out impossible: the hardware is just too diverse, it requir…

> A better C++ is by definition a better C The definition is wrong, then. I wrote C++ for most of my career. And as of late, I found myself avoiding more and more features from it.…

> Go is a better C already It’s not. Garbage collection made sure of it. I believe everyone agrees that a "better C" has to have manual memory management. Most even rule out Go as …

> Advances in quantum research and development have shifted the risk horizon. We believe cryptographically relevant quantum computers could arrive sooner than previously expected A…