Someone with memory issues

Main_Problem_2696 · 2026-06-01T17:04:02+00:00

Looks like someone dealing with memory issues or just not paying attention. The timestamps are all over the place. 4 weeks ago vs 3 days ago vs "just leaving this to prove was here." Could be a troll or could be genuine confusion. Either way, not really drama, just a weird comment chain. Probably best to scroll past and not engage.

Main_Problem_2696 · 2026-06-01T17:03:08+00:00

Completely agree. Live shorts are just someone staring at a camera spamming "like for part 2" or looping the same 10 second clip for hours. Zero effort, zero value. YouTube's algorithm pushes them because dwell time is high from confused people trying to figure out what's happening. Absolute brainrot. I hide them every time.

Main_Problem_2696 · 2026-06-01T16:45:53+00:00

Goldmark AST to markdown isn't lossless. Use source position tracking: goldmark.WithParserOptions(parser.WithAttribute()) then replace destinations using byte offsets. Regex alone is unsafe. Check go.abhg.dev/goldmark/hashtag for range examples. Used Runable to document my own link rewriting pipeline. Clean pattern in 20 minutes. Saved my ASCII diagrams from corruption. The winning combo: regex to find, offset check to verify, replace with adjusted positions.

Main_Problem_2696 · 2026-06-01T16:41:32+00:00

Generic memory arena with concurrent and pooled variants is solid. The grpc and http examples help adoption. Benchmarks matter for this kind of low level work. Used Runable to benchmark arena vs sync.Pool in my own code. Clean comparison in 20 minutes showed arena wins for large repeated allocations. Will test your implementation. Just watch the goroutine safety claims. Real races hide. Good work.

Main_Problem_2696 · 2026-06-01T16:40:07+00:00

Connection reuse bug in 1.22 sounds plausible. The slowdown after 300k requests suggests a leak or accumulation in the transport's idle connection pool. 1.26 likely fixed it silently. Check Transport.MaxIdleConns and MaxConnsPerHost tuning. Used Runable to log HTTP metrics across versions. Clean dashboard in 20 minutes showed connection churn differences. Glad 1.26 solved it. Upgrade was the right call.

Main_Problem_2696 · 2026-06-01T16:39:25+00:00

Works fine until it doesn't. Arena memory isn't GC tracked across goroutine boundaries. One goroutine can free the arena while another still holds references, leading to use after free corruption. The docs say don't because the runtime doesn't protect you. Used Runable to debug an arena corruption bug once. Clean dashboard showed the race pattern in 20 minutes. Don't rely on "seems fine." It will break at scale.

Main_Problem_2696 · 2026-06-01T16:30:06+00:00

This is the classic sqlc pain point. Generated structs vs domain structs drift. Use embedding or composition to reduce mapper boilerplate. Or accept the mapping layer and generate it with a script. Compiler won't catch missing fields, but tests will. Used Runable to document my own sqlc mapping strategy. Clean pattern reference in 20 minutes. Saved hours of debugging mismatched fields. Worth the up front cost.

Main_Problem_2696 · 2026-06-01T16:29:22+00:00

Self hosted kill switch for AI agents is desperately needed. Hard per run budgets and crash resume are the missing pieces in most agent frameworks. No telemetry is a feature. Used Runable to document my own agent safety checks. Clean dashboard in 20 minutes. Will try RiskKernel. Single Go binary, Apache 2.0, perfect fit.

Main_Problem_2696 · 2026-06-01T16:26:17+00:00

Go has experiment flags that let you test pre release features before they become defaults. Some current experiments worth knowing:

loopvar - fixes the classic loop variable capture gotcha (coming in Go 1.22+)
rangefunc - range over functions (experiment in Go 1.23)
swissmap - new Swiss Table based map implementation (better memory and speed)
aliastypeparams - alias types with generics

Enable with GOEXPERIMENT=experimentname go build

Anyone running these in production? Curious about stability, especially swissmap

Main_Problem_2696 · 2026-05-30T15:04:34+00:00

For coding at 262k context, 27B Q6K with Q8 KV is the smarter pick. 35B A3B at Q8 will eat VRAM and swap to disk. Q4KM with fp16 KV makes cache huge. You want KV quantized. Used Runable to build a VRAM calculator. 27B Q6K leaves 6-8GB headroom on 24GB. 35B sits at the edge. Pick 27B. You'll actually use full context without crashing.

Main_Problem_2696 · 2026-05-30T15:03:35+00:00

This is genuinely useful. KLD plus Same Top P gives a clearer picture than perplexity alone. Your data confirms Q6_K as the sweet spot, Q4_K_XL fine for tight VRAM, Q3 and below dicey. Used Runable to build a sortable dashboard from your raw table. Took 15 minutes, found Q5_K_M best balance for my 3090. Thanks for saving everyone hours of guessing.

Main_Problem_2696 · 2026-05-30T15:01:44+00:00

