=== ANCHOR POEM ===
╔══════════════════════════════════════════════────────────────────────────────────┐
║ wish there were ascii characters that took up more than one line of code │
║ vertically. │
║ │
║ wonder if we could use a sorting algorithm, or markup language, or something │
║ like that to organize less structured data along user-customizable rules. │
║ Like, a code editor that worked with your ideas, rather than the strict │
║ expression of your text. You could pretty much write in any language, even │
║ pseudocode, and the LLM behind the scenes would translate whatever you wrote │
║ into whatever result you needed. Writing Rust, but need to fit in with C code? │
║ No worries it'll translate for you. As long as the end result is functionally │
║ the same, which could be verified by running two separate VMs that ran │
║ interpreters every time you saved. And as long as their translation layers │
║ matched completely, then odds are they're the same. And if not, well, the │
║ programmer can always debug it. It's not like this would be running on │
║ something that needed to perform in the moment? Like, improv instead of │
║ tragedies, or battles instead of strategies │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧═══════════════════════════════════─────────────────────────┴──────────┘
=== SIMILARITY RANKED ===
--- #1 fediverse/5765 ---
╔═══════════════════════════════════════════════════════════════════════───────────┐
║ Lua is the most fun language to write code in! The reason is because it's so │
║ simple, it distills programming down to it's basics, and there's very few │
║ surprises. Plus, you can use it like a bash script, meaning it's great for │
║ writing little utilities. │
║ │
║ why are we so attached to monolithic massive programs without shared memory? │
║ we could just write to the hard drive by file.io'ing a file and opening it │
║ later in a different program. What's the deal with databases, whatever │
║ happened to just loading things into a datastructure? │
║ │
║ oh, is your filesize too massive? what if we redundancied and abstracted and │
║ concentrically inter-co-acted and thus our familiar forces are defined. │
║ │
║ who are your true foes, in [checks notes] computer programming? um, probably │
║ complexity, probably logical incongruities, probably │
║ future-technical-debt-style incomprehensibilities, probably stuff that doesn't │
║ really have anything to do with the hardware but instead is mostly software. │
║ │
║ essentially, organization, but done on a whim. │
║ │
║ "but $?" │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧════════════════════════════════════════════════════════════┴──────────┘
--- #2 fediverse/4596 ---
═════════════════════════════════════════════════════════════──────────────────────
@user-1707
hey, I'm working on a project. Might need some python, I tend to prefer Lua
but it's pretty similar. It uses fediverse software and cheap hardware, think
raspberry pi's except risc-v
also it might use distributed local LLMs not to generate text, that's garbo
and lame and stupid. Instead it uses them to transform text, maybe even
translate text, into a more summarized form. Intentionally losing data, like a
jpeg compression but for text.
Might need some python for that. To glue it all together. The "distributed"
part is a whitelist, so we'd need to write that too. Various small little
utilities like that for connectivity.
oh also there's a one-way ethernet cable that connects two of the boards so
we'd need to store some information (easy) and send some UDP packets (hard)
anyway it's pretty neat, lmk if you want my contact details and I can tell you
about it. I might even be able to pay you.
(everything open source, no telemetry, no backdoors, everything private is
encrypted, etc etc)
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════════════════─────────────────────┘
--- #3 fediverse/928 ---
═══════════════════════════════════════════════────────────────────────────────────
@user-226
especially if you teach them how to use the terminal.
the amount of problems I could solve increased exponentially once I learned
basic python and BASH.
I love using "tldr", which is a summarizer for man pages. You can use it to
store custom notes (and import some from the community) which show you how to
complete common tasks. It's so nice when you can see the options laid out in
use right there for you whenever you type "tldr " - I personally use
"tealdeer" which is a tldr browser written in Rust. It's pretty nice because
you can write a note for yourself every time you solve a particular problem,
and then if you ever need to do it again it's there for you, easy to access.
of course, if your problem isn't listed, that's okay. That's what the man
pages are for. As long as you teach them how to search with \/ they can find
anything. Especially the \/-f[space] trick, to search for the -f flag for
example.
some organizers won't need the terminal, some will. if they pay attention,
great!
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘
--- #4 fediverse/2124 ---
╔═════════════════════════════════════════════════════─────────────────────────────┐
║ seriously, just google docs mixed with WC3 editor. │
║ │
║ boom, infinite storytelling device. As long as you were good with it, which │
║ was something that a CHILD could learn in like 3-6 months. │
║ │
║ Seems like it could be an ENTIRELY NEW SKILL that people could play with. │
║ │
║ But no, we learn excel and word in class at middle school. │
║ │
║ boring. │
║ │
║ I'd rather learn Bash or terminal customization or memory hierarchy │
║ organization. │
║ │
║ Yeah I mean that's cool but dude have you heard of multithreading? It's so │
║ cool, you can run like 500 different thoughts at once. It's amazing. │
║ │
║ ... I dunno, but I'm sure there's times when you'd want to use it. Like, │
║ processing a lot of data little-by-little. │
║ │
║ like, what if you had a camera feed of EVERY social media perspective AT ALL │
║ TIMES. Like, an instance admin streaming your inputted text to their databanks │
║ that they can project onto an LLM which interprets and identifies mis-aligned │
║ or altered direction units and mark them as "flagged", whatever that means, │
║ for their future the algorithm doesn' │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧══════════════════════════════════════════──────────────────┴──────────┘
--- #5 fediverse/5405 ---
══════════════════════════════════════════════════════════════════════─────────────
can't stop thinking about a visual programming editor that can be interacted
with in the same way that people are used to (think chromebooks dragging and
dropping icons in a web UI) but produces a text-file full of code and all the
required compilation scripts for any language the user requires...
seriously, programming is not THAT different between the different languages.
especially the main ones. they're all essentially variables and function calls
at the end of the day, so why not abstract away all the extra details and
build something that n00bz can actually use to build things.
I technically could make this but I don't have the bandwidth and I don't think
it's important really? who can say, the tools tend to co-create the solutions
in my experience.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════────────────┘
--- #6 fediverse/5291 ---
═════════════════════════════════════════════════════════════════════──────────────
the most important skill I can think of for a linux software engineer is the
ability to connect multiple systems together and turn windows and macintosh
devices into Linux devices so that datacenters can be built out of whatever's
on the around.
there's this programming language I like called Chapel for distributed
computation computing which is also cool, if you're more of the programming
type.
networking security I believe often has hardware solutions, so getting the
crypto-graphy boys and the PCB girls together to work on some jams is a good
and productively useful gathering of insightful events
"but ritz computers should only be used to solve problems that people have,
not make more problems!" ah yes but have you considered that problems find
you, and the computers help you work through them
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════════════════════════─────────────┘
--- #7 fediverse/2754 ---
══════════════════════════════════════════════════════─────────────────────────────
┌────────────────────────┐
│ CW: is-that-rude??-wha │
└────────────────────────┘
AI engineers only ask users for prompts because they don't have any ideas of
their own
i'm a programmer, I think of AI like a tool, like a for loop or something.
it's trivial to script together a local LLM that can process your stuff 1s
slower every time you click the mouse, but like... who cares, right? everybody
needs a chatbot...
then they plan to script together a computer system that operates just like a
corporation and it's like... no way, now there's something that can compete.
and they don't know how to implement it. (but they're working on it)
like, think about the absolute most automated Microsoft Teams or Discord could
be.
there's SO MUCH of your text-based information that they could process
ANYTHING.
well, anything that's been performed before.
there'll still be a need for people, who actually apply the things they've
learned. and -- stack overflow --
alt text that has a list of attributes that are poster-selected that can be
described one-by-one (to paint a picture)
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘
--- #8 messages/755 ---
═════════════════════════════════════════════════════════════════──────────────────
Code editor that moves boxes by saving over the file with a lua script every
time you moved a function call around.
Oh lemme start at the beginning:
A code editor program that's like a text editor like Vim or Emacs. If you
don't know what those are, you should probably learn Emacs. Or Vim. Up to you.
Oh right so if you do know what those mean, here's the idea: the white space
matters. It's counted and tracked into variables in a LUA script which
interface with the Vim C keybindings.
"run a function within a c program or LUA script which calls a bash command
which opens Vim for example with a file you want to edit. Then, inside the
file, your spaces and tabs would WYSIWYG for the various food ads placed
about, and then you could very easily create game design knowledge.
WASD to move, alternatively hjkl
It would run a check every time the file updates and depending on how it
changed it'd mark certain variables which would change the website as the user
moved things around.
It's just files. And files are just bits. But files are a useful abstraction,
If you realize that "ugly hacking" should be industry standard.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════════════════════─────────────────┘
--- #9 fediverse/6144 ---
╔══════════════════════════════════════════════════════════════════════════────────┐
║ what if every word I ever said online was searchable by database style │
║ uploading and linking? │
║ │
║ ... er, what if I made a neocities page that was algorithmically generated and │
║ sorted each of my posts by LLM statistically derived similarity to each post │
║ that the user clicked on? essentially, "here's the closest sounding or feeling │
║ related posts" but in plain HTML cached and pre-rendered rainbow table style. │
║ │
║ could run a waterfall style top-down data processing script on it once, then │
║ you'd have the HTML files generated. If you added new poems you'd have to scan │
║ through it again, but it shouldn't take long with a decent embedding model │
║ (note: not english, but trained on statistics only) │
║ │
║ ah, that sounds pretty fiddly, I think I'll ask an LLM to write it for me. As │
║ long as I have the intention in mind, it's basically just like writing a │
║ letter to a friend and asking them to build it for you, right? I don't mind │
║ writing the documentation, so long as it's okay if it's in prose. You can make │
║ a copy and rewrite for me │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧════════════════════════════════════════════════════════════╧══────────┘
--- #10 fediverse/1121 ---
═══════════════════════════════════════════════────────────────────────────────────
@user-812 @user-826
there should exist either the assurance that the default configuration does
not overheat or crash your computer (as Windows and Mac claim to offer) or the
OS should provide the capability to solve any configuration problems that may
prevent a user for utilizing their system as they desire. (as does Linux)
they're all Turing machines after all, why would they not be interoperable?
Even if there's a translation layer, as long as the functionality of the
software is the same, why would there ever be considerations as to whether or
not a program would be able to be run on a particular computer?
lack of hardware capabilities I can understand, that just means you need a
better computer. But why, if the code is visible, would your computer not
develop understandings about how to run each and every conceivable program
written using known languages like C or Python? Seems like pretty basic stuff
to me. (endless sufficient backwards compatibility)
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘
--- #11 fediverse/2056 ---
╔═════════════════════════════════════════════════════─────────────────────────────┐
║ sometimes I think about how you can store number values in letters, in │
║ addition to numbers. Like, ascii values for each word of your grandma's maiden │
║ name. All you have to do is encode it, and suddenly "44 means something │
║ different than Q" │
║ │
║ if I showed up at your place and used your username as a password to a public │
║ key I'm showing you in my hand, would you trust me then? Would you trust if we │
║ ran the simulation on your computer versus mine? Would you trust if I had │
║ never told you I knew where you lived? │
║ │
║ ... probably, tbh, I'm desperate for adventure. Though I got some good things │
║ going for me, so you'll have to convince me. (not the right attitude in an │
║ election year, just saying) │
║ │
║ why are elections so perilous this is NOT what democracy is designed for │
║ │
║ when kids cry in preschool, they're sent to a different room (or put outside) │
║ until they stop making noise and ruining it for others. That's just natural, │
║ like "hey baby let's walk around the block while I bounce you on my shoulder │
║ and hum calming music to │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧══════════════════════════════════════════──────────────────┴──────────┘
--- #12 fediverse/4125 ---
═══════════════════════════════════════════════════════════────────────────────────
@user-883
yeah that's probably better too since it'll be easier so there'll be fewer
bugs, especially since processing audio isn't usually performance critical ^_^
TBH I just want people to make more threading primitives like locks,
semaphores, and iterators. Like... thread pools, or hashmaps that run a
function on each record stored within every time each of the threads passes a
checkpoint, or paginated arrays of data that run a function on themselves and
the records near them (with slightly different input values, of course) idk
what those are called but I can't resist putting them in everything
Anyway I do think multithreading programs that don't need it will teach you to
be a better programmer, so... depends on what you're working on I guess. Are
you preparing to be ready and working, or are you ready and working?
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════════───────────────────────┘
--- #13 fediverse/1329 ---
╔═══════════════════════════════════════════════───────────────────────────────────┐
║ @user-941 │
║ │
║ well, your computer only has so many 1s and 0s that it can use at once. Like, │
║ having a trillion hands that can each hold a single grain of rice. Every │
║ character in that txt file would be like, 8 grains of rice, minimum, meaning │
║ you'd need at least 8 "hands" (or spots to put a zero or a one) for each │
║ letter! │
║ │
║ Hmmmm that's a lot of bits and bytes if everyone's writing to the same file. │
║ Maybe if we split the file up into smaller sections, then we could just read │
║ part of it at once. Then we could "scroll" through it to make sure we've read │
║ the whole thing, starting from the top and going to the bottom. │
║ │
║ ah but if everyone's SSHing into the same computer and reading it there, then │
║ that computer will have to present different parts of the file at different │
║ times to different people, as they read from the top to the bottom. Maybe we │
║ could just send them the file, so they can read it at their leisure? │
║ │
║ Yeah! And we could use tags to organize it and make it look pretty, like an │
║ HTML file except... wait hang on │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧════════════════════════════════════────────────────────────┴──────────┘
--- #14 fediverse/6383 ---
══════════════════════════════════════════════════════════════════════════════─────
nobody wants to write computer code that lets Java programs call Rust
functions.
An LLM is excellent for this task, since it's relatively easy busy work that
doesn't
reflect any meaningful implementation decisions besides "I should be able to
call that Rust function in my Java code"
In addition, it is technically efficient at it as well, because most of
compatibility
is matching up two sets of documentation. Easy for a text-processing machine.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════════════────┘
--- #15 fediverse_boost/5981 ---
◀─╔═══════════════════════════════[BOOST]════════════════════════════════────────╗
║ ┌────────────────────────────────────────────────────────────────────────────┐ ║
║ │ Some programming languages I’ve tried and liked and would recommend to others:C (especially C89/C90/“ANSI C” and C99)posix shell, bourne shell, and similar shells (bash, ksh93, mksh)PHPScheme (depending on the vibes I’m getting from someone I might recommend)Common Lisp (Same caveat as Scheme)Emacs Lisp (Same caveat as Scheme and Common Lisp)Motorola 68000 assembly │ ║
║ │ │ ║
║ │ Some languages I’ve tried and liked but would not recommend to others:Hewlett-Packard RPL (Actually I might recommend it to someone but it has to be a very specific kind of person)FORTH (same as RPL)Commodore BASIC (Microsoft BASIC) for the VIC-206502 assembly (so bad it’s good)Z80 assembly │ ║
║ │ │ ║
║ │ Some languages I’ve tried, did not like, and would not recommend to others:COBOL (maybe I could get used to it? I can at least read it. Just it’s so painfully like writing SQL statements without being as generally useful as SQL database queries)Kotlin (Like that feeling when you read words that alone you understand, but together in a sentence they make zero sense)JavaClojure (a.k.a. “Let’s make Common Lisp but make it worse”)Rust (stands for “Ridiculous Use of System Time” or something as far as I am concerned, heavy on memory and storage and super slow to compile and reads like Kotlin)TI BASIC (TI-82/83/84 style; TI-89 is a little bit better but still not good)C++ (unless you’re just writing almost completely C and building it with a C++ compiler)x86 assembly (I kind of like it but mostly don’t, there are better and more coherent CISC processor ISA’s if you’re into that) │ ║
║ │ │ ║
║ │ I should put Javascript somewhere, so I’ll say that it’s possible to write javascript code that I like and can read. Just no one chooses to do it anymore. There was a window between the time JQuery started to fade and all these stupid fucking “web frameworks” took off that it was somewhat tolerable. │ ║
║ └────────────────────────────────────────────────────────────────────────────┘ ║
╠─────────┐ ┌───────────╣
║ similar │ chronological │ different ║
╚═════════╧════════════════════════════════════════════════════════════┴───────╝─▶
--- #16 fediverse/899 ---
╔══════════════════════════════════════════════────────────────────────────────────┐
║ frankly I'm just excited to see what humanity does with the endlessly │
║ calculated and stored blockchains. Like, that's a good set of pseudo-random │
║ data, I wonder if we could build something off of it that wasn't exclusively │
║ money? like, a necklace, I dunno. │
║ │
║ or like, a numbers station x2, where each message is accompanied with a │
║ pre-calculated destination somewhere on this endless and │
║ impossible-to-understand string of data. and that part is what seeds the next │
║ code. once you start reading, certain numbers would be "flags" while others │
║ would be "data" and they'd each have the same size on the hardware. that way, │
║ they're impossible to predict. │
║ │
║ ah, but wouldn't it be noticable that certain results seem to appear next to │
║ one another? well, isn't that just cryptology? Could probably be defeated if │
║ you had an AI advanced enough, just saying. something that sorted through │
║ massive mounds of data and gave you results in garbled or broken english. what │
║ a wonderful tool, that's wonderfully mis-abused, perhaps in the fu │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧═══════════════════════════════════─────────────────────────┴──────────┘
--- #17 fediverse/282 ---
════════════════════════════════════════════───────────────────────────────────────
@user-209
I think you're right. Every letter in the variable name is another byte the OS
has to keep track of, which was a bigger problem in the past than it is today
(when it's been made irrelevant)
it's interesting how habits persist though the conditions that caused them
have faded. like a personal reflection of the environment you learned in.
"A a = new a();" is much more concise and (crucially) you can fit more words
to the right.
"a + b = c; c -= 2; f_z.write(c); f_z.close();" could conceivably be written
on a single line if you have short variable names. and when you only have so
many lines...
glad we're not constrained by those things anymore. the skeletal code that we
look at daily is much clearer - scope is more important, and so it makes sense
to encourage a coding style that illustrates it. however I can't help but
think block formatting like this could be useful in some situations, such as
when you'd normally be compelled to write a function for an operation that
runs once or more.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════──────────────────────────────────────┘
--- #18 fediverse/5911 ---
╔═════════════════════════════════════════════════════════════════════════─────────┐
║ I was always fascinated by the Linux way of programming. Need to do something? │
║ write it into a script! You never know when you'll need it again. Then, just │
║ stay organized, religiously so, and understand that you will forget about │
║ stuff. But, you'll come across it eventually, ready and willing and able to │
║ help you. │
║ │
║ if you don't want me using AI, then give me ~20 junior developers. Which is │
║ more efficient, do you think? │
║ │
║ "girl you haven't even tested your vibe-coded slop, how do you know if it │
║ works" │
║ │
║ oh I'm sure it doesn't, but it's the thought that counts │
║ │
║ ... I guess I'm just saying, please don't burn the data centers. Computers are │
║ not only bad for the environment when they're burnt, but also we can use them │
║ for all kinds of neat things. Even if it takes a lot of energy, just... build │
║ more solar panels and only use the computers for important stuff? │
║ timeshare-style? │
║ │
║ \@/documents/books/man-and-the-computer.pdf │
║ │
║ that was my mother's book... I love her. I miss that side of her. She fled │
║ when the cancer came. │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧════════════════════════════════════════════════════════════╧═─────────┘
--- #19 fediverse/2638 ---
══════════════════════════════════════════════════════─────────────────────────────
I really do believe that you can write any computer program you'd like with a
combination of Lua, Bash, and C.
Bash to start the program and enable updates / configuration, Lua to handle
the scripting and ordering of events, and C (or Rust) to execute performance
intensive sections. (often in their own threads)
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘
--- #20 fediverse/247 ---
═══════════════════════════════════════════────────────────────────────────────────
@user-195 parallel is when two programs run simultaneously, like two parallel
lines (threads) that never touch.
concurrent is when the two lines are split up into chunks and the program
switches between them - like this: -----_----
enter alternate universe
parallel is when two programs operate on the same axis - usually time - and
never interfere with each other. the OS will switch between them as
appropriate to make sure they never intersect. Sorta like this: -----_----
concurrent is when two programs are executed simultaneously, primarily
constituting computation correlated with collective contents of coordinated
collaboration between contextually related coroutines.
It's simple, even a beginner could figure it out.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════───────────────────────────────────────┘
|