I don’t understand the hate for voyager. Sure it had some problems, but I thought it was great. Both at the time and looking back on it

You don’t lose info as long as the offset is marked correctly

Logging in local time is fine as long as the offset is marked. Everything else I agree with you though

At my work, we have a big Rails app with lots of tests

Of course they need a blog post to get test times down to something that’s already way too slow. Ruby and Rails are such a dumpster fires

Wtf. You can’t possibly be suggesting that any of this is a good idea

It’s because it’s hard to make them correct. It’s not any harder to write it in rust than in C. Just C lets you do it wrong

IE you can quickly and easily write C that compiles but has runtime issues.

So what’s “easy” about it then? Just getting something to compile? That’s not a very good measure of “easyness”.

How so? That’s like, the thing that makes rust awesome to write.

Coding is rust is amazing. It feels so right

Why not choose rust instead of C, then you can trivially write python bindings directly to your rust https://pyo3.rs/v0.21.0-beta.0

Yes Rust is harder to write than C

I would totally argue with this. Rust is way easier to write than C

Yeah, I missed the part where they wanted it to be built into the browser

To compile stuff for macs without having to buy a mac

It doesn’t have to be fully unique either. How about revisiting the delta quadrant?

I see, I guess I get the point they’re making. We can do iframe reloads based on clicks without javascript, why not div reloads. I think framing it as a way of doing this without javascript rather than without a framework would be clearer and a better argument

I just want a new series like voyager. Taking place in the future (not prequels), doing something unique, having a cohesive progressive storyline but not necessarily extremely serialized like picard, and with new characters

I’m confused. This is exactly what https://htmx.org/attributes/hx-target/ is for since they’re already using htmx. This doesn’t make sense to add to the html spec unless ajax requests themselves are added such that browsers will do this automatically. Which I don’t think anyone wants.

Making a change in 5 places sucks, making it in 2 could be reasonable. If 2 pieces of code are similar but different enough, I’ve seen way too often people try to force them into a common abstraction. That’s more what the article is about.

Use an IDE if you aren’t already. Jetbrains stuff is great. Having autocomplete is invaluable.

Careful with this. Not everything needs to be reusable, and copy/paste isn’t inherently bad.

https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction