A01375332 Compiler Design Blog

  Web Assembly looks like a really powerful tool for web development once it is completed and all of the features are out there. I really liked that at the end Lin gave the advice to not use it for application development just yet, it felt like honest, and it is important to recognize the present capabilities of your software. Although the blog is from 2018, so I am not sure how much has Web Assembly improved in these 3 years since.   Looking at the Web Assembly Concepts page that we had to read for the quiz it still says that it still can’t directly access the DOM so I will suppose that it is still not ready for applications. Programming this kind of compiler with efficiency being such a large focus can’t be easy. Probably Web Assembly would have been a nice tool to learn in the Graphics course as right now we are using libraries of JavaScript to do our projects and the teacher gave us a warning of being mindful of which models we use as they may cause performance issues. Some of us

I did not know that this course project had different versions, the web based version sounds interesting such as I would consider web development one of my weak points so it would help to strengthen it and have a deeper understanding of web development, but at the same time is one of my weak points so the course would have probably been harder. The advantage of the C# version of the project is that C# in the compiler faces we have done is really similar to other object-oriented languages we have used, so it is not really hard to adapt to it. Although at the moment we haven’t had the need to use some of the more advanced things we read about in the book. Something that really piqued my interest, and I would really like to learn is to set up a web server as it sounds like something important, but in previous courses was skimmed over and only seen really briefly or replaced by AWS buckets. Also, I did not expect to read about the changes that this undergraduate program has gone throug

  I would not consider the Clojure interpreter implement with Clojure that we saw during the Programming Languages courses as ‘cheating’, but certainly the SIF interpreter does look like a more interesting example. Just that S-expressions make me remember Clojure and I tried to like it, but I could not. While reading the article I became more impressed of Ruby as a programming language as it has some really interesting features such as the code blocks that I would like to learn better because I do not understand them completely, that every class even the base classes of the language can be easily modified, or that you can modify classes mid program although that one I am not sure in which situation would be used. Overall, I am enjoying Ruby a lot more than Clojure. The exercise sounds like a good way of improving object-oriented programming while better understanding interpreters and the particularities of Ruby, although the choice of Ruby as the programming language seems kind of we