#lobi — Public Fediverse posts

I've read the article with keen interest. Keep up the great work on curl @bagder

#curl #get #programming #technology #fetch #networking #https #http #ftp #OpenSource #POSIX #BSD #freeBSD #ghostBSD #openBSD #Linux #win64 #mac

🦋💙❤️💋#Lobi 💙💕🌹💐💙🦋

Spare these few minutes to read this long long toot about Large Language Models

I've been working with POSIX Operating Systems for many many decades. Seek my other posts for more information check my GitHub page where some of the stories have been entered.

A lot has been written and screamed about vibe coding. I'm going to give you a short and concise rundown.

Individual X cannot even write a hello world program in the BASIC programming language. This individual has played with a Large Language Model and knows that such a system can write that BASIC program for him.

He fires up the model and asks for a Hello World program in Commodore 64 BASIC

The model response with

10 PRINT "fa wakkà"
20 GOTO 10

Individual X cannot analyze the code. He doesn't know that the second line will loop the program to the first and thus will create an infinite loop on his C64 emulator. Individual X has never worked on a physical bare metal C64. He doesn't know how to stop the code

The large language model created the second line because many hits in his database have a Hello World program for the C64 written in exactly this manner. The large language model is like a parrot which talks. The model doesn't understand what it says the model has no notion of understanding just like the parrot.

Individual executes the code and cannot stop it because he doesn't know that control break exists for that on the C64

Thus his C64 is in an infinite loop and he doesn't know what to do.

Now I will go to that same large language model. I not only know how to solder the Program Logic Array 906114 on the C64 with a mandatory heat sink I also know how to write code in assembly and I know many ROM subroutines of the C64 by heart including

JSR $FFD2

A sub routine which prints a character on your video VIC chip.

When I see that the model puts line 20 I immediately delete that line because it's unnecessary.

Now extrapolate this on a full program, with 20000 lines of code, complete with libraries and API created by a large language model when the task is given by a vibe coder.

Since individual X cannot even analyze Commodore 64 basic code of a Hello World program, consisting of two lines where the second line is unnecessary, the person has no chance in hell to analyze the above given program

There are people walking around on this planet, who think that they will be able to write software, with a large language model, as their boss and think that that software will be usable in the field

When the 20,000 line program breaks, the API is totally unusable and the task for that program crashes the whole server on the bare metal, censored will hit the fan

I urge everyone who uses large language models for any subject, that they should be an absolute master of the subject, where they use the model as a low level assistant

Thank you for reading

#LLM #programming #damage #Slop #AI #illusion #skill #logic #coding #vibe #vibecoding #homosapiens #species #global #technology #Terra

🦋💙❤️💋#Lobi 💙💕🌹💐💙🦋

I've taken the time to read this IT notes Story where we are reminded to use Open Source Code in the diverse way it's intended

I can give you an example regarding the _if tools_
**ifconfig** is in my _muscle memory_ the things that I need executed from this program just fly out of my fingers in reflex mode
I've been using the if tools ever since we needed to _compile everything_ ourselves, when we wanted to run an Open Source Environment, where the kernel was written and delivered in source code only.
If this is the first toot you read by me, I've been with the Open Source community on the Linux side since the alpha versions were coded and distributed through Usenet, in comp.os.unix.*

In that period you were grateful when a task set that you needed to execute, had a program, which would either make your task easier or better manageable, than doing everything by hand in a laborious manner

Ever since the beginning there are different GNU programs, written in the Richard Stallman period, that can do similar things. All you need to do is choose what you like and stick with it
If you do not like the way it works, you can fork it & change the code, if you don't know how to write a line of code, there are _manual pages_ available which you can use as teaching methods to learn how to code yourself
All you need to be for that is an _autodidact_
You have the power of the **Source Code** readily available right in front of you

At a certain point in time _Bram Molenaar_ did not like the way VI worked; he want it more than vi offered. At this point in time Bram Molenaar programmed vim on the _Amiga_ computer. Since the true Open Source form was followed vim was also distributed in Source form and was happily adopted by others who were thinking in a similar manner as Bram Molenaar and they started to contribute to that program.
vi is a vital program on UNIX systems. What Bram has made, is create a _choice_ for people who want it more than what vi offered.

# vim & vi happily coexist!

## This is the beauty of Open Source

At a later point in time this is also what happened with the programmer who wanted more than what the if-tool set offers. Thus the command set of _ip_ was programmed. Similar to vi and vim they happily coexist.

### However on the distribution level something changed.

