The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Running TempleOS in user space without virtualization
TempleOS is an experimental OS designed to be simple and self-hosted with a JIT compiler. I was mesmerized by it but didn't like the hassle of using virtual machines to boot it up and move files around from the virtual drive.<p>My project lets you run TempleOS as an app of some sort instead of using a virtual machine to run it - this brings a lot of benefits like speed, seamless filesystem integration (virtual machine development with stock TempleOS is really a pain.), command-line mode where you can code in HolyC on the command line instead of TempleOS' GUI.<p>Its user-space nature lets it do networking quite easily with the FFI - it even features an IRC server, client and a wiki server!<p>I've also added a bunch of third-party games and software written for TempleOS on the Community folder, I hope you people take a look and enjoy!
Show HN: Running TempleOS in user space without virtualization
TempleOS is an experimental OS designed to be simple and self-hosted with a JIT compiler. I was mesmerized by it but didn't like the hassle of using virtual machines to boot it up and move files around from the virtual drive.<p>My project lets you run TempleOS as an app of some sort instead of using a virtual machine to run it - this brings a lot of benefits like speed, seamless filesystem integration (virtual machine development with stock TempleOS is really a pain.), command-line mode where you can code in HolyC on the command line instead of TempleOS' GUI.<p>Its user-space nature lets it do networking quite easily with the FFI - it even features an IRC server, client and a wiki server!<p>I've also added a bunch of third-party games and software written for TempleOS on the Community folder, I hope you people take a look and enjoy!
Show HN: Running TempleOS in user space without virtualization
TempleOS is an experimental OS designed to be simple and self-hosted with a JIT compiler. I was mesmerized by it but didn't like the hassle of using virtual machines to boot it up and move files around from the virtual drive.<p>My project lets you run TempleOS as an app of some sort instead of using a virtual machine to run it - this brings a lot of benefits like speed, seamless filesystem integration (virtual machine development with stock TempleOS is really a pain.), command-line mode where you can code in HolyC on the command line instead of TempleOS' GUI.<p>Its user-space nature lets it do networking quite easily with the FFI - it even features an IRC server, client and a wiki server!<p>I've also added a bunch of third-party games and software written for TempleOS on the Community folder, I hope you people take a look and enjoy!
Show HN: 5 Years Ago I made the Recovery Kit, I just made the RK2
The Recovery Kit 2 is another cyberdeck that for me is part computer, part backup device, and part functional movie prop. It's been fun to build, and the HN community has been great with ideas- especially around hosting and getting me off Squarespace. I hope you all enjoy!
Show HN: 5 Years Ago I made the Recovery Kit, I just made the RK2
The Recovery Kit 2 is another cyberdeck that for me is part computer, part backup device, and part functional movie prop. It's been fun to build, and the HN community has been great with ideas- especially around hosting and getting me off Squarespace. I hope you all enjoy!
Show HN: 5 Years Ago I made the Recovery Kit, I just made the RK2
The Recovery Kit 2 is another cyberdeck that for me is part computer, part backup device, and part functional movie prop. It's been fun to build, and the HN community has been great with ideas- especially around hosting and getting me off Squarespace. I hope you all enjoy!
Show HN: Using Google Sheets as the back end/APIs of your app
Hello everyone!<p>At a company I worked for, we needed to develop an MVP (basically a web page) and apply certain business logic to a Google Drive spreadsheet that was frequently updated by the Sales team.<p>In this case, we had two options:<p>Develop a backend to replace the current spreadsheet and have the sales team use it as a new "backoffice" - This would take a very long time, and if the hypothesis we were testing was wrong, it would be time wasted.<p>Create the web page and use Google's SDK to extract data from the spreadsheet.<p>We chose to go with the second option because it was quicker. Indeed, it was much faster than creating a new backoffice. But not as quick as we imagined. Integrating with Google's SDK requires some effort, especially to handle the OAuth logic, configure it in the console, and understand the documentation (which is quite shallow, by the way).<p>Anyway! We did the project and I realized that maybe other devs might have encountered similar issues. Therefore, I developed a tool that transforms Google spreadsheets into "realtime APIs" with PATCH, GET, POST, and DELETE methods.<p>Since it's a product for devs, I think it would be cool to hear your opinions. It's still quite primitive, but the basic features already work.<p><a href="https://zerosheets.com" rel="nofollow">https://zerosheets.com</a>
Show HN: Using Google Sheets as the back end/APIs of your app
Hello everyone!<p>At a company I worked for, we needed to develop an MVP (basically a web page) and apply certain business logic to a Google Drive spreadsheet that was frequently updated by the Sales team.<p>In this case, we had two options:<p>Develop a backend to replace the current spreadsheet and have the sales team use it as a new "backoffice" - This would take a very long time, and if the hypothesis we were testing was wrong, it would be time wasted.<p>Create the web page and use Google's SDK to extract data from the spreadsheet.<p>We chose to go with the second option because it was quicker. Indeed, it was much faster than creating a new backoffice. But not as quick as we imagined. Integrating with Google's SDK requires some effort, especially to handle the OAuth logic, configure it in the console, and understand the documentation (which is quite shallow, by the way).<p>Anyway! We did the project and I realized that maybe other devs might have encountered similar issues. Therefore, I developed a tool that transforms Google spreadsheets into "realtime APIs" with PATCH, GET, POST, and DELETE methods.<p>Since it's a product for devs, I think it would be cool to hear your opinions. It's still quite primitive, but the basic features already work.<p><a href="https://zerosheets.com" rel="nofollow">https://zerosheets.com</a>
Show HN: Mazelit - My wife and I released our first game
Hey folks,<p>About a year ago my wife and I, both closing in on 40, quit our jobs at Red Hat to start a games company and learn game development. Many things happened along the road, and about a week ago we released our first (small) game on Steam.<p><a href="https://store.steampowered.com/app/2816120/Mazelit/" rel="nofollow">https://store.steampowered.com/app/2816120/Mazelit/</a><p>The demo is free to play up to level 8 (the final game plays up to level 80) and we'd appreciate any feedback you have, whether it's for the store page or the game itself.<p>We made the game in Godot 4.2 in roughly 3 months and I was working full time next to it. Since we ran into a bunch of roadblocks, we decided to also offer the entire source code up as a DLC in case someone wants to go look how we implemented the game, mod the game, or compile it for a different platform. The only thing we can't redistribute with the game code is the Steamworks SDK, which is available for download from Steam. (The game minus integration is fully runnable without the SDK, though.)<p>Cheers and happy weekend!
Show HN: Mazelit - My wife and I released our first game
Hey folks,<p>About a year ago my wife and I, both closing in on 40, quit our jobs at Red Hat to start a games company and learn game development. Many things happened along the road, and about a week ago we released our first (small) game on Steam.<p><a href="https://store.steampowered.com/app/2816120/Mazelit/" rel="nofollow">https://store.steampowered.com/app/2816120/Mazelit/</a><p>The demo is free to play up to level 8 (the final game plays up to level 80) and we'd appreciate any feedback you have, whether it's for the store page or the game itself.<p>We made the game in Godot 4.2 in roughly 3 months and I was working full time next to it. Since we ran into a bunch of roadblocks, we decided to also offer the entire source code up as a DLC in case someone wants to go look how we implemented the game, mod the game, or compile it for a different platform. The only thing we can't redistribute with the game code is the Steamworks SDK, which is available for download from Steam. (The game minus integration is fully runnable without the SDK, though.)<p>Cheers and happy weekend!
Show HN: Mazelit - My wife and I released our first game
Hey folks,<p>About a year ago my wife and I, both closing in on 40, quit our jobs at Red Hat to start a games company and learn game development. Many things happened along the road, and about a week ago we released our first (small) game on Steam.<p><a href="https://store.steampowered.com/app/2816120/Mazelit/" rel="nofollow">https://store.steampowered.com/app/2816120/Mazelit/</a><p>The demo is free to play up to level 8 (the final game plays up to level 80) and we'd appreciate any feedback you have, whether it's for the store page or the game itself.<p>We made the game in Godot 4.2 in roughly 3 months and I was working full time next to it. Since we ran into a bunch of roadblocks, we decided to also offer the entire source code up as a DLC in case someone wants to go look how we implemented the game, mod the game, or compile it for a different platform. The only thing we can't redistribute with the game code is the Steamworks SDK, which is available for download from Steam. (The game minus integration is fully runnable without the SDK, though.)<p>Cheers and happy weekend!
Show HN: Next-token prediction in JavaScript
What inspired this project today was watching this amazing video by 3Blue1Brown called "But what is a GPT?" on Youtube (<a href="https://www.youtube.com/watch?v=wjZofJX0v4M" rel="nofollow">https://www.youtube.com/watch?v=wjZofJX0v4M</a> - I highly recommend watching it). I added it to the repo for reference.<p>When it clicked in my head that "knowing a fact" is nearly synonymous with predicting a word (or series of words), I wanted to put it to the test, because it seemed so simple. I chose JavaScript because I can exploit the way it structures objects to aid in the modeling of language.<p>For example:<p>"I want to be at the beach",
"I will do it later",
"I want to know the answer",
...<p>becomes:<p><pre><code> {
I: {
want: {
to: {
be: { ... },
know: { ... }
}
},
will: { ... }
},
...
}
</code></pre>
in JavaScript. You can exploit the language's fast object lookup speed to find known sentences this way, rather than recursively searching text - which is the convention and would take forever or not work at all considering there are several full books loaded in by default (and it could support many more).<p>Accompanying research yielded learnings about what "tokens" and "embeddings" are, what is meant by "training", and most of the rest - though I'm still learning jargon. I wrote a script to iterate over every single word of every single book to rank how likely it is that word will appear next, if given a cursor, and extended that to rank entire phrases. The base decoder started out what I'll call "token-agnostic" - didn't care if you were looking for the next letter... word... pixel... it's the same logic. But actually it's not, and it soon evolved into a text (language) model. But I have plans to get into image generation next (next-pixel prediction), using this. Overall the concepts are similar, but there are differences primarily around extraction and formatting.<p>Goals of the project:<p>- Demystify LLMs for people, show that it's just regular code that does normal stuff<p>- Actually make a pretty good LLM in JavaScript, with a version at least capable of running in a browser tab
Show HN: Next-token prediction in JavaScript
What inspired this project today was watching this amazing video by 3Blue1Brown called "But what is a GPT?" on Youtube (<a href="https://www.youtube.com/watch?v=wjZofJX0v4M" rel="nofollow">https://www.youtube.com/watch?v=wjZofJX0v4M</a> - I highly recommend watching it). I added it to the repo for reference.<p>When it clicked in my head that "knowing a fact" is nearly synonymous with predicting a word (or series of words), I wanted to put it to the test, because it seemed so simple. I chose JavaScript because I can exploit the way it structures objects to aid in the modeling of language.<p>For example:<p>"I want to be at the beach",
"I will do it later",
"I want to know the answer",
...<p>becomes:<p><pre><code> {
I: {
want: {
to: {
be: { ... },
know: { ... }
}
},
will: { ... }
},
...
}
</code></pre>
in JavaScript. You can exploit the language's fast object lookup speed to find known sentences this way, rather than recursively searching text - which is the convention and would take forever or not work at all considering there are several full books loaded in by default (and it could support many more).<p>Accompanying research yielded learnings about what "tokens" and "embeddings" are, what is meant by "training", and most of the rest - though I'm still learning jargon. I wrote a script to iterate over every single word of every single book to rank how likely it is that word will appear next, if given a cursor, and extended that to rank entire phrases. The base decoder started out what I'll call "token-agnostic" - didn't care if you were looking for the next letter... word... pixel... it's the same logic. But actually it's not, and it soon evolved into a text (language) model. But I have plans to get into image generation next (next-pixel prediction), using this. Overall the concepts are similar, but there are differences primarily around extraction and formatting.<p>Goals of the project:<p>- Demystify LLMs for people, show that it's just regular code that does normal stuff<p>- Actually make a pretty good LLM in JavaScript, with a version at least capable of running in a browser tab
Show HN: I made a new sensor out of 3D printer filament for my PhD
Here's a "behind-the-scenes" look at my development of a cool sensor during my PhD (electrical engineering). This sensor is only about 1/3 of my total research for my degree and took about a year.<p>I've been on HN for a while now and I've seen my fair share of posts about the woes of pursuing a PhD. Now that I'm done with mine I wanna share some anecdotal evidence that doing a PhD can actually be enjoyable (not necessarily easy) and also be doable in 3 years.<p>When I started I knew I didn't want to work on something that would never leave the lab or languish in a dissertation PDF no one will ever read. Thanks to an awesome advisor I think I managed to thread the needle between simplicity and functionality.<p>Looking back, the ideas and methods behind it are pretty straightforward, but getting there took some doing. It’s funny how things seem obvious once you've figured them out!<p>Oh, I love creating GUIs for sensor data and visualizations as you'll see -- it's such a game changer! pyqtgraph is my go-to at the moment - such a great library.
Show HN: I made a new sensor out of 3D printer filament for my PhD
Here's a "behind-the-scenes" look at my development of a cool sensor during my PhD (electrical engineering). This sensor is only about 1/3 of my total research for my degree and took about a year.<p>I've been on HN for a while now and I've seen my fair share of posts about the woes of pursuing a PhD. Now that I'm done with mine I wanna share some anecdotal evidence that doing a PhD can actually be enjoyable (not necessarily easy) and also be doable in 3 years.<p>When I started I knew I didn't want to work on something that would never leave the lab or languish in a dissertation PDF no one will ever read. Thanks to an awesome advisor I think I managed to thread the needle between simplicity and functionality.<p>Looking back, the ideas and methods behind it are pretty straightforward, but getting there took some doing. It’s funny how things seem obvious once you've figured them out!<p>Oh, I love creating GUIs for sensor data and visualizations as you'll see -- it's such a game changer! pyqtgraph is my go-to at the moment - such a great library.
Show HN: I made a new sensor out of 3D printer filament for my PhD
Here's a "behind-the-scenes" look at my development of a cool sensor during my PhD (electrical engineering). This sensor is only about 1/3 of my total research for my degree and took about a year.<p>I've been on HN for a while now and I've seen my fair share of posts about the woes of pursuing a PhD. Now that I'm done with mine I wanna share some anecdotal evidence that doing a PhD can actually be enjoyable (not necessarily easy) and also be doable in 3 years.<p>When I started I knew I didn't want to work on something that would never leave the lab or languish in a dissertation PDF no one will ever read. Thanks to an awesome advisor I think I managed to thread the needle between simplicity and functionality.<p>Looking back, the ideas and methods behind it are pretty straightforward, but getting there took some doing. It’s funny how things seem obvious once you've figured them out!<p>Oh, I love creating GUIs for sensor data and visualizations as you'll see -- it's such a game changer! pyqtgraph is my go-to at the moment - such a great library.
Show HN: I made a new sensor out of 3D printer filament for my PhD
Here's a "behind-the-scenes" look at my development of a cool sensor during my PhD (electrical engineering). This sensor is only about 1/3 of my total research for my degree and took about a year.<p>I've been on HN for a while now and I've seen my fair share of posts about the woes of pursuing a PhD. Now that I'm done with mine I wanna share some anecdotal evidence that doing a PhD can actually be enjoyable (not necessarily easy) and also be doable in 3 years.<p>When I started I knew I didn't want to work on something that would never leave the lab or languish in a dissertation PDF no one will ever read. Thanks to an awesome advisor I think I managed to thread the needle between simplicity and functionality.<p>Looking back, the ideas and methods behind it are pretty straightforward, but getting there took some doing. It’s funny how things seem obvious once you've figured them out!<p>Oh, I love creating GUIs for sensor data and visualizations as you'll see -- it's such a game changer! pyqtgraph is my go-to at the moment - such a great library.
Show HN: I made a new sensor out of 3D printer filament for my PhD
Here's a "behind-the-scenes" look at my development of a cool sensor during my PhD (electrical engineering). This sensor is only about 1/3 of my total research for my degree and took about a year.<p>I've been on HN for a while now and I've seen my fair share of posts about the woes of pursuing a PhD. Now that I'm done with mine I wanna share some anecdotal evidence that doing a PhD can actually be enjoyable (not necessarily easy) and also be doable in 3 years.<p>When I started I knew I didn't want to work on something that would never leave the lab or languish in a dissertation PDF no one will ever read. Thanks to an awesome advisor I think I managed to thread the needle between simplicity and functionality.<p>Looking back, the ideas and methods behind it are pretty straightforward, but getting there took some doing. It’s funny how things seem obvious once you've figured them out!<p>Oh, I love creating GUIs for sensor data and visualizations as you'll see -- it's such a game changer! pyqtgraph is my go-to at the moment - such a great library.
Show HN: Deco.cx – realtime TypeScript web editor
Hi, HN.
Gui, Lucis, and the deco.cx team here — we're a bunch of Brazilians building an open-source, all-in-one web editor for the modern TypeScript dev. Check out our GitHub at <a href="https://github.com/deco-cx/deco">https://github.com/deco-cx/deco</a> and discover more at our site <a href="https://deco.cx/" rel="nofollow">https://deco.cx/</a>.<p>We built frontend tools at a hyper-growth e-commerce platform for 9 years. Deco.cx is the thing that we wish existed when we were managing hundreds of enterprise-grade React-based websites.<p>The gist is: JSX, HTMX, TypeScript, Tailwind and Deno. All visually editable in a beautiful, collaborative, REALTIME (!) admin UI. Great for devs, great for content.<p>In essence, we're a git-based TypeScript-first configuration management system. We take TypeScript code that represents your site, your entities, your UI, and we allow anyone to "save" configuration and content based on those types.<p>It's great for developers, because you can code directly on the web, or on your machine, and get instant feedback. You "export interface Props" and boom, an automatic form is generated. It's great for the business users, the content editors, because you just press "." (dot) in your keyboard and you go into a visual edit mode for the page you're at right now. Everything the developer exported in TypeScript is editable.<p>And when you hit "publish", it's already live, with a proper CDN, proper caching, everything already setup and just working. Ready to scale!<p>But you can't fly blind. We're democratizing pro-level tools for web analytics and observability by bundling in our Pro plan: fully-managed Plausible analytics and HyperDX observability. Check them out — these are great tools on their own, and they shine in the deco.cx platform bundle.<p>We don't want to be the only answer, we don't claim to be right about anything, we just want to make the friendly and accessible open-source tool that we wish existed when we were junior developers. If you want to participate, please join our discord community at <a href="https://deco.cx/discord" rel="nofollow">https://deco.cx/discord</a><p>on open-source: our admin UI core is not ready for prime time, we're working to open-source it this year. but basically everything else, our integrations, templates and configuration management runtime are all open-source already! take a look at these: <a href="https://github.com/deco-cx/deco">https://github.com/deco-cx/deco</a> <a href="https://github.com/deco-cx/apps">https://github.com/deco-cx/apps</a> <a href="https://github.com/deco-sites/storefront">https://github.com/deco-sites/storefront</a> Making the admin UI core extensible and open source is a MAIN OBJECTIVE for this year, so expect news here soon!<p>Thanks for your support!
Show HN: Deco.cx – realtime TypeScript web editor
Hi, HN.
Gui, Lucis, and the deco.cx team here — we're a bunch of Brazilians building an open-source, all-in-one web editor for the modern TypeScript dev. Check out our GitHub at <a href="https://github.com/deco-cx/deco">https://github.com/deco-cx/deco</a> and discover more at our site <a href="https://deco.cx/" rel="nofollow">https://deco.cx/</a>.<p>We built frontend tools at a hyper-growth e-commerce platform for 9 years. Deco.cx is the thing that we wish existed when we were managing hundreds of enterprise-grade React-based websites.<p>The gist is: JSX, HTMX, TypeScript, Tailwind and Deno. All visually editable in a beautiful, collaborative, REALTIME (!) admin UI. Great for devs, great for content.<p>In essence, we're a git-based TypeScript-first configuration management system. We take TypeScript code that represents your site, your entities, your UI, and we allow anyone to "save" configuration and content based on those types.<p>It's great for developers, because you can code directly on the web, or on your machine, and get instant feedback. You "export interface Props" and boom, an automatic form is generated. It's great for the business users, the content editors, because you just press "." (dot) in your keyboard and you go into a visual edit mode for the page you're at right now. Everything the developer exported in TypeScript is editable.<p>And when you hit "publish", it's already live, with a proper CDN, proper caching, everything already setup and just working. Ready to scale!<p>But you can't fly blind. We're democratizing pro-level tools for web analytics and observability by bundling in our Pro plan: fully-managed Plausible analytics and HyperDX observability. Check them out — these are great tools on their own, and they shine in the deco.cx platform bundle.<p>We don't want to be the only answer, we don't claim to be right about anything, we just want to make the friendly and accessible open-source tool that we wish existed when we were junior developers. If you want to participate, please join our discord community at <a href="https://deco.cx/discord" rel="nofollow">https://deco.cx/discord</a><p>on open-source: our admin UI core is not ready for prime time, we're working to open-source it this year. but basically everything else, our integrations, templates and configuration management runtime are all open-source already! take a look at these: <a href="https://github.com/deco-cx/deco">https://github.com/deco-cx/deco</a> <a href="https://github.com/deco-cx/apps">https://github.com/deco-cx/apps</a> <a href="https://github.com/deco-sites/storefront">https://github.com/deco-sites/storefront</a> Making the admin UI core extensible and open source is a MAIN OBJECTIVE for this year, so expect news here soon!<p>Thanks for your support!