A moe model you say? How kawaii is it? uwu
I hate that I laughed at this. Thanks ;)
Readit Newsnoxa commented on Arcee Trinity Mini: US-Trained Moe Model arcee.ai/blog/the-trinity... · Posted by u/hurrycane
noxa commented on Serflings is a remake of The Settlers 1 simpleguide.net/serflings... · Posted by u/doener
It's a shame that Pioneers of Pagonia doesn't stick to the same strict path-network mechanic, that was my favourite part of the earlier Settlers that later went away.
From the recommendation of another commenter, here's a more recent indie game that seems focused exactly on that style of path logistics:
As a Settlers 1/2 fan I spent quite a bit of time in The Colonists - can recommend it if you liked the road building/flag mechanics and the chill gameplay.
Thank you for saying what this entire blog post doesn't. It's actually disrespectful of Google to launch this without even a mention of the fact that it is based on VSCode.
+1 - it also doesn't support remote ssh (the open vsx variant), so is probably only focused at local web design development vibe coding ;(
Should have just been an extension with a paid plan.
noxa commented on Kvcached: Virtualized, elastic KV cache for LLM serving on shared GPUs notion.so/yifanqiao/Solve... · Posted by u/Jrxing
Neat! As someone working in this space and feeling like I've been taking crazy pills from how these "duh, CPU solved this 30 years ago" things keep slipping it's great to see more people bridging the gap! Unfortunately CUDA/HIP (and the entire stack beneath them) virtual memory management ops are very expensive host APIs (remapping a big block of pages can be O(n^2) with page count and fully synchronize host/device (forced wait idle), take kernel locks, etc) so it hasn't been viable in all cases. If your workloads are submit/wait with host in the loop the VM tricks are ok but if you are trying to never block the GPU (pipeline depth > 0) you really want to avoid anything that does a page table modification (until we get GPUs that can pipeline those). vkQueueBindSparse is one of the few async APIs I've seen, and CUDA has cuMemMapArrayAsync but I haven't yet used it (because arrays are annoying and without being able to inspect the driver I'm sure it's probably doing the wrong thing).
I've had good luck with indirection tables used during lookup inside of the kernels consuming/producing the kvcache data - it's essentially user-mode remapping like they do here: you can publish a buffer offset table and threads are uniform, have coalesced reads to the table, and cache the offsets no problem. You have the same memory locality issues as VM (contiguous virtual but potentially random physical) but are not limited to device page sizes and since you can update while work is in-flight you can be much more aggressive about reuse and offload (enqueue DMA to cold storage to evict from VRAM, enqueue DMA to copy from cold memory into reused VRAM, enqueue offset table update, enqueue work using them, repeat - all without host synchronization). You can also defrag in-flight if you do want to try to restore the physical locality. It's nothing crazy and fairly normal in CPU land (or even classic virtual texturing), but in ML GPU land I could write a big paper on it and call it SuperDuperFancyAttention4 and publish press releases...
As an old school TT/TTD fan this gives me so many good vibes :)
Been fun watching the progress and I do recommend people check out the demos on Steam if you just want to have a good nostalgia break even if the game isn't fully there yet.
Would be cool if this supported the various fp8 formats that have been shipped on GPUs recently!
noxa commented on Show HN: Hyvector – A fast and modern SVG editor hyvector.com... · Posted by u/jansan
Neat! I want this project to succeed.
A couple First Impression Experience pieces of feedback:
* when it first starts, how about a blank untitled document to play with, and maybe select a fun tool like the Bezier pencil as the initially selected tool. I was able and motivated to click around, realize there was no open document (probably the biggest stumbling block), create a new document, change the tool, and start playing, but many users won't be.
* it seems like a small thing, but please make the default canvas a bit larger (maybe 512 or 500 square). Again just more fun in that critical 10-20 second window, which is all most people will realistically give when checking out a new thing. If you can't hook 'em in that timeframe, they simply browse away and you lose a ton of folks.
Looks very good, thank you for sharing.
Agreed! Looks great, but I did immediately click the pencil to doodle and was disappointed nothing happened. When I created a new document and tried to use the pencil nothing happened. I never figured out how to use it. I tried the Bezier tool and was able to add some nodes but was not able to manipulate them with any of the tools. Maybe dragging is entirely broken on Chrome/Windows?
And is Seattle, “Jeff Bezos” says the crosswalk is sponsored by Amazon Prime and exhorts you not to tax the rich.
I love that it played the Bo Burnham "jeff bezos" song - such incredible art.
noxa commented on Show HN: Game Bub – open-source FPGA retro emulation handheld eli.lipsitz.net/posts/int... · Posted by u/elipsitz
Fantastic project and great writeup! The screen tradeoff with needing triple buffering but getting integer scaling was interesting to hear about - any feeling as to whether it adds human-noticeable latency vs. original hardware?
Very cool to see my project posted here!
The motivation behind a lot of this was to have community LLVM implementations of runtime functions normally provided by the vendor libraries (C math, printf, malloc), but if you implement one function you may as well implement them all.
Realistically, the infrastructure behind this project is more relevant than the C library calls themselves. The examples in the linked documentation can be used for any arbitrary C/C++ just as well as the LLVM C library, it's simply statically linking. This is what allowed me to compile and run more complicated things like libc++ and DOOM on the GPU as well. The RPC interface can also be used to implement custom host services from the GPU, or used to communicate between any two shared memory processes.
Just wanted to say thanks for pushing on this front! I'm not using the libc portion but the improvements to clang/llvm that allow this to work have been incredible. When I was looking a few months back the only options that felt practical for writing large amounts of device code were cuda/hip or opencl and a friend suggested I just try C _and it worked_. Definitely made my "most practical/coolest that it actually works" list for 2024 :)