4 ms·

“Nobody could have seen this coming…”? Well apparently a lot of people did. Maybe Jarred didn’t, maybe you didn’t, but most people correctly predicted what was

“Nobody could have seen this coming…”? Well apparently a lot of people did. Maybe Jarred didn’t, maybe you didn’t, but most people correctly predicted what was coming.

embedding-shape 5mo ago
See what coming?! I really don't understand what's going on here. Correctly predicted what, that Bun was being rewritten into Rust? I'm not sure anyone doubted that, all the work they did was public??? What on earth is going on here?
- grayhatter 5mo ago
  > What on earth is going on here? With the nearly complete PR with the port to rust, a number of people predicted that it was going to happen. They were assured it's unlikely to happen and then they were accused of overreacting over effectively nothing. When those same people who were already upset about the rewrite, learned that their predictions the same ones that were rudely dismissed, were in fact, correct, they became upset again; this time about being lied to. Correct or not, it's reasonable to conclude they were lied to. Especially given they correctly predicted the future.
  - famouswaffles 5mo ago
    >Correct or not, it's reasonable to conclude they were lied to. No it's not. If we were 9 days away from a human written version of this experiment then yeah it would be reasonable to conclude they were lied to, because a human written version would progress so much slower and steadier that it's very unlikely you hadn't made up most of your mind a week before merge time. But it's not human written. It's months, perhaps years of work compressed into a week, where the machine can go from 'nothing is working' to 'everything is working' in a few days. There is nothing reasonable about concluding you must have been lied to when such a delta in such a short time is possible. And if people fail to see that, then perhaps the initial assertions about an emotional meltdown were not so far off after all.
    - wiseowise 5mo ago
      I might surprise you, but tech projects have social part of it. Decisions like that are discussed with community. It is completely fine to not give a single shit about community, but then don't act surprised when community doesn't give a shit about you.
      - famouswaffles 5mo ago
        Decisions like this are discussed however the maintainers of the project wish to discuss them. And a majority of the time, these decisions are made and discussed solely by the maintainers, so I really have no idea what you're talking about.
- BoorishBears 5mo ago
  It's really simple. 9 days ago this is how the migration was described: > I work on Bun and this is my branch > This whole thread is an overreaction. 302 comments about code that does not work. We haven’t committed to rewriting. There’s a very high chance all this code gets thrown out completely. > I’m curious to see what a working version of this looks, what it feels like, how it performs and if/how hard it’d be to get it to pass Bun’s test suite and be maintainable. I’d like to be able to compare a viable Rust version and a Zig version side by side. 9 days after that comment, the rewrite has been merged to master. 9 days after "this is my branch" "the code doesn't work" "I'm just curious" "high chance it's thrown out"... it's merged to master. - Some people saw the original as an attempt to downplay the importance of the branch in response to negative feedback, rather than accurately describing what the branch represented. Those people essentially predicted that Bun's actions would shortly reflect much more conviction than was being let on. Experiments graduate to production all the time, but given the timelines involved, their predictions were correct.
  - famouswaffles 5mo ago
    Stop thinking about '9 days' like it means the same thing in an era where machines can generate thousands of lines of code in a few hours. There is no way a human rewrite like this wouldn't be roughly at the same stage with a 9 day delta. In that case, some of these accusations would be reasonable to make. But that is not the case here.
    - wiseowise 5mo ago
      [flagged]
      - famouswaffles 5mo ago
        Making a factual statement is drinking Koolaid ? Okay
    - BoorishBears 5mo ago
      You know, we used to look down on engineers who didn't realize there's more to software than the raw lines of code.
- wiseowise 5mo ago
  > I'm not sure anyone doubted that, all the work they did was public??? https://news.ycombinator.com/item?id=48019226 https://news.ycombinator.com/item?id=48019226 > This whole thread is an overreaction. 302 comments about code that does not work. We haven’t committed to rewriting. There’s a very high chance all this code gets thrown out completely.
- antonvs 5mo ago
  > What on earth is going on here? Irrational armchair quarterbacking driven by emotional reactions to change and perceived threats. It’s not worth worrying about this specific instance, but the overall trends could get messy. This is just a taste of that.

