aecsocket

Picked up a 1975 film camera in Japan and it follows @usgraphics philosophy on design. It's a tool that trusts the person who uses it: it doesn't hide the complexity of a photo from you, but gives you the tools to take a good shot. Form follows function.

@HSVSphere @dioxuslabs How's SQLite + a sync engine? Any Rust solutions?

.@dioxuslabs hello dutch looking funny guy, make a truly great, correct and composable sync engine for local first apps that is OSS and won't disappear when the creator loses interest and my soul is yours (+ other benefits, such as an endless stream of shilling)

The year is 2125. We have conquered the stars and have global peace worldwide. IPv6 is still not widely supported. Fell for dual-stack binding AGAIN award.

@bgianf It's a Framework 13: frame.work/laptop13

@aecsocket What laptop is that?

This is an NFC smartcard... but it's not the NFC you're thinking of! Japan's transit cards - IC cards - use their own type of NFC not often found in the West. NFC FeliCa's story is interesting, and I've written a post about it here: aruarian.dance/blog/japan-ic-…

2 of my blog posts on the HN front page, and I only submitted one of them. I think this means that people are interested in my work?😅

@derek_j_morris @usgraphics not Soviet, but there was a HN post on this idea of "maps are a perspective of the maker" news.ycombinator.com/item?id=408536… escapethealgorithm.substack.com/p/should-this-… interesting read, gave me a new perspective on cartography

@usgraphics There was an old tweet about a Soviet map of San Francisco that made me realize: maps are a perspective of the map maker, same as a photographer.

There is a deeper point here about fixed vs. flexible design, I don't know how to explain it but I can try with examples. The more you generalize, the worse it gets. Variable fonts have a problem where it is impossible to evaluate every single point in the domain space of interpolation by eye. You can use various animation tools to get a feel for it and check all axes but still, the craftsmanship suffers on a relative basis. In UI, we saw a huge decline in usability after responsive design was mandated on designers in early 2010s. So instead of designing for a specific class (say, Desktop computers), we slapped responsive design which was neither good at Desktop, nor Mobile. Given x hours of design time that was spent solely on one class of application, now we decided to spread that over a huge domain space of possibilities. Even more extreme would be to compare a hypothetical design process of designing for e.g. 1200x1200 pixel 10.3" screen vs. designing for all screen sizes from billboards to Apple Watch. The latter will be extremely sloppy. If you try to make UI rules with breakpoints, at the extreme end of it—you have specified so many rules that it is indistinguishable from designing separate UIs in the first place. If you're designing for 1200x1200 pixel 10.3" screen, you can spend more time tailoring the UI to that specific size. Same thing happens in print vs. digital media—one is fixed and the other flexible. This specificity vs. generalization trade-off is the root of problem everywhere in so many domains, from cartography to collapsible furniture. Death by requirements. And it probably has to do with some information theory stuff—you have to give up bandwidth for fidelity and vice-versa.

Graphs and plots always look cool. This is aeronet 0.7.0-alpha.2, a transport-agnostic low-level networking library for @BevyEngine, with high-level entity replication by bevy_replicon. With WASM browser support, and Steam sockets coming soon! github.com/aecsocket/aero…

@roadtovostok Ok a bit simpler than his approach, but this sounds like it's better for performance, and still looks awesome 😄

@aecsocket It's just a simple 128x128px scrolling displacement map and two normal maps on top of that.

I started modifying the maps for Public Demo 2 this week. One map (Shipyard) needed a completely new solution for water to work with this new engine. Here's a small video clip of a water shader I made yesterday. It should be quite lightweight in terms of rendering performance.

A server-side rigid-body physics framework for #Minecraft, using @dimforge's Rapier engine. Zero mods or resource packs (!!), just some clever coding. Still got some optimisations and features to make (water buoyancy?👀). Works on Fabric as well! github.com/aecsocket/ratt…