Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

The selfish gene states quite well why this happens and is normal in the statistical sense.

I don't think a lot of people today would challenge dawkins on that.


Are you kidding? It's a political pamphlet, many scientists have aimed criticism at it.


In my headcanon the downvotes are from dudes that read The Selfish Gene in high school and got some feeling of epiphany, and now did a bit of web searching that angered them.

Dawkins is a radical genetic reductionist, this book is his defense of this position. In the face of criticism he has moved on from the conclusions he presents in it towards a focus on phenotype reminiscent of older biological paradigms.

One obvious critique is that if he was correct in the book, evolution would have played out much differently and most likely not moved on from single cell organisms. This is why his loyalists over time has moved from studying animals to find something that seems like evidence to preserve the conclusions, to studying bacteria.

Another is that the most well known expression of genetic selfishness in humans would be cancer, which is clearly not the dominant mode of cellular reproduction.

There are more cleanly scientific objections, famously locusts, i.e. epigenetics.

He wrote at a time when the last remnants of aristotelian views of animals withered away, leaving an ideological vacuum. Previously the entire animal was thought to be the evolutionary atom, similar to an aristotelian form, against which Dawkins proposed his radical genetic reductionism.

The main reason that the book has been as influential as it has, is that it is aimed at laypeople and cherrypicks and frames things to drive home a political view that is much easier to understand and accept than the mess we're actually in.


Can you please edit out swipes and putdowns from your posts here? Your comment contains some interesting information and would be much better without that first sentence.

We've had to ask you this more than once recently:

https://news.ycombinator.com/item?id=42605019

https://news.ycombinator.com/item?id=42554816

If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.


No, I can't, I'm not allowed to edit the post.


The request is to edit them out of your future posts. Sorry if that wasn't clear.


Right, I'll do my best to keep that in mind.


The patriot act stayed in place 3 times longer than initially said.

It removed the habeas corpus for 15 years.


Would slow down battery innovation. Form factor is constantly changing right now.


My first job was with plone. I hated it. Then I learned the twisted ecosystem and had a moment of crisis.

Those are the devil pits of the python world.

Thank god for django and asyncio.


Python programming Plone was painful.

However, I learned so much from the entire system.

* The CSS of the Plone theme was a Masterpiece. There is a very good reason why Wikipedia used a near direct copy Plone’s CSS for most of the 2000s. Using just a layer of CSS and minor changes to the templates, I could radically re-theme an entire site in a short amount of time.

* Plone enforced semantic HTML and used XHTML. Regardless of what you think of the value of semantics and XHTML, it thought me how to create well structured HTML at a time when the web was full of very broken HTML4

* While programming was painful, Plone’s UX for content managers was first rate. I was invoked in testing Plone, Joomla, Drupal and WordPress. Plone got top marks by a large margin

* Again too marks for Accessibility. In 2005, I built a Plone site for a nonprofit that worked with the blind. I remember users saying they could not believe how easy Plone was to use using the Jaws screen reader

* Multi-lingual sites with workflows for translators. Last year I ran into a translator who used a Plone site I build 20 years ago. They lamented that none of the sites the work on today are as good as that old Plone site.

* etc


Yes it was a good tech from the user perspective.

If you could make it render fast enough, that is.

And twisted did make use cases possible in python that would have been near impossible otherwise.

If you could debug it, that is.


Timd to show jujutsu to the intern


Napoleon Bonaparte was lieutenant-colonel of a battalion at 23.


Had he not been lieutenant-colonel at that age maybe he could have had a quiet happy life instead of ruining and ending the one of thousands of his contemporaries and having his own life end so badly.


I guess that's true, but we're straying from the point of discussion I think.


Why do all those micro framework copy the worst aspects of flask?

The global request object, the bad integration with sqlalchemy, the strong coupling with an application object that forced the indirection of blueprints...

If you start again from scratch, forcing people to migrate their stack and therefor leave their ecosystem behind, at least fix the glaring API problems.


What does are you taking? Do you need to ramp it up or cycle it? What's your source? Anything else important to know?


And the amazing algo that made skype work as a P2P system with very little bandwidth circa 2000 is now lost. Locked down in Microsoft's proprietary attic gathering dust while each conf app gets worse as the time goes by.


The better syntax used to be a selling point, but now with AI being able to generate any trivial one-liner and minor scripts you need on a day-to-day basics, have a bad syntax would only affect bigger projects, which I would not write in Fish shell anyway.

It's a hard sell.


Generative AI might be able to generate them, but it's still on you to understand the result and check that it indeed does what you want. And with the sometimes very nuance- or foot-gun-rich syntax of bash, that's rather a significant burden, if you're not familiar enough with the syntax to write the script yourself in the first place.


Speak for yourself, but I would not want to be beholden to AI for every trivial shell one-liner. "Sorry boss, ChatGPT is down, I can't count how many *.txt files are in this directory. See you tomorrow!"

I'll take the better syntax, thanks.


To be fair, even local, small language models fare pretty well in such things (both explaining and writing).


Heaven forbid you read a man page. Even though Bash is weird, it's fully documented.


Documentation is useless if you don’t know what to look for. Which manual page do I open to find out what :(){:|:&};: means without already knowing?


Scripting languages are so dynamic, flexible, arcane, and subtle and the consequences for getting scripts wrong are so potentially catastrophic for a system that they are absolutely the last thing I would ever dare generate via LLM.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: