=== ANCHOR POEM ===
═══════════════════════════════════════════════════════────────────────────────────
@user-570
I can write C in Rust, but I can't write Rust in any other language.
there's a lot of unique semantic options for accomplishing things that I
already know how to do that I often find my syntax is pretty... basic. lots of
manual assignments, no more than 4 or 5 levels of function nesting.
I like to use threads and arrays, and think about in-game simulation more like
a calculation than an input-reacting device. though input would certainly be
encouraged to make the simulation more precise.
the borrow checker gets in my way, but that's not too big of a problem - I
just have to copy a bit more data around. Easy peasy.
(I'm a bit rusty, but I can learn syntax)
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════───────────────────────────┘
=== SIMILARITY RANKED ===
--- #1 notes/portfolio ---
═══════════════════════════════────────────────────────────────────────────────────
game design:
spiral dominions
symbeline gdd
Joust
War (bytecode VM)
grid based warcraft map with random terrain and custom AI
Progress
[Title of Game]
I appreciate Rust, I can understand Rust, but I can't write Rust.
Python just kinda... works. It doesn't have a lot of the type checking that
other languages have, so it requires some vigilance and diligence. But that's
alright, you just gotta work on it.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════───────────────────────────────────────────────────┘
--- #2 fediverse/5212 ---
════════════════════════════════════════════════════════════════════───────────────
the reason you start with a game engine is because then you'll have tools to
make however-many games you want. Tools that you know intimately enough that
you can debug and improve them without breaking your creative flow by learning
something new halfway through a project
the whole point of individualized projects instead of viewing each computer as
a complete and total whole (why do we need servers again?) is that you can
paint a picture of where the design of the program is intended to go, such
that all the considerations are in place and whatever issues or struggles you
might face along the way are adequately addresssed, -- stack overflow --
[because I mistyped addressed] -- -- if you know what "stack overflow" means
you have intimate knowledge of the technology, and can probably guess what it
means in context when I say it. "nuts I lost that train of thoguht" -- stackl
ov
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════════════════════════════──────────────┘
--- #3 fediverse/9 ---
═════════════════════════════════──────────────────────────────────────────────────
@user-8 I love theory too! So far software engineering has been mostly UI and
databases and such and like... I'm not into HTML, thank you very much.
Gimme a Rust project or something and I'll excel
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════─────────────────────────────────────────────────┘
--- #4 fediverse/2879 ---
══════════════════════════════════════════════════════─────────────────────────────
┌────────────────────────┐
│ CW: re: tech info-dump │
└────────────────────────┘
@user-1370
I love this a lot! I want to put function pointers in a "matrix architecture
array" and make them point to different functions at different points in the
program. I bet you could even point them at each other, so like if M and Y
then point at N, A, Y or something.
this is really cool I like stuff like this tomorrow I'll take pictures of
something similar I'm working on! I abandoned it tho hehe anyway remind me if
I forget!!
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘
--- #5 fediverse/3154 ---
═══════════════════════════════════════════════════════────────────────────────────
┌───────────────────────────┐
│ CW: re: cursing-mentioned │
└───────────────────────────┘
@user-1461
yes... I like tree shapes, you have to address them differently. Lots of
pointers, in my experience, which can be kinda fun.
I also like large heaps / soups of data that points to one-another. Structs
thrown in a pile with pointers to each other. It's great! So long as those
pointers can also point back, and you can properly trace how data flows
through the system... That's the hard part, I think.
trees though... You can start by just saving a "next / previous" with one or
both being arrays of pointers to the next or previous entries. Note: plural,
entries. That's the fun part - non-linear trees teehee
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════───────────────────────────┘
--- #6 fediverse/3034 ---
═══════════════════════════════════════════════════════────────────────────────────
@user-570
I've messed around with Bevy and the library most similar in C is Raylib. in
Lua it'd be Love2D I think.
I love the idea of those systems. I haven't built a full game using them but I
can conceptualize operations within them easier using a framework like that
versus a game engine like Godot.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════───────────────────────────┘
--- #7 fediverse/466 ---
═════════════════════════════════════════════──────────────────────────────────────
I love Linux. All I have to do is type "authserver" and "worldserver" and
wouldn't you know it suddenly a universe is created (with very constrained
rules) that anyone might inhabit should they desire to. It's not like I'm
perfect - oh wait I have a toot about that, gimme a sec
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘
--- #8 fediverse/572 ---
═════════════════════════════════════════════──────────────────────────────────────
Hi, I'm learning about semaphores right now and trying to explain them to a
friend. But I only sorta understand how they work - can anyone look at this
pseudocode and tell me if I'm on the right track?
![Some C pseudocode working through the semaphore design pattern. Here's the text of the pseudocode: /* no lock example */ void start_thread(int* x) { *x += 1; } int main() { int x = 0; for (1000 times){ start_thread(&x); } print(x); } /* in this case you have no idea what will print because thread A will take x and be like "ah yes it's 423" and then in the next instruction it'll be like "I'll increment this to be 424" and in the next one it'll say "okay now it's time to store 424 in the variable X" but like... there's a thousand threads all doing that at the same time, so odds are you'll have 5 that are like "ah yes this is 423 I'll set it to 424" */ /* not a good plan. Need a lock, so only one thread can use it at once. */ /* mutex example: */ void start_thread(int* x, int* x_mutex) { *x += 1; *x_mutex = 0; } int main() { int x = 0; int x_mutex = 0; for (1000 times){ while (x_mutex != 0){ } /* do nothing */ x_mutex = thread_id; start_thread(&x, &x_mutex); } print(x); } /* this should print 1000, but it's basically as slow as doing it single threaded. */ #define MAX 10 void start_thread(int* x, int* x_semaphore) { *x += 1; *x_semaphore += 1; } int main() { int x[MAX]; int x_semaphore = MAX; for (1000 times) { for (int i = 0; i < MAX; i++) { x_semaphore -= 1; start_thread(&x[i], &x_semaphore); } while (x_semaphore != MAX) { } /* do nothing */ } int value = sum(x, MAX); print(value); }](/similar-different/media/224b236a8660c34a.png "Some C pseudocode working through the semaphore design pattern. Here's the text of the pseudocode: /* no lock example */ void start_thread(int* x) { *x += 1; } int main() { int x = 0; for (1000 times){ start_thread(&x); } print(x); } /* in this case you have no idea what will print because thread A will take x and be like \"ah yes it's 423\" and then in the next instruction it'll be like \"I'll increment this to be 424\" and in the next one it'll say \"okay now it's time to store 424 in the variable X\" but like... there's a thousand threads all doing that at the same time, so odds are you'll have 5 that are like \"ah yes this is 423 I'll set it to 424\" */ /* not a good plan. Need a lock, so only one thread can use it at once. */ /* mutex example: */ void start_thread(int* x, int* x_mutex) { *x += 1; *x_mutex = 0; } int main() { int x = 0; int x_mutex = 0; for (1000 times){ while (x_mutex != 0){ } /* do nothing */ x_mutex = thread_id; start_thread(&x, &x_mutex); } print(x); } /* this should print 1000, but it's basically as slow as doing it single threaded. */ #define MAX 10 void start_thread(int* x, int* x_semaphore) { *x += 1; *x_semaphore += 1; } int main() { int x[MAX]; int x_semaphore = MAX; for (1000 times) { for (int i = 0; i < MAX; i++) { x_semaphore -= 1; start_thread(&x[i], &x_semaphore); } while (x_semaphore != MAX) { } /* do nothing */ } int value = sum(x, MAX); print(value); }")
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘
--- #9 fediverse/3151 ---
╔══════════════════════════════════════════════════════────────────────────────────┐
║ ┌───────────────────────────┐ │
║ │ CW: re: cursing-mentioned │ │
║ └───────────────────────────┘ │
║ │
║ │
║ @user-1461 │
║ │
║ I'm best at Bash. │
║ │
║ I'm most capable with Lua. │
║ │
║ My favorite is C. │
║ │
║ I'm not a good programmer, I think too hard. Massive systems are too large for │
║ me. I like laying out data, whether that be by files and programs in Bash, │
║ arrays and tables in Lua, or memory and datatypes in C, I like to think about │
║ how programs are constructed. │
║ │
║ Which functions point to which piles of numbers? what do they do when they get │
║ there? │
║ │
║ I think I'm better as an artist. But I can do systems administration quite │
║ well (with Bash and a guiding hand telling me what and why to do) │
║ │
║ ... though I kinda suck at technical sysadmin, like Gentoo. There's too much │
║ terminology - why is data too complicated? Just use data! │
║ │
║ anyway. I sound opinionated, but I listen closely to good arguments and │
║ quickly change my tune when I am incorrected. I am a team player, and I firmly │
║ believe that sometimes a bad plan executed with cohesion and precision is │
║ better than the best play executed too late and with too little strength. │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧═══════════════════════════════════════════─────────────────┴──────────┘
--- #10 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 │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘
--- #11 fediverse/1977 ---
═════════════════════════════════════════════════════──────────────────────────────
functions should be forced to describe the context of why they were being
called. I think it would help debug a lot if we supplied a reasoning for each
and every request [function call] that we made. We might even be able to parse
them into semantic pyramids which we could sorta use to estimate [tree-like
scanning] how and why the program did do wrong.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════════─────────────────────────────┘
--- #12 fediverse/617 ---
═════════════════════════════════════════════──────────────────────────────────────
So much of computing is just... handling the quirks of hardware and presenting
it to the user (programmer) in a way that is sane and makes sense, instead of
the arcane and [nebulous/confabulous/incomprehensible] way that physical
nature demands our absurdly potentialized computational endeavors be.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘
--- #13 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 │
╘═════════╧╧════════════════════════════════════════════════════───────────────────────┘
--- #14 fediverse/849 ---
╔══════════════════════════════════════════════────────────────────────────────────┐
║ 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 │
╚═════════╧═══════════════════════════════════─────────────────────────┴──────────┘
--- #15 fediverse/3756 ---
════════════════════════════════════════════════════════───────────────────────────
┌──────────────────────┐
│ CW: LLM-mentioned │
└──────────────────────┘
@user-1071
I have plenty of things made, but none of it organized : (
Kinda makes me wish I could like... train an LLM on my social media posts and
use it programmatically somehow to help me organize my stuff into different
categories according to what kind of topic or style they were written in.
Hmmm......... There's no way I could do it, I mean, there's no way I could
organize and edit my stuff, but with the help of a computer I might.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════════════════──────────────────────────┘
--- #16 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 │
╘═════════╧╧═══════════════════════════════════════════════════════════════────────────┘
--- #17 fediverse/5850 ---
══════════════════════════════════════════════════════════════════════════─────────
@user-1074
if you'd like I can give you a lua script which will take your fediverse
archive and turn it into a pdf which you can edit or print or whatever. Might
be a fun diversion from posting. You can reply to yourself, add
clarifications, change some things, put things in a new light, add context,
etc... before you know it you'll have something printable. Could even pull out
your best stuff and make zines.
should require just a little configuration to suit your setup. That's part of
how I stay "productive" without posting all the time.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════════────────┘
--- #18 fediverse/633 ---
═════════════════════════════════════════════──────────────────────────────────────
@user-192
the neat thing about BASH is that it's the glue that holds all your other code
together. Write libraries in C and call them with BASH - accomplish broader
tasks that are easier to co-create. That's why I like it - it's not the most
important, but it's quite beneficial I think _^
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘
--- #19 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 ║
╚═════════╧════════════════════════════════════════════════════════════┴───────╝─▶
--- #20 fediverse/3574 ---
════════════════════════════════════════════════════════───────────────────────────
@user-1564
I love the concept of this! Maybe if HTTP is too complex, you could try
another simpler server? I don't know the complexity of the programs I use
every day, but I'm sure there's one that's very simple. Even just a simple IRC
style chat server that just... sends text from person A to person B depending
on their username (like a glorified Router or Switch)
Reminded of this video tbh...:
https://www.youtube.com/watch?v=gGfTjKwLQxY
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════════════════──────────────────────────┘
|