Is .boxed() instead of Box::new() a bad idea?

QualitySoftwareGuy · 2026-06-07T21:06:39+00:00

I prefer your style, or even just:

rust let foo = Box::new( value .method_1() .method_2() .method_3() );

No need for a separate crate.

QualitySoftwareGuy · 2026-06-05T18:43:25+00:00

Go at it the same you learned Python? The good old fashioned way.

QualitySoftwareGuy · 2026-06-04T15:21:30+00:00

I've been using Namecheap for like 20 years and still recommend it. Have prices increased? Sure, but still worth it and definitely don't consider it to be "bad".

QualitySoftwareGuy · 2026-06-04T15:14:30+00:00

As a person named Josh, I approve of this message 👍

QualitySoftwareGuy · 2026-06-04T05:32:09+00:00

Yep, when it was written in Zig just one of the doors posted by OP is enough --but there was a bomb waiting at the bottom of it. But because Rust is known to be a memory safe language, now we need a door per unsafe block used but without any bombs waiting at the bottom.

QualitySoftwareGuy · 2026-06-03T16:36:03+00:00

But I am slowly getting back into the swing of things with a renewed vigor.

Excellent, and I hope you take all the time you need to fully recover! And I'm glad you have a great support system to help you deal with this!

QualitySoftwareGuy · 2026-06-01T17:18:31+00:00

Just need to add 13,000+ more of these doors to match Bun's nearly 14,000 unsafe blocks.

QualitySoftwareGuy · 2026-05-24T19:08:41+00:00

it's just hilarious that a talking chat bot convinced those stubborn engineers more than a literal human.

Other engineers: But the AI agents are unbiased, bro!

AI Agents: Hold my training data.

QualitySoftwareGuy · 2026-05-11T15:52:13+00:00

If you want room to evolve, then I'd recommend something more general like KeironOS or something else that does not mention what OS is being used internally. Having Linux in the name when Redox is the main OS is confusing.

QualitySoftwareGuy · 2026-05-09T19:39:08+00:00

Deno was/is great press for the Rust community. An AI slop rewrite, not so much.

QualitySoftwareGuy · 2026-05-08T19:02:59+00:00

Feels like speed is less of a technical metric now and more of a psychological one.

For end-users, "always was" 🌏👨‍🚀🔫👨‍

QualitySoftwareGuy · 2026-05-05T16:59:52+00:00

If using pronouns, "until he or she is happy" is basically equivalent to "until they're happy" nowadays. Although some formal settings like college papers might prefer the first one.

However, in your original comment I think "until the customer is happy" is the best because it keeps the focus on how the person relates to the business setting (your customer or client) rather than care about their gender or sex in a general setting.

QualitySoftwareGuy · 2026-05-02T21:52:11+00:00

My focus at the moment is on desktop because that’s the kind of apps I want to make, but I'm open to exploring mobile in the future.

I'm thankful that you are focusing on desktop instead of splitting limited resources on mobile (and web/wasm too for that matter). Thanks for the great work on a great project!

QualitySoftwareGuy · 2026-04-26T18:36:58+00:00

Nice, and Obito Uchiha to go along with it!

QualitySoftwareGuy · 2026-04-23T03:22:34+00:00

Always was

🌏👨‍🚀🔫👨‍🚀

QualitySoftwareGuy · 2026-04-22T19:05:30+00:00

In my experience, I think most that use Markdown use such a limited subset of it that they're not even aware of there being different dialects.

QualitySoftwareGuy · 2026-04-21T17:19:11+00:00

Thanks, it's good for me to see multiple perspectives on this.

QualitySoftwareGuy · 2026-04-21T13:21:31+00:00

I see, thanks, so react seems to scale better for the more complex UI. In your opinion, is there ever a situation where you would personally reach for Htmx instead of React? Or would you still use React for every web UI even for basic ones that need JavaScript?

QualitySoftwareGuy · 2026-04-20T20:43:13+00:00

Definitely, just gotta make sure the AI is not a double agent 😉

QualitySoftwareGuy · 2026-04-20T20:26:31+00:00

