Okay, I’ll spend one last reply on this, because I don’t appreciate getting a strawman assigned to me. I didn’t say getting “every character’s expressed desires being instantly granted” is the main thing making fiction interesting. I said it’s seeing actions play out that you normally don’t is what it makes it interesting. That’s quite a different thing.

And no, I still don’t think it’s a major plot point. It’s a plot point, yes, but the movies also left it out without real impact to the plot. That’s not a major plot point to me.

that’s a reason to have Beverly suggest it. Not a reason to have it actually happen.

Sorry, but that’s just silly. If it were brought up as a suggestion that didn’t happen, that would be even weirder than it actually happening. As a writer, you don’t go around finding reasons to block your character’s ideas, because that’s a horribly anti-climactic thing to do, teasing your readers for no purpose, but worst of all, you don’t get to see how the action pans out if it does happen, which is the primary thing that makes fiction interesting to begin with.

And no, not every action needs foreshadowing either. In the grand scheme of things, this whole scene that people fuss about isn’t a major plot point in the book. I read the book twice (though even the second time was a while ago), and I had pretty much forgotten about it, until I saw people complaining it. But it still seems as if you think King has some moral obligation to guard and guide the actions of his characters. He doesn’t, and thankfully he doesn’t, because his books are more interesting for it.

As a writer, I disagree. Writers often write thinking from the perspective of their characters. If something makes sense from the character’s perspective, they’ll write it. It’s not an endorsement by the writer, it just makes for a natural and believable progression and that’s why the book is better for it.

I can bet you King never decided that he should include such a scene because it would make the book better. He did it because he was writing from her perspective, and it popped into his mind as something that made sense for her to do.

It’s not a fantasy, not an endorsement, and not a post-rationalisation either. And knowing his writing style, upon reflection he probably felt it belonged for shock value alone. Writers do have a knack for pushing boundaries, and he’s certainly got a taste of it.

I think there is an objective good. That goodness is Life itself. So long as we treat all Life with respect and try to live a life of balance, that makes us good. You are right though that this is still a very simplified view, and what it means to “live in balance” can depend on the situation or environment. But it’s a starting point at least.

As for forgiveness, it’s a choice. If someone makes an honest mistake, it should be easy to forgive them, as whatever harm they caused was not intentional. But if someone makes a wilful mistake, it will be harder to forgive them. And yet, because forgiveness is a choice, we can look at the reasons why someone acted in a manner that was harmful, and still decide to forgive them, especially if they repent.

As for consequences, those are results of our actions, whether intentional or unintentional. They are not strictly related to the concept of forgiveness, but generally speaking, we find it easy to forgive someone if their actions are harmless, or if the consequences don’t affect us personally. But if someone’s actions do affect us, we find it harder to forgive, regardless of whether something was an honest mistake or not. But the key to forgiveness, in my opinion, is that we need to look beyond the consequences and look beyond how we were personally affected. Forgiveness is a choice, and that choice is easier to make if our emotion is not muddied by consequence.

Silver actually interacts horribly with and ruins the flavour of some foods. There’s a reason why silver cups often have gold plating on the inside to not ruin the taste of wine.

I’d stick with the steel any time.

I can take this one: Because he doesn’t actually care about creating anything of value. If he truly believed in it, you’re right, Twitter or even Tesla’s software engineers would be on the chopping block and he’d replace them with AI as soon as he can. But he doesn’t.

He knows this is a longshot. Most likely to fail, but very profitable on the near-impossible chance that it works. But he doesn’t care even if the odds are truly impossible. Because this is an investment opportunity, so people will throw money his way, no matter what the odds.

People assume he’s an idiot, and he is. But he’s not stupid, at least not in every way. He certainly has a skill for separating others from their money, which he happily takes advantage of.

That’s fair, although technically you could catch SIGSEGV and release resources that way too.

Also, given that resources will be reclaimed by the OS regardless of which kind of crash we’re talking about, the effective difference is usually (but not always) negligible.

Either way, no user would consider a panic!() to be not a crash because destructors ran. And most developers don’t either.

“An abrupt exit”, more commonly known as a “crash”.

