Yet Another ScreenA History of Grave Visions and Relevant Ascension Lecture
The group of Bird People students gathers before a respected professor to learn the harsh truth.
Yet Another ScreenWorldEdit for Minecraft 1.21.1
How to WorldEdit - Basics
Yet Another ScreenLlama 3 405B Explains Julia - 01
The first Julia lesson from Llama 3.1 405B
Yet Another ScreenA History of Grave Visions and Relevant Ascension Lecture
The group of Bird People students gathers before a respected professor to learn the harsh truth.
Yet Another ScreenWorldEdit for Minecraft 1.21.1
How to WorldEdit - Basics
Yet Another ScreenLlama 3 405B Explains Julia - 01
The first Julia lesson from Llama 3.1 405B
Subscribe to Yet Another Screen
Subscribe to Yet Another Screen
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
Well, well, well. Julia's a deep subject. For one thing, having just spent months trying to convince different versions of PIP to work nicely with my OS; By which I mean, "Watching Ubuntu's package manager fight Python's package manager", I must say the fluidity of the package system and the version consistency being sane is a huge relief. I am sure there's many areas in which my misguided eyes were solely to blame for my Python frustrations, but the obvious disambiguation with regards to Julia is still more attractive from the perspective of learning fresh.
I've decided to take a new tack in learning Julia. I'm going to assume, from the start, that all tutorials are inherently flawed and must be generated by the most recent AI model, then tested, then organized in a humanly sane manner in order to be trusted or helpful. As this is my new premise, I shall be sharing all of my learning on this platform, where you may find all of my future work. This shall be the log, the data dump, and the source of truth for each of my experiments once proven even slightly salvageable. I hope this helps someone eventually, and may we all enjoy the journey.
Unfortunately, the second I discover the perfect platform, I find that Julia does not have built in syntax highlighting for Julia... </3...
As such, I shall be embedding Github Gists for all future source code. They look nicer than any website's built-in syntax anyway though, not due to platform laziness but due to Github's sole purpose as the world's code super-highway Long Live FOSS!!!
Which brings me to licensing. All tutorials of mine are MIT license, as I feel copyleft is currently unfeasible for many companies due to the fact that we ( Software Engineers ) have used, "Proprietary, Compiled/Obfuscated Software", to cover, "Lazy, Insecure Software", for decades.
I'm also doing something that people may find odd. I'm intentionally marking all of my official posts and content as MIT License as well, because I really, really just wish to contribute my feeble ideas to the pool of human ideals and content. If anything I do serves to further even 1 other human in the progress of the species, I have succeeded in my goals. Talk to you all later.
-<3
Julia - Some Notes. GitHub Gist: instantly share code, notes, and snippets.
Well, well, well. Julia's a deep subject. For one thing, having just spent months trying to convince different versions of PIP to work nicely with my OS; By which I mean, "Watching Ubuntu's package manager fight Python's package manager", I must say the fluidity of the package system and the version consistency being sane is a huge relief. I am sure there's many areas in which my misguided eyes were solely to blame for my Python frustrations, but the obvious disambiguation with regards to Julia is still more attractive from the perspective of learning fresh.
I've decided to take a new tack in learning Julia. I'm going to assume, from the start, that all tutorials are inherently flawed and must be generated by the most recent AI model, then tested, then organized in a humanly sane manner in order to be trusted or helpful. As this is my new premise, I shall be sharing all of my learning on this platform, where you may find all of my future work. This shall be the log, the data dump, and the source of truth for each of my experiments once proven even slightly salvageable. I hope this helps someone eventually, and may we all enjoy the journey.
Unfortunately, the second I discover the perfect platform, I find that Julia does not have built in syntax highlighting for Julia... </3...
As such, I shall be embedding Github Gists for all future source code. They look nicer than any website's built-in syntax anyway though, not due to platform laziness but due to Github's sole purpose as the world's code super-highway Long Live FOSS!!!
Which brings me to licensing. All tutorials of mine are MIT license, as I feel copyleft is currently unfeasible for many companies due to the fact that we ( Software Engineers ) have used, "Proprietary, Compiled/Obfuscated Software", to cover, "Lazy, Insecure Software", for decades.
I'm also doing something that people may find odd. I'm intentionally marking all of my official posts and content as MIT License as well, because I really, really just wish to contribute my feeble ideas to the pool of human ideals and content. If anything I do serves to further even 1 other human in the progress of the species, I have succeeded in my goals. Talk to you all later.
-<3
Julia - Some Notes. GitHub Gist: instantly share code, notes, and snippets.
No activity yet