joesb

Either the package does or the developers do. And only one of them has compilation checks.

And what does DOS attacker want you to do? Not crashing the whole service to deny others of the service?

When a process is used to serve multiple requests, I don't think you need to let the whole process terminate just because there is a bug dealing with a single request. Just because we can not reason about the current request does not mean the only way to get to the clean state for other requests is to terminate the whole process.

I'm lost on how should I integrate all these "languages" of Racket into a single application. Like, I can see there are `typed/racket`, `racket/gui` and `scribble/base` languages. But how do I write a GUI application that create PDF while also having all the code be typed? I tried following Racket tutorial multiple times but I'm still lost on how to tied each unrelated "languages" together.

IMO, each chapter of the tutorial just talk about unrelated "language" and then never once show how they all work together. One chapter will talk about web server but not class system, then another chapter will talk about another "language" that support class but then never write web server in it.

The game doesn't have to be started from scratch.

For example, get him to write game on top of Roblox. Or any other game that allow simple mod.

If you want to get more hands on, there are plenty of game engines that is simple to write, many are in Python.

If you have an iPad, there are lots of Game coding app, like Swift Playground.

It's not completely about handling unplanned failure, but handling alternative path when the condition for one path is not met. For example, when you perform `withdrawMoney()` it can fail because there's not enough money in the account. This has nothing to do with your coding failure.

If you have if/else in your code, you don't think "If one path fail, so can the other path, so I never handle the other path".

> If my code works out of the box in an unmodified browser, then it is Vanilla JS. If I have to load a framework for it to work, then it isn't, period.

Minor nitpick, third party library and framework does not modify your browser. They all still run on unmodified browsers.

What is this article's obsession with things being "processed" food? Is "processed" the new "chemical"?

It's like the article trying to keep repeating the words "processed", "ultra-processed", "hyper-processed" as if it's some scary boogey man.

Which is fine if your company and teams use React a lot.

Why introduce inconsistency in everyone's workflow just because this specific page is a simple contact form?

The fact that it is just a simple contact form is exactly why you should use the same tools and workflow that everyone in your team has already been using.

Write what other people knows so you don't have to be the one maintaining it.

Why not? At that size, it takes less than your client can blink to load it.

Why is it relevant? The point is you are not the one needing to remember.

One day React could change from using Virtual Dom to the Svelte way and most user of library wouldn't notice.

The point of the article is that React remember where to make the modification for you.

I think OP was just saying that even if the article were true, it didn't mean that someone who claim to be one of those people actually were.

And that's a problem because?

> But our low-level motor actions and perceptions, coordinated by the brain, require a lot of precise computation.

But we don't actually do that precise computation though. try repeating any action exactly and you will see some inaccuracy.