htsh's comments

On: Does anybody like React?

[htsh]

i much prefer svelte but the rest of the world does not

[steve_taylor → htsh]

I was all in on Svelte and SvelteKit until I started encountering CSS weirdness caused by a bug that the Svelte developers said is "by design", namely that components' CSS isn't removed from the document after the last instance of that component is no longer rendered. This resulted in a situation in which styles became dependent on the navigation path the user takes, leading to weird an unpredictable layout issues. I couldn't stomach solving this by using Tailwind.

Then Svelte 5 came along and made Svelte more like React. At first, there were just a few simple runes, but then the runes started proliferating like crazy to solve other runes' problems. At that point, Svelte was dead to me and I went back to React/Next.

The right path for Svelte to take would have been to continue to refine Svelte 4.

[maxbond → steve_taylor]

Interesting, so if I'm understanding correctly, component A's style was supposed to change when component B was present, and this was implemented as styling rules in component B? Why was Tailwind necessary rather than moving these rules to component A (which I know would probably require some gnarly selectors)?

I don't want to be a "you should've double bagged it" guy, I'm just curious. Svelte is not the be all and all, if you moved on to greener pastures more power to you.

[maxbond → htsh]

There are dozens of us

[jtbaker → htsh]

Launching a new product in SvelteKit! Coming from Vue and it has been mostly great.

[holler → htsh]

I feel the same way about ember.js :]

On: Phi-4-reasoning-vision and the lessons of training a multimodal reasoning model

[htsh]

yes! especially b/c i want to process a lot of email and directories full of old, personal documents

On: Apple's 512GB Mac Studio vanishes, a quiet acknowledgment of the RAM shortage

[htsh]

are we sure the RAM market will stop being insane in a year or two or could this be the new norm?

[gzread → htsh]

Every ten years the RAM cartel raises prices (it's not really about AI, see Gamer's Nexus) and every ten years it is forced to lower them again.

[onli → htsh]

Why should it be the new norm? We have an abnormal situation now, of massive amounts of investor money being poured into unprofitable bets, that this time had the side effect of eating up hardware components. There are two possible outcomes:

1. Yes, it's the new normal, then production capacity will be increased and prices fall.

2. No, it's not the new normal, the bubble pops and component prices come crashing down when buyers default etc.

Option 2 has been the normal outcome of these situations so far. But sure, questions remains how long all of this will take.

[lukan → onli]

Option 3: the global wars increase and continue to be the new normal with shipping routes disturbed until the climax, china annexes Taiwan.

In that case prices will continue to rise (among other things).

[mikkupikku → htsh]

I don't know if it'll be a year or two, hard to say exactly when the AI bubble will pop, but I feel quite certain it's coming. The AI stuff is great but most of the money being thrown around to all these different companies is mostly going to be wasted. Investors don't know who the winners and losers will be, just like when people were investing in pets.com instead of amazon.com.

On: Claude Code: connect to a local model when your quota runs out

[htsh]

thanks! came in here to ask this.

we can do much better with a cheap model on openrouter (glm 4.7, kimi, etc.) than anything that I can run on my lowly 3090 :)

[parthsareen → htsh]

Also recently added ollama launch claude if you want to connect to cloud models from there :)

On: The unreasonable effectiveness of an LLM agent loop with tool use

[htsh]

I have been doing this with claude code and openai codex and/or cline. One of the three takes the first pass (usually claude code, sometimes codex), then I will have cline / gemini 2.5 do a "code review" and offer suggestions for fixes before it applies them.

On: Qwen3: Think deeper, act faster

[htsh]

curious, why the 30b MoE over the 32b dense for local coding?

I do not know much about the benchmarks but the two coding ones look similar.

[Casteil → htsh]

The MoE version with 3b active parameters will run significantly faster (tokens/second) on the same hardware, by about an order of magnitude (i.e. ~4t/s vs ~40t/s)

[genpfault → Casteil]

> The MoE version with 3b active parameters

~34 tok/s on a Radeon RX 7900 XTX under today's Debian 13.

[tgtweak → genpfault]

And vmem use?

[genpfault → tgtweak]

~18.6 GiB, according to nvtop.

ollama 0.6.6 invoked with:

    # server
    OLLAMA_FLASH_ATTENTION=1 OLLAMA_KV_CACHE_TYPE=q8_0 ollama serve

    # client
    ollama run --verbose qwen3:30b-a3b

~19.8 GiB with:

    /set parameter num_ctx 32768

[tgtweak → genpfault]

Very nice, should run nicely on a 3090 as well.

TY for this.

update: wow, it's quite fast - 70-80t/s on LM Studio with a few other applications using GPU.

On: OpenVINO AI effects for Audacity

[htsh]

A lot of us have ryzen / nvidia combos... hopefully, soon, though.

[bigbones → htsh]

Openvino runs fine on AMD last I checked

[_carbyau_ → bigbones]

Maybe it does, however the system requirements page makes it looks like it supports everything BUT AMD.

https://docs.openvino.ai/2024/about-openvino/release-notes-o...

[7speter → _carbyau_]

It supports AMD cpus because, if I understand correctly, AMD licenses x86 from Intel, so it shares the same bits needed to run openVINO as Intel’s cpus.

Go look at CPUs benchmarks on Phoronix; AMD Ryzen cpus regularly trounce Intel cpus using openVINO inference.

On: Official DeepSeek R1 Now on Ollama

[htsh]

assuming you want to run entirely in GPU, with 12gb vram, your sweet spot is likely the distill 14b qwen at a 4bit quant. so just run:

ollama run deepseek-r1:14b

generally, if the model file size < your vram, it is gonna run well. this file is 9gb.

if you don't mind slower generation, you can run models that fit within your vram + ram, and ollama will handle that offloading of layers for you.

so the 32b should run on your system, but it is gonna be much slower as it will be using GPU + CPU.

prob of interest: https://simonwillison.net/2025/Jan/20/deepseek-r1/

-h

[jordiburgos → htsh]

Thank you!! I just loaded it a fits in memory as you said.

I am testing it now and seems quite fast giving the responses for a local model.

On: I turned my open-source project into a full-time business

[htsh]

As a longtime user of nodemailer, thank you.

I am gonna check out emailengine for future work.

On: MobileDiffusion: Rapid text-to-image generation on-device

[htsh]

Dreambooth was kinda great?

That said, I agree that I wish there were more done post-research towards products with some of this stuff.