@[email protected] isn't hermes supposed to be faster?
i heard some really good things about it, like type-aware compile-time optimizations (though now i cant find any source on that, maybe they just made this up)
somehow github actions kinda suck
- api is very limited:
there's no way really to download a cache entry via api
artifacts api doesn't provide a way to find artifacts by name
"create workflow dispatch event" doesn't fucking return the created run's id
- you cant use matrix within composite actions, you need to do that wherever you use the composite action
- caches are very half-assed and again introduce too much boilerplate
ended up just making an incredible crutch to invoke another workflow from a workflow via api and waiting for it to finish, and then manually download its artifacts. this way i can save up to 2-5 minutes on each run
> Found 29 errors.
>
> You may have discovered a bug in Deno. Please open an issue at: https://github.com/denoland/deno/issues/
oh my fucking god not again
slow types compiler when the types are actually slow: :troll:
<small>tbf the types are fast actually, it's the module resolution that is slow</small>
maybe that was not a very good idea - like 99.9% of these are child process overhead, the actual runtime of the script is at most 1-2ms. i should probably at least do some serious caching, it took 17s on a simple test project, it would take at least few hours on a real project this way :neocat_googly_shocked:
huh, typescript doesn't support async module resolution hosts, and deno works around that (from what i understood) by..
having it send tasks to native code and then block on them ([src](https://github.com/denoland/deno/issues/2626)) :neocat_googly_shocked:
welp, https://npm.im/deasync it is then
how do i teach my adhd self not to have arguments online
the most fucking pointless waste of time
but it's so fun every time and i keep falling for that...
it's really sad that there are no *good* and *maintained* component libraries for solid. or any libraries for that matter. most of stuff like "X but for solid" is updated once in a moon and rarely has more than like 100 stars
which is really a bummer, solid is literally so much better than react, but for commercial projects people still choose react just because of the ecosystem :neocat_cry:
one thing i really disliked about tailwind when i tried it is the fact that it doesn't promote consistency and semantics like at all.
like yeah, you have a bunch of colors and pre-defined border radiuses, but just because there are **so many of them** i really don't see any benefit to just writing `*px` directly.
proper design systems don't have 30 gap sizes and 50 different border roundings. of course there's nothing *stopping you* from putting an arbitrary value, but the pre-defined one should really be opinionated, otherwise there's not much point in the design system.
your "expertly-crafted default color palette" is good and all, but i don't really want to remember that my "brand" color is indigo-420 (or was it 666?) and that normally my paddings are 4 but i crank them to 6 if i really want to.
and making a component for *everything* just so i can reuse stuff quickly gets too tiring, and a very delicate game of balancing the component being opinionated vs the component allowing for any kind of usage you want it to.
also a weird thing with tailwind is that half their utilities have naming like *-xs/sm/... and another half is just straight up numbers.
@[email protected] ну не совсем, там есть вещи которые через инлайн стили ты не сделаешь. по типу всяких медиа-запросов и ховер стейтов и всякого такого. но вообще да, типа того))0
someone should make shadcn-style component collection (not as opposed to "component library". you literally copy-paste components from there) but with css modules instead of tailwind
classnames dreamt up by the utterly deranged
i feel bad opening issues for them to just be closed as duplicate/'working as intended"/some silly fix i somehow overlooked
i did look through docs and even looked into sources, so it's not like i am to blame, but still i feel bad for wasting people's time like that 😖
dear americans
nobody outside usa knows what the fuck are EST EDT ET PST CST and 289191 other "standard" timezones.
please for the love of god use UTC+X
sincerely, :haggard:
@[email protected] @[email protected] wdym? for users with a public follower/following list literally nothing is stopping someone from looking at them, nor scraping them to build a social graph
@[email protected] tbh i wonder if apple changed that after getting myriads of opposite reports from people who have never used a dumb physical calculator.
i might be misremembering, but im fairly sure it would have resulted in 200 5-6 years ago
@[email protected] i get it, but the ui does not reflect that.
theres almost no way for the user to know that the app remembered enough context to perform such a computation.
in other words, if i re-opened the app after i typed 50+50* - i wouldnt really be able to tell the difference.
i just checked, unlike +-, */ operators in ios calculator in fact don't act exactly the same way, their buttons stays active as if i was holding it until i start typing a number. which is better than nothing, but still an awful ux tbh