zeroimpl

Because then a missing comma somewhere becomes a weird bug, as opposed to a syntax error.

Languages with implicit string concatenation using no operator have found it to be a common source of bugs, eg python. See https://news.ycombinator.com/item?id=29841560

Same sort of problem. I have an account like that which was giving these messages and after trying a lot of things over few weeks I gave up.

Some long time later (year+) I retried and got in. I attempted to change the security settings, but it wouldn’t let me.

Some long time later again, I’m now locked out again.

This whole thing is ridiculous. I know the password, and have access to the account to which it forwards all emails. It should be obvious that their is no IP address which regularly uses this account, and that they are clearly locking out the account owner for no good reason.

I’m also curious how modern languages compare to older variants. Even modern English to Shakespeare stuff.

I think to measure efficiency of a written language, you’d have to time how long it takes people to read it (and correctly answer some questions to prove they understood it).

Exactly. At least make it something like --jps for strings and --jpn for numbers.

There are certainly tradeoffs, which is why I said I’d like the option.

Since I’m moderately familiar with the other language, I really just need the translation for words I don’t understand or mis-hear.

There is such a thing as a real-time translation. I’ve heard it in news broadcasts when a politician speaks a foreign language. It also happens all the time at the UN and other international negotiations. It works well but has downsides such as occasional latency while the translator needs to hear a few more words before they can translate.

A pet peeve of mine has been subtitles which flip the order of words, particularly when the sentence is broken into two lines. Like the spoken text in foreign language is “A murderer is... Joe” but it gets translated to “Joe is a... murderer”.

The other day I happened to see live content with closed captions, and I thought I would love the option to see subtitles like this, where words are translated precisely when spoken.

Do you have stock options and/or is it a small company where the success of the team may have a significant impact on the ability of the company to promote you in the future?

If either of those is the case, I think there may be reason to escalate as it does impact your future.

In case you missed the discussion on Moxie’s comment:

https://news.ycombinator.com/item?id=29845208

It sounds like these problems would be easier to address if the project maintainer adopted a CI/CD workflow. Just make sure that if it’s a public repo to setup proper access control.

I find the opposite pattern. The first week or so of a vacation I keep wondering about work and how the team is doing. It takes a while before I stop caring (and start ignoring work email). This is usually sped up by finding some side project to work on.

Yeah I think something like this is the way to go. The table name needs to be listed in a consistent manner like all other joins, and I don't think the syntax should be different depending on which order the tables are listed in.

With the above proposal, it seems the foreign key name could be left out in the common case of there being only one fkey between the two tables too.

I’d have gone with bq myself

[t rotateBy: a around: v] // This is Objective-C

I’ve never seen Smalltalk before, but I did find the verbose syntax of ObjC had some benefits.

That being said, typical C programmers don’t add all that whitespace, so the “who needs dots” and stuff is a bit misleading.

I tried turning on IPv6 on my VPS server running Docker. Not knowing much about IPv6, I naively assumed it’d just work. Evidently not, and you either need to run a NAT service or your containers become publicly routable, both having major caveats that I didn’t want to deal with.

The notion that every endpoint has a globally unique address, with prefixes coming down from some upstream provider is just fundamentally incompatible with how IPv4 networks are designed today.

Thanks, I’m not too knowledgeable on this subject, but given that the phrase 他不在這裏 can be understood entirely by looking up the definitions of the individual characters (which I don’t think have changed much over time), but not so for 佢唔喺呢度, it seems like your original assertion is false, and the root problem is Cantonese just differs too much from traditional written Chinese.

I don’t follow. Written Chinese predates the CCP by a very long time.

More specifically, 他不在這裏 is a phrase that I could imagine being used in official written text in past dynasties. But 佢唔喺呢度 does not.

You're not wrong, but sometimes simple formats aren't as simple as they look. It sounds like what you want is basically a format like /etc/os-release:

    NAME="Rocky Linux"
    VERSION="8.5 (Green Obsidian)"
    ID="rocky"
    ID_LIKE="rhel centos fedora"
    VERSION_ID="8.5"
    PLATFORM_ID="platform:el8"
    PRETTY_NAME="Rocky Linux 8.5 (Green Obsidian)"
    ANSI_COLOR="0;32"
    CPE_NAME="cpe:/o:rocky:rocky:8.5:GA"
    HOME_URL="https://rockylinux.org/"
    BUG_REPORT_URL="https://bugs.rockylinux.org/"
    ROCKY_SUPPORT_PRODUCT="Rocky Linux"
    ROCKY_SUPPORT_PRODUCT_VERSION="8"

On the surface this seems great, but those quotation marks are kind of annoying. Is it possible there's an escape syntax that's used in case the name also includes quotes? eg VERSION="8.5 (Green \"Aqua\" Obsidian)"? Is it also possible you can embed newlines in between the quotes too? Who knows... Thankfully with JSON there is a simple spec.

You'll prefer JSON the minute it becomes:

    cpu: 0.2
    kb_read_s: 0.12
    mac_addr: 10:AA:FF:00:55:66

Routers know how to figure out what route to use for a given IP.

If they apply this algorithm to the source IP and find that the optimal route to the source is a different interface than it was received on, that’d potentially be a red flag. But if the optimal route to the source is the same as the optimal route to the destination, that’d be a huge red flag.

Not exactly - the problem is mostly when doing variable expansion. The fact that bash treats "$x" and $x as different is a bit of a design flaw. Of course there's still an issue with evaluating dynamically generated code, but that problem is partly solved by working with arrays.

Don’t you just treat the range as half-open? Eg a '[)' range in Postgres.

No. The target is normally a primary key but the source is not. The source is rarely even unique.

The actual content (eg pictures, videos and text) all look better on a retina screen. I don’t think people buy retina screens so that the UI elements look prettier.

Yeah I’ve run into this a few times. In Postgres, you can’t add a foreign key referencing columns that aren’t indexed. I assume this is for performance reasons so inserts/updates are efficient, but there is no such check that the source columns are also indexed, so updates/deletes on the referenced table can be terribly slow.

Seems like salt was only invented 8000 years ago

https://en.wikipedia.org/wiki/Salt

If you subnet it as 2.0.0.0/31 it should work as far as I’m aware.

Feels like next somebody should setup a DNS system at 2.0.

From my experience, if you give pretty-printed JSON to a YAML parser, it will explode.

Sounds like you are using a specialized parser. At that point, it’s not YAML.

I feel you could use it for like 10 seconds to get some inspiration and then trivially come up with something much better. It’s kind of like brainstorming with somebody who speaks before they think.