goapp VS vilmos

2022 update. At the time of writing this update, it's been over a year since I published this article. At the end of this article I promise a part two, which I must admit, will probably never come for a couple of reasons. I no longer use this structure (I still think this article gives people some help to get going, but would like to update it at one point. I suggest you checkout this repo. Secondly, in regards to integration testing, I've just relased a full-length article about it which you can find here.

I wrote this article a year ago and there is much I would change about it today. I still post it because I think there are something to be learned from this, at least to get a end 2 end description of one way to structure Go applications. There are many other options, and today I would suggest that you check out this repository.

Also regarding how you organise the code you could check out https://github.com/bnkamalesh/goapp

I've been using https://github.com/bnkamalesh/webgo for all my projects. Also, I follow https://github.com/bnkamalesh/goapp to organize code

https://awesome-go.com is a good place for aggregated resources. Also regarding code organization, I've done something, which l follow till date, https://github.com/bnkamalesh/goapp

I've been using this for a while now, (Goapp)[https://github.com/bnkamalesh/goapp]

I've been using goapp for a long while now

in which case, you might like this one

vilmos is a stack-based programming language written by me based on colors and images instead of code, so you can basically write a programs just by drawing a picture. What I linked in the post above is the interpreter that makes runnable images written following vilmos language specs. In vilmos, each pixel of the given image rapresents a single instruction (for example: push to the stack, print from the stack, duplicate the top of the stack, and so on..), so what the interpreter does is reading the given image pixels and compare their RGB values with the operations RGB values specified in the documentation. But you can define also custom color codes to override the standard ones!

I report here vilmos language specification. Feel free to collaborate to the project, suggest changes and updates, and fix unexpected behaviours. I hope you will enjoy it!

Thank you! It is an interpreter for a language written by me based on colors and pictures instead of coding. You can see language specifications here Do you think I have to change something on the Readme to make it more clear? And if it's a positive answer, then what would you suggest?

Very clever observation! :D Actually, it refers to the Hungarian name. As mentioned in the language specification, in LANGUAGE.md file of the repository, the language name comes from the Hungarian painter Vilmos Huszár because of his paintings involving blocky shapes, just like the pixels needed to program in vilmos.