• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: August 4th, 2023

help-circle
  • No, Ollama is running on an old PC with a GeForce 1060 and 16gig of ram…

    Yes, it’s a “webserver” running in the background exposing an API.

    However, if I “top” my system, without chatting, it sits at 0% usage; it’s only when asking that the system peeks at around 55-70% CPU.

    You have to understand there is 2 things here: the server and the model. The server is always running, but requires next to nothing in terms of resources.

    The model is what computing your questions, this is the heavy part. It’s started on use, then after a delay, it’s closing.

    TL;DR To answer your real question, you could use Ollama on the same system that you are using.


  • During that time, you can easily install Ollama on an old computer.

    With a client like Oatmeal, you can save your session/ reload/delete as you wish; so your model remembers what you want.

    I am running llama3.1:8b, it’s good enough for the day-to-day operations.

    • Need for a spyware: 0
    • Need to take screenshots of my desktop: 0
    • Need to buy another computer for the hype chipset: 0
    • Need of Microsoft bullshit: 0

    My old computer is apparently “not good enough” for windows 11, but it’s surely good enough for my personal AI running on Linux though!









    • Zig uses allocators, which will inform you if you are leaking memory.
    • Zig comes with defer/errdefer to simplify the resource cleanup (and for ergonomics).
    • Zig comes with Optionals to manage nulls.
    • Zig comes with slices (ptr + size) to manage all the bound-checking.
    • Zig automatically check for overflow/underflow arithmetic.
    • Zig will check for pointer alignments when casting between pointer types.

    => Zig is designed to make you do it right easily, and very hard to do it wrong.

    In other words, Zig will let you be, but warn you when you are doing something wrong, where Rust is like Karen who is always screaming at you for every word you are typing.

    To summarize, you really need to /want/ to fuck up to fail your memory management… If after all that you still can’t manage your memory, it might be better for you to look for another carer.

    Something is sure thou, Zig is very safe - just as it’s safe to cut my veggies with a knife. I might cut a finger and bleed a little bit, but I will not use plastic knife “because it’s safer”.

    Moreover; You are talking like if Rust is safe, all the time, which is not true in reality:

    52.5% of the popular crates have unsafe code. Therefore, in an average real-world Rust project, you can expect a significant number of the dependent crates to have unsafe code – Source

    Basically, you’re comparing a hypothetical world where Rust is always safe to a superficial glance at Zig’s capabilities to claim a “winner” here.

    And for the String library… Are you fucking serious? Do you want to compare the Zig’s Std library versus the famously tiny Rust Std library? Really?


  • Rust in Linux lead retires

    “I was expecting [Rust] updates to be faster, but part of the problem is that old-time kernel developers are used to C and don’t know Rust,” Torvalds said. “They’re not exactly excited about having to learn a new language that is, in some respects, very different. So there’s been some pushback on Rust.” Torvalds added, however, that “another reason has been the Rust infrastructure itself has not been super stable.” – Source [24-09-03]

    I’m not sure that’s something to be crowing about, mate…



  • C wasn’t my first language, but I learnt the most whilst learning C…

    People are talking about footguns and what not security related issues. I agree it’s easy to write bad C code, but if you want to learn what’s going on, learn C.

    Today I know a dozen of programming languages and C has always been in a special place in my heart. I am using Zig for my personal projects at the moment. It’s similar to C, without the pitfalls, and my C knowledge still helped me to learn that language.

    Learning C is a service you are doing to yourself for the rest of your life.




  • My personal experience is most people who are using git with a GUI are the same people who are asking my help to git-fu their git-problems…

    Most GUIs only offer a subset of the git functionalities and hide what’s really going on by obscuring gitshell with “their workflow”.

    In all cases, use what you like; some people like the shell. Cheatsheets are normally only for learning purposes and usually don’t stick for long, it’s not an end game thing…