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

181–190 of 194 posts

Re: Why I forked httpx

#181

Post by dirkc »

simlevesque wrote: post #122
dirkc wrote: post #49

Earlier quoted context omitted.

You would think that sending HTTP requests is a basic capability, but I've had fun in many languages doing so. Long ago (2020, or not so long ago, depending on how you look at it) I was surprised that doing an HTTP request on node using no dependencies was a little awkward: const response = await new Promise( (resolve, reject) => { const req = https.request(url, { }, res => { let body = ""; res.on("data", data => { b…

And you don't handle errors at all...

Left as an exercise for the reader... ;p

Re: Why I forked httpx

#182

Post by woodruffw »

Pay08 wrote: post #180
woodruffw wrote: post #151

Earlier quoted context omitted.

It's popular enough to be worth using as a datapoint. What's the point of the question?

I don't think it is worth using as a datapoint. Webdev is simply not what Rust was made for. It'd be somewhat like PHP having inline assembly.

I don't think this is relevant on three grounds:

1. Whether or not it was "made for" webdev, people do use Rust for that.

2. Plenty of people write networked Rust that interacts with HTTP. That code requires an HTTP stack, even if it isn't web development.

3. Like all of the other examples, Rust does have an excellent third-party HTTP stack (reqwest and its underpinnings). So it's not like Rust fails to do HTTP.

Re: Why I forked httpx

#183

Post by hitekker »

mananaysiempre wrote: post #75
forkerenok wrote: post #37

Earlier quoted context omitted.

What's the drama around starlette? (Can't find anything)

https://github.com/Kludex/starlette/issues/3180 and before that https://github.com/Kludex/starlette/issues/3042

lovelydinosaur appears to be undergoing a mental health crisis. Besides the drama and lies, I notice they (I think they?) seemed to misname the maintainer on purpose. They did it in the first thread, which the maintainer tried to correct, and they misnamed him again in the second thread.

Mia Kimberly Christie seems like dangerous person.

Re: Why I forked httpx

#184

Post by fastily »

hitekker wrote: post #183
mananaysiempre wrote: post #75

Earlier quoted context omitted.

https://github.com/Kludex/starlette/issues/3180 and before that https://github.com/Kludex/starlette/issues/3042

lovelydinosaur appears to be undergoing a mental health crisis. Besides the drama and lies, I notice they (I think they?) seemed to misname the maintainer on purpose. They did it in the first thread, which the maintainer tried to correct, and they misnamed him again in the second thread. Mia Kimberly Christie seems like dangerous person.

This has been ongoing for some time. I’ve raised valid issues in several encode projects and received rude/dismissive comments from this individual. I’ve reviewed their recent interactions with others on GitHub and it’s obvious that Mia (tom?) is super toxic/drama seeking

Re: Why I forked httpx

#185

Post by globular-toast »

kurtis_reed wrote: post #149
globular-toast wrote: post #50

Earlier quoted context omitted.

Right, my suspicion was correct. When I interacted with them a few years ago they seemed perfectly nice and friendly, but seem to have gone off the rails more recently. It's an uncomfortable situation and I've a feeling people are afraid to discuss this kind of thing but we really need to. People are a risk factor in software projects and we need to be resilient to changes they face. Forking is the right way, but pla…

Who are they?

As far as I can tell, the following names all refer to the same person:

- lovelydinosaur,

- Mia Kimberly Christie

- Kim (Christie)

- Tom Christie

Re: Why I forked httpx

#187

Post by niekiepriekie »

simlevesque wrote: post #122
dirkc wrote: post #49

Earlier quoted context omitted.

You would think that sending HTTP requests is a basic capability, but I've had fun in many languages doing so. Long ago (2020, or not so long ago, depending on how you look at it) I was surprised that doing an HTTP request on node using no dependencies was a little awkward: const response = await new Promise( (resolve, reject) => { const req = https.request(url, { }, res => { let body = ""; res.on("data", data => { b…

And you don't handle errors at all...

It's node. Why do errors if you can simply ignore them.

Re: Why I forked httpx

#188

Post by globular-toast »

znpy wrote: post #101
globular-toast wrote: post #50

Earlier quoted context omitted.

Right, my suspicion was correct. When I interacted with them a few years ago they seemed perfectly nice and friendly, but seem to have gone off the rails more recently. It's an uncomfortable situation and I've a feeling people are afraid to discuss this kind of thing but we really need to. People are a risk factor in software projects and we need to be resilient to changes they face. Forking is the right way, but pla…

> but places like GitHub have sold people on centralisation. We need to get back to decentralised dev. I don’t think that’s the case. It’s more of a marketing/market incentive. It’s great pr to be associated with the most famous project, way less so to be associated with a fork, at least until the fork becomes widespread and well recognised. GitHub does make it fairly easy to fork a project, I wouldn’t blame the situ…

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.

Re: Why I forked httpx

#189

Post by znpy »

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

Earlier quoted context omitted.

> but places like GitHub have sold people on centralisation. We need to get back to decentralised dev. I don’t think that’s the case. It’s more of a marketing/market incentive. It’s great pr to be associated with the most famous project, way less so to be associated with a fork, at least until the fork becomes widespread and well recognised. GitHub does make it fairly easy to fork a project, I wouldn’t blame the situ…

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 bother with being owner of a specific repository, but just fork it and move on. and github supports forking sufficiently well for this purpose.

Re: Why I forked httpx

#190

Post by ldng »

fastily wrote: post #184
hitekker wrote: post #183

Earlier quoted context omitted.

lovelydinosaur appears to be undergoing a mental health crisis. Besides the drama and lies, I notice they (I think they?) seemed to misname the maintainer on purpose. They did it in the first thread, which the maintainer tried to correct, and they misnamed him again in the second thread. Mia Kimberly Christie seems like dangerous person.

This has been ongoing for some time. I’ve raised valid issues in several encode projects and received rude/dismissive comments from this individual. I’ve reviewed their recent interactions with others on GitHub and it’s obvious that Mia (tom?) is super toxic/drama seeking

They always were but it's clearly spiraling faster.
Post reply on HN