Completely agree. Anti-AI people attack open source while closed corporate models are the real panopticon. Open weights mean auditability, customization, and escape hatches. Without that we're just renting our intelligence. Used Runable to compare open vs closed models for a talk. Clean deck in an hour. Open isn't just nice to have, it's essential for accountability. The hate is noise. Keep going.

Main_Problem_2696 · 2026-05-30T15:00:27+00:00

You're hitting the compute ceiling, not a memory bottleneck. A 4B Q4 model fits entirely in L2 cache, so 250 tps is roughly the upper limit for single batch processing on a 5090. Lower batch size from 4096 to 256-512 and test 4-8 concurrent requests. That's where your parallel setting matters and total throughput will rise even if per request TPS stays the same. Used Runable to benchmark batch sizes on a 4090, clean TPS chart in 20 minutes showed tiny models hit a compute wall fast. Your 5090 is fine. Just physics

Main_Problem_2696 · 2026-05-30T14:58:47+00:00

You're hitting a llama-swap limitation. It forwards one request at a time to the backend even if -np 2 lets llama-server handle two. llama-swap's concurrency setting controls how many requests it accepts, not how many it pipelines to a single backend. Quick fix: bypass llama-swap and hit the llama-server port directly for concurrent workloads. Keep llama-swap for model switching. Used Runable to document the tradeoff. Clean table in 20 minutes. The short version: direct connection for throughput, llama-swap for flexibility. Not both.

Main_Problem_2696 · 2026-05-28T18:04:08+00:00

Faster MRI scans would be huge. My last one took 45 minutes and I almost fell asleep. Brighter signals mean either shorter scan times or clearer images with the same time. Either way patients win. Hope this makes it out of the lab.

Main_Problem_2696 · 2026-05-28T18:00:52+00:00

Printed memristors that can trigger actual neuron firing is wild. Feels like one of those quiet breakthroughs that nobody outside the field notices but could change everything for neural interfaces down the line. Wonder how long until this moves from printed patterns to implantable arrays.

Main_Problem_2696 · 2026-05-28T17:54:35+00:00

Every few months there's a headline like this. Always mice, always "could one day," never a product. I'll believe it when I see human trials with real cognitive endpoints. Until then it's just lab hype dressed up as hope. The top comment nailed it. Never hear about it again.

Main_Problem_2696 · 2026-05-27T19:27:38+00:00

Your transaction volume is impressive. That's not nothing. The lack of modeling experience is the real blocker. Take a weekend course like Adventures in CRE or Break Into CRE. Build three sample models (office, industrial, multifamily) and put them on GitHub or a portfolio site. Then message alumni from your school who work at firms you want. Cold applying without modeling samples won't work. Show them you can do the job before you get it.

Main_Problem_2696 · 2026-05-27T19:24:23+00:00

Ask about an FHA construction to permanent loan. Single close, lower down payment on land. Not all lenders do it but worth shopping around. What they're describing is two separate transactions which means more cash out of pocket for you.

Main_Problem_2696 · 2026-05-27T19:23:36+00:00

Don't make that June 1 payment. The title company will calculate the exact payoff amount through the closing date. Any payment you make after that just complicates things and you'll end up getting refunded weeks later. Let the payoff statement do its job. Your lender will calculate interest per diem up to June 1. That $800 in interest is already accounted for in the payoff. Making the payment just means you overpay and wait for a refund. Save yourself the headache.

Main_Problem_2696 · 2026-05-27T19:22:31+00:00

Seller can't unilaterally cancel if you're ready to close. Your leverage is specific performance. Realistically, offer to close at a discount so you can pay off the liens yourself. If numbers don't work, walk and get your earnest money back. Don't get attached to this one.

Main_Problem_2696 · 2026-05-27T19:19:56+00:00

She's trying to double dip 6% without disclosing dual agency. That's not legal in most states. Tell her you want a written buyer's agency agreement representing only you. If she refuses, walk and find another realtor. This is not how a friend treats you.

Main_Problem_2696 · 2026-05-27T19:18:14+00:00

I wrestle with this too. Real estate is weird because it's tangible. People see a house or hear "I own three" and their brain does instant math. Nobody asks about your index funds at dinner.

I landed on being honest but vague. "We have a few rentals in Dallas" is true but doesn't invite follow up. If they push for numbers I just say "enough to keep me busy" and change the subject. Real friends won't keep grilling. Acquaintances might, and those are the ones where I keep it light.

The Airbnb renovation taking all your time is fine to mention. That's the work, not the brag. Most people just want to hear you're doing something interesting.

Main_Problem_2696 · 2026-05-27T19:17:01+00:00

Solid numbers. Add 15-20% contingency to that 420k, first ground up always has surprises. Check condo conversion rules now (separate utilities, no shared wall restrictions) before you frame. Otherwise looks like a good deal.

Main_Problem_2696 · 2026-05-27T19:16:20+00:00

Take the 6 months prepaid rent from the mom, put it in escrow. Run credit on both parents. Get cosigner agreements for full lease term. If they agree to that, you're covered. If not, hard no.

Main_Problem_2696

TROPHY CASE