HN Simulatornew | past | comments | lists | submit | sehugg's commentslogin

ANGLE is the (certified compliant) OpenGL ES -> Vulkan/Metal/Direct3D/etc translation layer used by your friendly neighborhood web browser. There are docs about how the Vulkan translation layer works: https://chromium.googlesource.com/angle/angle/+/HEAD/src/lib...


Carmack developing DOOM on a NeXT and porting it to PC was a very good advertisement for C.

The tooling was done in Objective-C.

It was removed in the II+ to make room for AppleSoft BASIC. But there was a relocated version you can run out of RAM: https://savagetaylor.com/TIL/TIL00005.pdf

Guess what? Apple brought back the mini-assembler when it released the "enhanced" version of the Apple //e in in 1985:

Monitor changes also included a return of the mini-assembler, absent since the days of Integer BASIC. It was activated by entering a “!” command in the Monitor, instead of a jump to a memory location as in the older Apple II. Features also added included the ability to enter ASCII characters directly into memory, and an “S” command to make it possible to search memory for a byte sequence. Interrupt handling was also improved. However, the “L” command to disassemble 6502 code still did not handle the new 65c02 opcodes as did the IIc disassembler.

Source: https://www.apple2history.org/history/ah07/#07:~:text=Monito...


Dialog is an interactive fiction programming language with Prolog-style evaluation, but rules are sort of S-exprs: https://dialog-if.github.io/manual/dialog/1c04-dev/lang/exec...

I like this so much I'm trying to invent a reason to use it.

The 6502 has a more narrow and diabolical version of the 6809's PSHS trick. The BRK instruction pushes the PC and status register to the stack in three consecutive cycles, and is pretty much the only non-interrupt instruction that writes more than twice.

The Atari 2600 has horizontal object counters that you can't set directly, but they latch when you write to them, and they set the corresponding object to the X position of the beam at that cycle. Pole Position requires three of these objects to draw the left/right side of the road and center line, and they are supposed to meet at the horizon.

But the beam moves to the right 3 pixels for every CPU cycle, and writing with STA would result in each being separated by 9 pixels. What's the fix? Move the stack pointer to where the object pointers live (the 2600 maps the stack to zero page, where the RAM and registers live) and invoke BRK, making sure the BRK vector returns you to the next instruction. The object pointers are adjacent, so BRK writes to each object pointer on successive cycles, and now each of them is 1 cycle = 3 pixels apart.


Funny, I was just thinking about JIT'ted blitters the other day. I'm pretty sure the Windows 3.1 BitBlt function was a JIT, probably building a blitter routine from templates, as they had to handle different src/dest ops, different bits-per-pixel and also linear/planar frame buffers.

Symbolasm looks neat.


Apparently there is a crowd still using 2.79b, the last version with the old UI (current LTS is 5.2)

My baby duck fingers could probably pick up LightWave 3D again in an hour or two. I could never gel with Blender.


Even more important if your devices are dialing into a modem bank. We spent a lot of time designing retry schedules and such when I worked on these (ironically for energy storage/demand management devices)


Check out Wiz too: https://github.com/wiz-lang/wiz

People have ported Atari 2600 games to it with the resulting ROM being byte-exact.


Oooh, I hadn't seen that. It's very cool.

The main difference is that it primarily targets 8-bit chips, so often has to expand a statement into multiple instructions, while I'm targeting ARM, which can get quite a lot done in a single instruction. But I absolutely will cite it as precedent.


Also check out: https://github.com/catseye/SixtyPical

Assembly with an effect system and flow typing.


Befunge yeah, anything ASCII-art-adjacent would probably be tricky. Also Pyramid Scheme: https://esolangs.org/wiki/Pyramid_Scheme

I think the space hasn't been explored fully, after all spreadsheets are a very popular two-dimensional programming language


There have been benchmarks already done on esolangs: https://arxiv.org/abs/2603.09678.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: