Remote: Open to remote, hybrid, or on-site (SF Bay Area).

Willing to relocate: No

Technologies: Full stack (Node/.NET/Go/Next.JS), Gen AI/ML (PyTorch/ONNX), distributed infra (e.g. AWS/GCP/Azure/On-prem) Resume/CV: https://1drv.ms/b/c/aae0b153e80e54d2/IQB2LREvdOgWQYanTlHOhHl...

Email: nick@night.ms

13 years of engineering leadership in FAANG; 20+ years of software engineering industry experience. Looking for Sr. EM / Director roles. Check out my open-source projects at https://www.github.com/nickna

*What makes it different:*

- Dual execution modes - interpret TypeScript directly OR compile to native .NET executables - Full C# interop - compile TypeScript to DLLs that C# projects can reference with full type safety

*What works today:*

- Core TypeScript: classes, interfaces, generics, async/await, decorators - Advanced types: union/intersection types, literal types, type guards - Compiles to verifiable .NET IL with performance comparable to hand-written C# - 80+ unit tests, supports most of TypeScript's feature set

*Why I built it:*

I wanted to understand how TypeScript really works under the hood, and I thought .NET developers might appreciate being able to run TypeScript without Node.js. The AOT compilation to .NET IL was a fun challenge - mapping TypeScript's structural type system to .NET's nominal types required some creative solutions.

*Current limitations:*

- No npm module support (yet) - Some advanced type system features are still in progress - Standard library is partial (see STATUS.md)

The repo has detailed architecture docs if you're curious about the implementation details. Would love feedback, especially from TypeScript or compiler folks!

Example usage: ``` # Install dotnet tool install -g SharpTS

# Interpret sharpts script.ts

# Compile to .NET sharpts --compile script.ts dotnet script.dll ```

Happy to answer questions!

Comments URL: https://news.ycombinator.com/item?id=46557698

Points: 6

# Comments: 1

If Microsoft had their way, I imagine they would require verification through their driver lab that does this for a living (https://learn.microsoft.com/en-us/windows-hardware/drivers/i...)

https://en.wikipedia.org/wiki/IMAX#Dome_and_Omnimax

Most YC founders seem to be new college graduates instead of seasoned FAANG folks. I'm in the latter camp and believe I'm better off leveraging my connections because I've aged out of YC.

In the olden days, getting a Regus desk required an office tour appointment, followed by paperwork. Now they have an app, and nobody needs to send or receive a PDF.

The original name for .NET was Next Generation Windows Service (NGWS), and before that it was Project 42.

And then the first .NET tutorial site we built was called GotDotNet.com. Engineers didn't get a say in the name.

Source: I was a SWE (SDE) in the .NET Framework team in 2000.

NGCB (Nev. Gaming Control Board) does regular on-site audits of the machines and the central configurations to ensure that they are compliant.

The root cause of the SDK fragmentation is because Microsoft sees diminishing returns for Windows.

After Silverlight failed to gain adoption, they started losing interest in the desktop. When Windows Phone was killed, there was even less interest in UWP.

It's a shame because .NET is quite nice.

I've had their gigabit fiber service in SF for the past two years. The few times I've had to call and inquire about a service issue, I was able to speak to someone within a minute of calling. And if you check their forums, you'll find their CEO responding to questions.