┌─────────┐┌───────────┐
│similar│chronological│different │
╘═════════╧╧════════════════════════════════════════════════════════════════════───────┘
--- #4 fediverse/4318 ---
═══════════════════════════════════════════════════════════────────────────────────
last month I found a desk fan by the dumpster that seemed to be in pretty good
condition. So I brought it inside and took it apart. I couldn't get it working
though, so it sat on my floor for 3ish weeks in many pieces. One day I decided
to turn it on and it worked for some reason?? and tonight I just got it all
re-assembled and working. It works! I'm so glad.
┌─────────┐ ┌───────────┐
│similar│chronological │ different │
╘═════════╧╧════════════════════════════════════════════════════───────────────────────┘
--- #5 fediverse/2631 ---
══════════════════════════════════════════════════════─────────────────────────────
┌─────────┐ ┌───────────┐
│similar│chronological │ different │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘
--- #7 messages/535 ---
═════════════════════════════════════════════════════════──────────────────────────
┌─────────┐ ┌───────────┐
│similar│chronological │ different │
╘═════════╧╧══════════════════════════════════════════════════─────────────────────────┘
--- #8 fediverse/5944 ---
══════════════════════════════════════════════════════════════════════════─────────
I swear, Lua has the worst manual out there.
I was looking for a definition of this function called io.flush(). Here's what
I found: [picture 1]:**io.flush ()**
Equivalent to io.output():flush().
okay, so what's io.output():flush()? [one result found] and it's the thing I
just found. great.
okay, so how about io.output()? [third picture]:**io.output ([file])**
Similar to io.input, but operates over the default output file.
and**io.write (···)**
Equivalent to io.output():write(···).
I know the text is blue, but it's not clickable. It's just text, not a
hyperlink to more comprehensive documentation.
There's also file:flush(), but that doesn't seem relevant to what I'm looking
for, because I'm working with lines and not files:**file:flush ()**
Saves any written data to file.
there are no more references to flushing, nor outputting of input nor output.
this manual sucks.
ah, well, back to vibe coding I go.
EDIT: at least it's all on one page.
┌─────────┐┌───────────┐
│similar│chronological│different │
╘═════════╧╧══════════════════════════════════════════════════════════════════─────────┘
--- #13 fediverse/1495 ---
╔════════════════════════════════════════════════──────────────────────────────────┐
║ LOOK AT THIS GORGEOUS THING │
║ │
║ ==== │
║ │
║ alt-text: pictures of a clear plastic xbox controller. It's shown on my │
║ porch-deck with the sunlight streaming in, and there seems to be a sparkle in │
║ the sheen of the transparent covering. Perhaps it's reflections from the │
║ various circuits and gizmos that are apparent in it's central form, or perhaps │
║ it's simply a trick of the light. Upon being placed in shadow, the │
║ inner-workings do not appear to sparkle in that same way, so perhaps the │
║ beauty is derived from the slivers of the sun that danced across the space │
║ between earth and our star. In any case, the entire controller is quite dusty, │
║ as if it had been hidden in a paper grocery bag that was shoved in the back of │
║ the closet of a boy who doesn't think to clean often. Frankly it's just not │
║ worth the trouble, and if he made any messes he would pick them up... but why │
║ bother with the little stuff? it's good enough, this is how he lives, so why │
║ would we be inconsiderate of his lifestyle? the final picture is of the audio │
║ jack. │
╟─────────┐ ┌───────────┤
║similar│chronological │ different │
╚═════════╧═════════════════════════════════════───────────────────────┴──────────┘
--- #14 notes/division-by-zero ---
══════════════════════════════════════─────────────────────────────────────────────
--{{{ introduction
When division is explained at the elementary arithmetic level, it is often
considered as splitting a set of objects into equal parts. As an example,
consider having ten cookies, and these cookies are to be distributed equally
to five people at a table. Each person would receive 10 / 5 = 2 cookies.
Similarly, if there are ten cookies, and only one person at the table, that
person would receive 10 / 1 = 10 cookies.
So, for dividing by zero, what is the number of cookies that each person
receives when 10 cookies are evenly distributed among 0 people at a table?
Certain words can be pinpointed in the question to highlight the problem.
The
problem with this question is the "when". There is no way to distribute 10
cookies to nobody. Therefore, 10 / 0 —at least in elementary
arithmetic—is
said to be either meaningless or undefined.
- wikipedia, division by zero, 7-12-23
alright I have several problems with this. I like the idea of dividing
cookies, but I disagree with their conclusions. So dividing by integers works
as
they say, but division by zero is a little different - they say "the problem
with this question is 'when'" when in reality 'when' is the same for this
question as it is for any of the others. Obviously, zero is just a number. Why
would this be any different? The computational actions necessary to complete
this statement all occur at the same time, because they are by definition
immutable. You cannot change any equation, you only generate new ones.
Okay so here's my thinking. To answer the question "what is the number of
cookies that each person receives when 10 cookies are evenly distributed among
0
people at a table?" we simply have to answer the question. "How many cookies do
I get?" well, none, because you weren't at the table. In fact nobody was at the
table, so the result is that nobody got zero cookies.
You might even say you have a remainder of 10 cookies, as none of them were
distributed.
10 / 0 = 0 remainder 10
^^^ that's how I think it should be. I have an algorithmic justification, and
excuse me as I don't have a mathematical proof or anything. Math was never my
strong suit, there's too many symbols and strange names for obvious operations
that get in the way of the abstract big picture.
ahem...
abstract:
Given: x = 13 / 3 what is x?
step 1: convert 13 to base 3
step 2: digit shift right by 1
step 3: convert back to binary
--}}}
--{{{ step 1:
v
start with the binary number 1101 which is 13 in decimal. To convert to a base
3
number, \___________________.
\ |
first start with the Least Significant Bit (LSB) which is 1. So our
base-3 number starts with 0001.
v
Next, move to the next bit: 1101
^-----It's a zero so we can skip it.
Which means our
base 3 number remains unchanged as "0001"
v
Next, move to the third bit: 1101
^-----It's a 1, which evaluates to 4 in decimal,
meaning we should add 4 to our base 3
number
base 3
4 in base 3 is "11", which means we 0001 <----- 1 in decimal
should have a base 3 number of "12" now. +0011 <----- 4 in decimal
=0012 <----- 5 in decimal
\_________ 2? -> yes,
base 3
remember?
Next, move to the fourth and final bit: 1101
^ --it's a 1, which evaluates to 8 in
0012-----.____________ decimal. 8 in decimal is "22"
in
+0022-----. \ base 3, which means we
need to
=0111 \ T---- add "22" and "12" in base 3
\__________/ to get our final number
of
13. Which should evaluate
step 2: to 0111 in base 3.
.____.
bit shift |0111| to the right,
|>>>>|
|0011|--->1 underflow
.----.
meaning the base 3 number is now 0011 with an underflow (remainder) of 1
step 3:
convert back to binary, meaning 0011 in base-3 becomes 4 in decimal or 0100 in
binary. Store the underflow as the remainder.
===============================================================================
=
okay that's great and all, but what does this have to do with dividing by zero?
great question, me. I have two questions I want to pose to you:
1. what happens when trying to divide by 1 with this algorithm?
- you convert to base 1
\
wait hang on base 1? Sounds made up... Well, its
not!
or at least if it is, then I'm the one who made it
up
so... yeah
|
okayyy how does base 1 work?
\
glad you asked.
--}}}
--{{{ bases
--}}}
--{{{ decimal (base 10)
--}}}
--{{{ binary (base 2)
--}}}
--{{{ digit shifting
--}}}
--{{{ bases higher than 2 and not 10
--}}}
--{{{ base 1? base 0?
--}}}
┌─────────┐ ┌───────────┐
│similar│chronological │ different │
╘═════════╧╧═══════════════════════════════────────────────────────────────────────────┘
--- #15 fediverse/4964 ---
══════════════════════════════════════════════════════════════════─────────────────
┌─────────┐ ┌───────────┐
│similar│chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════────────────────┘
--- #16 fediverse/2874 ---
══════════════════════════════════════════════════════─────────────────────────────
┌────────────────────────────┐
│ CW: re: unsolicited advice │
└────────────────────────────┘
@user-192
yeah it's not a new problem, but I really want to play nowwwww T.T
┌─────────┐ ┌───────────┐
│similar│chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘
--- #17 fediverse/1182 ---
═══════════════════════════════════════════════────────────────────────────────────
mitski
┌─────────┐ ┌───────────┐
│similar│chronological │ different │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘
--- #18 notes/game-design-documents ---
═══════════════════════════════════────────────────────────────────────────────────
game designs are like a presentation - given to the company as a pitch for the
product. It'd be recorded and used as training material for new employees.
It was, of course, developed using knowledge gained in the before.
But anyway it was like a roadmap - a guidebook - a puzzle - and a frame
Then, each piece was created with a great focus - and people were assigned to
prepare for certain parts. This way, you could keep the most skilled workers
and
disregard the rest. What happens when they're unemployable? AI will replace
them. But they're still good fine people who we chose to have at our company.
So
why should they be punished? We as a society should care for all those who will
not or cannot contribute to the system - it's built into our very genetic code.
Cooperation is the essence of our liberation - without two perspectives, we are
bound to be lost. Once lost, diversity of thoughts is often quite sought as a
"secret sauce" that describes when we are lost.
These words may not inspire thee. They might even never be false. It could just
not be your understanding. That's okay.
┌─────────┐ ┌───────────┐
│similar│chronological │ different │
╘═════════╧╧════════════════════════════───────────────────────────────────────────────┘
--- #19 messages/767 ---
══════════════════════════════════════════════════════════════════─────────────────
┌─────────┐ ┌───────────┐
│similar│chronological │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════────────────────┘
--- #20 fediverse/3389 ---
════════════════════════════════════════════════════════───────────────────────────
A screenshot of Ocarina of Time showing the Goron's Ruby.
alt text:
a screenshot of the Goron's Ruby from Ocarina of Time.
A smooth, flat stone comprised of two materials. The hardened outer shell is
thick with spiritual energy, and it radiates light the way a rippled piece of
silk folded over a malleable piece of gold.
the inner jewel is crystallized like the purest ice, but a bright shade of
crimson white. it seems to radiate an aura of affection and the yellow-gold
back-piece can be seen peaking through it's mostly transparent core. (think
like fog or thick mist or steam or smoke).
┌─────────┐ ┌───────────┐
│similar│chronological │ different │
╘═════════╧╧═════════════════════════════════════════════════──────────────────────────┘