What this is is there's one compiler here that supports these two different language modes.

这意味着有一个编译程序能够支持这两种同的语言模型。

To deal with different underlying hardware, each computing architecture needed its own COBOL compiler.

为处理同的底层硬件，每种计算架都需要自己的COBOL编译器。

It's not writing the compiler from scratch.

这是从头开始编写编译器。

We don't have to build our own compiler anymore.

我需要自己建编译器。

So yeah, he's, he's, you know, He's a, he's a compiler.

所没错，他是个，你知道，他是个编译器。

He has a eureka moment and remembers the compiler.

他灵光一闪，想起编译器。

And it's actually hard to, you can, it's easy to write a compiler and then have it be spaghetti code.

实际上很难做到，你可很容易地编写一个编译器，然后让它变成一团乱麻的代码。

They said anybody who can write, who can translate Fortran into the language of their machines is allowed to make Fortran compilers too.

他说，任何会编写程序、能把Fortran翻译成他机器语言的人，也被允许制作Fortran编译器。

In fact, a lot of times I'd say, yeah, it's super easy to write a compiler if you're not writing the parser nor the code generator.

事实上，很多时候我说，是的，如果你需要编写解析器和代码生成器的话， 写一个编译器超级简单。

So we had the very first CUDAJIT and the very first ATJIT compiler that in 2012 for 13, you could run not just a Vuefunk on CPU, but a Vuefunk on GPUs.

所我有首个CUDAJIT和首个ATJIT编译器， 在2012到2013年间， 你仅可将Vuefunk运行在CPU上，还可将其运行在GPU上。

If you go through the currently Remix docs, there are a lot of notes here and there about how something is not supported in the classic Remix compiler, but is now supported in the Remix Vite build engine.

如果你查看当前的Remix文档，会发现在很多地方都有注释说明某些功能在经典的Remix编译器中被支持，但在新的Remix Vite建引擎中已经被支持。