x-yl

el mes pasadodiscuss

> GPU sharing with docker and VMs

This should work without needing a reboot. You do have to bind the vfio driver at boot, but the archwiki gives a script to unbind vfio and load the Nvidia driver: https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF#Bi...

Which anecdotally worked fine on my RTX3050.

I did give up as well though, all of this is just too much of a faff. Hopefully Intel continues to make strides with their discrete graphics. They are the only manufacturer without DRM blocking this feature which the hardware can obviously do.

x-yl

el mes pasadodiscuss

Through the magic of Claude, here is what the two hundred and eleven javascript files that GitHub loads on accessing an empty repo with just .md files (https://github.com/github-samples/.github):

  ┌─────────────────┬───────┬────────────┬────────────┐
  │    Category     │ Files │ Total Size │ Total Time │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Copilot         │    32 │   1,749 KB │   1,141 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ GraphQL / Relay │     4 │   1,629 KB │     190 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Primer Design   │     4 │   1,617 KB │     329 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Highlighting    │     4 │   1,048 KB │     414 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Code View       │    14 │     966 KB │   1,226 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ React Core      │     6 │     692 KB │     446 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ UI Components   │    26 │     674 KB │   1,541 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ SVG             │     2 │     634 KB │      51 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Code Editor     │     9 │     615 KB │     366 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Vendored        │    17 │     608 KB │     986 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Issues          │    13 │     589 KB │     504 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Markdown        │     8 │     321 KB │     198 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Runtime         │    12 │     263 KB │     807 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ HTML Parsing    │     2 │     235 KB │     152 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Navigation      │    11 │     230 KB │     362 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Web Components  │     7 │     229 KB │     540 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Comments        │     4 │     131 KB │     146 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Analytics       │     5 │     103 KB │     348 ms │
  ├─────────────────┼───────┼────────────┼────────────┤
  │ Other           │    32 │     484 KB │    2099 ms │
  └─────────────────┴───────┴────────────┴────────────┘

Times given for a 150 Mbps WiFi connection.

Some personal highlights:

- Syntax Highlighting for every obscure language under the sun. Seems like the language analysis they do the repository does nothing.

- Shipping the editor on pages where there is no editor

- Shipping Copilot prompts. Incredible. { prompt:\"Analyze the test coverage of this codebase. Identify areas with missing or insufficient tests and add comprehensive test cases to improve coverage.\" }

- Just a javascript file with a massive 500K SVG.

- I don't really know anything about GraphQL & Relay. But 1.4 megabytes of generated ASTs?

- Shipping Protobuf, YAML, Lodash (hashing, unicode, collections), Typebox, GSAP and Framer

x-yl

hace 2 mesesdiscuss

In my experience LLMs (I speak mainly of Claude Code & Cursor) write very poor quality Rust.

They treat it like it's JavaScript, falling back to using String/&str needlessly instead of making new types. They do ugly `static Mutex<Refcell<` a-la global JS variables for info sharing instead of working out the lifetimes to do it properly. It loves making functions infallible and then panic-ing within them and certainly I wouldn't use them for unsafe at all - they hallucinate safety comments which are in fact, totally unsound.

Of course these are all surmountable with an experienced developer to regularly step in and unfuck the code, but forcing them into 'harder' territory where every problem is not solved by a .clone() and an Arc<Mutex<>> means they will spend minutes 'thinking' about basic lifetime issues until I step in and add the missing `move` in a closure.

x-yl

hace 2 mesesdiscuss

The simplicity of Gorilla is attractive but for better compression ratios without too much extra compute I'd instead recommend Sprintz: https://github.com/dblalock/sprintz.

The downside is that (a) Sprintz requires the data to be quantised to fixed point integers, usually fine if the data is coming out of a sensor of some sort and (b) the Huffman coding step of Sprintz requires dynamic memory allocation, whilst Gorilla is almost trivially implemented without it.

Also see Chimp, which proposes some small tweaks to Gorilla to improve its performance: https://dl.acm.org/doi/abs/10.14778/3551793.3551852

x-yl

hace 2 mesesdiscuss

It says at the bottom:

> This story is based on original reporting by Christina Larson for National Geographic. Read the full feature on National Geographic

https://www.nationalgeographic.com/science/article/artificia...

x-yl

hace 9 mesesdiscuss

An optional challenge gives an implementation of arrays for jlox at least: https://github.com/munificent/craftinginterpreters/blob/4a84...

Submissions

Is generative AI replacing junior workers?

comments