While I won't say that writing a text editor or rewriting (base) Emacs is easy, I think it is all about the ecosystem. There's lots of Emacs reimplementations out there, some really good ones (like Lem), but they all have the same shortcoming: "no org mode", "no magit", and so on.
Emacs has a truly enormous ecosystem and only a reimplementation that runs everything unchanged has a chance of attracting enough attention. There was a time that that was seen as a worthwhile venture: Elisp was limited and slow. However, now with CL compatibilty and native compilation, I don't see it happening. Not in the sense of something standing up that can and will actually replace Emacs.
The sort of protections that you're offered by your CPU and modern OSes aren't offered by GPUs and their libraries, yet. So you're back in the '80s, when your Mac or MS-DOS machine would crash hard on the smallest issue. That's life, I'm afraid.
Lower settings. Sorry, thats all there is to it. 8GB is not a lot these days (i have two older cards in my PC and they're both 12). Textures, screen resolution, there's a bunch you can do.
Crashes are unavoidable, given that everyone wants max performance everywhere, things get shipped with all the debugging and checking stripped.
While I won't say that writing a text editor or rewriting (base) Emacs is easy, I think it is all about the ecosystem. There's lots of Emacs reimplementations out there, some really good ones (like Lem), but they all have the same shortcoming: "no org mode", "no magit", and so on.
Emacs has a truly enormous ecosystem and only a reimplementation that runs everything unchanged has a chance of attracting enough attention. There was a time that that was seen as a worthwhile venture: Elisp was limited and slow. However, now with CL compatibilty and native compilation, I don't see it happening. Not in the sense of something standing up that can and will actually replace Emacs.
Worse is better :-)