ingenieroariel

Letoram: "In this post I will lay out the ongoing work on detaching from a terminally online life, and how the project will be maintained once the fabled 1.0 release hits. This is still ongoing, and not something I would dare to suggest that you consider for your own projects."

With Apple devices you get very fast predictions once it gets going but it is inferior to nvidia precisely during prefetch (processing prompt/context) before it really gets going.

For our code assistant use cases the local inference on Macs will tend to favor workflows where there is a lot of generation and little reading and this is the opposite of how many of use use Claude Code.

Source: I started getting Mac Studios with max ram as soon as the first llama model was released.

The scipy/numpy to matlab is a good example. In my opinion it is on its way but in many places the timing is more like 2010-2013 where a lot of people knew python was the future but universities still used only Matlab.

I think the answer depends on the country: In places where the government uses QGIS it is like Blender. In places where ESRI has a stronghold it is like LibreOffice.

It is a gui framework that allows you create terminals where you can detach any running process into another terminal.

Since it is a complete toolkit, you can have detachable applications where you send both code and state to a server and retrieve it from another device (like Apple's continuity).

In the end it is just a bunch of lua scripts talking to other components via /dev/shm and to other computers using a new protocol called a12://