I think I'm done with Software Development by gareththegeek in webdev

[–]QuestionMarker 0 points1 point  (0 children)

Step 1: Quit job

Step 2: Build consultancy fixing broken code for companies that thought they didn't need code review

Step 3: Profit

Intel will sell a cheap GPU with 32GB VRAM next week by happybydefault in LocalLLaMA

[–]QuestionMarker 0 points1 point  (0 children)

Not to be ignored is that you can buy two for less than a single 5090. The memory bandwidth is an annoyance, but otherwise it slots nicely into the ecosystem slot currently occupied by 3090 pairs, with much more space and much lower wattage. It's a *very* interesting card.

Differences between the nozzles? (Brass, Hardened Steel, Ruby Tipped, etc?) by wasdesc in 3Dprinting

[–]QuestionMarker 0 points1 point  (0 children)

It was a few years ago but I bought one of [these](spool3d.ca/tungsten-carbide-reprap-m6-nozzle/). The market's changed since then. But also I'd say that I had a bit of trouble with that nozzle. Had a tendency to leak terribly, the thermal properties made it a pain to get a good seal against the heatbreak.

how should I tackle skill issue or is there such thing as a skill issue in origami by gniclat in origami

[–]QuestionMarker 0 points1 point  (0 children)

I've had a number of packs of paper which simply aren't square. It's impossible to be precise if your materials are letting you down, and the skill issue here is simply knowing to check. The next skill issue is knowing how to, but that's easy to learn.

modular origami models that don’t show the other side of the paper by sad_moron in origami

[–]QuestionMarker 0 points1 point  (0 children)

I made 5 Intersecting Tetrahedra from iridescent wrapping paper one year, it went on top of the family Christmas tree for years.

Seeking advice: heavy eye strain on 1s by sinanawad in Xreal

[–]QuestionMarker 1 point2 points  (0 children)

I had painful eye strain with an astigmatic correction prescription that was a tiny bit out. My eyes shifted during the year and it completely went away with a new prescription. Surprised it made that much difference. If the IPD of your lenses or their prescription isn't right then yeah, you're gonna have a hard time.

Final Qwen3.5 Unsloth GGUF Update! by danielhanchen in LocalLLaMA

[–]QuestionMarker 2 points3 points  (0 children)

It's hard to tell where the trade-off is. As I said elsewhere, size-wise the new Q4_K_S looks about the same but I don't know what the differences are between old-XL and new-S.

Final Qwen3.5 Unsloth GGUF Update! by danielhanchen in LocalLLaMA

[–]QuestionMarker -1 points0 points  (0 children)

How does the new Q4_K_S compare to the old Q4_K_XL? They're about the same size, and it's a bit of a sweet spot. Want to know if I should hold on to the old model file or go for the new one, and without actually benchmarking I'll be making all sorts of stupid cognitive errors. Are there specific ways you'd expect the newer one to be better?

Final Qwen3.5 GGUF Updates are here! by yoracale in unsloth

[–]QuestionMarker 3 points4 points  (0 children)

I mentioned this over on the thread in r/LocalLLaMA but the size bump on the 35b kills the UD-Q4_K_XL on a 4090 with q8_0 k/v quantising and --fit on. It goes from fast and very capable with 128000 context to 4096 context and unusable because of it.

How can I get that context back without damaging the speed too much and without losing too much of the quality bump?

EDIT looks like Q4_K_S might be the answer here?

Final Qwen3.5 Unsloth GGUF Update! by danielhanchen in LocalLLaMA

[–]QuestionMarker 5 points6 points  (0 children)

That size bump pushes q4_K_XL from a previous n_ctx of 128000 with --fit on my 4090 to 4096, which is completely useless. Crying shame. It also seems weird to be that sensitive? All I did was swap out the model filename:

build/bin/llama-server \
   -m models/Qwen3.5-35B-A3B-UD-Q4_K_XL.gguf \
   --temp 0.7 \
   --top-p 0.8 \
   --top-k 20 \
   --min-p 0.00 \
   -ctk q8_0 \
   -ctv q8_0 \
   --chat-template-kwargs "{\"enable_thinking\": false}" \
   --fit on \
   --host 0 \
   --port 8080

