moeris

I think their point was that J and SQL target different domains, and each will be stronger in its respective domain. If I want to join two tables, filtering on some value, sorting, and viewing the first ten results, SQL will likely be the cleaner syntax. If I want to apply a polynomial function to a list of values, and calculate the standard deviation of the result, J will be much cleaner.

There's some similarity, at a high level, with how they work. But it doesn't really make sense to say one is, overall, better than the other, because they don't solve the same problem. It's like saying a hammer is better than a screwdriver.

Yes. The bar for sentience is quite low. It only means that one is capable of feeling sensations. (For example, Wikipedia gives the definition, "Sentience is the capacity to experience feelings and sensations.")

That's not how copyright works. Simply rewording each question will still violate copyright when you're copying all of the questions. I couldn't just reword Harry Potter and republish all of the novels. Likewise, copying some small portion may fall under fair use.

> Seller warrants that to the best of their knowledge, no existing claims or liens exist on the transferred Soul and agrees that any prior commitments that are in their power to dissolve are formally dissolved by the formation and signing of this agreement.

Does this mean that Christians would be bound to being baptized prior to selling their soul?

J has no operator precedence, and evaluates from right to left. Pretty easy to get used to.

> You may not care, but using code blocks that offer a note compact and clear expression is certainly more courteous.

I disagree, and so it's not likely "certain".

I do think that nitpicking over formatting is rather unproductive and rude, though. And it had wasted considerably more space than a format that you happen to dislike, but that others are fine with.

Like I said, I don't care. If you do, then that's on you.

> Markdown doesn't sorry ``` fenced code blocks

There isn't a single markdown. There are many different flavors, and all of them are markdown. Many include ``` (GitHub, Kdoc, pandoc, reddit, commonmark), especially as it allows you to specify the language if you want. I actually don't know if any tool I use that doesn't support them.

I appreciate the hint about code blocks. However, the point of markdown is to be readable without special rendering, so I really don't care that much.

I also disagree about not using ```. It's useful when writing markdown in an interface that swallows whitespace.

You can write APL or J in a way that is readable. Part of the problem is that most people's exposure to array languages is in the context of code golf or leetcode-style problems.

In some areas, if you're familiar with the language, it's much more readable than other languages due to being more concise.

For example, if you wanted to calculate the sample standard deviation

```

mean =: +/ % #

sum_of_squares =: +/@:*:@:(] - mean)