“Nobody could have seen this coming…”? Well apparently a lot of people did. Maybe Jarred didn’t, maybe you didn’t, but most people correctly predicted what was coming.

embedding-shape 5mo ago

See what coming?! I really don't understand what's going on here. Correctly predicted what, that Bun was being rewritten into Rust? I'm not sure anyone doubted that, all the work they did was public??? What on earth is going on here?

grayhatter 5mo ago
> What on earth is going on here? With the nearly complete PR with the port to rust, a number of people predicted that it was going to happen. They were assured it's unlikely to happen and then they were accused of overreacting over effectively nothing. When those same people who were already upset about the rewrite, learned that their predictions the same ones that were rudely dismissed, were in fact, correct, they became upset again; this time about being lied to. Correct or not, it's reasonable to conclude they were lied to. Especially given they correctly predicted the future.
- famouswaffles 5mo ago
  >Correct or not, it's reasonable to conclude they were lied to. No it's not. If we were 9 days away from a human written version of this experiment then yeah it would be reasonable to conclude they were lied to, because a human written version would progress so much slower and steadier that it's very unlikely you hadn't made up most of your mind a week before merge time. But it's not human written. It's months, perhaps years of work compressed into a week, where the machine can go from 'nothing is working' to 'everything is working' in a few days. There is nothing reasonable about concluding you must have been lied to when such a delta in such a short time is possible. And if people fail to see that, then perhaps the initial assertions about an emotional meltdown were not so far off after all.
  - wiseowise 5mo ago
    I might surprise you, but tech projects have social part of it. Decisions like that are discussed with community. It is completely fine to not give a single shit about community, but then don't act surprised when community doesn't give a shit about you.
    - famouswaffles 5mo ago
      Decisions like this are discussed however the maintainers of the project wish to discuss them. And a majority of the time, these decisions are made and discussed solely by the maintainers, so I really have no idea what you're talking about.
BoorishBears 5mo ago
It's really simple. 9 days ago this is how the migration was described: > I work on Bun and this is my branch > This whole thread is an overreaction. 302 comments about code that does not work. We haven’t committed to rewriting. There’s a very high chance all this code gets thrown out completely. > I’m curious to see what a working version of this looks, what it feels like, how it performs and if/how hard it’d be to get it to pass Bun’s test suite and be maintainable. I’d like to be able to compare a viable Rust version and a Zig version side by side. 9 days after that comment, the rewrite has been merged to master. 9 days after "this is my branch" "the code doesn't work" "I'm just curious" "high chance it's thrown out"... it's merged to master. - Some people saw the original as an attempt to downplay the importance of the branch in response to negative feedback, rather than accurately describing what the branch represented. Those people essentially predicted that Bun's actions would shortly reflect much more conviction than was being let on. Experiments graduate to production all the time, but given the timelines involved, their predictions were correct.
- famouswaffles 5mo ago
  Stop thinking about '9 days' like it means the same thing in an era where machines can generate thousands of lines of code in a few hours. There is no way a human rewrite like this wouldn't be roughly at the same stage with a 9 day delta. In that case, some of these accusations would be reasonable to make. But that is not the case here.
  - wiseowise 5mo ago
    [flagged]
    - famouswaffles 5mo ago
      Making a factual statement is drinking Koolaid ? Okay
  - BoorishBears 5mo ago
    You know, we used to look down on engineers who didn't realize there's more to software than the raw lines of code.
wiseowise 5mo ago
> I'm not sure anyone doubted that, all the work they did was public??? https://news.ycombinator.com/item?id=48019226 https://news.ycombinator.com/item?id=48019226 > This whole thread is an overreaction. 302 comments about code that does not work. We haven’t committed to rewriting. There’s a very high chance all this code gets thrown out completely.
antonvs 5mo ago
> What on earth is going on here? Irrational armchair quarterbacking driven by emotional reactions to change and perceived threats. It’s not worth worrying about this specific instance, but the overall trends could get messy. This is just a taste of that.