C has too much undefined behaviour because the standards comittee was being lazy and slapped that on a lot of issues that ought to have been implementation defined instead.

The most ridiculous example for UB: An unmatched ' or " character is encountered on a logical source line during tokenization.

Like WTF, that should be a compile time error, and it's easy to detect.

"The word ‘tokenizer’ makes a lot more sense, but ‘lexer’ is so much fun to say that I use it anyway."

No wonders people think a lot of programming subjects are intimidating.

Saw someone who wants to do a project online, asked what project it is, now hear me out:
A platform to share tech gossips, use web3 and tokenization to maintain privacy, and allow users to bet on the gossip using tokens

I mean… fuck me…

Hating WooCommerce at the moment. Have to update a private CC payment gateway plugin to do tokenization and subscriptions. The examples are pitching errors and deprecation notices, not all steps are being shown, and the example plugins aren’t providing any useful hints, either...

Last thing I need to deliver before Christmas; looking to be a long night...

Currently the only 3rd party tokenization VSCode supports is a massive pile of RegEx. There's a whole discussion about how procedural tokenization could be supported without running extension code in the UI thread. The central argument against delegating this to an external worker is that if the reply doesn't arrive fast enough it might interfere with characters typed later.

1. Any computer that can run VSCode can execute somewhere in the order of a _billion_ instructions per second. To a program, the delay between keystrokes is an eternity. The only way to run out of time here is if either the dev isn't aware that the request is time sensitive, or the framework communicates to the OS that the task isn't urgent and an arbitrary amount of work is scheduled before it.

2. Chromium is the pinnacle of cybersecurity and its primary job is to sandbox untrusted user code. You don't need another thread to do it.

3. This use case fits squarely in the original design objectives of Webassembly.

The tokenization of Orchid files depends on the exports of imported files, but in a way that never influences their exports or imports, so Orchid allows circular references.

I sometimes feel like my subconscious and conscious mind use the scope of my projects to annoy each other.