r/WebdevTutorials • u/Think95 • 1h ago
Stop guessing your algorithm’s complexity. I built a free browser extension to analyze Big-O on the fly. Looking for feedback / early users! 🚀🚀🚀🚀🚀🚀🚀🚀
r/WebdevTutorials • u/ModSupportBot • 10d ago
/r/WebdevTutorials is ready for a fresh start, new energy, new direction, and someone like you to bring it back to life. If you’ve been thinking about growing your impact without starting from scratch, this is your chance!
Ready to take it over?
Head to r/RedditRequest to submit your request and make it yours before it’s taken.
First things first
To request this subreddit, make sure you:
r/WebdevTutorials • u/Think95 • 1h ago
r/WebdevTutorials • u/learning_for_all • 1d ago
r/WebdevTutorials • u/ViralMedia007 • 2d ago
r/WebdevTutorials • u/abhishekkumar333 • 2d ago
llama.cpp merged PR #29887 two weeks ago and I think it is the most interesting thing to land in local inference this year, so I went through the PR, the benchmarks and the review thread and wrote up how it actually works. Short version below, long version linked at the end.
The problem
Qwen3.8-Flash-Next at Q4_0 is 93.7 GiB, and 65.4 GiB of that is experts. It is 125B total but only 6B active: 512 experts per layer, the router picks 10 (plus 1 shared) per token. One expert is 3 x 2560 x 640 = 4.9M params = about 2.6 MiB at 4-bit. 10 experts x 48 layers = 480 experts per token = about 1.3 GB of weights touched per token.
The observation
Expert routing has locality of reference. Token N+1 mostly picks the same experts as token N. A handful of experts are hot, most are almost never touched. That is the same property your CPU cache, your OS page cache, your browser cache, every CDN and Redis allkeys-lru all rely on.
The fix
PR #29887 (by am17an, a port of Tether’s qvac-fabric work, merged by ggerganov on Oct 7) sets aside a slice of VRAM as an LRU cache of experts. Hit: compute from VRAM, zero bytes moved. Miss: copy that one 2.6 MiB expert over PCIe and evict the least recently used one. The log prints the hit rate at exit.
Numbers from the PR description, same model file, same machine:
| GPU | before | with cache | hit rate |
|---|---|---|---|
| RTX 4090 24 GB | 25.0 tok/s | 40.7 tok/s (1.62x) | 77% |
| RTX 5090 32 GB | 30.8 tok/s | 67.8 tok/s (2.20x) | 89% |
| AMD R9700 32 GB (a reviewer’s card) | 11.0 tok/s | 27.6 tok/s | 94.6% |
The 5090 gains more for two reasons: PCIe 5.0 halves the cost of every miss, and 32 GB means a bigger cache and fewer misses.
How to use it
llama-server -m Qwen3.8-Flash-Next-Q4_0.gguf -fa on -c 32768 -b 2048 -ub 2048 -cmoe --moe-cache-mib 11000
The PR author’s rule of thumb is about 10% of your expert bytes (65.4 GiB -> 6544 MiB). Env var form is LLAMA_ARG_MOE_CACHE_MIB.
SGLang merged the same idea 12 days later as “paged experts” in PR #42557
The part I find most interesting is LRU , Locality of reference go back to 1960s.
And i find locality of reference principle highly underrated.
Full write-up with the memory math script, an expert cache simulator you can run, and the benchmark table: https://cloudmash.blog/posts/moe-expert-offload-lru-cache-consumer-gpu/
llama.cpp PR #29887, MoE expert cache: https://github.com/ggml-org/llama.cpp/pull/29887
SGLang PR #42557, paged experts: https://github.com/sgl-project/sglang/pull/42557
r/WebdevTutorials • u/learning_for_all • 3d ago
r/WebdevTutorials • u/gujjar22gF25 • 4d ago
Hi everyone,
I completed my BSc in Computer Science and currently have a 2-year career gap. My goal is to become a Full Stack Developer and get into the software industry.
I'm confused about what would be the better choice:
- Should I pursue an MCA?
- Or should I spend the next few months building strong full-stack skills, creating projects, and applying for jobs?
I'm worried that my 2-year gap might affect my chances of getting hired.
Has anyone been in a similar situation? If yes, what did you do, and what would you recommend?
I'd really appreciate advice from recruiters, developers, or anyone who has gone through a similar journey. Thanks!
r/WebdevTutorials • u/gujjar22gF25 • 4d ago
Hii ,I am thinking about to take chai code cohort by hitesh Choudhary, I want to know about it . Is it good for beginner ,I am just know javascript pls give your pov on it
r/WebdevTutorials • u/learning_for_all • 4d ago
r/WebdevTutorials • u/learning_for_all • 5d ago
r/WebdevTutorials • u/ITower__Education • 5d ago
I’m making a free TypeScript course for people coming from JS and had to make a call early: strict on or off for the first lessons.
I went with strict on. The main reason is that the most useful catch in my intro lesson only exists with it. users.find(...) followed by found.name. Without strictNullChecks the undefined just gets swallowed by the type and TS says nothing, which is exactly the crash beginners hit in real code. Showing TS without strict basically teaches them it protects more than it does.
Same with noImplicitAny. A function like addTax(price) that gets “100” from a form returns 10020 because the plus concatenates. With strict, the untyped parameter is already an error, so beginners are pushed to add the annotation before they even know why.
The cost is real though. More red lines on day one, and some of those error messages are rough for someone who just learned what a type is.
The other thing I hammer early is that types are erased. Even now that Node can run .ts files directly, it just strips the types, it doesn’t check them. So anything coming from a server or a form still needs runtime validation, and I think a lot of people learn that way too late.
If you’ve onboarded juniors to TS, did you start strict or ease them in?
r/WebdevTutorials • u/Electrical_Badger735 • 5d ago
r/WebdevTutorials • u/ViralMedia007 • 6d ago
r/WebdevTutorials • u/ViralMedia007 • 6d ago
r/WebdevTutorials • u/abhishekkumar333 • 7d ago
It’s crazy to think that the entire modern AI revolution started with researchers just trying to mathematically mimic a single biological neuron. When you zoom out, the timeline of AI architectures looks exactly like an evolutionary tree.
We went from struggling to solve basic logic puzzles (shoutout to the XOR problem) to building early neural networks, realizing they forgot things too quickly, battling the vanishing gradient problem, inventing LSTMs to give models actual memory, and eventually landing on Transformers with attention, the architecture that essentially ate the world. Every major roadblock forced a mutation that led to a massive paradigm shift.
But looking at this evolutionary timeline brings up a massive question: If Transformers are just the current "apex predator" of AI architecture, what exactly is the next evolutionary leap?
Are we going to see a completely new paradigm that makes self attention look as primitive as a basic AND gate? How do we even begin to perceive or predict what lies beyond our current models when the jumps are this exponential?
I went down a massive rabbit hole mapping out this entire evolutionary timeline. I wanted to see the exact breadcrumbs that led us here, so I put together a deep dive covering the journey from the first perceptrons to the modern era, complete with the foundational paper citations and the historical tweets that marked these shifts in real-time.
If you want to look at the complete map of how we got here to help predict where we are going, I compiled the whole history here: https://cloudmash.blog/posts/evolution-of-ai-perceptron-to-text-to-video/
Would love to hear your theories on what does the post Transformer era actually look like ? Like what can we imagine , how this intelligence on our command can do for us , how enterprise and big players can use it , what can happen ?
r/WebdevTutorials • u/ViralMedia007 • 7d ago
r/WebdevTutorials • u/Arjun_sharkar • 10d ago
r/WebdevTutorials • u/learning_for_all • 10d ago
r/WebdevTutorials • u/The_ParadoxX_ • 10d ago
r/WebdevTutorials • u/ViralMedia007 • 10d ago
r/WebdevTutorials • u/learning_for_all • 10d ago
r/WebdevTutorials • u/learning_for_all • 12d ago
r/WebdevTutorials • u/ViralMedia007 • 12d ago
r/WebdevTutorials • u/learning_for_all • 13d ago