From 095c74db90ba735c308569f8dee4c41456d5588d Mon Sep 17 00:00:00 2001
From: declantsien <51986034+declantsien@users.noreply.github.com>
Date: Tue, 10 Jan 2023 04:39:55 +0000
Subject: [PATCH] Update and rename README.md to README.org
---
README.md | 113 -----------------------------------------------------
README.org | 10 +++++
2 files changed, 10 insertions(+), 113 deletions(-)
delete mode 100644 README.md
create mode 100644 README.org
diff --git a/README.md b/README.md
deleted file mode 100644
index 351f9f2d186..00000000000
--- a/README.md
+++ /dev/null
@@ -1,113 +0,0 @@
-
-
-[](https://gitter.im/emacsng)
-[](https://github.com/emacs-ng/emacs-ng/actions?query=workflow%3ACI)
-[](https://www.reddit.com/r/emacsng/)
-
-# emacs-ng
-
-A new approach to Emacs
-
-
-
- homepage •
- Deno/Javascript •
- webrender •
- ng-module •
- handbook •
- faq
-
-
-
-## Intro
-
-emacs-ng is based off of the `master` branch of emacs, and regularly
-merges in the latest changes (this branch includes the native
-compilation feature from Andrea Corallo).
-
-The last merged commit is `6ebe8b03d8` (Aug 24 2021).
-
-## Motivation
-
-The goal of this fork is to explore new development approaches. To
-accomplish this, we aim to maintain an inclusive and innovative
-environment. The project is not about replacing elisp with a more
-popular language like Javascript. We just want to make emacs more
-approachable for people who don't like lisp as much as we do.
-
-Contributions are welcome from anyone and we are always happy to
-invite new people to the project. We are open towards interesting
-ideas to make emacs better.
-
-## Why Emacs-ng
-
-This project should be considered an additive native layer over emacs,
-bringing features like Deno's Javascript and Async I/O environment,
-Mozilla's Webrender, and other features in development. emacs-ng's
-approach is to utilize multiple new development approaches and tools
-to bring Emacs to the next level. It is maintained by a team that
-loves Emacs and everything it stands for - being totally
-introspectable, with a fully customizable and free development
-environment. We want Emacs to be a editor 40+ years from now that has
-the flexibility and design to keep up with progressive technology.
-
-## Contributing
-
-Emacs combined with the rust ecosystem brings a lot of
-possibilities. If you have any idea for a new feature, just open an
-issue before starting work so we can give you some feedback.
-
-We try to maintain a list of "new contributor" friendly issues tagged
-with "good first issue". You should also take a look at our
-[handbook](https://emacs-ng.github.io/emacs-ng/handbook/getting-started/).
-
-## Features
-
-### Webrender
-
-[WebRender](https://github.com/servo/webrender) is a GPU-based 2D
-rendering engine written in Rust from Mozilla. Firefox, the research
-web browser Servo, and other GUI frameworks draw with it. emacs-ng use
-it as a new experimental graphic backend to leverage GPU hardware.
-
-### Dynamic modules
-
-Allow dynamic modules to access *more of Emacs's internals*. Dynamic
-modules can be written to take advantage of these extra
-functionalities when they are available, while at the same time being
-*fully compatible* with vanilla Emacs.
-
-### Deno/Javascript
-
-One of emacs-ng's primary features is integrating the [Deno
-Runtime](https://deno.land/), which allows execution of JavaScript and
-Typescript within Emacs. The details of that feature are listed below,
-however many users would ask themselves **WHY JAVASCRIPT?** JavaScript
-is an extremely dynamic language that allows for a user to inspect and
-control their scripting environment. The key to note is that bringing
-in Deno isn't JUST JavaScript - it's an ecosystem of powerful tools
-and approaches that Emacs just doesn't have currently.
-
-* TypeScript offers an extremely flexible typing system, that allows
- to user to have compile time control of their scripting, with the
- flexibility of types "getting out of the way" when not needed.
-* Deno uses Google's v8 JavaScript engine, which features an extremely
- powerful JIT and world-class garbage collector.
-* Usage of modern Async I/O utilizing Rust's Tokio library.
-* Emacs-ng has WebWorker support, meaning that multiple JavaScript
- engines can be running in parallel within the editor. The only
- restriction is that only the 'main' JS Engine can directly call lisp
- functions.
-* Emacs-ng also has WebAssembly support - compile your C module as
- WebAsm and distribute it to the world. Don't worry about packaging
- shared libraries or changing module interfaces, everything can be
- handled and customized by you the user, at the scripting layer. No
- need to be dependent on native implementation details.
-
-#### Performance
-
-v8's world-class JIT offers the potential for large performance
-gains. Async I/O from Deno, WebWorkers, and WebAsm, gives you the
-tools to make Emacs a smoother and faster experience without having to
-install additional tools to launch as background processes or worry
-about shared library versions.
diff --git a/README.org b/README.org
new file mode 100644
index 00000000000..6558390454f
--- /dev/null
+++ b/README.org
@@ -0,0 +1,10 @@
+#+html: features/webrender
+
+#+html: Not worth it. Too much work. Abandon...
+Would be easier if we just use Webrender as an alternative rendering engine like Cairo.
+We could just obtain an OpenGL context from native_display_handle using surfman. Not sure
+how much benefits we would gain from there, since the underline core is still Emacs's redisplay.
+
+Also, Winit is in early stage. And Emacs Webrender output implementation is not fully finished yet.
+
+