Is the project active? #12
Comments
|
No. I don't currently have time to work on this. There are some similar projects which seem to be more active:
|
|
I'm not guaranteed to work on this, but I thought of looking it over at the very least. I was definitely interested in creating or working on an LLVM-IR, even though I'm super-busy right now. A good ahead of time for a standard language like this would mean incredible things for backend development, as I see it. |
|
I am keen on working on this. But I intend |
|
Sounds cool. I look forward to seeing it.
Nathan Eggers.
…________________________________
From: Elliott.Wen ***@***.***>
Sent: Tuesday, June 29, 2021 5:01 AM
To: ts-llvm/ts-llvm ***@***.***>
Cc: Eggers, Nathan D ***@***.***>; Comment ***@***.***>
Subject: [EXTERNAL] Re: [ts-llvm/ts-llvm] Is the project active? (#12)
I am keen on working on this. But I intended to make it work on microcontrollers.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#12 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIFMN3FBE47JHAG55QWKB4LTVGDVJANCNFSM4HLKYHFQ>.
The [EXTERNAL] tag in the subject line identifies emails that do NOT originate from an ETSU person or service. Please exercise caution when handling emails from external sources. Any email that is unsolicited and requires you to take immediate action, appears to be forged or is PHISHING for information can be verified by emailing the ITS Help Desk.
|
|
Why stopped, it's really nice and cool project. I hope you find some time to keep this project up to date. Best wishes. @emlai |
|
yes. it would be really nice if we can figure out a roadmap for this project. For example, what language features need to be supported. And we can start from there.
I am keen to help too.
…Sent from my iPhone
On 29/08/2021, at 12:18 AM, Max Base ***@***.***> wrote:
Why stopped, it's really nice and cool project. I hope you find some time to keep this project up to date.
Best wishes. @emlai
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
|
Here's the more elaborated reason why I stopped working on this: Most TypeScript projects want to use NPM libraries written in JavaScript or non-strict TypeScript. I think making those libraries interoperate with the LLVM-compiled TypeScript is a huge amount of work. Compiling just the statically-typed subset of TypeScript to LLVM is already a lot of work by itself. Compiling those JS or non-strict-TS libraries into LLVM is probably not worth it, because they will probably run faster on an optimizing JS engine designed to run that kind of code, such as V8. Instead calling them via Node Addons or WebAssembly could make more sense, if possible. There is a very small subset of projects that avoid these problems entirely: projects that don't use NPM libraries and are written in strictly typed subset of TypeScript. But I think there are many existing languages better suited for those kinds of projects. So in conclusion, there's a lot of uncertain hard work to be done with this project, and it's not clear if the benefits are worth it. At least to me. So that's why I stopped working on ts-llvm. Instead I'm focused (when I have time) on creating a new language that's specifically designed to be very statically typed and optimizable, but with some of the high-level type-system features and ease-of-use that make TypeScript so great, such as compile-time null-safety. If you're interested, the project is on my GitHub profile. If someone wants to continue the work on ts-llvm, the roadmap is outlined in issues #6 and #7. |
|
That makes a lot of sense actually. I've been looking into the architecture of V8/Node and may move towards an embedded approach instead. Since they are written in C/C++ it should be easier to use Clang to get these working. It still more or less works as interpreted, but can work in embedded, which was the larger goal. I'm interested in remote desktop architectures and wanted a multi-language paradigm to control these. This is a project that is too large for me alone, and I have a lot of other things going on. The use of the embedded systems is to create a sensor network, like with industrial control architectures. The remote desktop would be an entry point to multi-system control. Lots of little parts and pieces and nothing is quite settled in yet. I've got an interest in large ideas, I guess.
Nathan Eggers.
…________________________________
From: Emil Laine ***@***.***>
Sent: Monday, August 30, 2021 12:00 PM
To: emlai/ts-llvm ***@***.***>
Cc: Eggers, Nathan D ***@***.***>; Comment ***@***.***>
Subject: [EXTERNAL] Re: [emlai/ts-llvm] Is the project active? (#12)
Here's the more elaborated reason why I stopped working on this:
Most TypeScript projects want to use NPM libraries written in JavaScript or non-strict TypeScript. I think making those libraries interoperate with the LLVM-compiled TypeScript is a huge amount of work. Compiling just the statically-typed subset of TypeScript to LLVM is already a lot of work by itself.
Compiling those JS or non-strict-TS libraries into LLVM is probably not worth it, because they will probably run faster on an optimizing JS engine designed to run that kind of code, such as V8. Instead calling them via Node Addons or WebAssembly could make more sense, if possible.
There is a very small subset of projects that avoid these problems entirely: projects that don't use NPM libraries and are written in strictly typed subset of TypeScript. But I think there are many existing languages better suited for those kinds of projects.
So in conclusion, there's a lot of uncertain hard work to be done with this project, and it's not clear if the benefits are worth it. At least to me.
So that's why I stopped working on ts-llvm. Instead I'm focused (when I have time) on creating a new language that's specifically designed to be very statically typed and optimizable, but with some of the high-level type-system features and ease-of-use that make TypeScript so great, such as compile-time null-safety. If you're interested, the project is on my GitHub profile.
If someone wants to continue the work on ts-llvm, the roadmap is outlined in issues #6<#6> and #7<#7>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#12 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIFMN3HQ2ZUYZI6KGBRJPATT7OTLDANCNFSM4HLKYHFQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
The [EXTERNAL] tag in the subject line identifies emails that do NOT originate from an ETSU person or service. Please exercise caution when handling emails from external sources. Any email that is unsolicited and requires you to take immediate action, appears to be forged or is PHISHING for information can be verified by emailing the ITS Help Desk.
|
|
@Technotechbloggie9 did you see wasm3 and WAMR projects? |
|
As this project is not active, Can I notify ppl about my project which is similar to this one. I have very good progress already. https://github.com/ASDAlexander77/TypeScriptCompiler |
Is this project still active?
The text was updated successfully, but these errors were encountered: