# orderedItems[].object.content
@chromakode @falsevacuum

I think this is actually my twitch profile pic

# orderedItems[].object.contentMap.en
@chromakode @falsevacuum

I think this is actually my twitch profile pic

# orderedItems[].object.content
@mlohbihler aw, the fundamental fabric of the universe didn't pop out at you?

# orderedItems[].object.contentMap.en
@mlohbihler aw, the fundamental fabric of the universe didn't pop out at you?

# orderedItems[].object.content
(the first one is a crackpot stringing together a bunch of jargon to sound smart and the second is a postgrad doing groundbreaking work in Farey sequences)

# orderedItems[].object.contentMap.en
(the first one is a crackpot stringing together a bunch of jargon to sound smart and the second is a postgrad doing groundbreaking work in Farey sequences)

# orderedItems[].object.content
the r/math subreddit is really funny because sometimes you get stuff like "on the equivalence of the kth multinomial klein bottle and the Bernoulli-Lagrange hyperdistribution matrix of Collatz convergences" and then other times you get stuff like "can someone tell me how fractions work"

# orderedItems[].object.contentMap.en
the r/math subreddit is really funny because sometimes you get stuff like "on the equivalence of the kth multinomial klein bottle and the Bernoulli-Lagrange hyperdistribution matrix of Collatz convergences" and then other times you get stuff like "can someone tell me how fractions work"

# orderedItems[].object.content
@agierscher @nicemicro I mean I am a ReactJS expert

# orderedItems[].object.contentMap.en
@agierscher @nicemicro I mean I am a ReactJS expert

# orderedItems[].object.content
@Ninji imagine if any game engine every six months was like "wait actually we came up with a better way to do things delete all your old code and start over again or you Suck."

# orderedItems[].object.contentMap.en
@Ninji imagine if any game engine every six months was like "wait actually we came up with a better way to do things delete all your old code and start over again or you Suck."

# orderedItems[].object.content
@Ninji yeah... I feel like a lot of react developers started only knowing webdev and react. they don't realize there are other, possibly better models, they're stuck in the cave trying to figure out how to make the shadows crisper.

I think it's telling that in most react conferences, it's never "here's what I built in React", it's "here's a new tool I built for React" -- it's a community obsessed with "making creating faster" rather than actual creation

# orderedItems[].object.contentMap.en
@Ninji yeah... I feel like a lot of react developers started only knowing webdev and react. they don't realize there are other, possibly better models, they're stuck in the cave trying to figure out how to make the shadows crisper.

I think it's telling that in most react conferences, it's never "here's what I built in React", it's "here's a new tool I built for React" -- it's a community obsessed with "making creating faster" rather than actual creation

# orderedItems[].object.content
@josh_clone@lgbt.io the alternative, like I said, is using immer, in which case I have to explain why we're using this third-party library and why the damn library doesn't just make it easy in the first place.

# orderedItems[].object.contentMap.en
@josh_clone@lgbt.io the alternative, like I said, is using immer, in which case I have to explain why we're using this third-party library and why the damn library doesn't just make it easy in the first place.

# orderedItems[].object.content
@amorphophalex I recently gave a fortune reading off of a deck of uno cards, it's certainly doable and really fun

# orderedItems[].object.contentMap.en
@amorphophalex I recently gave a fortune reading off of a deck of uno cards, it's certainly doable and really fun

# orderedItems[].object.content
@josh_clone@lgbt.io for context, I'm working with a developer who's also coming into this from a game dev perspective, and I'm just annoyed I'm going to have to explain why you can't do array[x][y] = n, instead doing

setArray(array => array.map((row, i) => i === x ? row.map((cell, j) => j === y ? n : cell)) : row)

# orderedItems[].object.contentMap.en
@josh_clone@lgbt.io for context, I'm working with a developer who's also coming into this from a game dev perspective, and I'm just annoyed I'm going to have to explain why you can't do array[x][y] = n, instead doing

setArray(array => array.map((row, i) => i === x ? row.map((cell, j) => j === y ? n : cell)) : row)

# orderedItems[].object.content
@josh_clone@lgbt.io it's not *failing* per se, it's just *annoying*

# orderedItems[].object.contentMap.en
@josh_clone@lgbt.io it's not *failing* per se, it's just *annoying*

# orderedItems[].object.content
This zealous insistence on immutability seems like it makes sense at first but quickly falls apart for anything bigger than a simple Counter app. The amount of gymnastics to get around "just update the damn value" spawned an entire cottage industry under the boogeyman of "but your app might show an updated value!", despite the fact that there are entire sections of documentation and blog posts dedicated to the many, many pitfalls of not doing everything quite exactly right.

# orderedItems[].object.contentMap.en
This zealous insistence on immutability seems like it makes sense at first but quickly falls apart for anything bigger than a simple Counter app. The amount of gymnastics to get around "just update the damn value" spawned an entire cottage industry under the boogeyman of "but your app might show an updated value!", despite the fact that there are entire sections of documentation and blog posts dedicated to the many, many pitfalls of not doing everything quite exactly right.

# orderedItems[].object.content
My current problem now is I want to store state data for a 2d array of coordinates that needs to be frequently updated. My options are:

* store it as an object, converting each coordinate to a string key (ew)
* store it as an array of arrays, needing to do complex code copying manipulations in order to get just one (1) entry updated
* use a whole-ass third party library (!!) in order to use mutable notation, which *still* copies a whole-ass object under the hood

# orderedItems[].object.contentMap.en
My current problem now is I want to store state data for a 2d array of coordinates that needs to be frequently updated. My options are:

* store it as an object, converting each coordinate to a string key (ew)
* store it as an array of arrays, needing to do complex code copying manipulations in order to get just one (1) entry updated
* use a whole-ass third party library (!!) in order to use mutable notation, which *still* copies a whole-ass object under the hood

# orderedItems[].object.content
I'm getting back into it for a new project after doing gamedev and other stuff for almost a year and like, like, goddamn is React badly designed.

# orderedItems[].object.contentMap.en
I'm getting back into it for a new project after doing gamedev and other stuff for almost a year and like, like, goddamn is React badly designed.

# orderedItems[].object.content
primebow #math #mathstodon #dataviz

# orderedItems[].object.contentMap.en
primebow #math #mathstodon #dataviz

# orderedItems[].object.attachment[].name
A graph of numbers from 2-127 based on prime factorizations. The numbers are represented as bars representing their prime factors and scale logarithmically. Each prime factor is a different height and color (with 2 being short and red while the largest prime is almost the size of the whole graph and deep blue). The factors of a number are stacked on top of each other.