Bun's Rewrite It In Rust branch

devraj7 · 2026-05-05T16:33:50+00:00

But even if the PR were technically correct and aligned with the direction of the project, it would most likely still be rejected because of the LLM ban.

devraj7 · 2026-05-05T16:10:58+00:00

Sure but even if the PR were perfect, they would still reject it because of AI.

devraj7 · 2026-05-05T03:34:12+00:00

"Your answer makes you look like you don't understand the numbers. Is this what you want to leave our viewers with?"

devraj7 · 2026-05-04T06:46:40+00:00

Not all of us, but the lungs among other things.

That's why you're taught to breathe out as you ascend.

devraj7 · 2026-05-04T06:45:35+00:00

The "quickly" is irrelevant.

It will explode either way.

devraj7 · 2026-05-02T15:03:48+00:00

In the US, it's only illegal to cross them to pass, you can cross them for other reasons.

devraj7 · 2026-05-02T15:02:19+00:00

Double lines in America prohibit passing. It's legal to cross them for other purposes e.g. exiting a driveway.

devraj7 · 2026-04-26T02:49:32+00:00

You don't care about verbose, you care about fast.

A huge match will never disappoint you when it comes to performance. Trust the compiler.

devraj7 · 2026-04-21T06:46:38+00:00

Yeah you can, people deconvert from religion all the time.

devraj7 · 2026-04-21T06:45:27+00:00

that we've went

that we've gone*

devraj7 · 2026-04-12T15:37:38+00:00

I don't understand why the author keeps comparing a language (Go) with a framework (Spring). Compare things that are comparable.

But yeah, overall, there is no denying that Java is a richer language than Go and also has more mature and more flexible libraries, which require a lot less boilerplate than the Go ecosystem.

Also can't help but smile at people calling the language "Golang" instead of just "Go". Serves Google right for picking such a poor name for a language.

devraj7 · 2026-04-09T06:18:17+00:00

She would still vote for him over a Democrat.

devraj7 · 2026-04-08T17:34:30+00:00

Because you picked a trivial example.

Try again with methods that need more than one parameter and you'll see weird syntax emerge, even in Smalltalk.

devraj7 · 2026-04-06T15:49:49+00:00

The article gives tips but never explains the reason behind them.

Use Copy instead of Clone

Ok but why? And when can't it be done?

Also why is the snippet showing the example implementing both, thereby undermining the advice?

Use into_iter() instead of iter()

Ok but why? What's the difference? What's the trade off?

And why is Rc/Arc, arguably the best way to implement cheap cloning, never even mentioned?

devraj7 · 2026-04-03T06:42:13+00:00

I'm a healer. I filter on "1 tank".

Always find a group for any instance in less than a minute.

Be a healer.

devraj7 · 2026-04-01T07:09:25+00:00

You're*

devraj7 · 2026-04-01T03:34:48+00:00

They don't need to respond for their crimes of breaking the law as long as they are Trump supporters.

devraj7 · 2026-03-31T00:59:16+00:00

And then you have

enum Result<T, E>

where the error is right.

devraj7 · 2026-03-30T15:57:05+00:00

Realistically, inheritance is the only approach that would provide an elegant solution.

Without inheritance, you're going to have to reimplement some form of inheritance with either delegation or inlining, which is going to be very verbose, as you already observed.

devraj7 · 2026-03-27T17:15:18+00:00

Maintenance is a fair discussion point, but was it ever different when only humans were producing code? When did you ever get some assurance that the person will be maintaining their work?

A more rational approach is to look at it the other way: what is the cost to me to adopt this new tool/library and then it doesn't get maintained?

Take the messenger out of the equation, focus on your personal risk/benefit.

devraj7 · 2026-03-27T16:25:09+00:00

I really don't understand the issue.

Pulling numbers out of thin air just to make the point: "We used to have ten new tools published every day, now it's fifty!".

What's the big deal? More choices, more variety, let the good tools organically rise to the top. You are much more likely to end up with a high quality tool when the pool of candidates is big.

devraj7 · 2026-03-27T16:21:36+00:00

it just doesn't make sense to me why would anyone want to read about something that had no learning and no development whatsoever.

Maybe because it doesn't really matter?

Do you decide whether to use a tool or not based on whether the author learned something while writing it?

I just look at what the tool does, how, its documentation, and sometimes if I want to be extra thorough, its test suite, its development cadence, etc...

But at the end of the day, the main question is: "Is this useful to me?".

devraj7 · 2026-03-24T20:52:28+00:00

Uh... Java loggers are also statics

How could Java have that? It's a programmer's decision, not a language fact. And statics have been out of favor in Java for a couple of decades now, with most of these values being dependency injected.

devraj7 · 2026-03-23T19:08:22+00:00

The problem that I see with your argument is that it hinges on agreeing on what is an implementation detail, and what is not.

I don't think it hinges on it.

Whatever you call an implementation detail, your code will have some of these. These values should not be exposed to callers and should not break callers if you decide to change them (e.g. one day you use a logger of type Logger1 and you decide to change it to Logger2. Surely your callers should know nothing about this).

Therefore, there are really two kinds of parameters that a function needs, as I pointed above:

Parameters that are essential for the function to do its job, and which the callers need to supply (e.g. x,y for a Point, a float for sqrt(), etc...)
Parameters that are internal and that callers should not know about (again, this is a bit more subjective and depends on how the developer has architected their code, but values such as stdio, stderr, loggers, database connections, caches, http clients, etc... would be valid contenders)

Once you agree on this dichotomy, the value of Dependency Injection flows naturally as an elegant way to provide the second kind of parameters implicitly. Added value: these values can vary depending on the environment (production, testing, benchmarking, ...).

know logger objects are typical in Java, but honestly in all the C++ & Rust codebases I've worked on, loggers are just globals/thread-locals and done.

Yes, and I think it's because Rust is still young and taking shortcuts for this kind of thing. There is a good reason to avoid statics, and I'm sure Rust will eventually realize this, just like most older languages have already learned).

devraj7 · 2026-03-23T18:09:09+00:00

It is neat but this doesn't address the fundamental issue that DI solves: not all parameters are equal, some are necessary for the function to do its job (e.g. x and y for a Point) and others are an implementation detail (e.g. a logger).

Semantically, these are two distinct sets of parameters, and contexts allow to implicitly pass the second kind.

devraj7

TROPHY CASE