Most people prefer traditional architecture
131 by alihm | 46 comments on Hacker News.
Tampilkan postingan dengan label Hacker News. Tampilkan semua postingan
Tampilkan postingan dengan label Hacker News. Tampilkan semua postingan
Selasa, 15 September 2026
Senin, 14 September 2026
Minggu, 13 September 2026
Sabtu, 12 September 2026
Kamis, 10 September 2026
New top story on Hacker News: Show HN: DOOM in the kernel, or fibers in eBPF
Show HN: DOOM in the kernel, or fibers in eBPF
6 by ayles | 2 comments on Hacker News.
Some time ago my coworker who was working on first version of Perforator ( https://ift.tt/B7Q8I5J ) kept talking about eBPF, so I got curious about its ISA and restrictions. That was around the time I read about DOOM on pregnancy test, so I thought: "what if someone run DOOM inside of Linux kernel in eBPF? Surely, with some restrictions, this should still be possible?" I started to play around with it somewhere in 2024 - first stripping DOOM to bare minimum that is needed for showcase, simplifying code and trying to pass first restrictions that I encountered - function limit, recursion, memory access and checks. I tried to do this by hand, but it was, well, tedious labor. So I changed direction and instead started to do some of the things with LLVM-passes - rewriting memory access, simplifying and rewriting loops etc. But there were just so many corners. And given absence of time and all, I forgot about this project. But couple months ago I thought: "LLMs are quite good nowadays, so why not try again this time with more hands". I tried different approaches on how memory access could be "virtualized", how loops can be made bounded, and in general - how to run unbounded logic on such a machine. When I got DOOM running, I got carried away. Approach was so "generic", so it would be a crime not to try to run more things. And now we have it - lua running on xdp hot path, llama2 working with softfloats, and even cpython, that did not fit initially into 1M verifier budget, is running there now thanks to freplace. There is ton of work to do in order to make programs run faster, to make integration easier, but working examples are already there.
6 by ayles | 2 comments on Hacker News.
Some time ago my coworker who was working on first version of Perforator ( https://ift.tt/B7Q8I5J ) kept talking about eBPF, so I got curious about its ISA and restrictions. That was around the time I read about DOOM on pregnancy test, so I thought: "what if someone run DOOM inside of Linux kernel in eBPF? Surely, with some restrictions, this should still be possible?" I started to play around with it somewhere in 2024 - first stripping DOOM to bare minimum that is needed for showcase, simplifying code and trying to pass first restrictions that I encountered - function limit, recursion, memory access and checks. I tried to do this by hand, but it was, well, tedious labor. So I changed direction and instead started to do some of the things with LLVM-passes - rewriting memory access, simplifying and rewriting loops etc. But there were just so many corners. And given absence of time and all, I forgot about this project. But couple months ago I thought: "LLMs are quite good nowadays, so why not try again this time with more hands". I tried different approaches on how memory access could be "virtualized", how loops can be made bounded, and in general - how to run unbounded logic on such a machine. When I got DOOM running, I got carried away. Approach was so "generic", so it would be a crime not to try to run more things. And now we have it - lua running on xdp hot path, llama2 working with softfloats, and even cpython, that did not fit initially into 1M verifier budget, is running there now thanks to freplace. There is ton of work to do in order to make programs run faster, to make integration easier, but working examples are already there.
Rabu, 09 September 2026
Selasa, 08 September 2026
Senin, 07 September 2026
Minggu, 06 September 2026
Sabtu, 05 September 2026
Jumat, 04 September 2026
New top story on Hacker News: Show HN: TERMy – A fast terminal assistant that does not use LLMs
Show HN: TERMy – A fast terminal assistant that does not use LLMs
1 by gioscarab | 0 comments on Hacker News.
I love research and development, you may have heard of me because of PJON (Padded Jittering Operative Network). It is a network protocol I started developing in 2010, which was recently implemented in silicon by the ETH Zurich university thanks to the research of Pius Sieber. I am excited to share with you TERMy, a terminal assistant built on top of the NPC-Forge framework. Unlike everything else being built today, TERMy does not use embeddings, machine-learning or LLMs. It runs on the CPU (even on a Raspberry Pi Zero) both in the terminal or client-side in a browser tab and responds in milliseconds. It is a cynical but very knowledgeable Linux terminal assistant that translates your natural language into shell commands without relying on a single artificial neuron. I had a chance to focus for 2 months on my personal projects since early July, during the strange times of AI price hikes and the end of subsidized tokenmaxing. I was curious to see if I could develop from scratch a terminal assistant capable of handling simple natural language requests. I have a bad memory and got used to ask to copilot "activate the virtual environment" or similar trivial operations spending a non negligible sum every month. I started thinking, maybe I can do something to make my workflow more efficient? Do I really need trillions of parameters to accomplish those tasks? How it Works When you type a prompt, it goes through a lightweight NLU pipeline written in ~1000 lines of Python that implement the following steps: 1. Strip expletives, interjections, encouraging, discouraging and thanking words (remove noise) 2. Sentiment analysis 3. Exact Match (very fast) 4. Template Match (slower) 5. Probabilistic Match (even slower) Step 5 relies on: 1. IDF (Inverse Document Frequency) to identify rare words. 2. BOW (Bag Of Words) to accommodate word inversions. 3. IDF weighted Levenshtein to safely handle typos. Permission gating is hardcoded into the dataset and enforced for all potentially destructive commands, so it's inherently safer than letting an unpredictable LLM run wild on your machine. - TERMy in operation: https://www.youtube.com/watch?v=qeIp0xePLBg - Variance and typo tolerance: https://www.youtube.com/watch?v=tQvGDk6fkk0 - Copilot integration: https://www.youtube.com/watch?v=Wzzouhq2a8A - Advanced features: https://www.youtube.com/watch?v=qeIp0xePLBg - Source Code: https://ift.tt/bMvQfV3
1 by gioscarab | 0 comments on Hacker News.
I love research and development, you may have heard of me because of PJON (Padded Jittering Operative Network). It is a network protocol I started developing in 2010, which was recently implemented in silicon by the ETH Zurich university thanks to the research of Pius Sieber. I am excited to share with you TERMy, a terminal assistant built on top of the NPC-Forge framework. Unlike everything else being built today, TERMy does not use embeddings, machine-learning or LLMs. It runs on the CPU (even on a Raspberry Pi Zero) both in the terminal or client-side in a browser tab and responds in milliseconds. It is a cynical but very knowledgeable Linux terminal assistant that translates your natural language into shell commands without relying on a single artificial neuron. I had a chance to focus for 2 months on my personal projects since early July, during the strange times of AI price hikes and the end of subsidized tokenmaxing. I was curious to see if I could develop from scratch a terminal assistant capable of handling simple natural language requests. I have a bad memory and got used to ask to copilot "activate the virtual environment" or similar trivial operations spending a non negligible sum every month. I started thinking, maybe I can do something to make my workflow more efficient? Do I really need trillions of parameters to accomplish those tasks? How it Works When you type a prompt, it goes through a lightweight NLU pipeline written in ~1000 lines of Python that implement the following steps: 1. Strip expletives, interjections, encouraging, discouraging and thanking words (remove noise) 2. Sentiment analysis 3. Exact Match (very fast) 4. Template Match (slower) 5. Probabilistic Match (even slower) Step 5 relies on: 1. IDF (Inverse Document Frequency) to identify rare words. 2. BOW (Bag Of Words) to accommodate word inversions. 3. IDF weighted Levenshtein to safely handle typos. Permission gating is hardcoded into the dataset and enforced for all potentially destructive commands, so it's inherently safer than letting an unpredictable LLM run wild on your machine. - TERMy in operation: https://www.youtube.com/watch?v=qeIp0xePLBg - Variance and typo tolerance: https://www.youtube.com/watch?v=tQvGDk6fkk0 - Copilot integration: https://www.youtube.com/watch?v=Wzzouhq2a8A - Advanced features: https://www.youtube.com/watch?v=qeIp0xePLBg - Source Code: https://ift.tt/bMvQfV3
Kamis, 03 September 2026
Senin, 31 Agustus 2026
New top story on Hacker News: Konrad Zuse Museum shutting down due to lack of funding
Konrad Zuse Museum shutting down due to lack of funding
54 by virtualritz | 13 comments on Hacker News.
https://ift.tt/k05GAWO... (auf Deutsch)
54 by virtualritz | 13 comments on Hacker News.
https://ift.tt/k05GAWO... (auf Deutsch)
New top story on Hacker News: Show HN: Floe – an open-source plugin for sample libraries – CLAP/VST3/AU
Show HN: Floe – an open-source plugin for sample libraries – CLAP/VST3/AU
9 by windell | 2 comments on Hacker News.
I'm Sam, I make sample libraries (as FrozenPlain). These sample libraries run inside Floe, my audio plugin for Linux, macOS and Windows. It's designed for musicians, composers and producers - typically people involved with film/TV/game scoring or ambient music. I open-sourced it primarily because I'm very fond of this philosophy and I want to open the door for serving a wider audience than just my own libraries. It's totally free, no sign-ups. You'll need a DAW. To try it: - Download and install Floe: https://floe.audio - Download your choice of free packages: https:floe.audio/packages#community-packages or https://ift.tt/dRWwjDN - Install the packages using Floe's 'Install Package' button. https://ift.tt/swlWTxX I'm curious about HN's thoughts regarding the open-source nature, directions I could take for expanding the audience, and the Lua based sample-library it has ( https://ift.tt/wGcOD0Y ). Thanks.
9 by windell | 2 comments on Hacker News.
I'm Sam, I make sample libraries (as FrozenPlain). These sample libraries run inside Floe, my audio plugin for Linux, macOS and Windows. It's designed for musicians, composers and producers - typically people involved with film/TV/game scoring or ambient music. I open-sourced it primarily because I'm very fond of this philosophy and I want to open the door for serving a wider audience than just my own libraries. It's totally free, no sign-ups. You'll need a DAW. To try it: - Download and install Floe: https://floe.audio - Download your choice of free packages: https:floe.audio/packages#community-packages or https://ift.tt/dRWwjDN - Install the packages using Floe's 'Install Package' button. https://ift.tt/swlWTxX I'm curious about HN's thoughts regarding the open-source nature, directions I could take for expanding the audience, and the Lua based sample-library it has ( https://ift.tt/wGcOD0Y ). Thanks.
Minggu, 30 Agustus 2026
Langganan:
Postingan (Atom)