they [recommend](https://docs.deno.com/runtime/manual/advanced/typescript/types#type-checking-web-workers) using triple-slash directives for that.
except
> The one disadvantage of this, is that it makes the code less portable to other non-Deno platforms like tsc, as it is only Deno which has the "deno.worker" library built into it.
ok whatever lets just use ts's default `webworker` i guess?
nope! they are not fucking available when publishing to jsr!!
> triple slash directives that modify globals (for example, `/// <reference no-default-lib="true" />` or `/// <reference lib="dom" />`) are not allowed. Instead instruct the user of your package to specify these directives. file:///worker.ts:1:1
what the fuck duh
i made some kind of crutch to bypass that, but their awesome fucking typings don't include stuff for workers (because apparently workers are type-checked with a different `lib`). which makes me resort to these awesome hacks. blehhh
yet another insane crutch made in 2 hours for local jsr instances, yayy. this time - to populate local instance with upstream packages.
something that should honestly been done in jsr itself, similarly to how verdaccio handles it (by simply proxying shit), but whatever lol.
sometimes i feel like i made more useful tooling around jsr than jsr devs themselves tbh
if only deno supported per-scope `JSR_URL`-s...
i should open an issue about that actually
@[email protected] tfw пытаешься погуглить а гугл сука стал дерьмом в последнее время
как и все остальные поисковики
и тебе приходится идти спрашивать у знающих людей или разбираться самой
спасибо капитализм
@[email protected] @[email protected] @[email protected]
> ping in the push message, and then the app fetches everything it needs and displays the notification itself
yeah afaik on ios that requires a special entitlement by apple which they are quite unwilling to give away
ok so that's how physical exhaustion feels like
my hands are shaking, i can barely stand straight, i get annoyed really easily, which when coupled with me being clumsy because of exhaustion drives me fucking mad
maybe making my a/c smart wasn't worth that...
@[email protected] well there's [assemblyscript](https://www.assemblyscript.org/) :D
but the main issue with first-class wasm in browsers is that most of the web/dom apis are not exposed into wasm directly and require at least some javascript glue anyway
and the other reason is that they are all very much designed for javascript, which would make it pretty hard to bring to wasm. also wasm doesn't have a standard abi btw.
i think more people should consider js not a language but a compilation target. something like java bytecode or cil.
because realistically very few people write js by hand, and instead write typescript or whatever. especially when it's now simpler than ever (with bun and tsx)
js is objectively a bad *language*. because of... a lot of reasons.
but when all you do is write **safe** typescript (as in, no `any` and `as` and other ~~ungodly~~ unsafe operations), js is actually a very good *compilation target*.
decades of standards and optimizations in runtimes made js very flexible, portable and fast.
more people should realize it.
holy fuck
i never understood why are people so fucking obsessed with money. its genuinely so fucking sad that everything just becomes shittier every day..
when i was a small kid i was always inspired by corpo founders. not because of the money - but because they wanted to make the world a better place, to build a product that would make our lives easier, more productive and more fun. but now everything just fucking sucks. all they care about are fucking numbers.
its honestly just disgusting and sad
i even looked at tcpdump. there's literally zero hint. at some random point all pending requests just `RST, ACK` at me and that's it.
how am i supposed to even debug this...
docker networking is killing me
why do http requests between containers just randomly fail with ECONNRESET what the fuck aaaaaaaaa :neocat_googly_shocked:
@[email protected] oh god windows sucks lol
i once had to implement args escaping for batch and it was fucking hell because different built-in utilities used different escaping mechanisms 🥴.
weird how it has only recently been discovered though
@[email protected]
@[email protected]
> According to our policy. We can only perform a breaking change in a semver-patch release if it's a security vulnerability is found. That was the case.
still sucks though...
node 22 release is so cool holy shit
like, every feature highlighted in the [announcement](https://nodejs.org/en/blog/announcements/v22-release-announce) is so cool and honestly should have been in node a long time ago
i don't like how even despite me being the only person on this instance, not all posts are indexed, and i can't find shit if i need something later...
like, i understand that some people want to not be search-able by randos because of privacy or moral reason or whatever. im the same. but like...
i've seen that post
i'm following you
im the only one here, and it *will* stay like that for the foreseeable future
and it's not like im going to share this index with anyone
i should be able to look it up later...
i wonder if i get cancelled/defed-ed for making a patch that disables that filter
thanks microsoft very cool.
how the fuck do you forget to sign your repos??
and it's not the first time either, most of google results for this error are microsoft forgetting to sign their shit :neocat_googly_shocked:
cw2: sui mention
like, the last episode just feels as if the author was just pressured to not have the "good" ending, because that would promote satou's actions or whatever. the entire episode is just a cascade of awful decisions on her behalf.
both times i watched i felt such fucking cringe from her returning to the apt that is potentially on fire. she could totally just brush it off and be like "eh, whatever, we'll have an actual wedding wherever we end up". but she didnt. and then when she decided to go back up the already burning building instead of just kicking asahi's ass and running away.
like what, why, what the fuck, thats so much out of character for her.
and then she for whatever reason decided she wanted for shio to stay alive, despite that she will definitely suffer after that...
if you needed a "bad" ending why not just make them double suicide, why make shio suffer even further...
i also kinda feel bad for her aunt...
i cant accept this ending, ill keep pretending i didnt see the last 2 minutes and that they both died there.
@[email protected] я не уверена что такое есть вообще где либо. отчасти потому что комьюнити не очень одобряет такое, отчасти потому что активитипаб дермище
it always feels so weird writing apps when most of the time i write libraries.
in libraries you try to accomodate for every possible usecase, while in apps you can just do whatever works. most of the time you don't need to future-proof, because you can always just refactor or add features without worrying much about breaking shit.
it just.. requires a very different mindset, and every time i switch it always feels very wrong to just *do whatever works*
i kinda got better at this over time thanks to my job - i got scolded on code review for accomodating for use-cases that weren't used in the app at all at first, but i still can't not have thoughts like "what if we want X later"