In a nutshell: put two different frames in sequence, and you have an animation.
21 karma · joined July 20, 2023
In a nutshell: put two different frames in sequence, and you have an animation.
> When a tool blurs the line between who performed the task
Who saws the wood? He who operates the tool, or the tool performing its function? What is the value of agency in a business that, supposedly, sells product? Code authorship isn't like writing, is it? Should it be?
Or is the distinction not in the product, but in the practice? Is the difference in woodworking vs lumber processing?
Or is it about expectation? e.g. when we no longer expect a product to be made by hand due to strong automation in the industry, we prepend terms such as "hand-made" or "artisanal". Are we currently still in the expectation phase of "software is written by hand"?
I have no dog in this race, really. I like writing software, and I like exploring technology. But I'm very confused and have a lot of questions that I have trouble answering. Your comment resonated though, and I'm still curious about how to interpret it all.
> The top-end Ryzen AI Max+ 395 configuration with 128GB of memory starts at just $1999 USD. This is excellent for gaming, but it is a truly wild value proposition for AI workloads. Local AI inference has been heavily restricted to date by the limited memory capacity and high prices of consumer and workstation graphics cards. With Framework Desktop, you can run giant, capable models like Llama 3.3 70B Q6 at real-time conversational speed right on your desk. With USB4 and 5Gbit Ethernet networking, you can connect multiple systems or Mainboards to run even larger models like the full DeepSeek R1 671B.
I'm futsing around with setups, but adding up the specs would give 384GB of VRAM and 512GB total memory, at a cost of about $10,000-$12,000. This is all highly dubious napkin math, and I hope to see more experimentation in this space.
There's of course the moving target of cloud costs and performance, so analysing break-even time is even more precarious. So if this sort of setup would work, its cost-effectiveness is a mystery to me.
[0] https://frame.work/be/en/blog/introducing-the-framework-desk...
From my experience, achieving provider independence boils down to: own your stack, work offline-first, test failure modes constantly.
Been trying to get a setup going with NixOS + local AI + custom CLI tools for development work, and I never would have thought to pursue this sort of thing if I hadn't found these people. Great stuff!
Oh and ORCA is a LOT of fun! Give it a shot if you're into sounddesign, or generative electronic music stuff: https://100r.co/site/orca.html
No good deed left unpunished.
That friction has always been there, in my experience. But this is the first time I'm seeing it happening around me. LLM's are so divisive, and yet the more extreme positions on either side seem to be digging their heels in, as if the tech is not in flux.
Maybe we need a little Cave Johnson energy: https://www.youtube.com/watch?v=Dt6iTwVIiMM
This looks much more thought out, thanks for sharing!
It would likely quickly devolve into typical editor config bikeshedding, only AI powered? At least for me, maybe someone smarter could streamline it enough to be useful though!
Even just keeping their views in mind as I'm learning and experimenting, I'm noticing there's so much cloud-dependence without good reason, beyond "convience"? Really glad to have discovered their work early in my career, it's been nothing but quality learning!
I don't want to be bound to the "modern world" and its city centers. I want to see the rest of it too, to stray from the fire of a broadcast tower without being left in the cold. I have a torch, I just need to light it.
I'm in the process of learning how to work with AI, and I've been homebrewing something similar with local semantic search for technical content (embedding models via Ollama, ChromaDB for indexing). I'm currently stuck at the step of making unstructured knowledge queryable, so these docs will come in handy for sure. Thanks again!