=== ANCHOR POEM ===
═════════════════════════════════════════════════════════════════════════════──────
UIs with big, chunky pixels, bigger than retro gaming, like using integer
scaling in a retro game.
.
becomes
..
..
(except actually square)
then, you can sculpt those pixels if you really need to, to create
high-resolution displays used locally, to increase user-performance flow rate.
the old UIs weren't bad - they were constantly tested, as they were new and
emerging technology. The old UIs had different constraints than our 2560x1440p
monitors have to say. However, they still made correct decisions, so if
desired their decisionmaking can be used to inform future UI design as well.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════════════════════════════════════─────┘
=== SIMILARITY RANKED ===
--- #1 fediverse/1601 ---
════════════════════════════════════════════════════───────────────────────────────
@user-1037
Cool I'm into that stuff too : )
It had a very slick ui, very responsive if I remember correctly. Like, 60fps
in the browser kind of thing. Or maybe that was just the pre-rendered teaser
trailer shot idk.
honestly might have just been a front-end project or an animation, idk if it
actually worked as a programming language. But it seemed like a cool "UI" into
programming.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════════════──────────────────────────────┘
--- #2 fediverse/5402 ---
══════════════════════════════════════════════════════════════════════─────────────
@user-1773
that point about HTML is soooooo good
like, we could be designing websites like we design video game UIs but instead
we use React which fills your browser with insecure-by-design javascript
generated visuals
or, even better, or just use HTML like a config file
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════────────────┘
--- #3 fediverse/2886 ---
══════════════════════════════════════════════════════─────────────────────────────
@user-1209
display scaling accomplishes a similar goal through a different mechanism. You
might find that the visuals are sharper, however you will need to configure
every program to use this functionality (if it's present, which it's not in
most programs) - for OS level things this is usually a good option.
Changing the resolution will change the size of ALL visuals on your computer,
but they might be fuzzier (but if you're blind as a bat, why would you care
about fuzziness? It's all fuzzy!)
increasing the font size can also make it easier to read, which both of these
options are doing in a sorta round-about way.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘
--- #4 messages/127 ---
═════════════════════════════════════════════──────────────────────────────────────
All I want for my mobile computing is the ability to use the interface of
android to access resources and perform tasks that are relevant to my primary
computer. Like, a mainframe with the phone as a terminal. Except instead of
text, it's buttons and sliders and all the things that mobile UI experts have
spent so much time carefully crafting.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧══════════════════════════════════════─────────────────────────────────────┘
--- #5 fediverse/6015 ---
══════════════════════════════════════════════════════════════════════════─────────
┌──────────────────────┐
│ CW: AI-mentioned │
└──────────────────────┘
In 2025, if you want to create a piece of software your options are to either:
devote your life to it, or use AI to build a semi-working prototype that you
can use to pitch your idea to a bunch of people who have devoted their lives
to learning how to use your idea as documentation while they build it from
scratch, throwing out most of the code but keeping all the checklists and
progress-trackers you built along the way, perhaps even utilizing some of your
tooling that you used while constructing the scaffolding of this monstrous
application that you won't be using most of the source-code for.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════════────────┘
--- #6 fediverse/639 ---
╔═════════════════════════════════════════════─────────────────────────────────────┐
║ or like, a window that your window manager could window manage as it pleased. │
║ I'm thinking of like, i3 or dwm where you have "tiles" instead of "windows" │
║ you drag around. Really saves on screen real estate, but it lowers the ability │
║ of your screen to show width. Or height, depending on how you set it up, but │
║ since monitors tend to be wider than height-er (higher?) they (the users) tend │
║ to use setups that sacrifice width for visual density. │
║ │
║ anyway in such a setup the screen is divided into like, 3rds or 4ths, and each │
║ window takes up part of it. That way you can reference information from │
║ multiple sources without having to move anything but your eyes. Really helps │
║ with keeping it all in your head, because eyes are not reading information │
║ like a computer - they aren't using a cursor, it's not one bit of text at a │
║ time. Well, unless you're reading of course. But generally when looking at │
║ something it's a more parallel experience - shining through and forth from to │
║ our gods. Wow, cells in the body have an intere │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧══════════════════════════════════──────────────────────────┴──────────┘
--- #7 fediverse/2947 ---
╔══════════════════════════════════════════════════════────────────────────────────┐
║ the downside of Proton and Lutris is now the ONLY games that work on Steam are │
║ either continually updated (untenable) or playable on Lutris or Proton. Same │
║ thing with Wine, though there's always at least one decent substitute. │
║ │
║ kinda makes me want to write a manager-style program which runs programs using │
║ whichever version of their git repository would work best for their system / │
║ configuration / purposes. Idk how I would start working on that though. │
║ │
║ I bet you could make one that acted like a shop, but where you didn't charge │
║ any dollars. You could like... "swipe" through UI options, and pick whichever │
║ felt most useful for your setup. Like, how some people use i3 and some use dwm │
║ │
║ with maybe inspectors that are modeled off of video-game style "options" GUIs │
║ that mainly correspond to flags on the command/terminal line or compilation │
║ flags │
║ │
║ I feel like that kind of abstraction would make it a lot easier for users to │
║ adjust their system. they're noobs, after all. gotta show them all the choices │
║ in one place... │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧═══════════════════════════════════════════─────────────────┴──────────┘
--- #8 fediverse/646 ---
╔═════════════════════════════════════════════─────────────────────────────────────┐
║ @user-470 │
║ │
║ oh sorry I'll "en-longify" that for you: │
║ │
║ most monitors have a fixed resolution, somewhere between 720 pixels wide and │
║ 480 pixels high to 2560 by 1440 pixels high/wide. │
║ │
║ This is due to both the desire for humans to read left to right (ingrained in │
║ our minds at a very young age by learning to read) (or right to left, same │
║ direction) that we develop the desire for wide-screen monitors. │
║ │
║ Therefore, the windows of perception that we have unto this digital world are │
║ constrained (necessarily) to their own individual specifications. Of which, │
║ the property value "width" is more valued than "height". Because of this, we │
║ believe that computers are mistakenly re-acclimated - for everything is most │
║ efficient when it's aligned to the smallest bits of it's design. │
║ │
║ sorry, I like programming in C. Basically I'm very porous, and thinking about │
║ low level topics (like C programming) is an easy way to burn characters when │
║ there's only so many in the mastodon post that I can use to express my intents │
║ and tr │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧══════════════════════════════════──────────────────────────┴──────────┘
--- #9 fediverse/1116 ---
╔═══════════════════════════════════════════════───────────────────────────────────┐
║ ┌──────────────────────┐ │
║ │ CW: eye-contact │ │
║ └──────────────────────┘ │
║ │
║ │
║ It's important to build self-hostable computing components of video games (as │
║ in, old style games where you could host a server on any machine instead of │
║ just the ones owned by the corporation) (as in, your machine, yes yours) │
║ (something you can control and observe, something within your control) │
║ │
║ ======================= stack overflow ===================== │
║ │
║ there are two ways to play Unreal Tournament (capture the flag) gamemode. The │
║ first is to run past all your enemies and fire at them as you pass, which is │
║ what some of the bots are designed to do. The rest stay on defence, and defeat │
║ any enemies that approach. │
║ │
║ however, they never push the borders of their "territory" forward - each │
║ according to the different "lanes" or "directions of approach" │
║ │
║ I like the use 32 bots, to simulate a more consistent gameplay experience. It │
║ feels more like ww1, fighting over ground, pushing forward and attempting to │
║ outmaneuver your foes. │
║ │
║ some allies will approach from behind, and you let them pass forward while │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧════════════════════════════════════────────────────────────┴──────────┘
--- #10 messages/574 ---
═══════════════════════════════════════════════════════════────────────────────────
Steps to make a game waterfall style:
Lay out all the data structures
Build methods which manipulate those structures (think getters and setters)
Then build machinery which operates upon those structures using those methods,
like game loops, cooldown timers, and status effects
Then develop a way to present it to the player using UIs, visuals and
graphics, narratives, sound, all that junk that's probably someone else's job
anyway
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════════───────────────────────┘
--- #11 fediverse/894 ---
═══════════════════════════════════════════════────────────────────────────────────
a code editor that only highlights the lines that have been specifically
flagged to have a certain function. Like, rendering, or sound, or GUI, or data
storage, or logic, or control flow.
then, when the user is browsing, they can say "only show me these types of
functions" with a very advanced filter mechanism. The editor would highlight
the ones that were relevant and related, as according to user-defined flags
that were set when writing it originally. In this way, by using a bit more
syntax, even if it's literally just blocks of [category] labels (like how """
or ``` often starts or ends a comment block)
highlighting with colors is great, but what if we de-emphasized the stuff that
didn't matter? by increasing the opacity more closely aligning the font color
to the background color, we could make a bit of text seem to "fade" from
perspective, while still readable the user's eyes would not be drawn to it.
Then, according to the labels marked as filtered, certain text would be bold,
highlighted, o
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘
--- #12 fediverse/2887 ---
══════════════════════════════════════════════════════─────────────────────────────
@user-1379
mine is only 22" I think and it's about the same distance so now that I think
of it my poll might be flawed! I forgot to account for screen size!
You're right a proper scale is better quality-wise, but it doesn't always
scale everything y'know? plus changing the resolution is more low-tech which
is my vibe hehe
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘
--- #13 fediverse/3568 ---
════════════════════════════════════════════════════════───────────────────────────
@user-1556
I think they should be viewed in whatever resolution they were recorded in,
otherwise they look fuzzy as the pixels need to smush themselves together to
be correctly represented on screen.
videos should be recorded in whatever resolution your monitor supports, and
ideally as high as possible. Unless storage space is a concern, in which case
1080p is more than sufficient.
Storage gets cheaper and cheaper every year, but people across the world
upload like, 200 years of videos to Youtube every day or whatever (made up
that number but it's absurd) so maybe curated collections of videos are more
important than scraped archives?
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════════════════──────────────────────────┘
--- #14 messages/379 ---
════════════════════════════════════════════════════───────────────────────────────
take the "green bordered unit icon" from legion TD and apply it to the
economic output of the game - like, "it would be best to build 2 of these
units, so you get 140g because they're 70g each" and if the player disagreed
they could guess their own conclusion and if you were right, well then that's
what you remember, but if they were, then you remember theirs (and that it was
theirs). In doing so ================================================== stack
over flow ====
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═════════════════════════════════════════════──────────────────────────────┘
--- #15 fediverse/940 ---
═══════════════════════════════════════════════────────────────────────────────────
@user-652
just made a game for GGJ in Godot and I have to agree. Godot is so
frustrating, but one thing I have to concede is that once you get your head
around it the GUI part is actually incredibly powerful.
My next game I'm going to make in Raylib, and if the UI bit proves too
difficult I'll probably end up back at Godot.
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘
--- #16 fediverse/5689 ---
═══════════════════════════════════════════════════════════════════════────────────
why don't we make large arrays of vram that are slightly slower because
they're farther on the circuit-board from their host and their reception at
the processing section has to be gated such that they all enter to be
processed at once.
like that one infinite scrolling XKCD cartoon where the things move from one
screen to the other simultaneously assembly line style.
[fail safes. https://xkcd.com/2916/#xt=7&yt=35 ]
if we all feel like we're doing nothing, we'll all grow tired of it and decide
to do some prevailing. gosh I wish I wasn't so useless is code for
![why don't we make large arrays of vram that are slightly slower because they're farther on the circuit-board from their host and their reception at the processing section has to be gated such that they all enter to be processed at once. like that one infinite scrolling XKCD cartoon where the things move from one screen to the other simultaneously assembly line style. [fail safes. https://xkcd.com/2916/#xt=7&yt=35 ] if we all feel like we're doing nothing, we'll all grow tired of it and decide to do some prevailing. *gosh I wish I wasn't so useless* is code for](/similar-different/media/fad27564ee1f4a49.png "why don't we make large arrays of vram that are slightly slower because they're farther on the circuit-board from their host and their reception at the processing section has to be gated such that they all enter to be processed at once. like that one infinite scrolling XKCD cartoon where the things move from one screen to the other simultaneously assembly line style. [fail safes. https://xkcd.com/2916/#xt=7&yt=35 ] if we all feel like we're doing nothing, we'll all grow tired of it and decide to do some prevailing. *gosh I wish I wasn't so useless* is code for")
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════════════════════───────────┘
--- #17 fediverse/1602 ---
╔═══════════════════════════════════════════════════───────────────────────────────┐
║ @user-1037 │
║ │
║ those all seem really cool though! They all kinda have the same basic UI tho, │
║ kinda feel like there's opportunities for different kinds of expression. Like, │
║ in game design there's a lot of different genres, and yeah sidescrollers │
║ include mario and sonic but they're both very different experiences. So too │
║ perhaps could we interact with our computers by programming them in more │
║ engaging ways. │
║ │
║ they say some people are visual learners, others need to be taught, some │
║ people need to watch someone else doing it, and a few might just learn by │
║ plugging their brains into a computer and downloading a black belt in kung fu. │
║ │
║ Maybe typing long paragraphs of logic makes sense for some people, I know for │
║ most it doesn't come naturally. Maybe some people are more used to like, │
║ looking at maps that you can examine at different levels of abstraction. Like │
║ players who play Paradox games zooming from a national perspective to states │
║ and individuals and all the other things they might want to strategize using. │
║ Or m │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧════════════════════════════════════════────────────────────┴──────────┘
--- #18 fediverse/4029 ---
══════════════════════════════════════════════════════════─────────────────────────
what if a very slow LLM continuously generated text and was in a
back-and-forth with it's user who guided it through the training process as it
set weights as it chose
basically, let the computer decide how it wants to be like
could even filter it through multiple levels, like, top one is highly
intelligent, bottom ones are quick and only producing the vaguest output - but
the higher up you go in the tier, the more "up the tree node graph map" you'd
be, and the more you could have summarized for you, and passed up a layer.
observing multiple places at once, incorporating them bit-by-bit into their
digital "me".
like, have an LLM or machine learning whatever track a user as they use social
media.
could do it like a game, where you track the movement of the mouse and eyes
or more like a statistical model, where you
================== stack overflow ================
where you measure the quantity of each UI element's uses, and the general
context associated with that use. tracking data with data...
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════────────────────────────┘
--- #19 fediverse/240 ---
╔═══════════════════════════════════════════───────────────────────────────────────┐
║ ┌──────────────────────┐ │
║ │ CW: game-design │ │
║ └──────────────────────┘ │
║ │
║ │
║ i like to design games. my darling is a game based on Majesty (2000) the │
║ Fantasy Kingdom Sim. you can think of it like a management strategy game where │
║ you control the knobs and levers that a fantasy monarch might have - │
║ allocating funds, placing quest bounties, hiring heroes, and organizing the │
║ peasantry. the important part is that your units are not controllable - they │
║ just do their own thing. │
║ │
║ unrelated, but I think we should design games as APIs that a user's preferred │
║ tool could interface with and render as they will. it'd help a lot with │
║ cross-platform compatibility and would allow people to customize parts of the │
║ game to their desires. │
║ │
║ unrelated, but I think if you could design an AI that could play games │
║ (perhaps through an API) that it hadn't been trained on, I think you would │
║ have a pretty convincing argument for abstract "problem solving" capabilities. │
║ │
║ unrelated, but games like the one I described are good for situations where │
║ people don't have to trust their monarch. to it you are AGI │
╟─────────┐ ┌───────────┤
║ similar │ chronological │ different │
╚═════════╧════════════════════════════════────────────────────────────┴──────────┘
--- #20 fediverse/4092 ---
═══════════════════════════════════════════════════════════────────────────────────
why not make a unified fediverse identity that can post on whatever instance
it wants?
... hmmm could be accomplished with a layer of abstraction. You could use a
"fediverse client" software to enter text into an HTML page which would have
it's own UI and stuff and would organize your accounts and instances such that
you could mark like, 3-7 as places you'd like to put a particular message.
Then it would just... do it
l m a o spam is gonna get sooooo much worse before it gets better
but trust me, we'll figure it out. And it won't be long, either. It's a
solvable problem, we just haven't built anything to handle it yet.
... yet...
┌─────────┐ ┌───────────┐
│ similar │ chronological │ different │
╘═════════╧╧════════════════════════════════════════════════════───────────────────────┘
|