@tadeumaia@timneutkens What version of Next?
You could export a trace of what next-server is doing and have your agent analyze the memory spans. I could probably give you a prompt to explain the file format to an agent
@hirbod Still sounds like a good stress test for Turbopack to iterate on.
I'd also like to have better logging exposure for agents to answer questions like "why is my page compilation so slow?" and immediately find issues like this
@hirbod None of these things should be happening, and I’d love to get to the bottom of it.
If you can share the Next version and maybe a trace file (https://t.co/NHaw34uhJ6) the team can look into it — just DM me
@alex_barashkov@cachesaur Vite and Turbopack do different types of work at page load time. But regardless, Turbopack and next server shouldn't be hitting 30GB. DMs are open if you're willing to share more details.
@alex_barashkov@cachesaur Turbopack is designed to cache. It trades compute time for RAM use - Much faster compile, but more memory.
Still, long running servers end up continuing to allocate ram as you develop more of your app, so the team is working on ways to keep the RAM usage down
@_n13u_@timneutkens I work on Turbopack today, and I used to manage the Flow team at Meta. Flow support in SWC is still very new.
We can test stripping Flow syntax when we pick up the latest SWC version, but because it's so new it may not work well
Wrote more about my DOS-Compatible OS, talking about how the kernel and DOS API are structured: https://t.co/JqkOtkwgye
There was a lot of inline assembly and register juggling to jump in and out of the system calls. Learning how to use QEMU's debug monitor was critical here.
Currently implemented: about half of the INT 21h DOS APIs, most of a FAT12 filesystem, disk and console drivers, and a COMMAND .COM prompt that can list directories and run other programs. Lots to still do!
During some recent leave from work, I built a DOS-compatible OS that can run programs originally written for DOS. It's been an exciting project that's wayyyy outside my wheelhouse and comfort zone.
I've started writing about the process as well: https://t.co/vcuLCDAdhh
10+ years ago I fell into a $10M investment fund when I worked at @facebook. It did pretty well and we ended up as the 1st investors in @lyft (IPO-ed last week). A few thoughts about seed investments & how diverse investment teams really make a difference. https://t.co/fuMCLsA1mT
Using a rural internet conn is always good for empathy, but this current time made me realize how many sites are using iconfonts.
When we talk about FOIT or FOUT, we should also be concerned about FOUC - Flash of Unknown Character - boxes with Xes errwhere
@atul_jindal While we use a native version of React VR at Oculus, it's not available to external devs yet because it has a lot of Oculus-specific nuances. We do hope to one day let people write React and publish apps to the store, though!
Started a new wasm emulator using the same WebGL2 memory-mapped-graphics methods from my GB one. Brought up both the CPU and basic rendering in a single night!
@alfredofrlp SDF rectangles for all Views, instead of tessellation. We've always had SDF text, though we're about to make text rendering configurable so people can use different fonts with more ease.
As we support more internal use cases at Oculus, React 360 is actually becoming a powerful "React Native for WebGL" core with some 3D/VR functionality layered on top...
I'm excited about the new, way-fast, SDF-rendered Views landing soon
Oculus Go early adopters! If you're planning to transport your sweet new headset a lot, I recommend investing in a bag designed for photographers. They're designed to protect lenses, and have removable inserts that can snugly nestle your HMD.
Opened up the code for the #WASM GB emulator: https://t.co/yZQmKr6lI7
Broke down the arch in the readme, more documentation will get dropped in as I find the time.