Microsoft chose Go instead of C# or Rust to rewrite TypeScript

Clouudy Swergers123 at gmail.com
Sun Oct 5 22:41:36 UTC 2025


On Sunday, 5 October 2025 at 03:51:54 UTC, Kapendev wrote:
> On Wednesday, 1 October 2025 at 23:49:12 UTC, Clouudy wrote:
>> This is one of my bigger gripes about the way the DLF handles 
>> things. What's the point of things like a borrow checker, 
>> fancy DFAs for move semantics, or Phobos v3, if the language 
>> doesn't even have a debugger for every platform that is able 
>> to properly display its native types?
>
> DLF this, DLF that... It's getting kinda tiring lol.
>
> We already have debuggers, so not sure what the issue is. If 
> they are "bad" at showing information, then that's a debugger 
> problem. The RAD Debugger might be nice, though I haven't tried 
> it myself.

One of the nice things about a good debugger is that you can view 
everything as it is at runtime; it's much easier to understand 
certain variables and data structures if you can actually look 
inside them at the time of execution instead of relying on stuff 
like print statements or your own expectations/knowledge of the 
code base.

I've tried to find any possible debugger that could solve this 
problem, including the RAD Debugger, but none of them could do 
everything I needed. And AFAIK there already were complaints 
about debugging in DMD, to the point that they're even on the 
GitHub for the compiler IIRC.

I think that a lot of the complaints about no visual progress 
being made on tooling or the language in general could be solved 
by a roadmap or some way to direct the community towards making 
their own contributions towards a specific goal, and then 
choosing a new goal after that one's been completed. Anything 
that makes the experience more streamlined would help, tbh.


More information about the Digitalmars-d-learn mailing list