herriojr

It's not just that. If you pay to shoot a lion, it's not going to be a young lion that will sire a lot of children. It will be an old lion that is actually reducing the potential population growth. This is a good thing if we want to increase the number of lions.

Hunting is a necessary evil. In terms of US conservation locally, hunting is fairly highly regulated. It is actually needed in a lot of areas where people go hunting for deer due to natural predators no longer existing. If it wasn't for hunters, there would be large population growths of deer to the point where they begin to kill off other species that rely on the same food sources as well as starve themselves.

In the past, before things were so regulated, it wasn't unusual for populations to be decimated by humans. Passenger Pigeons are now extinct; Deer, Bison, and Elk in certain areas were killed off. Heck, in Ohio, Deer were reintroduced after being decimated, so they would run-a-muck if there was no hunting unless they were to reintroduce wolves to the area (good luck getting people to agree with this).

All of this is due to humans creating imbalances in nature that conservation is now trying to keep in check, and hunting is necessary for certain species which no longer have natural predators, or in the case of lions, to ensure males that will sire more children get a chance to.

Here's some Ohio History on Fauna: https://ocvn.osu.edu/news/ohios-wild-history-frontier-fauna-...

TLDR -- unchecked hunting bad, regulated hunting good

I haven't played with kafka in a while, but basically,

1. each group id represents a point in the stream that a consumer is processing off of. You could technically have multiple processes consuming off of a single group id.

2. there was a configuration on time to keep things there as well as space if I remember correctly, but basically, there has to be. There's a pretty hard limit on what all you can store on disk.

edit: changed consumer id to group id. If you want more info, feel free to ping me about the ecosystem

My wife actually did a study of this a long time ago for her Master's degree after having dealt with EEG Biofeedback training under supervision of an MD for years. She had a bunch more participants. In short, Binaural Beats don't work.

edit: I'll see if I can get a link to her paper

I totally agree that it comes down to who the code is written by. I've done both python and java, and in python I would go so far as to define interfaces as a form of documentation in my python code so people who use it know what I expect out of their classes which want to interact with my object. It doesn't require the class to explicitly implement the interface but they can if it makes sense (fairly similar to Zope Interfaces I guess). Unfortunately, I don't see this a lot in most python applications and you're left searching around through calls to figure out exactly what is required of the object being passed in. Look at a lot of popular libraries -- you are still left searching through code just to see what can possibly be returned because they aren't always the same type -- also, exceptions aren't part of the function or method definition, which means if you don't document your exceptions, I'm up shit creek. I think a lot of the problem around the python ecosystem, again, that I've seen, is people just don't follow best practices -- documentation, it's a core component if python development -- It's one of the arguments they use against static typing. Personally, I think python developers need to be much more strict about development practices than java developers. I think it's a lot easier to make bad python code than it is to make bad java code. The same goes for C, which I used to also do as well. To be a good C developer, you have to be very strict and structured (however, for somewhat different reasons). With great power comes great responsibility.

I've seen shit java code as well. A lot of bad java code usually revolves around things not being modular or not having some form of consistent development patterns or not breaking methods down into simpler sub-problems -- I think documentation isn't as important as it is in python for the fact that I know exactly what is being returned, what exceptions can be thrown, and what exactly needs to be passed in just by looking at a method. In terms of the business logic associated with the class, that still needs to be documented.

That said, I understand why python is generally used at startups -- it allows fast initial development where at startups, time is critical. Long term development really relies a lot on the teams ability to make structured decisions and organize their code, which is a difficult task in any language.