I've always just used slice. Works the same across both strings and arrays, and the way negative indices are handled feels more intuitive.
02.12.2024 00:31
👍 2
🔁 0
💬 0
📌 0
I've always just used slice. Works the same across both strings and arrays, and the way negative indices are handled feels more intuitive.
I don't think they have to be for-profit companies, but the existence of another for-profit company competing and potentially outcompeting Bluesky's own app would really put these decentralization ideals to the test.
Would love to join if there's still a spot! :)
Done! :)
Yep, fly still has egress, but a lot more reasonable than AWS! :)
Yeah sort of haha, we save the assets to S3 for the durability guarantees, and then serve them over our global nginx-based CDN hosted on fly.
Would love to be a part of this one! :)
Yep! We only support client-rendered React apps so far, but we do everything 100x+ faster. :)
Hmm is it just me or is the default Bluesky discovery feed a bit too random?
I've been engaging with tech/programming stuff almost exclusively since I made this account, but 90% of the posts on my discover feed is still not tech/programming stuff.
💯
Also why I'm not a fan of git commit/push hooks. A lot of times I commit/push just to save my work, run CI, or deploy a preview to poke around in, any friction added to that process is super painful.
Missed out on the first one. Hopefully I can make it onto this one? 🙏
Not sure if I'm cool enough, but it's worth a shot! 🙂
Play with the live version here:
reflame.app?%7Er_preview...
Good night!
And here it is in the opposite corner. 😪
Yes, of course I did dark mode too. 😫
Help. I'm addicted to @motion.dev. 😱
This capability would be pretty crucial for building a performant polyfill to something like github.com/tc39/proposa... (which I plan on evolving my bundle format into eventually).
Happy to draft up a proposal if someone on tc39 might be willing to help champion it!
There's no way to assign a custom URL to a dynamic JS module (created through createObjectURL) for the purpose of relative import resolution and import map scoping.
My new JS bundler is at least 10x slower at runtime because of this (see network tab on reflame.app).
Yes definitely this too. I use a M2 MacBook Air as my main dev machine specifically for the silence. So refreshing!
I have the M4 Mini on my desk right now running Llama 3.2 vision and fans don't seem to be even spinning up!
Not to mention they have one of the best platforms out there for running LLMs efficiently in terms of both cost and power, thanks to unified memory. Surely that would be an amazing sell for today's server market?
In fact that's exactly why I bought my base M4 Mini.
Apple would probably dominate the server CPU market if they decide to enter it.
I kinda wish they would since everything I deploy to prod end up performing much worse than even on my M2 Air due to how crazy far ahead they are on single threaded perf.
Apparently the base model M4 Mac mini idles at 2-3w with low power mode, 4-5 without.
That's Raspberry Pi levels of efficiency. Bonkers especially considering the fact that most workloads can finish 100x faster and go to idle 100x sooner than on a pi.
I'm pretty sure I've seen this eyeball icon just about every day for the past decade but never bothered to hover over to see what it does. 🤦
These optimizations are great and all, but the UX around having to manually specify entry points has always been a huge point of confusion and frustration.
Thankfully with this change, we'll be able to get the best of both worlds!
We both cache package installations and bundles and load them for future deployments, and serve them up through our CDN as a separate set of resources from your app, so repeat visitors will always have them cached regardless of how frequently you update your app code!
2) Since NPM packages change very rarely compared to the rest of your code, we can get a ton of bang for our bucks by caching them independently from the rest of the app.
... and since NPM package installation & bundling is almost always the bottleneck in the overall deployment process, this can cut down deployment speeds drastically versus other approaches that bundle NPM packages and your own code together sequentially.
Reflame has always required specifying entry points to NPM packages up front, because it enables a few novel and hugely impactful optimizations:
1) We can start installing and bundling packages before we even start looking at the rest of your code...