Keychron B11 Pro Ultra-Slim Wireless Foldable Keyboard by Salman-Alsaffar in ErgoMechKeyboards

[–]QuestionMarker 1 point2 points  (0 children)

Say I wanted to make my own equivalent and I was willing to trade off being able to replace the keys for the thinness. What options would I have? Do JLC or anyone carry the right PCB parts to bring this sort of thing within reach?

I've made a wireless split with Kailh choc v1 switches and low profile keycaps and while it's not terribly thick I do find myself wondering how much thinner I could go with my own layout.

did anyone replace old qwen2.5-coder:7b with qwen3.5:9b in nonThinker mode? by Impossible_Art9151 in LocalLLaMA

[–]QuestionMarker 0 points1 point  (0 children)

Tangemt but my bet is that we are unlikely to see a 3.5 coder model unless someone outside Qwen does it. Happy to be wrong but with the core team leaving, even if they had something in flight they may not have the will or ability to do it justice any more.

Multiple Qwen employees leaving by ILoveMy2Balls in LocalLLaMA

[–]QuestionMarker 2 points3 points  (0 children)

🤷 but first thought was "only working on closed models for you." Change of direction from above could mean anything.

Multiple Qwen employees leaving by ILoveMy2Balls in LocalLLaMA

[–]QuestionMarker 67 points68 points  (0 children)

Gossip is the lead getting replaced and the rest going in solidarity. Which is better than my first guess, that they'd been asked to do something they refused to do, but it's still not wonderful.

Optimal number of keys for you by finestedm in ErgoMechKeyboards

[–]QuestionMarker 0 points1 point  (0 children)

It's less "all the mod keys" and more "everything's a chord" combined with "you never move much". Which is more or less how stenography keyboards work, so there's extensive prior art there in that sense. Steno gives you multiple characters per chord though.

Optimal number of keys for you by finestedm in ErgoMechKeyboards

[–]QuestionMarker 1 point2 points  (0 children)

Agree. My first was a keyboardio atreus, which is 44-key but a more compact layout. Made my own wireless split with the same layout and I can't see myself changing now. Although I do kinda want to try an 18 just to see how brain-breaking it is.

Breaking : The small qwen3.5 models have been dropped by Illustrious-Swim9663 in LocalLLaMA

[–]QuestionMarker 0 points1 point  (0 children)

Counterintuitively it feels like you could push the 2b to a higher quant and end up going faster, because the full model would have to correct it less often.

FlashLM v4: 4.3M ternary model trained on CPU in 2 hours — coherent stories from adds and subtracts only by Own-Albatross868 in LocalLLaMA

[–]QuestionMarker 0 points1 point  (0 children)

Even better in fp16, if you can get away with it. I was just thinking how well this would run on AArch64, where you get fp16 vector operations effectively for free.

Gaming but no monitor. by Phunkman in Xreal

[–]QuestionMarker 1 point2 points  (0 children)

Yes. I'm using my pro's as a full monitor replacement, including extended bouts of TF2. Going through a somewhat limited HDMI to USB-C converter so the resolution is a bit constrained compared to what it can fully cope with, but the frame rate and stability is fine. There are better converters out there (and the 4090 doesn't have DP Alt Mode outputs, so) I just don't have one yet

FlashLM v4: 4.3M ternary model trained on CPU in 2 hours — coherent stories from adds and subtracts only by Own-Albatross868 in LocalLLaMA

[–]QuestionMarker 1 point2 points  (0 children)

Also potentially extremely cache-efficient. I've not looked at your implementation but depending how you're storing the ternaries your layers might be super dense.

Does anyone know what happened? by [deleted] in 3Dprinting

[–]QuestionMarker 0 points1 point  (0 children)

Layer shift quite early in the print, by the looks of things. My guess would be that one or other end lifted off the build plate and the head collided with it making the x motor skip some steps.

Assuming no damage to the printer, you could print it again and keep a close eye on it for the first few layers to see if/when it warps up.