If so can you reccomend (link here) some of the resources which got you started?

FWIW there are blog posts from the same author of the Emacs setup: https://andreyor.st/tags/game1/

I use this for playing with Löve2D: https://sr.ht/~benthor/absolutely-minimal-love2d-fennel/

Can't say I made anything worth mentioning. There are some bigger templates available that I am sure do more useful things, but I prefer something small enough that I can see what is going on.

Worked fine even for getting things to run in LoveDOS, a port of some older Love2D version to MS-DOS. In practice compilation was a bit too slow for comfort, so a better way was to pre-compile the fennel-scripts to Lua and just run those.

I installed some LSP server for fennel that comes with optional built-in code completion for both Love2D and TIC-80. Works well in emacs.

Regarding execution, Elm is for client-side rendering, whilst this is for server-side rendering. As a language, they're very similar, one could even argue that Elm is a subset of Haskell :-)

As @theamk mentioned this visualization is based on Freebase Language Collection.

As a side-note on the matter I also couldn't find Swift, but was quite surprised that I found Elixir :)

I'm thinking that this is not as `black&white` as said.

There are accounts which actually are used by people/companies, they post authentic content but do some automated actions.

E.g. a company account which tweets authentic content for their field but on the other hand has automated retweets on certain hashtags in order to gain their authors as followers or to come up as related to other accounts in same field.

Also to mention that there are services such as IFTTT which actually can help you to automate such actions and make bot-like behavior.

I guess the same would apply to Instagram, Pinterest, Reddit, etc.

When I started learning Elixir/Phoenix this type of system was the first thing that came out of my mind when I was covering the Erlang/BEAM/OTP parts because of their nature.

If anyone else is interested in starting something similar in Elixir just ping me :)

But isn't channels the Phoenix abstraction (middleware) for websockets/sockets per se?

What I mean is why not write a sockets Phoenix channels transports adapter to be used instead of the default one & continue using the existing codebase? :)

Sorry! Reading my comment back, it's no wonder it was tough to follow.

Instead of writing: "I couldn't resist the fun of reimplementing it over sockets."

I should have wrote: "I couldn't resist building another version of Risk with Phoenix/channels/sockets because it should be mind-meltingly easier compared to all of the previous times I'd built it on other platforms"

I assume the OP is talking about reimplementing the channels client. Though now I'm not sure.

@AlaskaCasey is right. I'm a software engineer & my company is registered in my country. When I negotiate with clients I'm representing the gross amount & I deal with my taxes etc. in my country.

I just tried your link & it's a very interesting option to be honest :)

In my country (Macedonia) these reports on private held companies can be given after 2 fiscal years & you have to pay for them per company searched.

I'm very curious to see what's the case in other countries on this topic :)

Actually most western European countries have 'expat programs' for eastern European countries with job offerings mostly as babysitters/valets/waiters.

They're intended for young people & the stay is between 6 months & 2 years.

In that context 'expats' is used for temporal residence in foreign countries with no intentions to be made permanent. It's mostly intended for young people to travel around, not much for the financial benefit.

So in my understanding it's the intentions which define, not skin color / continents.

PS. The written above is a definition from my personal point of view :)

I was thinking about this a year ago & decided on Elixir. So far I have no regrets. As you mentioned Elixir satisfies all the conditions you mentioned. For the static typing part, I agree. But since there's no OOP, the flow of the information throughout the app is pretty explicit & the reasoning behind it is easy to be debugged.

There is static type checking/analysis available. Just use Dialyzer.

You're right. I've used it once as a part of an exercise in the "Programming Elixir" book and never again.

It should maybe come bundled with mix, as some other tools, that way it'll be more approachable.

Also there's a wrapper for it, which helps in the process.[0]

[0] - https://github.com/jeremyjh/dialyxir