Hemospectrum

> That is a fault of the programmer, not C.

It's common to hear this line from the C fandom, and very rare to hear a serious proposal for what to do with all this Bad Code written by Bad Programmers. The status quo is to rewrite the former from scratch, and totally ignore the latter in the hopes that they'll be magically pulled down to hell and have their hands burned off by daemons. As far as I know, that part doesn't actually happen. Instead, they just keep writing more Bad Code, and meanwhile the rewrites are just as liable to cause problems as whatever they replaced, because often as not, the people doing the rewrites also turn out to be Bad Programmers.

If pressed for actionable solutions, C advocates will sometimes mention tooling such as Valgrind and ASAN, as if merely having it exist guarantees that all C programmers are educated in its use and make it a part of their workflow. This clearly isn't the case. New programmers are still learning C from material written before such tooling existed. Old programmers are still recommending it. There's no path for Bad Programmers to become Good Programmers, except to be admonished in public to Stop Writing Bad Code.

Ultimately, I agree with you: The issue here isn't with the C language. It's with the people who use it. Their priorities do not include concerns like memory safety, and their normal response to questions of code quality is to make it somebody else's problem.

If the culture of the community were to change, I expect the language would follow.

Markdown is for writing human-readable text. Org-mode is for organizing many kinds of information (dates, tables, checklists...) in structured documents, while letting the user decide what that structure actually is. Both can be used for writing README files, but their feature sets are very different on the whole.

They can bundle the charges to the patrons to reduce cost to themselves, while still charging fees as if they were making individual transactions.

I’m inclined to believe they’re already doing this.

I’m mostly seeing a lot of Python. The examples show that multiple assignment unpacks collections, functions can be called with argument name assignment, and collections can be unpacked into named arguments, as opposed to using collections to replace named arguments.

You sure made some assumptions about me and ran with them. An assumption you could have made, but didn’t, is that I was speaking entirely from first-hand experiences and/or the experiences of people close to me. And an observation you could have made, but didn’t, is that only one part of my post resembled any kind of actionable advice: The solution anyone can offer.

I don’t know that there is a different solution. If your community dies, you can move on or die with it. But if someone’s going to celebrate that, I hope they realize what they’re saying.

> At the same time, each language is a barrier between people, one that prevents ideas to be shared and stories to be told. The fewer such barriers we have, the easier it becomes to understand others. Literally.

This is an easy opinion to harbor when you speak a language whose future is pretty much secure.

Imagine if you woke up one day and you were the last person who knew a word of English. All the English-language music you've ever heard, all the books and movies, etc., are now totally incomprehensible to everyone you'll ever meet. All copies of them, and indeed, all English text except for whatever's in your pockets, is gone. All the place names you know are removed from the map. All English words borrowed by other languages are gone. Every native English speaker (aside from you) has disappeared, and their very names are unpronounceable to the world's remaining population. Maybe even the Latin alphabet is gone.

You get to keep all your memories, but naturally nobody shares them or has reason to believe they actually happened. Most people don't care to hear about them. If they do, they see them as a curiosity, a museum piece to be put in a display case, not something with the slightest relevance to their own lives.

You can't even tell English-language jokes anymore. They aren't funny in translation.

Of course this leaves you isolated. And of course there's a solution anyone can offer you: Forget about English. Adopt a whole new life where you're a normal person who speaks a normal language that other normal people understand. Your identity as an English speaker is entertaining for about five minutes, but ultimately an inconvenience to society. Hurry up and let it go.

If this sounds harsher than what you were trying to say, perhaps you've underestimated what a language is to the people who speak it. It's more than just a list of words.

First AWS, now this.

At what point does the DOJ step in? Isn't this anticompetitive behavior? I've heard that Reagan-era deregulation changed a lot of the relevant law, but I'm not clear on how. Is Walmart doing this with the expectation of impunity because there's no longer a crime to charge them with, or because they see themselves as immune to prosecution?

Cloudflush.

> this is a very common misconception for some reason

The use of the umbrella term "intellectual property" is a deliberate tactic to seed that type of misinformation in public discourse, so that people will assume these different concepts are equivalent and that protections applying to one of them apply to all of them. You're seeing cases where this tactic has succeeded.

Yes. The "urge" part means "work:" Thaumaturgy is using magic to do work, and a demiurge was just a craftsman or artisan until Plato borrowed the term for theological purposes.

