Deschide articolul original într-un tab nou Schimbarea acestei opțiuni se aplică imediat și reîncarcă pagina.
LECTURA
Înapoi la articole →

Around IT in 256 seconds

nurkiewicz.com/feeds/posts/default
Vizitează site-ul

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 10

  1. Your First Virtual Machine: Write yourself a compiler, Part IV

    (Around IT in 256 seconds)

    In the previous article, we emitted an intermediate representation (IR) for our programming language that is easier to process than source code.

  2. Compiling to intermediate representation: Write yourself a compiler, Part III

    (Around IT in 256 seconds)

    It’s time to dive a bit deeper and abandon the naive realm of interpreters.

  3. mastodon.social Archive

    (Around IT in 256 seconds)

    This entire page was generated using a script that can be found here: github.com/nurkiewicz/nurkiewicz.com/tree/master/src/mastodon-import.

  4. Arithmetic interpreter: Write yourself a compiler, Part II

    (Around IT in 256 seconds)

    In the previous article, we created the most naive interpreter, which can basically execute number + number expressions.

  5. The simplest interpreter: Write yourself a compiler, Part I

    (Around IT in 256 seconds)

    I’ve always felt that writing a compiler is the most romantic software engineering task.

  6. Rewriting my 2005 C++/OpenGL game in Go

    (Around IT in 256 seconds)

    Twenty years ago I wrote CuTe - a 3D Tetris clone in C++.

  7. OpenTelemetry glossary: 30 terms you should know

    (Around IT in 256 seconds)

    If you’ve ever stared at a Grafana dashboard pretending to understand what’s going on - this post is for you.

  8. Podcast everything: how to turn any content into podcast feed

    (Around IT in 256 seconds)

    I’ve been listening to podcasts for more than a decade.

  9. Best places to commute from in Warsaw: public transit heatmap

    (Around IT in 256 seconds)

    Location, location, location!

  10. Is ‘return await’ redundant or necessary in JavaScript?

    (Around IT in 256 seconds)

    In JavaScript, should we await on a returned promise or not?