@whitequark afaik there should never be ethyl-cyanoacrylate in surgical glue. It polymerizes faster than 2-octyl, leading to shorter and brittle chains (not great for squishy humans) and breaks down sooner, potentially releasing formaldehyde into the not yet healed wound.
I wouldn't be surprised if 2-octyl actually also works better for gluing things that are subject to stress cycles due to it being less brittle...

@sci_photos ja oder du schreibst halt statt python vernünftigen C code, dann reichen auch 16 🙃

In part 3 of writing a #brainfuck #compiler in #assembly and C++ we start the reimplementation and introduce some useful abstractions:
https://thacks42.github.io/2024/05/04/writing-a-brainfuck-jit-for-fun-and-profit-part-3.html

it is time

@loeb It's called redundancy, for when you want to be *really* sure about the state of A1 :P

Must've felt really down when I designed this one...
#pcb #kicad #hardware

In part 2 of my series on writing a #brainfuck #compiler in #assembly we discuss (and implement) some simple optimization passes and draft a way forward to more complex ones...
https://thacks42.github.io/2024/02/10/writing-a-brainfuck-jit-for-fun-and-profit-part-2.html

@aziz on x86-64 you either globally enable or disable paging (and thus virtual memory) using CR0. This then sets the behavior of *all* instructions referring to memory.
This requires you to set up a proper page table pointer in CR3,
and will then be used by the MMU to map virtual to physical address space.
You can explicitly load/flush cache lines on x86-64.

Did you ever hear about Turing completeness, #brainfuck or spent too much time with a CS-theory major? Did you ever think about writing a #compiler but had no idea how to even start?

For whatever reason I wrote a brainfuck compiler in #assembly and c++ and finally managed to finish the first part of my blog article about it:
https://thacks42.github.io/2023/10/30/writing-a-brainfuck-jit-for-fun-and-profit.html

Boop'n'Loop will be back at #cccamp23
https://chaos.social/@vidister/110510603277160960

This time @janamarie and I will also bring a chonky analog mixing console. Enough inputs, outputs, and busses will be available for all your gadgets that create or mangle sound~

Bring your flow3r, gameboys, walkmans, portable synthesizers, trackers, soldered effects, etc. and let's jam together. Create noise, techno, chiptune, μRaves, be creative!

@vidister @janamarie Is this already set up? and if so, where can we find it?

Sooo... someone told me there's a black market for these and they are worth a lot...?
:trans_flag:

RJ-45 connectors are cheap, durable, and have a decent mechanism for retaining cables.
Patch cables are cheap as well...
#kicad can't shout at us for abusing them...
So just use them for whatever data you need to get from A to B :P

@casandro yes although sadly they are not covering all four possible orientations for non-symmetrical devices (e.g. diodes).
Also support for these characters in commonly used fonts might still take quite some time whereas the box-drawing-characters are supported in most monospace fonts I've looked at.
This was actually a somewhat important point to me: aside from the bd-chars there are very few non-ascii chars in use and those that are seem to be commonly implemented.

Wohl eins der größeren #Hardware Projekte @neotopia in the making!
Für mehr Frischluft im Space 👾

Need to use #fixedpoint numbers on your #embedded target because it lacks a #FPU
Don't like using clunky C libraries to chain function calls if you just want to do some basic math?
Care about #performance?

Then this might be for you:
<https://github.com/thacks42/fixed_point_math>

Supports #floatingpoint literals,
all basic arithmetic operations,
boolean expressions,
and more!

try it out on godbolt:
<https://godbolt.org/z/1qr631MKe>

render your kicad schematics in unicode.
inspired by @janamarie https://github.com/thacks42/kicad-to-unicode