> Having recently noticed a little carpal tunnel (though in truth I don't know how to distinguish the two)

Carpal tunnel syndrome is a specific condition where your carpal tunnel constricts around a nerve. RSI is the umbrella term for these types of injuries.

The Rust community is pretty good at turning specific complaints into actionable proposals. Could you perhaps be more specific about what nice things in Modula/Delphi/Eiffel are missing from other languages, or about what might be different if Go or Rust borrowed more of their influence?

I believe it. Even in the released game, the NPCs' schedules break down on certain edge cases and they revert back to this kind of chaotic behavior. I've watched Quill-Weave sneak across town and follow someone into a temple to steal food out of his pockets, because her travel schedule (regularly visiting a certain town) was disrupted by interactions with the player.

> edge - the thing that connects nodes

Or "leaf" for singly-connected nodes. Or "graf" for that matter.

Last time I checked, the filesystem (HFS+) still supported resource forks, but in OS X they're neither necessary nor sufficient for their intended purpose. In classic Mac OS this was the only way to bundle parts of an application together and present them to the user as a single file. In OS X, that's done with plain old directories.

> It's not as if sunlight is a sparse resource (on a global scale)

But land is, particularly arable land, and particularly in a country like Japan. You can see for yourself in the picture that they have ~15 tiers of gardens, compared to a maximum of two or three when using sunlight. And sure, you could probably devise some method of piping and reflecting sunlight through to the lower tiers just to avoid consuming electricity, but then it wouldn't work at night, wouldn't work as well in winter, and so on.

Yep, a lot of people have noticed that. He's mentioned Rust in a few of his videos (and the compiler devs are always taking notes about his grievances) but he doesn't seem interested in working with the Rust community in any way. He considers Rust too ideologically opinionated to be of use to him.

That shouldn't ever be necessary. Part of the point of Rust is that you can do unsafe low-level work, so long as you tag it with the "unsafe" keyword to enable pointer arithmetic and so forth.

"Literary fiction" might sound redundant, but in fact it's jargon used by critics, usually to describe a certain range of writing styles in which all of the implied drama takes place in the characters' inner emotional states rather than anything explicitly described in the narration or dialogue. It's usually contrasted with "genre" fiction, I guess because they wanted a broader term than "pulp."

> That's the same situation languages like Factor and even Haskell saw seven years ago. The former is more or less dead and and the latter still never "broke out".

Kind of a nitpick, but "breaking out" was never a goal of the forces behind Haskell, and in fact contrary to their stated desires. Much of Haskell's value was always (and continues to be) its variety of tools for expressing the semantics of the problem the code tries to solve — features which we now see spreading rapidly among mainstream languages. The rest of its value (and its primary purpose) was as a research tool for developing such features. There's still a lot of work to be done in exploring that frontier.

That's because drivers are sloppy about enforcing it, even though it's been company policy for however many years.

You can click on the folder icon at the top of a Finder window and drag it into an open/save dialogue, or drag it into a Terminal window to get the absolute path. This works with individual files, too.

Almost: Intermediate representation. "Intermediate" because its primary purpose is communication between different phases of a compiler in a serializable form. Some compilers actually have multiple IRs for different stages; for example, GHC will first turn Haskell code into "Core," followed by STG, C--, and LLVM IR.

They do time out. As I understand it, this is an artifact of an implementation detail rather than part of the design. As such, the amount of time between reposts is nondeterministic.

The design of Swift was influenced by Rust. However, most of the resemblances are superficial or relate only to areas where Rust in turn was heavily influenced by other languages. For example, Rust's memory management model could not work in Swift (because this is an area where Swift remains compatible with Objective-C).

Apparently the hyphen isn't there by mistake. Here's the blog source repo: https://github.com/Mattias-/Mattias-.github.io

Are you perhaps using a browser or a DNS stack that rejects this type of domain name?

That isn't the first time such a comparison has been made, and the people making it are always remarking more on the culture surrounding the language than its implementation details (not that the latter are irrelevant, but Python certainly could be a Compiled Language™ if Guido so chose). The takeaway here is that both Go and Python codebases lend themselves to team efforts between early contributors and new arrivals, because the set of idioms you'll find is very consistent from one codebase to the next. This promotes a certain confidence in teams working on very large projects, as well as tools that must be maintained for a long period of time. It's a hard thing to measure. You certainly won't identify it just by asking what features the language has.

For the second, note that sharks are fish.

It bubbles up as far as an `unsafe { ... }` block, but no higher.

WINE and ReactOS have been known to share code, in both directions. It's not a zero-sum game.