José Valim – The foundations of the Elixir type system

https://www.youtube.com/watch?v=giYbq4HmfGA

Discussions: https://discu.eu/q/https://www.youtube.com/watch?v=giYbq4HmfGA

#elixir #programming

We passed the €30,000 threshold on the Godot Development Fund today! 🎉

Thanks everyone for your support! 💙

Our current goal is to reach 50k as soon as possible, to secure the current payroll, and enable us to add a couple more developers to the team.

https://fund.godotengine.org/

I will be at #FOSDEM this weekend.

If you can find me there you will receive minidisc.tokyo or cdrom.tokyo stickers.

Open-source hardware smartwatch based on @NordicTweets nRF52833 (and soon nRF5340) and running @ZephyrIoT RTOS. #wearables #oshw #opensource
https://www.cnx-software.com/2023/01/21/zswatch-open-source-hardware-nrf52833-smartwatch-runs-zephyr-rtos/

Original tweet : https://twitter.com/cnxsoft/status/1616659795112775681

Crazy how no other language I know of other than #Ada use a second stack to return “indefinite objects” (arrays without a statically known size, etc.). In the whole body of Ada code I've seen, it easily removes 60–70% of cases where you'd normally dynamically allocate. It has all the benefits of the stack where everything is nicely scoped, and it even works on real-time and/or embedded systems!

In most Ada code the only reason you'd need to do dynamic allocation is if you need a data structure that contains indefinite objects (e.g. an array of strings) or you're interfacing with some C API. And in the former case there's a good variety of data structures in the stdlib that abstract away the fact they allocate stuff so you don't even have to worry about it then.

Computers used to scream out in pain when we connected them to the Internet.

This was a clue and we just didn't listen.