peter madsen-mygdal

Agreed that some streamlining is needed.. Believe avm_builtins/i2c_driver.c and avm_builtins/i2c_resource.c are direct drivers, port/nif with pro/cons, which is fine, though only having one, would be simpler. Additionally there is i2c_bus...

Let's back out mix.lock here - I also believe this change bumps the minimum elixir version in mix.exs?

Backing out mix.lock here is only to avoid conflict with how it's part of #41 - in a different shape.

I'm more inclined towards deleting file(and folder) or commenting out `import (Mix.)Config` line, effectively leaving the entire file commented out - as it not used, and probably shall never be...

Looking good, I would back out the readme changes - pending other PR, or wait for it to land and rebase.. And then just the minor nitpicks.. Thanks!

Let's back out mix.lock and it should be good to go. Adding it at this stage only creates issues, and solves none. (eg is this mix.lock valid on elixir 1.X),...

great work @joustava - thank you, and apologies for things not being straightforward...

uf2tool is there because it's a dep. Believe "Mix is not part of the runtime env", which is also why we have that deprecation/migration Mix.Config->Config afaik, so they should not...

these all currently works: ```elixir ExAtomVM.hello() |> IO.inspect() ExAtomVM.PackBEAM.module_info() |> IO.inspect() Mix.Tasks.Atomvm.Check.module_info() |> IO.inspect() ``` My current thought is install instructions should include `runtime: false` eg: `{:exatomvm, git: "https://github.com/atomvm/ExAtomVM/", runtime:...

We should make sure to get both sites up, and keep them in sync (served from same place). Then search engines will pick up the change in `` etc. just...