Intro Future

Blender is a 3D design software with a built-in video editor and a powerful compositor, among other relatively hidden gems. The advantage of these tools in a 3D design app might not be obvious to some but it saves from having to learn workflows of multiple apps. Once a user is comfortable with Blender's basic workflow and key commands, it's much easier to learn other parts of the software. Rather than exporting rendered videos to edit in another software, they can use the workflow they're already familiar with to edit within Blender. To be forthright, Blender has a steep learning curve. It takes time to get acquainted with it. The reward being increased productivity through familiarity with an intuitive and fast workflow. Once that time is taken, the same workflow can be applied to other aspects of design like video editing and compositing. What we want is a workflow that's far easier to learn than Blender's. Notepad for Windows provides our base experience. An

CSS is amazing, but the HTML DOM isn't. It's just so heavy. Maybe if JSON or some similar format could replace HTML/XML, it could be made lighter? Better, I think, would be to use a human readable format like Eno . It's as terse but much easier to read than JSON.

CSS is arguably the best means of UI customization. Consider an example of graphic-editing of UI elements: https://initialaudio.com/how-to-skin-sektor/ Using CSS, all elements in that project could potentially be done without graphics. Pros practically all designers now know CSS it's vastly capable Cons can't really decouple CSS from HTML whereas HTML is the biggest performance bottleneck (we'll solve this using different means) The Problem Unfortunately, CSS can get incredibly bulky. So what if we could design using CSS in a way that could feasibly be compiled to a local app? In general, everything would be styled using CSS, in the same bulky way it exists in browsers. But when compiled, it's no longer bulky. Benefits we have the full flexibility of CSS for all apps we have the full speed of native apps if needed

Pixel and vectors, video and text. What if we built one editor that could handle all these cases and more? One editor using one human-readable text format for files. If we use Markdown, we can use code blocks to represent binary data, if needed. Besides being able to store binary data, we could create human-readable data sections using formats like Eno . We could even include executable code.  With the flexibility of Markdown and its respective code blocks, we could store any type of data in a manageable way. So the file format for our all-purpose editor is plain text, Markdown. We'll build our editor for text processing. But from the start, we must account for all editing needs. We're building a text editor that can do what Photoshop does, and what Premiere does. So first and foremost, everything those editors can do, our editor must be able to do using plain text. From there, we can create intuitive graphic interfaces to facilitate different workflows. Those UIs will basica

Markdown converts to HTML. It’s designed to do that. But it’s drastically simpler in form than HTML. What if we could replace HTML altogether? Right now, Markdown is built to support HTML directly. So to support Markdown is to support all of HTML as well. What if we just remove the HTML support and build Markdown as the language the browser understands natively? Benefits: Markdown is far easier to read than HTML. It’s far faster to parse, no open/close tags. Smaller file size; since there are no open/close tags. Tying in with the proposal to code in English , Markdown would provide a familiar, written form to compliment the English language. CSS and JavaScript Both CSS and JavaScript can be included using code blocks. body { background : white ; } console . log ( 'This will be executed.' ) ; Further Consideration Various projects already exist to simplify use of Markdown either within HTML or by using an HTML page for boilerplate and Markdown file(s) for

Recent terminals like Alacritty and Kitty have proved OpenGL is the fastest way to handle text rendering. Xray , the potential next generation of Atom text editor rightly seems to follow suit. Meanwhile, Linux distros like Ubuntu have long been using OpenGL for general rendering to great success as seen with compositors like Compiz . It seems OpenGL might be the best technology for any and all rendering needs. If an OS is built on and uses OpenGL for everything, the consistency could yield great results. Text editing, image manipulation and even office apps would be as fast as possible.