VCs are not particularly well known for their commitment to building products that they can't make money off of. They'll promise you the OSS world and then as soon as they can they'll pull the rug out from under you.
The problem is that they need to find some way to not only make the money back but multiply it.
That’s where the “you’re getting screwed” comes into play - we don’t know yet how they will screw us, but it’s gonna happen
I wish they offered some managed bridging to local NVMe storage. AWS NVMe is super fast compared to EBS, and EBS (node-exclusive access as block device) is faster than EFS (multi-node access). I imagine this can go fast if you put some kind of further-cache-to-NVMe FS on top, but a completely vertically integrated option would be much better.
Since EFS is just an NFS mount, I wonder if you could do this yourself by attaching an NVMe volume to your instance and setting up something like cachefilesd on the NFS mount, pointed to the NVMe.
Would
mkfs.ext4 /dev/nvme0n1 && \
mount /dev/nvme0n1 /var/cache/fscache && \
mount -t s3files -o fsc fs-0aa860d05df9afdfe:/ /home/ec2-user/s3files
work out of the box? It does for EFS. It hardly seems worth it to offer a managed service that's effectively three shell commands, but this is AWS we're talking about.
> - fsc – This option enables local file caching, but does not change NFS cache coherency, and does not reduce latencies.
If the S3 Files sync logic ran client-side, we could almost entirely avoid file access latency for cached files and paying for new expensive EFS disks. I already pay for a lot of NVMe disks, let me just use those!
>This option enables local file caching, but does not change NFS cache coherency, and does not reduce latencies.
That's true for any NFS setup, not just EFS. The benefit of local NFS caching is to speed up reads of large, immutable files, where latency is relatively negligible. I'm not sure why AWS specifically dissuades users from enabling caching, since it's not like bandwidth to an EFS volume is even in the ballpark of EBS/NVMe bandwidth.
Because without significant engineering effort (see the blog post), the mismatch between object store semantics and file semantics mean you will probably Have A Bad Time. In much earlier eras of S3, there were also some implementation specifics like throughput limits based on key prefixes (that one vanished circa 2016) that made it even worse to use for hierarchical directory shapes.
building for the loud users on a forum is generally a losing move. if we built notion for angry HN users, we'd probably be a great obsidian competitor with end to end encryption, have zero ai features, and make zero money.
X11 only is a bit of a bummer although I’m not surprised - i don’t think i’d target Wayland either for this sort of thing if i was a happy x11 user already.
I'm actually curious about that - this seems like something that should at least partially work through XWayland? Blindly speculating, it might not work against existing windows, but I'd expect things like system monitors and launching apps to not care.
To be honest, I am not sure, I will be working on those as the next big thing for Docking. I am uncertain of how much I can achieve on Wayland. Looking forward.
Tested today, most of it works using XWayland. Some applets won't like windows killer as it uses xkill, also some feature like window preview as Wayland do not give access to other screens, but also features like having the dock follow the mouse across different monitors.
Yes, indeed. The next I will be working with is Wayland. Let's see how hard that will be. I am sure there will be applet that I will never be able to port like Window killer that users xkill, etc.
Never fried one in bacon grease, but they are good with bacon and cheese. I have had more than one restaurant point out that their bacon wasn't vegetarian when ordering, though.
I think you could approximate a 4d projection onto a 3d display, much like we approximate a 3d projection onto a 2d display. So perhaps one could enjoy a fun and intuitive game of 4d doom if you have an appropriately fancy volumetric display. Pity they're so rare/expensive.
I've commented elsewhere about an 4D maze (https://urticator.net/maze/ - I am not the author) which mimics this by creating two 3D retinas in red/blue stereoscopic mode - when you cross your eyes just right you see a single volumetric 3D retina.
I read a novel when I was 14 or so who's premise is all about creatures inhabiting higher-dimensional space called "The Boy Who Reversed Himself" by William Sleator. I loved Sleator's books, they introduced me to really interesting concepts from theoretical physics as a youngun. If you find 4D Doom intriguing, I encourage you to borrow the book from your favorite ebook library, it's a quick fun read (at least, I remember it that way).
Loved this book! Part of this project started from wanting to make 4D creatures and train them to walk with RL. One interesting fact I learned is that ants would probably have 8 legs in 4D.
Why? Well, apparently ants have 6 legs because this allows tripod-gait, a simple leg movement that always keeps 3 stable points on the ground[1]
In 4D, you'd need 4 points on the ground, hence tetra-pod gait (4+4 legs).
You could of course do with less, I'd guess even as low as 1-2 if you have lots of muscles and good balance.
I'm still trying to wrap my head around the statement in the book (IIRC) that it takes 8 legs to be stable in 5 dimensions. I'd assumed it would be 6, but this is a layman's intuition. Maybe I'm remembering it wrong.
reply