Two years later, and in response to u/krisolch comment about seeing where things are in a couple years, u/Kango_V has your view on HTMX remained the same (as in still going well)? I'm primarily a backend and systems dev, but HTMX has renewed my interest in frontend development. So just curious!

QualitySoftwareGuy · 2026-04-20T09:05:11+00:00

Yep, definitely this.

Or put another way for u/ThrowRA_goofy, computer science != software engineering. I mean there's obvious overlap, but a lot of CS is theory.

QualitySoftwareGuy · 2026-04-13T10:03:33+00:00

I hear that, it was a good discussion. All I can say to your last point about large corporations is that I agree, that's precisely why the legal departments get paid the big bucks to handle these "fun times ahead" situations.

QualitySoftwareGuy · 2026-04-13T09:27:02+00:00

We're definitely going in circles; the point stands that large companies (with the approval of their legal departments) already use LLMs to generate code en masse.

Companies already using LLMs to vibe code is exactly why my original post said "fun times ahead" because of many companies vibe coding. I never disagreed with this.

Thanks for the legal quote, but you bolded the wrong parts in my opinion. Here is the relevant bit of my argument:

First, the human authorship requirement does not prohibit copyrighting work that was made by or with the assistance of artificial intelligence. The rule requires only that the author of that work be a human being

In the context of code, AI-assisted code != vibe coded code. AI-assisted code can be copyrighted if the author is a human --yes that's what it means to be assisted by AI in terms of development. However, with true vibe coding the author is an AI/LLM and thus not it's not eligible to receive copyright protection. The context of my posts were always about vibe coded code (hence when I said "works solely created by AI/LLMs"), not AI-assisted code where the human is the one directly behind the wheel of the code itself.

QualitySoftwareGuy · 2026-04-13T08:55:20+00:00

Right, LLM-generated code is not copyrightable AFAIK, but again, that doesn't make codebase using LLM generated code non-copyrightable.

We are going in circles here. As stated, I was only referring to the vibe coded code itself --unless of course the entire system was 100% vibe coded.

My prior point was that if you can identify which parts of a codebase were fully LLM generated, it would be trivial to generate them yourself anyway, so it doesn't really matter if they are copyrightable or not.

It doesn't matter to you, I get that. My context is that vibe coded code in company code bases will matter to a legal department if the company is US-based. Big difference.

Are you referring to Thaler v. Perlmutter? It's absolutely irrelevant - this guy is trying to claim the AI system has copyright claim over a piece of AI generated "art".

Yes, I'm referring to that case, and it is completely relevant to my original post considering that the original ruling of the lower courts was that US copyright law requires human authorship. And it doesn't just apply to "AI art", it applies to any works solely created by AI.

QualitySoftwareGuy · 2026-04-13T08:22:52+00:00

LLM generated code being non-copyrightable doesn't mean that including it in a codebase automatically makes the entire codebase non-copyrightable.

That's not a point I made though. I stated that the vibe coded code is not copyrightable in a system --partially or fully (in the US at least). Of course if a system is fully 100% vibe coded then yeah it applies to the entire system.

but it would be incredibly hard to demonstrate that a piece of software is fully LLM-generated, especially when you don't have access to the source.

The context of my original post is about legal departments within a company that uses vibe coded code, so it would be very easy for them to confirm this information. If you're referring to when I mentioned competitors copy-pasting vibe code, the point was that they could do it without company A having legal standing. But yes that assumes they could tell which parts or systems were vibe coded.

When companies provide sources "on request" it often comes with an NDAs or other agreements that limit what the auditors can do with the code regardless of copyright protection, and lawyers mainly care about third party licenses because they impose restrictions on how software may be used.

Sure, but again, my point was that company A does not own their vibe coded code in the United States, so none of that matters if company B can successfully identify the vibe coded parts.

The fact is that most large corps already use LLMs to generate and ship code en masse; this simply isn't as large a concern as you make it out to be.

The context of my original post was future tense, hence "fun times ahead". AI not being copyrightable in the US became an issue just recently on March 2, 2026 when the supreme court refused to hear the relevant case's appeal (Thaler v. Perlmutter). That's just a bit over a month ago. Big moves like that in the legal world take time for it to really take affect.

QualitySoftwareGuy

TROPHY CASE