levpopov

This is the best way. Inline duct fan and a flex hose running out of your window (you can print an adapter/connector to fit perfectly). It works very well even if your enclosure is not airtight (and it shouldn't be when printing PLA since you want a constant stream of air getting inside for cooling) - just let negative pressure do its thing.

This is fantastic, thank you for your work! I'm excited to see this project combine a clean API in a popular language, with a fast online playground that requires no installation. Having played with OpenSCAD and CadQuery in the past, this feels like a big step forward.

Some suggestions (I'm sure you've already thought of most of these):

- It would be great to have notebook-like UI to isolate steps and allow faster partial rebuilds.

- live editing is great, but it'd be nice to automatically stop in-progress rebuild if another edit is made while it's computing. Right now it seems to always let a rebuild complete even if it's already out-of-date.

- Search on API/docs page would be really handy

- Face/vertex filtering API looks cleaner than CadQuery's, and I'm excited to try it out. In a lot of cases I would still really like to just be able to click on the model and get a reference in code. Even if it's just an index that would break if topology has changed. Auto-generating stable references/filters would be even better, when possible.

Yes, thanks for the correction! In DIY keyboard community a microcontroller breakout board is often referred to as MCU which makes things confusing.

Very cool, and excited to see more "Geometry as Code" tools getting built. In addition to comparing to OpenSCAD it'd also be awesome to see a comparison to CadQuery.

This is mostly nonsense, you can easily check for yourself.

Load up the OP's page with Chrome dev tools network tab open.

Connection start: 90ms (60ms of which is SSL handshake) Request/Response: 30ms request / 30ms response

So the whole post is about yak shaving not splitting the 30ms response portion of a request that already takes 5x that (150+ms).

Sure it's a bit faster, but your users will not notice the difference between a 14kb page and a 15kb page over https (which you hopefully have on).

For sure, nothing is 100% secure (and even with multiple U-locks an angle grinder will win out after a while). I've had a good experience with hexlox so far - they are super hard to remove without a key. Haven't had any theft issues in multiple years of parking around San Francisco.

While the overall point of simple racks being better definitely stands, the premise that a bike needs two locks is just silly and impractical. Get wheel locks for your bikes - pinhead, hexlox (my favorite), etc. If your wheels are secured to the frame you just need to lock the frame with one lock/chain.

Takes way less time to park and you dont need to lug multiple 5lb locks (unfortunately thats how heavy secure locks actually are).

Given that most old Android phones stop receiving security updates after only a couple years from purchase, you should probably not do anything that involves connecting them to your local network.