a_t48

12 ms·

211.
by a_t48 1y ago
This is a fairly "common" technique for doing multiplayer randomizers. Typically on a smaller region, but you end up with some sort of scratch memory being used as a buffer for messages sent back and forth between the emulator and
212.
by a_t48 1y ago
Many years ago I worked on a mobile game with a similar effect for fancy cards you just won, but with a bonus twist - we used the phone orientation to adjust the “shine” like a real 3D object. Looks like from a sibling comment that iOS can
213.
by a_t48 1y ago
You don’t need Thor nor ROS for this, but it can certainly help.
214.
by a_t48 1y ago
Not saying you're wrong here, but if that 30 minutes doesn't include running tests it sounds like your Dockerfile is setup poorly. For a ci/cd setup it should take like...a minute at most, if you don't have heavy ML depe
215.
by a_t48 1y ago
Definitely going to save this for later and come back to it after I get some more CUDA experience under my belt. It feels so nice right now making nice beautiful to use pipeline code w/ npp and some CUDA kernels here and there, the cod
216.
by a_t48 1y ago
TBH automation for finding/filtering candidates, but preferably personal email to my inbox. I can tell when you’ve used some cruddy software to send automated follow-ups four times after I didn’t respond to the first message.
217.
by a_t48 1y ago
Yes but one image push for us is >10GB, due to ML dependencies. And even if it is intelligent and supports per layer caching, you can’t share between release branches - https://github.com/docker/build-push-action&#x2
218.
by a_t48 1y ago
Awesome. Technically you can go over the limit right now (ours was saying 93/10GB last I checked), but I don’t know the eviction policy. I’d rather pay a bit more and know for sure when data will stick around.
219.
by a_t48 1y ago
Nice! I was considering using some sort of pull through cache like this, but went with the solution that didn’t require setting up more infra than a bucket.
220.
by a_t48 1y ago
It was half a day of work to make a drop in action.yml that does this. Saved a bunch of money (both in bandwidth and builder minutes), well worth the investment. It really wasn’t a lot of customization. All our builds are on GHA definitions
221.
by a_t48 1y ago
The real GH LFS cost is not the storage but the bandwidth on pulling objects down for every fresh clone. $$$$$. See my other comment. :)
222.
by a_t48 1y ago
At my current job I've started caching all of our LFS objects in a bucket, for cost reasons. Every time a PR is run, I get the list of objects via `git lfs ls-files`, sync them from gcp, run `git lfs checkout` to actually populate the
223.
by a_t48 1y ago
I've looked into this a bit - the big blocker isn't on the transport/IPC library, but the serializer itself, assuming you _also_ want to support serializing messages to disk or over network. It's a bit of a pickle - at l
224.
by a_t48 1y ago
Thinking about this more, for consteval this should work - huh
225.
by a_t48 1y ago
I continue to maintain robotics software that nobody uses, such is life. :)
226.
by a_t48 1y ago
It would have been, but it looks like the difficulty there is that the type of `sizes` must be compile time known, but `std::transform` and friends don't really know about fixed sizes. Depending on the context, one can do `auto sizes =
227.
by a_t48 1y ago
Oh man, some of the code in the linked proposal: Old: template<class...> struct list {}; using types = list<int, float, double>; constexpr auto sizes = []<template<class...> class L, class... T>(L<
228.
by a_t48 1y ago
I've been down this road. I ended up with a config YAML (basically - an IDL) that goes into a pile of jinja files and C++ templates - and it always ended up better and easier to read to minimize the amount of jinja (broken syntax highl
229.
by a_t48 1y ago
Prediction: it will be used heavily for things like command line arg parsing, configuration files, deserialization, reflection into other languages. It will probably be somewhat a pain to use, but better than the current alternative mashup
230.
by a_t48 1y ago
I agree that uv's virtual envs are not special, what's special is tooling around d it that works fast and is easy to use.
231.
by a_t48 1y ago
uv is still pretty young, a year and a half since initial public release? It's gotten a lot of traction but yes, it hasn't eaten the "market" for python package management, quite yet. I'd bet that there are users an
232.
by a_t48 1y ago
ah, whoops, yes
233.
by a_t48 1y ago
uv solves or improves 2,3,5. (It's scary how often lately I find myself saying or seeing someone say that) --- For posterity - make depending on system python an antipattern uv is virtual env, uv managed python executable firs
234.
by a_t48 1y ago
You should be able to get another 45 bits or so by also using the orientation of the cards (everything except non face card Diamonds).
235.
by a_t48 1y ago
If/when we get BCI that inject a UI into our central nervous system, I’m sure this will get overused. :)
236.
by a_t48 1y ago
Yeah, I have in mind handling network messages, mainly. Thinking about it, I have this problem at two layers: - At the transport layer, I read in a header on a message (which may come in one byte at a time!), get a size for the serialized m
237.
by a_t48 1y ago
I’m excited to actually getting around to trying coroutines - they should be a good replacement for simple state machines. Rather than an storing an object with a state enum, I can write simple declarative code.
238.
by a_t48 1y ago
FWIW you can do the same thing in cpp, too - but Rust’s syntax certainly makes it easier.
239.
Show HN: uvtarget – a helpful utility to manage Python in CMake, powered by uv(github.com)
5 points by a_t48 1y ago|0 comments
240.
by a_t48 1y ago
Love it. It's tough to balance keeping the ship afloat vs giving back to the community, I think you've got a good thing going.

More ›