stdev =: %: @: (sum_of_squares % <:@:#)

```

Is pretty readable, I think. Of course, of you don't know the primitives, then it doesn't look like it's readable.

(I'm on my phone, so I may have typed something wrong.)

As someone who built a forge and a good deal of blacksmithing equipment in order to make tools for woodworking... This analogy is supposed to make the situation sound ridiculous, but it really isn't. If customizable physical tools were able to be created and destroyed as cheaply as objects on the heap, every carpenterwould want a tool factory factory factory. There's so many jobs where a custom tool is really useful.

It's definitely different depending on the state. In part because some states issue more teaching certificates per year. Michigan is one of those. At the time I was teaching, in around 2017, I had a friend get a job in Novi (Metro Detroit). The competition was pretty intense. See for example, [this posting](https://www.michigancapitolconfidential.com/novi-community-s...) which had over 900 applicants.

It took me over a year after graduation to get a job, and I had applied to over 130 postings. I ended up finally getting a job in an inner city school.

The situation could very well have been very different in Chicago, though, depending on a lot of factors.

I was a teacher in the Midwest before moving into programming. My salary was $28k. I worked in a larger city for a couple years and was making $35k for a while.

In order to afford student loan payments and rent, I worked three jobs. Still missed meals and was late in payments regularly.

The cities your mentioning are very high COL areas, and relatively affluent. Competition for those teaching positions is going to be very intense, and mostly go to senior teachers with at least 5-10 years experience. It's not representative of the nation.

Am I supposed to come away thinking they're both reasonable interpretations which accurately critique the main argument in this article? Because that's what I came away with.

(At the moment, the other to comment is about how focusing on positive goals is a good business strategy, not just light-stepping on legal egg shells.)

The renderings are almost entirely of white people. Are they not aiming for diversity, or is Arizona just very white?

> See Air Force pilots and Anthrax vaccine history. Rare but devastating consequences.

Do you have a source? Paul Offit, at least had said that we don't see vaccines causing long-term harm which aren't apparent within the first couple weeks. (In his interview on Oh No! with Ross and Carrie.)

> it may be anti-competitive

Unless contributions to add other search engines have been denied by the developers, it's not a strong argument.

Probably something in your system or network. The page loads fine in Firefox mobile, at least.

There's also the major system, which is probably better suited to English.

https://en.wikipedia.org/wiki/Mnemonic_major_system?wprov=sf...

> yes, trees/plants probably also feel some kind of pain

Are you kidding? How do you suppose one can feel pain without a nervous system? Magic?

That's more of an argument for them being overused, not for them being useless.

I disagree. I like to learn about the history and motivations behind a technology. It gives me context and helps me to remember facts that would otherwise be hard to remember, besides being enjoyable.

You mean former?

If you want the ability to pipe commands more natively, Kakoune does that. It also improves on vi's commands syntax, and allows multiple selections.

I switched to Kakoune after trying to find something more Acme-like for the terminal. In fact, I still use all the scripts that I wrote for Acme. To insert the results of a command, you can use `! <command>`. To pipe, highlight and use `| <command>`.

You don't get mouse chording, but I find I don't miss it too much.

> I think one of the advantages of a large/durable ecosystem is that it lets me worry less about problems I don't yet have.

That's true. If you're finding numerous workflow problems with neovim, it'll probably be true of Kakoune, as well.

> > Kakoune just feels better integrated with the environment > > Out of curiosity, is this an argument for enjoyment or productivity?

Both, though it's a more persuasive argument for productivity. Because it's easier to integrate with the environment, those workflow problems you mention can be solved by delegating to the environment, in some cases. For example, kakoune delegates to the environment for window management -- so things like resizing windows and switching between them is handled through tmux for me. Obviously, though, that's could be a poor substitution for some dedicated solutions in the editor. But overall, I prefer it, as it allows me to get familiar with unix utilities, which are useful in a wider range of applications. It also means there isn't an arcane scripting language associated with using the editor. I have a thing against vimscript.

> differences in keybindings are also worth a mention

I suppose. Having used vim for years, I was able to pick up the keybindings relatively quickly (< 1 day); they're almost identical. The main difference, that the selection comes before the action, also makes it easier to pick up.

But, yeah, that muscle memory is a loss. I find myself trying to do multiple selections and use kakoune keybindings in bash vi-mode, often.

> I'm not sure I can say the same about Kakoune, for example, which is a certainly a promising project but hasn't yet convinced me to jump the fence.

I've made that jump a couple of months ago, and so far I love it. There isn't as large of an ecosystem, but Kakoune just feels better integrated with the environment. Is your hesitancy based on some particular feature, or the ecosystem, or something else? Or is there some default that you dislike?

I feel like it doesn't need to have as many maintainers in order to be successful, because its philosophy is much more spartan. The maintainers pretty aggressively keep the project's scope in check.

You can't run it in crostini?

> I bet the engineers of MCAS didn't even have a view on the overall system

By system so your mean the MCAS, the airplane, it Boeing. I don't think you're correct if your mean the MCAS or how it integrated with the airplane. You don't think they had any sort of integration tests established? Also, one one the failings was that the system only relied on input from a single sensor, so that failing should have been extremely obvious.

Unless by system you mean Boeing as a whole. I'm sure that as a part of the requirements process they were told that the system can be deactivated (which it could be), and I'm sure they were probably unaware that pilots were not being trained in disabling the MCAS. That makes those technical failures still obvious, but nonetheless understandable and maybe even acceptable in that context.

> there are (in the US) government employees making sure they are safe. The workers are well represented by a strong union, have good healthcare and reasonable wages.

What country do you live in? Most teachers are employees of the local school district, not directly of the government. (When I was a Title I teacher, I was a federal employee, but that's not very common). I was never in a union, because there weren't any in the Detroit charter schools I worked at. And I only made $27,000 a year. Does that sound well-paid to you? Even though we had decent health care, with student loans I couldn't afford the copay, so I forwent any health care unless it was an emergency.