sending lots of hugs and love to everyone feeling that normative holiday squeeze 🫂
remember that the holidays are hard for a lot of folks. there's nothing wrong or weird with not feeling like you fit into things you dont want to be doing. if everyone else is enjoying doing stuff you dont like or are actively opposed to, that isn't a reflection on you. hold true to your values. let them define you. ❤️
if anything, its wrong to make people fit into situations they dont want to be in!
well anyway. i hope you ar least get to eat something yummy.
to clarify — most of Kazakhstan celebrates new year instead. its aesthetically the same as christmas. we too put up a spruce tree with shiny balls and have a red boomer come home and shower us with gifts. we just don't do that on the birthday of The Dude Who Came Back
I've written a tutorial of sorts, showing how to write a streaming XML sitemap scraper using Promistreams! https://wiki.slightly.tech/books/projects/page/example-project-scraping-xml-sitemaps
@mawr Nothing is ever same. It doesn't change anything about the harm that language bashing does, and it absolutely does harm with JS too.
@mawr @serapath Kindly refrain from language bashing in my mentions. It helps nobody.
See also: https://blog.aurynn.com/2015/12/16-contempt-culture
@joepie91 "if you disagree then you can just fork it" is a response that you'd only get from a developer to shut down genuine complaints often made by users who are themselves not developers and never will be developers.
It's a callous cop-out at best and a refusal to acknowledge and address poor design or critically missing features at worst.
@mawr @serapath Hm, I'm not sure that's entirely true, I guess it kind of depends on how you define 'fork'. For highly modular code, where a package does exactly one thing, it can make sense to fork it to fix a bug (if upstream is no longer actively maintained) or do some sort of project-specific optimization, for example.
But that's more a 'fork' in the sense of 'making a derived project', not so much in the sense of 'supplanting the original for community adoption'.
It occurs to me that this is rarely said out loud, but it probably should be:
The ability to fork open-source software is important, *but* the idea of "if you disagree then you can just fork it" is basically a lie. It has never worked that way and it will never work that way.
In reality you're dealing with project governance and so there are a lot of social factors (community support, motivation to 'compete' with the established name, etc.) that are critical to not having a fork wither on the vine.
And it's very difficult to pull that off, and usually requires a long history of growing resentment about the leadership of the forked project. This means a fork is rarely the best solution.
vaguely spicy take
@hazelnot My experience is that, at least in tech jobs, the more uncompromising you are, the better you tend to get treated by bosses. Similarly, charging more causes customers to be more respectful of your time...
@raito No conditions whatsoever, including and up to supporting `null` values, as there is no serialization step involved anywhere (unless you add a serialization stream, of course).
You represent the processing steps as a linear(-ish) Promistream pipeline in your code, but behind the scenes that essentially gets converted into a long chain of Promise handlers, so anything that can go in a Promise (which is everything) can go into a Promistream too :)
vaguely spicy take
@hazelnot They could, but it would be unreasonable
@raito So Promistreams are agnostic to the values that go through them; you totally could use them to design some sort of streaming component system (by streaming through component-shaped objects), but Promistreams *themselves* do not do anything with components, and it wouldn't be directly in scope.
Someone actually compared Promistreams to Rx.js earlier today, in concept, so you're probably not far off with your idea :)
(There *is* a plan to write an Rx.js adapter stream which can convert between Rx.js and Promistreams bidirectionally, so if such a component system already exists based on Rx.js, then Promistreams could plausibly interoperate with it)
vaguely spicy take
@hazelnot The actual rules you have to comply with (as enforced by eg. tax authorities) generally just specify that it must be concretely useful to the job in some way. This is trivially satisfied by hacker events if you're remotely working in tech.
Crucially, that specifies what property the trip *must* have. It doesn't specify what property the trip *must not* have. Whatever rules executives layer on top of that is 100% their own ideology, and that is on them.
(Also, it's standard practice for people to get completely and utterly drunk at 'boring' industry conferences too, so it's not like "injecting some kind of fun into events" is exclusive to hacker events anyway)
vaguely spicy take
People joke about "expensing hacker events as work trips" but actually I think that's genuinely a reasonable thing to do, even under the 'conventional' understanding of what constitutes a 'work trip' (for training and education).
There's no rule that says a trip must be boring to qualify as "materially useful to your job"! That idea is just some puritan(?) ideological nonsense, it has no bearing on how the world works.
In the process of moving to @joepie91. This account will stay active for the foreseeable future! But please also follow the other one.
Technical debt collector and general hype-hater. Early 30s, non-binary, ND, poly, relationship anarchist, generally queer.
- No alt text (request) = no boost.
- Boosts OK for all boostable posts.
- DMs are open.
- Flirting welcome, but be explicit if you want something out of it!
- The devil doesn't need an advocate; no combative arguing in my mentions.
Sometimes horny on main (behind CW), very much into kink (bondage, freeuse, CNC, and other stuff), and believe it or not, very much a submissive bottom :p
My spoons are limited, so I may not always have the energy to respond to messages.
Strong views about abolishing oppression, hierarchy, agency, and self-governance - but I also trust people by default and give them room to grow, unless they give me reason not to. That all also applies to technology and how it's built.