Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why I forked httpx

tildeweb.nl

Post reply on HN
Print view View original

191–194 of 194 posts

Re: Why I forked httpx

#191

Post by ial32 »

joouha wrote: post #130
robmccoll wrote: post #109

Earlier quoted context omitted.

Since modshim isn't money patching and appears to only be wrapping the external API of a package, if the change is deep enough inside the package, wouldn't you end up reimplementing most of the package from the outside?

Modshim does more than just wrap the external API of a package - it allows you to tweak something internal to the module while leaving its interface alone, without having to re-implement most of the package in order to re-bind new versions of objects. There are a couple of example of this readme: (1) modifing the TextWrapper object but then use it through the textwrap library's wrap() function, and (2) modifing the r…

I'm not necessarily interested in using modshim, but it got me wondering a couple of things out of curiosity:

- what's the performance like for big packages (say, pytorch)? Have you done some benchmarking?

- is typing kept for the shims? My immediate guess, again, without even trying it out, is not. If yes, how?

edit: formatting

Re: Why I forked httpx

#193

Post by duskdozer »

IshKebab wrote: post #186
duskdozer wrote: post #33

Earlier quoted context omitted.

I guess kind of obvious now noticing the rhyme

Yeah although in English I've only ever heard nigh-quest. Guess we're all getting it wrong.

For some reason the first thing I thought of on seeing it was a Monty Python reference

Re: Why I forked httpx

#194

Post by globular-toast »

znpy wrote: post #189
globular-toast wrote: post #188

Earlier quoted context omitted.

Just look at how much of the drama is caused by who "owns" the repository. In a decentralised model, which git perfectly supports, everybody owns their own branch(es). But all the issues etc. are stuck on the GitHub project.

> In a decentralised model, which git perfectly supports, everybody owns their own branch(es). But all the issues etc. are stuck on the GitHub project. yeah i'm gonna call BS on this. this kind of drama already existed when communities were "decentralised" and each one had its own forum, mailing list or whatever. the core of the issue here is about wanting to be the owner of a repository. so people should just not bo…

There are two main problems with "just fork" on GitHub and other forges:

1. Issues, PRs, discussions etc don't move over,

2. Discovery. When GitHub was in its infancy they made a big deal out of the "network" feature. Almost 20 years later it has languished, virtually unchanged in that entire time. When I think of decentralisation I think Bitcoin. We need a better way to "discover" the consensus fork. I feel like GitHub could do a lot to help, but they don't care.

Post reply on HN