draconic.one
shrk
scifi writer
airline pirrot
actual dragon
skater
artist
furry since forever
https://foxprints.org/
https://shark.community/@sekka/
sekka@discord
SekkaShark@telegram
is aka Kysh
fka Sasya Fox
251 posts
159 followers
271 following
Regular Contributor
Active Commenter
comment in response to
post
And I understand, conceptually, that people who don't want to leave all of their followers on there.
I didn't either.
But at this point, I'm running a little low on ... something ... for friends—especially queer, diverse, etc friends—who refuse to leave.
comment in response to
post
(And frankly, though it embarrasses me to admit it, I don't really understand the counterarguments because they often get extremely technical with functional programming jargon)
comment in response to
post
(And yes, to be clear, by "OOP" I do mean polymorphism and inheritance, at least to some degree, as well as message passing and such. Not necessarily all of the weird OO patterns, though, or the hyperencapsulation fetish thingy some OO programmers have . . . )
comment in response to
post
It looks wrong ...
comment in response to
post
Since people aren't upset about the fact that it's not allowed and say "don't fight the tools," I have to assume that there's some better way to do it—I'm just struggling to figure out what that is.
comment in response to
post
Conceptually, I feel like I want to separate my data model from the actions on it, but my data model contains different entity types that I'd like to logically separate. Directories within the same package would be ideal, but aren't allowed.
comment in response to
post
As far as I can tell, with go, it would just be:
<root>
| |-planet.go
| |-star.go
| |-event.go
| |-date.go
| `-(dozens of other files)
`cmd/
|
|-cli/
| `-main.go
|
|-webui/
| `-main.go
|
`-db/
|-sqlc.yaml
|-schema.sql
`- db.go
comment in response to
post
In my case, I have a bunch of different types (celestial bodies, events, my date type, etc), but they all (necessarily) reference each other. In another language, I might have:
<root>
time/
event/
location/
db/
ui/
webui/
etc, but I'm trying to figure out the right way here.
comment in response to
post
This may sound silly, but how do you deal with either having massive files, or a crapton of files in the same directory? Ideally I'd be able to have subdirectories in the same "package," but go doesn't allow that.
comment in response to
post
A little of column A, but shades of "the industry in general."
comment in response to
post
ilu 💜🦈
comment in response to
post
I saw your picture before I realized it was you, and my first thought was "Oh, Alaska."
I miss it.
comment in response to
post
You see this across all forms of media—the fear of risk taking by publishers, except when negative attention is desired for alternative marketing.
Worse, the publishers train the audience.
For better or worse, a starred review in yesteryear might net a few thousand sales, and that was success.
comment in response to
post
To succeed, you need to sell, because otherwise nobody will ever read what you've written. (And despite all of the "write for yourself!" advice, writing is, as you allude to, necessarily communicative. It requires a reader.) But to even get to that point, you have to please the algorithm of capital.
comment in response to
post
I think it's more insidious. I write science fiction, and I'm constantly talking with other writers who are so married to the concept of commercial viability that they're terrified of taking risks, which is what you're saying, but it goes deeper—they're also afraid to take chances with the formula.
comment in response to
post
💔
comment in response to
post
Oh also, gill smooches can be hot, too. <3 Gentle ones.
ON THE OUTSIDE.
comment in response to
post
Gills are sensitive and hot.
comment in response to
post
yes DEFINITELY. ^__^
comment in response to
post
Miss you! Hope you're doing great. <3
comment in response to
post
Badass <3
comment in response to
post
If you find that you've "solved" a problem in such a way, you haven't actually solved the problem, you've just gotten past the problem. Don't recommend your course of action to others.
comment in response to
post
Also, "I uh switched to wifi and it worked" is the sort of problem solving that's endemic to tech. I've always called it voodoo. (Relating to the pop culture concept, not actual Hatian vodou)
It's right up there with "reset your preferences," "reinstall drivers," "reboot," or "reinstall windows."