evmar

8 ms·

91.
Bringing Verse Transactional Memory Semantics to C++(unrealengine.com)
1 points by evmar 3y ago|0 comments
92.
by evmar 3y ago
They discuss this: "Table 1 illustrates that CoT paths do not consistently outrank non-CoT ones in the model’s probability assessment." and then look at table 1 to see some examples. E.g. in the first one the top 8 paths are wro
93.
by evmar 3y ago
Initially it was a combination of just for the fun of it (it's a small script, as OP described). Secondarily there was the feeling of "everyone is going to go work at [major competitor]" and I was curious whether I could col
94.
by evmar 3y ago
It was still going at the time I left (~2y). Most of the work of keeping it alive had been done by others for the last decade, so I hope someone else is still carrying the torch. We had the occasional HR interaction but to my recollection
95.
by evmar 3y ago
You are both right. Originally you could not email, and like the OP I kind of liked the ceremony of entrusting someone with a message to send from beyond the grave. But someone contributed the code to make the email work, likely after the
96.
by evmar 3y ago
I made epitaphs! AMA
97.
by evmar 3y ago
I'm sure the database is nice for other reasons, but also without really understanding the problem it sounds like you could represent two separate things here: (1) metadata about photos and their metadata sync state, (2) embeddings. Yo
98.
by evmar 3y ago
When I opened a Rust project I think the status bar said it was downloading Rust support, which supports your hypothesis. (Also it doesn't make much sense to bundle these things when they are all making new releases at different sched
99.
by evmar 3y ago
This looks really nice, but I am confused why the install is over 350mb, including a 300mb binary. I thought Electron-based stuff was big but this is even somehow more!?
100.
by evmar 3y ago
This article seems to make performance assertions that are not supported by what actually happens. E.g. "Passing by value is slower, since a new variable has to be created. Passing by reference just passes an address and the code uses
101.
by evmar 3y ago
Man, I remember* getting "coffee encrusted filet mingon with a vanilla glaze" at Charlie's back around this time, and thinking both "this is amazing" and also "this can never last". Also I remember many y
102.
by evmar 3y ago
Side note, most comments here are talking about Linux, but despite Windows having a nice async IO API, it turns out that it sometimes is also just sometimes synchronous, yikes. It includes some pretty big cases like "if the filesystem
103.
by evmar 3y ago
Possibly another way of expressing your point: after writing my above comment, I found myself wondering how much a system that kept these UAF pointers alive longer (to eliminate the UAFs, e.g a GC) would actually reduce the attack surface -
104.
by evmar 3y ago
I have written a lot of Rust, and I am describing something different. Rust lets you write code that cares a lot about memory (with lifetimes etc.) with either compiler assistance or without. What I am describing is code that doesn't
105.
by evmar 3y ago
It's interesting to browse the large collection under chrome/browser/ui and ponder over how many of them are use-after-free for data where the performance of manual memory management really doesn't matter. Like [1] whic
106.
by evmar 3y ago
If you're looking into a .wasm file I wrote an interactive viewer called weave[1]. Here is a demo with some Rust output: https://evmar.github.io/weave/?wasm/rust.wasm be sure to click on 'code' to d
107.
by evmar 3y ago
Ironically in the US if your car is heavy enough you get a tax break, which the auto manufacturers know and target: https://www.mbotw.com/section-179-tax-exemption/
108.
by evmar 3y ago
As a person who was initially disappointed by Go and who has come to love it, one of the biggest things I learned from watching it grow was the following: As far as languages go, Go is relatively well-funded. You can of course imagine hypo
109.
by evmar 3y ago
In n2[1] I needed a fast tokenizer and had the same "garbage factory" problem, which is basically that there's a set of constant tokens (like json.Delim in this post) and then strings which cause allocations. I came up with w
110.
by evmar 3y ago
For apps that show incremental progress it can be useful for a demo. Here's my build system going: https://asciinema.org/a/592924
111.
by evmar 3y ago
Skimmed the code, seems like https://humungus.tedunangst.com/r/pledge/v/tip/f/pledge.go ought to call xUnveilEnd() (...right?)
112.
by evmar 3y ago
I love how half the comments on here are about what a nice person the author of the site is. I, too, have had only positive interactions with Amit!
113.
by evmar 3y ago
My project https://github.com/evmar/retrowin32 includes a (Windows-agnostic) pure Rust instruction level emulator for x86, and if anyone is interested on hacking on one I'd love the help!
114.
by evmar 3y ago
This is a disappointing post -- they picked up a complex thing that they didn't fully understand, pushed some buttons, and then complained when it didn't work as they expected. I expect more from this blogger, whose content I thi
115.
by evmar 3y ago
I found the "snacking" metaphor that I think I learned from here[1] really helped me understand why I would sometimes get stuck in these kinds of corners. Its reframing helped me do it less. I find I reach for snacking when I&#x2
116.
by evmar 3y ago
It think you might not need to go via CString to get to the browser, given that the browser side doesn't care about NUL termination either. I think you could use Data.ByteString.Internal to grab the ForeignPtr/length out of the B
117.
by evmar 3y ago
Working on https://github.com/evmar/retrowin32 , I disassembled one old demo that wouldn't run on my native Windows machine -- turns out it was requesting 320x200 fullscreen resolution and aborting if it couldn&#x2
118.
by evmar 3y ago
Wow, you are thorough! I just include the date as metadata in the post input file and typed it wrong this time. I don't have any scheduling feature, the whole thing is incredibly manual ("make" followed by "rsync"
119.
by evmar 3y ago
It makes some sense to me. To support 64-bit x86 they need to ship 64-bit x86 versions of lots of system libraries, which itself is probably kind of a hassle and a waste of disk space for many users. Supporting 32-bit x86 would require an
120.
by evmar 3y ago
Thanks, fixed.

More ›