rest of the world is ctrl-c, ctrl-x and ctrl-v. but emacs is in completely different world.

for emacs to gain mindshare, it needs to meet people where they are, not where emacs was 30 yrs ago.

of course, emacs does not work reliably in windows, so that is another issue

M-x cua-mode enables a variety of “traditional” keybinds such as C-x / C-c / C-v for cut / copy / paste

Learning that those shortcuts are arbitrary, application-defined conventions is the first step toward enlightenment.

> of course, emacs does not work reliably in windows, so that is another issue

No, it's the same issue. In a Linux shell (say, bash or fish) ctrl-c is not "copy" but "terminate program". Most emacs editing keys (copy-paste, motion) work in the shell as they do in emacs, at least in fish and bash (and probably other places in Linux).

Ctrl-C in Emacs is not "terminate program", it is "start of user command", in most modes. Similarly, even in vi/vim, Ctrl-C does something completely different. So this has nothing to do with the terminal whatsoever.

It's an even more basic Unix affordance, that terminals had a key-binding that generated the interrupt signal, and programs could define useful behaviors that commenced upon receipt of interrupt.

It made sense that interrupt in Emacs could get into a controlled state of receiving the next command. It's a little bit like the SAK (secure attention key) concept, as seen with Windows use of ctrl-alt-del.

Edit: Ironically, as a long-term emacs user, I don't really remember any commands that start with ctrl-c! For me, the most common sequences start with ctrl-X or meta-X. Or the prefix search commands ctrl-S and ctrl-R.

If you are running Emacs, either in the terminal or in graphical mode, pressing Ctrl+C does not generate any interrupt signal, it simply passes the C-c key to Emacs, which is just a general key bind.

Now, C-c in particular is the key stroke which non-core modes are recommended to use for their key binds (for example, sgml-mode uses C-c as a prefix for all of its commands, e.g. C-c C-f for sgml-skip-tag-forward, C-c C-b for sgml-skip-tag-backward, etc). Running `killall -SIGINT emacs` will not be interpreted as a C-c key being hit in emacs, it will just cause emacs to quit.

The same thing is true for other terminal based programs, like vi. Pressing Ctrl+C in vi does not generate an interrupt signal, it just passes this key combo to vi to do with as it pleases.

Yes, but the old ways were that the terminal interface itself was in charge of translating this keycode to a signal, based on the line discipline of the terminal. It was a consistent behavior across many apps unless they took effort to modify the current terminal line discipline, i.e. put the terminal into a raw mode. And then many apps tried to do something appropriately signal-like when they decided to handle these input characters without signals.

Ctrl-c is mostly for modes, not core emacs. Org-mode and gnus have a lot of bindings. But there’s a convention that ctrl-c then <character> are not to be bound. There needs to be a modifier for <character>

yes, that is probably why the "one armed bandit" was called that. and the name is sufficient reason to keep any reasonable person away

vue is adding a vdom less route. but not going away from it anytime soon

why is RSC not considered react? it is designed by core React team, and heavily recommended by core React team. and needs deep support from react.

Subjective depending on who you ask, but for me RSC is not really representative of React usage. (I believe) the vast majority of React apps (and the vast majority of dev experience in React) are front end only. I have been writing React in some form for 8+ years, but never touched RSC.

It is, especially in big corps doing MACH with SaaS products, deploying into Vercel.

Doesn’t mean you have to use it.

no matter how good the results are, this kind of rewrites deserves an experimental build to be battle tested by bleeding edge users.

It takes a lot of rigorous testing automated and manual and by community before such changes are cosnidered permanent.

One does not simply YOLO a full langugae rewrite without user feedback. it is insane.

>One does not simply YOLO a full langugae rewrite without user feedback. it is insane.

The whole ai thing today is pretty insane, I would say. Why not ride with it, especially if your company is one of the biggest leaders?

But the official canary/bleeding edge/nightly/whatever version is now the LLM rewrite, yes?

The page is not loading for me.

tyscript compiler is a cli tool. and is run for short periods of time. GC collection and memory leaks should be least of issue to look for

can it run windows?

The one invented writing also invented reading

Not necessarily.

I heard somewhere that Onedrive goes one step further, i.e. deleting local files and keeping them only in cloud. so when people delete file from onedrive, they find local files already deleted

my wife had here google account storage full because photos does auto backup and even after i deleted the photos from google photos. Auto backup kicked in and re-added them.

Also, there is no good way to download all photos and videos for backup. they have to be manually selected. the ui is super frustating. and since the storage is shared with email, emails are blocked due to this