About

"The program should, in some way, expand the concept of what computer paint programs are, as well as what mark making can be."

Recent posts

Omar Rizwan @omar

it's interesting that for concurrent data structures i have much less trust in their baseline correctness, so if i use some random library from GitHub, i have a habit of looking up the author, figuring out their credentials and projects they've done, etc

Omar Rizwan @omar

Great answer https://stackoverflow.com/questions/19863734/what-is-pthread-mutex-adaptive-np/25168942#25168942

Omar Rizwan @omar

Finding a replacement for these books is not easy. To procure a new copy, you have to mail in the old-fashioned way: to an address printed on the title page. This is the paradox of Down Home Cookin’: to obtain a copy of Down Home Cookin’, one must already have a copy of Down Home Cookin’

Finding a replacement for these books is not easy. To procure a new copy, you have to mail in the old-fashioned way: to an address printed on the title page. This is the paradox of Down Home Cookin’: to obtain a copy of Down Home Cookin’, one must already have a copy of Down Home Cookin’

Omar Rizwan @omar

"First-class heaps that can be destroyed in one go" https://microsoft.github.io/mimalloc/group__heap.html

Omar Rizwan @omar

oh https://en.wikipedia.org/wiki/Marching_ants

Omar Rizwan @omar

Need cat-printer-sized Blue4est(R) receipt paper roll

Omar Rizwan @omar

uint15_t

Omar Rizwan @omar

Ok maybe I'm not installing this

Using procfs for OS X

To use procfs, you'll have to build your own copy of the OS X kernel. Booting a new kernel on your own hardware is a risky process, so I recommend that you start by getting a second disk and installing OS X on it

Using procfs for OS X

To use procfs, you'll have to build your own copy of the OS X kernel. Booting a new kernel on your own hardware is a risky process, so I recommend that you start by getting a second disk and installing OS X on it

Omar Rizwan @omar

physical computing as new programming material w/ new grain

at a deeper level, i think a thesis of these systems is that materials are important, that you'll make different (and novel) stuff when you're programming here than when you program in JS (or when you program an iPhone app, or a shader toy, or whatever)
that by imposing these weird constraints and giving you this database and these default-recognized statements to query & doing all this stuff with pieces of paper, we're trying to create (or at least fake) a new type of material
and so of course if you have a specific idea already in your head and want to execute it, you can execute it with the existing tools of a web browser or a phone or whatever, but we're interested in generating new ideas

(it's like if you were like, what's the point of oil paint, or watercolor, or acrylic paint, because you can probably mostly fake a specific image made by one with the others -- the point is that these all have different resistances and grains that lead you to make different stuff in the first place)

at a deeper level, i think a thesis of these systems is that materials are important, that you'll make different (and novel) stuff when you're programming here than when you program in JS (or when you program an iPhone app, or a shader toy, or whatever)
that by imposing these weird constraints and giving you this database and these default-recognized statements to query & doing all this stuff with pieces of paper, we're trying to create (or at least fake) a new type of material
and so of course if you have a specific idea already in your head and want to execute it, you can execute it with the existing tools of a web browser or a phone or whatever, but we're interested in generating new ideas

(it's like if you were like, what's the point of oil paint, or watercolor, or acrylic paint, because you can probably mostly fake a specific image made by one with the others -- the point is that these all have different resistances and grains that lead you to make different stuff in the first place)

Omar Rizwan @omar

Typical

[–]waptaff 29 points 5 years ago
Reiser4 was promising but its design was very different from the other filesystems, so it included a great deal of code working around the kernel VFS. The kernel maintainers didn't like the idea of adding that much code that was not shareable with other filesystems and wanted something cleaner. There was a long stretch of (frustrated) back-n-forth where code was patched to ease its inclusion into the kernel, then Reiser had to deal with the consequences of his crime and the project was mostly abandoned afterwards.

[–]cbmuser Debian / openSUSE / OpenJDK Dev 5 points 5 years ago
One of the main problems were that Hans Reiser and Christoph Hellweg, the then VFS maintainer, couldn’t get along with each other.

[–]waptaff 29 points 5 years ago
Reiser4 was promising but its design was very different from the other filesystems, so it included a great deal of code working around the kernel VFS. The kernel maintainers didn't like the idea of adding that much code that was not shareable with other filesystems and wanted something cleaner. There was a long stretch of (frustrated) back-n-forth where code was patched to ease its inclusion into the kernel, then Reiser had to deal with the consequences of his crime and the project was mostly abandoned afterwards.

[–]cbmuser Debian / openSUSE / OpenJDK Dev 5 points 5 years ago
One of the main problems were that Hans Reiser and Christoph Hellweg, the then VFS maintainer, couldn’t get along with each other.

Back to top Show older