I do think about that, when needed. My point is that these containers can be 'good enough' in places where it doesn't really matter, not that they're always the go-to thing. E.g. I really don't see any issue using a map as part of a configuration type of object which gets read from args or json and which only gets used once at application start.

It's really hard to take your comment serious because of generalization like this. Maybe they're not usable for your particular usecase but that doesn't mean they suck. Just like there's a 'million' ways that C++ sucks in your book, there's a reason there's millions of lines of code out there where these containers are valid usecases and hence work without issues whatsoever nor a need to replace them with something else.

Sort of (I mean: seeing void* and a size probably means 'arbitrary sequence of bytes' or something like that, but well it's void* so it can be like anything whereas with std::span you get more of a hint what's going on just based on the type), but not at the callsite which is what the author is referring to when it's about reinterpret_cast.

> I think the point is that it adds security, which the other options don't

Imo span also does that to some extent, but already when writing the code and not afterwards in e.g. static analysis. E.g. if I get an std:span I'd have to do counterintuitive things to misuse it. Annotating a void* still leaves it a void* which I then need to cast to char* if I think that's what it is intended.

Don't get me wrong: I've written my fair share of void* but these days I really feel like there's almost always a better thing which can be used instead. Though I do admit that since I've written and consumed a lot of code with such alternatives I'm not hindered by readability/apparent complexity of it anymore but I understand that's not the same for everyone.

Fair point (although to be honest: 'complexify' feels a bit of an exaggeration here to me), but the answer to this why is simple: document and express intent clearly. The compiler gave you an error first such that you're forced to consider what you're doing. Any seasoned C++ developer seeing this knows what this reinterpret_cast means.

> Wow. With std::span the complexity-meter bumps in the red zone and goes even higher!

Same remark: yes, it's a bit more text to read, but again: to me (and many others I'm guessing) this clearly expresses intent. I also do not find it particularly hard to read. I mean, it's C++, you're likely going to encounter templates at one point or another, except in super specific software perhaps. But no-one also ever argued the C++ learning curve was easy, and trying to make it easier by refusing to use features which were added for good reasons and instead going back to constructs which are the very source of those reasons seems a bit backwards.

> As a nice addition, if you use SAL annotations, the function could be decorated a bit to help code analyzers detecting memory bugs

Some might also say it complexifies and uglifies the code. And in any case makes it non-portable on top of that.

Anyway: you can calculate things for your particular rendering framework all you want, that only tells you when that software considers something visible, and you're still missing the extra frames the GPU driver or the monitor itself might add.

In the end total latency can ime only be measured accurately by measuring both the time when you send your 'show' command and measuring when the thing actually becomes visible (photodiode on the monitor, or one of those expensive monitors which can e.g. output a TTL signal upon seeing a certain pixel value).

But I was talking about partying: there's a fair share of EDM I can party to without any drugs. Goa trance is the main one btw. And I still get the feeling of connection with the rest of the crowd.

The nice thing if you find something is that it's also sustainable - as in: can do this for the rest of your life - which at least for me is definitely not the case with mdma.

Anyway: if there's anything I'd weep about it's that measures like these are needed in the first place. Far too little, far too late. But to be honest I stopped weeping and just do whatever I can personally such that the day I die I can at least have some peace with my life.

Saw them last year in Brussels. And while I agree with this and would go again and would recommend it to others, the side note for me is: I've listened to a lot of electronic music old and new and for my personal taste almost everything Kraftwerk makes is on the mediocre side. I'd never play it at home to listen to. But to see them in concert with pretty nice visuals and at the same time realizing they basically pioneered all of this 50 years ago does remain sort of mindblowing.

Very strange indeed.

It's agricultural output is insane for a country with its surface area.

Isn't that, just like in Belgium, mostly so for meat and derived products? Which also happens to be one of the worst situations (of natural food production) ecologically: grow and import a ton of corn and soy, export again, and in the meantime all the pesticides and methane and nitrogen and manure etc are left in your country.

Wow, TIL. Do you happen to know if IRC file sharing of obscure music is still a thing?

I get the sentiment but tend to I disagree. Maybe some very specific species might benefit somewhat, but in general the principle makes little sense. Whatever native fauna there is in your area spent thousands of years in relationships with other native flora and fauna. So not just plants, also the soil life, the combination of plants, the terrain variation and so on. Hence replicating that as close as possible should be what works best. Which a far as nectar/pollen goes means not a single species but a combination providing it throughout the seasons. Whereas 'long blooming and nectar rich' completely ignores specialist insects which only get nectar and pollen from one particular species or group of species, insects laying eggs on specific species only, and so on. Butterfly bush is considered a McDonalds for insects, and that's actually a pretty good metaphor. Red valerian is in the same ballpark.

Such numbers might be ballpark correct, but I think the "without them" here literally means "if we take current industrial agriculture and simply drop pesticides" i.e. without any other change. Pretty obvious that yes, doing so will easily get you to numbers of that magnitude.

So it's a bit strange not considering the various root causes of what requires those pesticieds in the first place: monocultures on dead soil and nothing which even begins to resemble a normal ecosystem in sight. Those causes happen to be exactly among the causes of the massive insect/more general biodiversity decline we're witnessing. Along with pesticides, sure, but habitat loss is likely an even bigger factor.

So while those biopesticides are probably a net win over what is used now, it's rather unclear if they'll have a meaningful impact on that decline. Which is why reports on solutions for the decline also always include adressing at least part of the root causes, like partial shifts back to landscapes which are a mix of nature and agriculture. Where there's at least a bush/tree line between fields, for instance. Which also helps keeping certain pests in control.

Imo the explanation is also done better than in the article.

Comments URL: https://news.ycombinator.com/item?id=47793400

Points: 1

# Comments: 0

Also not quite what the article is about.

You apparently have never heard or seen the fairly widespread 'the only difference is your perception' line of vegan merchandise which uses dog meat it in the opposite way: it calls out the hypocrisy of all meat-but-not-dog people. Not of a select group of people eating dog meat.

Your suggestions should be fine for hardware failure but I'd be more concerned about software failure: what if a bug in your software makes it unresponsive and stuck in the state with the flow open? Maybe a watchdog or some other system running in parallel checking for a heartbeat or a max amount of time water can be flowing?

In any case, for me this also sort of defeats the purpose: I'd rather break free from Google and Apple, not just (stock) Android and iOS.