
software engineer, https://teapawt.net/t.co/i1OvH7gkNI. low level but never ending, like π. built @datawanlabs
localhost
Joined July 2018
- Tweets3.7K
- Following603
- Followers1.2K
- Likes8.8K
Jafar Aziz retweeted
Finally, @Tan_Stack Start now supports React Server Components!
Start's RSCs are a truly fetchable, cacheable and composable primitive that work with your favorite tools instead of dictating your entire architecture.
Oh, and one more thing... "Composite Components" 😉
🔗⬇️🧵
Jafar Aziz retweeted
Women are the manager of the home, not a servant for you to say, “Why didn’t you do this? Why didn’t you do that? Why isn’t the house clean?” A woman is like a flower. A flower must be cared for and protected, and she will enrich you with her color, fragrance, and qualities.
Jafar Aziz retweeted
Penjelasan Ferry Irwandi tentang masalah gaji guru honorer telah digunakan oleh banyak pihak untuk menormalisasi nasib guru honorer agar mereka menyalahkan dirinya sendiri, yayasan, dan pemerintah daerah. Padahal, masalah guru adalah masalah kepemimpinan nasional.
-Thread-
Jafar Aziz retweeted
now we're getting a bunch of "if you don't like directives it's because you're not smart" posts
ok if we're gonna go there then let's go there
you babies think building software means doing create next app every 2 weeks on another dumbass side project you'll never finish and cramming 234 calls to 56 saas services
but some people work on other types of software where their backend runs as a standalone service running on node or bun or something else
there's a wide range of ways how this code gets compiled and run in production and they're all valid
providing a library type feature that requires a compiler means it has to support every single configuration of this
this is more to maintain, more opportunity for bugs, and undeniably more complexity
so choosing to use this new workflows library is now a much heavier choice - across all our projects i don't have a single dependency that works this way
effect manages to completely change js semantics and doesn't ask you to do this
and to illustrate my point if i wanted to use this library today i can't because all our stuff runs on bun and they need to ship some bun plugin that calls rust transforms
all so we can add a new kind of function coloring that's going to run into awkward apis for heavier work (which you haven't considered because remember you're a baby)
i'm not saying this library is bad it still looks pretty good and a lot people will find value out of it
but fuck off with the you're dumb if you don't like it shit
Jafar Aziz retweeted
IMAGINE SENDING 20 WARSHIPS TO INTERCEPT BOATS CARRYING MILK POWDER AND BABY FORMULA FOR STARVING CHILDREN. THIS IS THE GREATEST EVIL EXISTING IN THE WORLD RIGHT NOW!!!!!
Jafar Aziz retweeted
The courage of the Global Sumud Flotilla is inspiring.
I just learnt built and scaled their site + live tracker—using @Replit to get their message out.
Jafar Aziz retweeted
Ever dreamt of having a job where you deliver mail to the residents of a tiny planet? Us too.
messenger.abeto.co
#webgl #threejs
Jafar Aziz retweeted
Here's the mission:
1) Make something of yourself.
2) Marry well.
3) Raise the next generation.
It's hard, but why shouldn't it be?
Jafar Aziz retweeted
Every read from S3 takes 100ms-200ms on average. So reading a single byte takes roughly the same time as reading 10MB of data from S3 at 100MB/s speed.
This complicates designing high-performance databases with S3 storage. If the query needs reading a million of 1KB data blocks across different S3 object locations, then it needs 1M / 10 ops/sec = 100K secs = ~28 hours if it does this sequentially in a single thread. This can be optimized to 100 seconds by reading the blocks in parallel from 1000 threads.
Let's compare this to the database, which stores the data to local NVMe disk with 0.01ms-0.1ms read latency. A million of 1KB data blocks can be read sequentially from such a disk in 1M / 100K ops/sec = 10 seconds. This is a duration when the data isn't cached in the OS page cache yet. Otherwise the data will be read in less than a second. This results in 100x better query performance than at S3, without the need to fetch the data from 1000 parallel threads.



























