Yeah, you’re right. Lemmy is reddit, but worse, and very small. I have no doubt your contributions will keep it that way. I’m going to delete my account. This is just not worth anybody’s time and attention.

Even between Linux on x86 and Linux on x86. Thing was running fine for months, I make a small change, test, deploy to staging (same machine as prod, so that helped), and suddenly some library deep in the bowels of the app says that it can’t start a thread. Runs on my machine though. Turns out to be some incompatibility that had to be fixed by excluding seccomp. Version updates can be a bitch.

That’s TypeScript’s whole point. It’s not for the computer, it’s for the programmer. It’s to avoid you assigning a string to something you elsewhere assume to contain a number. In Typescript, there’s just no solution for this, except requiring the programmer to specify the type. It can’t be inferred flawlessly.

That’s such a weird take. Who cares what another language does? Your complaint was about typescript. Which lets the programmer decide what this should be. As you could have known.

But most likely it was just trolling. On the plus side, at least now I know that the rigid minded devs came here too, and took their righteousness with them.

Are you Larry Ellison? Because then your remarks would suddenly make sense.

It’s really simple: if you can’t avoid spreading your database over many machines, sqlite is not the tool to use. Pick another one. Even if you can run it on a single server, but need authorized network access from multiple backends, it’s not for you (although there are some services built around sqlite that might help). Pick something else. But don’t hate a perfectly fine, well defined tool for existing.

It doesn’t even apply to the members of the project. It’s St. Benedict’s rule, and only chapter 4 of it, relating to the life in a monastery, but “No one is required to follow The Rule, to know The Rule, or even to think that The Rule is a good idea.” It has a whole bunch of good advice for living in a community, interspersed with religion. But if you work together on a project, “be not lazy” is not a bad suggestion. Nor is “Be a help in times of trouble”. Many of those concepts have been proposed in other religions or social contracts all over the world. And it cannot be taken too seriously: “Speak no useless words or words that move to laughter”

As for programmers: Respect your seniors. Love your juniors.

So what’s the type of x in

x = 1;
x = x + "1";

number? string? string|number? any?

The ts compiler can make a fair amount of inferences, but at some points you need to nail down the type. Is that so bad?

Over here, it’s customary that some HR rep tells you most of that. There usually is a handbook with all the rules, so they know it by heart.

A question I find important is financial stability and outlook. How is the company doing? How’s the market? What’s the prognosis for staying afloat? Are they sure it will survive 1 year? 2 years? 5 years? These questions have different answers for different stages: a startup’s outlook can be determined by the need for VC capital, an established small-to-medium sized company depends on the state of the economy, so buffers are important.

It does explain the interest in rust.

That should be posted to Programming Humor.

It’s quite versatile. Originally for context-free grammars (although it’s likely someone has an extended version), so basically for “normal” programming language-style grammar. There are some limitations, but you’re not very likely to use them in a normal grammar, and they’re easy to rewrite.

Linear time for unamiguous grammars.

I do like the counter-intuitive/somewhat surprising answer given by AbelianGrape. It’s a tantalizing result, but telling which numbers are in the right place is cheating, isn’t it? It means you already have an O(1) addressable version of the sorted array. I doubt checking it without that knowledge is going to be faster than O(log n).