After a couple of decades I noticed that traditional tools, that have been tried, tested, stable and have withstood the test of time, were dropped from the base installations. You have to go and fetch them yourself. It was even done with _critical tools_ like the if tool set. It's not just one distribution that's doing it but different distributions.
I was busy with an installation; at a certain point I needed **ifconfig** to work on my network interface devices; I needed to configure something on the fly. Imagine my facial expression when I detected that ifconfig wasn't in the base installation!
The machine was in a _chicken egg_ situation because I had &no access to the network_ I had to stop, go to another place fetch the if tools separately, find out that they were dropped for reasons which were totally irrelevant to my work, go back to the machine, install them separately and in the process waste many valuable minutes of time.

It was then that I started to notice the pattern a pattern of **polarization** removing tools which are critical to base installations without leaving a warning

I had to _change_ my setup routine which has been working for decades in a _flawless_ manner, because someone somewhere decided that a good tool set became obsolete.

This polarization is not only in the choice of what commands are chosen to be in the base installation of a distribution, it's in many different sections of the open source community which is what Stefano has shed some light upon.

Polarization because of diversity is totally unnecessary, happy and peaceful coexistance is key

* You can love vim yet cherish vi
* You can glorify emacs yet admire vim
* I can love XCFE cherish LXDE, admire KDE & like GNOME all simultaneously

Depending up on what I'm doing, what machine I am working on (SBC server embedded system), what is needed on the task at hand, I simply adapt and work with the diverse tools available for free.

There is absolutely now need for polarisation or Toxic behavior in the Open Source ENV:

Another example is the direction that Gnome went many years ago.

In that period I used Enlightenment, Gnome, KDE and FVWM simultaneously on different machines. All WM are working in a manner that I like. When however the Gnome programmers decided to strip configuration features of the Desktop Environment, I didn't go on a rant, I didn't bother to fork, because of the massive amount of work involved.

I just left in Peace

Diversity is Vital. GNOME is Vital! We need them all

🦋💙#Lobi 💙🦋

#Story #Stefano #Programming #FVWM #LXDE #OpenSource #BSD #freeBSD #Linux #POST #X86 #technology #SBC

https://my-notes.dragas.net/2025/11/14/this-isnt-a-battle/

@PE0ALX

24 Hz to 18 kHz are correct ranges for vinyl, you're absolutely correct with the frequency interval you've cited.

The theoretical 14 Hz to 22 kHz can seldomly be reached due to rumble of the turn table motor and the direct drive lower harmonics interferences going through the tone arm. At the upper side of the spectrum vinyl quality, dust scratches and other factors, dampen audio reproduction. Of course wow and flutter also degrades LP frequency response in both directions just as 1/4 mastering tapes

The 96 kHz I was referring to is the digitized version that I've made of this masterpiece, which I also have in my Music Library.

Playing Kraftwerk Autobahn on vinyl triggers feelings of days long past, when PA Amps needed warming up to sound perfect.

Thank you 💕 for your reaction

🦋💙#Lobi 💙🦋

#Vinyl #records #frequency #response #WoW #flutter #rumble #noise #cartridge #moving #magnet #moving #coil

When I rode to my house yesterday in the afternoon I felt the energy in the street was not right

That was when I was 20 minutes out

At three 🕞 minutes distance I was absolutely certain that a lot was wrong, and I wasn't surprised when I saw the fire trucks close to the houses 🏠 in between the tax office and the brick street.

A massive fire 🔥 which started in an abandoned building {which burned to the ground} hit an apartment building with about 16 units, then raged through a wooden house where an acquaintance of mine lives, levelling that house in minutes. While the fire 🔥 was burning the wooden one story house was also charring the house beside it.

The fire department had experience with a massive fire in my street more than a decade ago, came with everything {twelve trucks including tankers} and they came fast.
Everyone who was living in the apartment building evacuated safely. A woman ♀️ who I know well confirmed that fact.
However my acquaintance was already intoxicated by the fumes and refused to leave the house thinking that the rescue team from the fire department were robbers!
He was standing with a shotgun ready, didn't point it at them, but refused to leave.
The rescue team was forced to leave him behind and he fell unconscious. When they heard the thump of his corpus hitting the wooden floor, they grabbed him and rushed him to hospital, where he succumbed to the smoke inhalation.

So the abandoned building ignited the apartment building which ignited the wooden house which charred the building beside it. In total three buildings burned, two charred and One person suffocated in the ER. The fire was under control within a very reasonable time, given the fact that my fire department does not have the equipment they need to get every year.

My sincerest Thanks goes to the fire rescue team, because without them the whole block would have burned down...

🌺💜🎼 🎶 🎸 #Lobi ✨ 💖💕🌹💐💖 💙💜💖🦋

#FireDepartment #FireTrucks #HouseFire #H2O #O2 #LossOfLive