kesh
design
kesh | design | |
---|---|---|
11 | 34 | |
19 | 11,349 | |
- | 0.2% | |
6.0 | 3.9 | |
5 months ago | 17 days ago | |
JavaScript | ||
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kesh
- Have any of you designed a conlang, and then designed a programming language based on the conlang or any fictional culture that would use it?
-
Too many words about Rust's function syntax
I have something similar in kesh, where : is the assignment operator and the type/signature may be "assigned" before the value:
-
Temporal Programming, a new name for an old paradigm
I'm not OP, in case you thought that :) kesh lives here. I tried incorporating some of the ideas discussed here, but posponed it to a later language, which I'm still thinking about.
-
What language features do you "Consider Harmful" and why?
This is a great idea that I've adopted for my PL. I took it a step further and also allow extensions of the core language to be specified, including profiles.
-
Let's talk about interesting language features.
My (non-existing) language kesh, designed to compile to TypeScript, has expression blocks. That was one of my first decisions.
-
October 2021 monthly "What are you working on?" thread
Still no work on a compiler, but more work on the documentation of kesh.
-
What are some simple but powerful compile-to-JS languages I might not know about, or that you are working on (not Elm, Reason, PureScript, or ClojureScript)?
I'm working on kesh, but it's only at the design stage. I have tried to make it simple yet powerful, so I thought I'd mention it even though you can't use it.
-
Why are you building a programming language?
I tried to distill down the most essential features of TS/JS (functional, prototypal) and then come up with new syntax and semantics that was minimal, orthogonal and hopefully easy to learn and use. The result is kesh and na.
-
September 2021 monthly "What are you working on?" thread
I like the way you think. I had the same goal with kesh. A minimal syntax is easier on the eye and lets you focus on the actual code.
-
August 2021 monthly "What are you working on?" thread
I'm only at the drawing board stage of kesh, a simple little PL that one day might possibly transpile to TypeScript. Not a single line of compiler code has been written so far, it's still all about syntax design and exploring ideas. kesh is mostly a pastime activity and something I can ponder over when I'm bored or can't sleep (which may be the reason I can't sleep).
design
-
Rust, WASM, and LOK
First of all, a quick rundown of what WASM is. It stands for Web Assembly. In essence, similar to how Java compiles down to a bytecode that is interpreted by a Java Virtual Machine, Web Assembly is a different bytecode interpreted by the browser. Many different languages can compile into WASM, and Javascript can interface with it like a module. In my case, I wrote a lot of the source code in Rust and compiled it down to a WASM module, then called into it from Javascript.
-
Surprisingly Powerful – Serverless WASM with Rust Article 1
WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. Wasm is designed as a portable compilation target for programming languages, enabling deployment on the web for client and server applications. - https://webassembly.org
-
Reaching and surpassing the limits of JavaScript BigData with WebAssembly
With WebAssembly we can compile our C++ codebase into a wasm module for the browser. So when you look at a SciChart.js chart you're actually seeing our C++ graphics engine wrapped for JavaScript.
-
WASM Instructions
I should add, however, that the unmentioned elephant in the room is V8 JIT (TurboFan), which simply doesn't handle irreducible control flow. While there are some valid theoretical arguments around the current arrangement in Wasm, looking at the history of the associated discussions makes it pretty obvious that having V8 support Wasm and generate fast code similar to what it can do for asm.js was an overriding concern in many cases. And Google straight up said that if Wasm has ICF, they will not bother supporting such cases, so it will be done by a much slower fallback:
https://github.com/WebAssembly/design/issues/796#issuecommen...
AFAIK no other Wasm implementation has the same constraint - the rest generally tend to desugar everything to jumps and then proceed from there. So this is, at least to some extent, yet another case of a large company effectively forcing an open standard to be more convenient for them specifically.
-
Supercharge Web AI Model Testing: WebGPU, WebGL, and Headless Chrome
https://github.com/WebAssembly/design/issues/1397
> Currently allocating more than ~300MB of memory is not reliable on Chrome on Android without resorting to Chrome-specific workarounds, nor in Safari on iOS.
That's about allocating CPU memory but the GPU memory situation is similar.
-
Build your own WebAssembly Compiler
As far as I can tell (5 minutes of internet research) this was to allow easier compilation to JavaScript as a fallback in the days when WASM wasn't widely supported.
"Please add goto" issue has been open since 2016:
https://github.com/WebAssembly/design/issues/796
Most interesting comment:
> The upcoming Go 1.11 release will have experimental support for WebAssembly. This will include full support for all of Go's features, including goroutines, channels, etc. However, the performance of the generated WebAssembly is currently not that good.
> This is mainly because of the missing goto instruction. Without the goto instruction we had to resort to using a toplevel loop and jump table in every function. Using the relooper algorithm is not an option for us, because when switching between goroutines we need to be able to resume execution at different points of a function. The relooper can not help with this, only a goto instruction can.
> It is awesome that WebAssembly got to the point where it can support a language like Go. But to be truly the assembly of the web, WebAssembly should be equally powerful as other assembly languages. Go has an advanced compiler which is able to emit very efficient assembly for a number of other platforms. This is why I would like to argue that it is mainly a limitation of WebAssembly and not of the Go compiler that it is not possible to also use this compiler to emit efficient assembly for the web.
^ https://github.com/WebAssembly/design/issues/796#issuecommen...
-
Flawless – Durable execution engine for Rust
When I implemented a WASM compiler, the only source of float-based non-determinism I found was in the exact byte representation of NaN. Floating point math is deterministic. See https://webassembly.org/docs/faq/#why-is-there-no-fast-math-... and https://github.com/WebAssembly/design/blob/main/Nondetermini....
-
Requiem for a Stringref
> To work with GC, you need some way to track if the GC'd object is accessible in WASM itself.
I've never heard of a GC with that kind of API. Usually any native code that holds a GC reference would either mark that reference as a root explicitly (eg. https://github.com/WebAssembly/design/issues/1459) or ensure that it can be traced from a parent object. Either way, this should prevent collection of the object. I agree that explicitly checking whether a GC'd object has been freed would not make any sense.
> The reason why you probably need a custom string type is so you can actually embed string literals without relying on interop with the environment.
WASM already has ways of embedding flat string data. This can be materialized into GC/heap objects at module startup. This must happen in some form anyway, as all GC-able objects must be registered with the GC upon creation, for them to be discoverable as candidates for collection.
Overall I still don't understand the issue. There is so much prior art for these patterns in native extensions for Python, PHP, Ruby, etc.
-
The Tug-of-War over Server-Side WebAssembly
Giving you a buffer that grows is the allocation approach I am talking about. This is not how your OS works. Your OS itself works with an allocator that does a pretty good job making sure that your memory ends up not fragmented. Because WASM is in between, the OS is not in control of the memory, and instead the browser is. The browser implementation of "bring your own allocator" is cute but realistically just a waste of time for everybody who wants to deploy a wasm app because whatever allocator you bring is crippled by the overarching allocator of the browser messing everything up.
It seems like the vendors are recognizing this though, with firefox now having a discard function aparently!
https://github.com/WebAssembly/design/issues/1397
- How do Rust WebAssembly apps free unused memory?
What are some alternatives?
ric-script - A modern scripting language; implemented in old school C, yacc & flex
content - The content behind MDN Web Docs
cubiml-demo - A simple ML-like programming language with subtyping and full type inference.
wave - Realtime Web Apps and Dashboards for Python and R
ghc-proposals - Proposed compiler and language changes for GHC and GHC/Haskell
interface-types
na - a minimal data notation format
Chevrotain - Parser Building Toolkit for JavaScript
durin - the Dependent Unboxed higher-oRder Intermediate Notation
WASI - WebAssembly System Interface
bluebird - A work-in-progess programming language modeled after Ada and C++
iswasmfast - Performance comparison of WebAssembly, C++ Addon, and native implementations of various algorithms in Node.js.