• 0 Posts
  • 94 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle




  • Hard disagree on them being the same thing. LLMs are an entirely different beast from traditional machine learning models. The architecture and logic are worlds apart.

    Machine Learning models are "just"statistics. Powerful, yes. And with tons of useful applications, but really just statistics, generally using just 1 to 10 variables in useful models to predict a handful of other variables.

    LLMs are an entirely different thing, built using word vector matrices with hundreds or even thousands of variables, which are then fed into dozens or hundreds of layers of algorithms that each modify the matrix slightly, adding context and nudging the word vectors towards new outcomes.

    Think of it like this: a word is given a massive chain of numbers to represent both the word and the “thoughts” associated with it, like the subject, tense, location, etc. This let’s the model do math like: Budapest + Rome = Constantinople.

    The only thing they share in common is that the computer gives you new insights.


  • You’re talking about two very different technologies though, but both are confusingly called “AI” by overzealous marketing departments. The basic language recognition and regressive model algorithms they ship today are “Machine Learning”, and fairly simple machine learning at that. This is generally the kind of thing we’re running on simple CPUs in realtime, so long as the model is optimized and pre-trained. What we’re talking about here is a Large Language Model, a form of neural network, the kind of thing that generally brings datacenter GPUs to their knees and generally has hundreds of parameters being processed by tens of thousands of worker neurons in hundreds of sequential layers.

    It sounds like they’ve managed to simplify the network’s complexity and have done some tricks with caching while still keeping fair performance and accuracy. Not earth shaking, but a good trick.



    • actually Nvidia largely does support wayland now

    • it’s on those applications to support wayland, not the other way around. X certainly wasn’t developed to support upstream.

    • adopted an extensible standard, regardless of how it makes you feel.

    • more secure and resilient to a variety of attacks, including keyloggers. Yes very bad.

    • how about the fact that nearly all X developers founded and are now supporting Wayland, and X hasn’t had meaningful development aside from break/fix patching for over a decade?

    • you probably shouldn’t.