alcinnz

alcinnz, 5 days ago

Several more links from Bjarnason's linkdump...

Generative AI Is Totally Shameless. I Want to Be It - Paul Ford @ WIRED:
https://www.wired.com/story/generative-ai-totally-shameless/

The Future of 11ty (2024) - Zach Leatherman:
https://www.zachleat.com/web/11tyconf-keynote-2024/

Some of my Eleventy Filters - Chris Burnell:
https://chrisburnell.com/article/some-eleventy-filters/

Baseline progressive enhancement - Jermy Keith "adactio":
https://adactio.com/journal/21128
Yup, this is my gripe about Baseline!

The wrong way to do Web Components - Go Make Things:
https://gomakethings.com/the-wrong-way-to-do-web-components/

alcinnz, 5 days ago

Last several links from Bjarnason's dump...

‘Magical thinking’: hopes for sustainable jet fuel not realistic, report finds - Oliver Milman @ The Guardian:
https://www.theguardian.com/environment/article/2024/may/14/sustainable-jet-fuel-report?CMP=Share_iOSApp_Other

The four causes of writer’s block and what to do about them - Suw Charman-Anderson "Chocolate & Vodka":
https://chocolateandvodka.com/2024/05/15/the-four-causes-of-writers-block-and-what-to-do-about-them/

The New Golden Age of Black and White Photography - Christopher J Feola @ Entax Forums:
https://www.pentaxforums.com/articles/photography/new-golden-age-bw-photography.html

So top-of-thread link for more links & commentary!

alcinnz, 5 days ago

@baldur Its worth emphasizing: These skills don't goes out-of-date! Browserdevs go out of our way to ensure the pages you've written yesterdecade still work!

New optional features have been added, & best practices have solidified since the 1990s... But still!

Having to periodically rewrite outdated code is something webdevs bring upon themselves! Having to keep ontop of the latest frameworks is something webdevs bring upon themselves!

alcinnz, 5 days ago

@teleclimber @baldur Oh yes, the cases where skills become outdated because we have better tools now!

alcinnz, 6 days ago

If we need a larger canvas, we could lean on the Compositor Coprocessor to blend in brush-strokes simulated from the full detail of (if we have it) the signal-processed & smoothed touchscreen input. Akin to Krita. We'd probably add a sidebar form to tweak this brush.

Or we might want to save input from the camera to edit! Likewise for the microphone, producing audio data.

In all these cases we'd want to compress this sheer quantity of data. And postprocess it!

2/3?

alcinnz, 6 days ago

Since I've established a couple graph viewers, we could use those to compose all the various "transcoding" (defined generously!) tools to tweak data however you want it. This could save as code for the Output Unit, whilst (with relatively little extra effort) providing a convenient tool to refine recorded images, audio, video, etc! Add a gesture to view results at any stage in the pipeline.

Maybe we'd add a few tools to use with it, as desired!

As for rendering text...

3/4!

alcinnz, 6 days ago

There'd be some Microsoft fonts we'd be practically expected to ship (non-commercial licensed). As for self-hosting the development of our own...

I'd need to render a menu of glyphs (labeling it before we have a font would be interesting... though we'd probably use Times or something), & overlay some draggable sprites upon the vector outline when editing an individual glyph.

Another editor could be used for the BIOS's font, based on the bitmap editor. Nudging towards compressibility!

4/4.5!

alcinnz, 6 days ago

As for auditory fonts... I've stated that I'd include a joystick in that form-factor. We could use it to select a parameter (in the Arithmetic Core) to nudge up & down as the voice reads out some text.

Or we could ship eSpeak's, since we'd be shipping their pronunciation rules! These could be edited as text.

For further creative tools... Maybe another metathread? This should be enough to self-host development of the OS.

5/5 Fin! Tomorrow: Collaborative editing!

alcinnz, 6 days ago

• Various upon copying data from, & pointers to, GElf_Sym objects to Elf_Data objects under lock with validation.

• Or from validated Elf_Data and Gelf_Sym both at separate given indices. Or at given validated index from validated GElf_Rela, or Gelf_Vernaux, GElf_Rel, GElf_Verneed, GElf_Move, GElf_Lib, etc.

• Same for Elf_Scn objects from GElf_Shdr.

So much of this looks practically identical!

2/3?

alcinnz, 6 days ago

• memcpy a GElf_Verdaux object to a validatedElf_Data at offset under lock. Or a GElf_Verdef.

• Copy P header to an indexed ELF header.

• Copy a validated & given E header to the given ELF file's one.

Skipping of the locked/validated data copying code... Beyond to say some are getters which returns the data they've copied...

• Routines to shift pointers forward/back to skip "notes".

• C headers require slightly more conversions between 64bit & 32bit variants.

3/4?

alcinnz, 6 days ago

• Lookuptable & routine for the memory sizes of different ELF headers.

• E header getter can skip looking so caller can aggregate the links.

• Various supporting macros & another sizing lookuptable.

• Iterators, with substantial initialization.

• Resolve relative pointers.

• Initialize new ELF sections, different routines for different types.

• Lookup a data section.

• Lazily-initialized (why?) version number.

• Write to a mmap'd file.

• Gather symbols from an ELF file.

4/5!

alcinnz, 6 days ago

• Gather bitflags, with separate routines for P/E/Data/S headers & the root file.

• Error reporting.

• Retrieve an AR header.

• Endianness conversion.

• Cloning ELF files.

• Interpret ELF file-reading commands.

• tsearch a data chunk.

• Retrieve an index for the S header, non-trivial.

• Fallback upon mmap failure.

• Linear-scan for certain headers, multiple routines.

• Find a certain string pointer.

• Bitwidth-appropriate table lookups.

• Clear a new E header.

5/5.5!

alcinnz, 6 days ago

• Initialize a new P header.

• Some bitwidth-appropriate table lookups calls the looked up method.

• Initialize & free an ELF file.

• ZLib compression & decompression.

• Lookup "AR" symbol.

• Checksums.

• Writing to an, ideally, mmap'ed file.

• Compute a default E header.

But mostly it defines C datastructures defining the ELF format.

5.5/5.5 Fin! Tomorrow: ELF commands!