If you’re going to argue that an exit through panic!() is not a crash, I will argue that your definition of a crash is just an abrupt exit initiated by the OS. In other words, there’s no meaningful distinction as the result is the same.

I would argue that because C is so hard to program in, even the claim to machine efficiency is arguable. Yes, if you have infinite time for implementation, then C is among the most efficient, but then the same applies to C++, Rust and Zig too, because with infinite time any artificial hurdle can be cleared by the programmer.

In practice however, programmers have limited time. That means they need to use the tools of the language to save themselves time. Languages with higher levels of abstraction make it easier, not harder, to reach high performance, assuming the abstractions don’t provide too much overhead. C++, Rust and Zig all apply in this domain.

An example is the situation where you need a hash map or B-Tree map to implement efficient lookups. The languages with higher abstraction give you reusable, high performance options. The C programmer will need to either roll his own, which may not be an option if time Is limited, or choose a lower-performance alternative.

Of course, but it needn’t be black and white. You can also diversify, make yourself less reliant on a single platform. And by doing so, enable your audience to follow you elsewhere. Or diversify into different activities altogether. And when it’s no longer half your income on the line, then switch.

But doing nothing and saying, “but half my income!”? That’s not only a choice, but also complacency.

Great points, except:

People can’t leave for anything smaller.

They can and some do. It’s still a choice.

Haha, sure thing!

So, today, TurboPascal isn’t a very popular programming language anymore. But that’s okay! We have new programming languages nowadays. Some of the popular languages that we use today include JavaScript, TypeScript and CSS. You don’t need to know much about these languages, except that they’re commonly used for creating websites and apps that run on the web.

Now, assume you want to create a website or a webapp, and you were to learn these languages for that purpose. In that case you have quite a learning experience ahead of you, which is great! Learning can be fun! But what’s not so great is that these languages have lots of room to make mistakes. Now, everyone makes mistakes, that’s just a fact of life, but when mistakes can be avoided, that’s generally preferred.

This is where Biome comes in: It is a tool – we call it a linter – that helps you to detect many kinds of common mistakes. It can show you where these mistakes are, and sometimes even fix them for you. It can also show you possible mistakes, things that are not necessarily a mistake, but things that look suspicious.

And on top of that, Biome offers you another tool: It’s called a formatter. When you write your code, it automatically takes care for you that the code looks consistent. So it fixes things like indentation and other use of whitespace for you, as well as where to place your parentheses and stuff like that.

Together, hopefully these two things can make your programming experience a little bit more enjoyable. Cheers!

They’re included in the beta!

Specifically, you can create GritQL plugins for custom linter diagnostics. There’s certainly more we’d like to do on that front, but we’re first going to see how these are being received to decide where to prioritise next.

I don’t have Nix experience myself, but what would it take to be better supported there? I think we’d be open to PRs for that ☺️

We don’t currently publish to Crates.io, but we do have CI integrations that can install without needing NPM.

Formatter and linter in one even :) I’ve updated the message at the top.

I’m making a case for custom codes, not for using a 200 status code with it. My reply said the 200 didn’t make sense.

Of course once you use custom codes, the actual HTTP status codes do become less important, because there’s some redundancy there. That’s not an argument to do it wrong, but it is an argument that accurate HTTP status codes are less of a priority. So understandably some people will take shortcuts.

Apparently you find this very frustrating, but in the end it’s just an implementation detail. But it also sounds like you’re more frustrated with the service API as a whole than the fact it uses custom error codes specifically, so I’m just going to leave it at that.

Well, looking at your example, I think a good case can even be made for it.

“s23” doesn’t look like an HTTP status code, so including it can make total sense. After all, there’s plenty of reasons why you could want custom error codes that don’t really align with HTTP codes, and customised error messages are also a sensible use case for that.

Of course duplicating the actual HTTP status code in your body is just silly. And if you use custom error codes, it often still makes sense to use the closest matching HTTP status code in addition to it (so yeah, I agree the 200 in your example doesn’t make a lot of sense). But neither of those preclude good reasons for custom codes.

Oh, and then I pair it with a very boring Dell mouse for extra style.

Ha, I better not tell you about the Apple Keyboard I use with my Linux laptop then. Don’t like macOS much, but I love their flat keyboards.