The best Hacker News stories from Show from the past day
Latest posts:
Show HN: A collaborative pixel drawing game for when you're bored (Attempt #2)
Previous thread: <a href="https://news.ycombinator.com/item?id=30167391" rel="nofollow">https://news.ycombinator.com/item?id=30167391</a><p>Hello again HN!
It's been 3 months since I last submitted this project and the back-end server software melted down.<p>I was really bummed that many people didn't get to play, so I've spent most of my spare time since that last post completely rewriting the back-end server software using small, carefully selected dependencies (C99, sqlite, mongoose.ws & cJSON)
I've done some basic performance testing and I'm cautiously optimistic that it can now handle up to ~1000 concurrent users.<p>If you have any ideas for improvements, do let me know! Bots are permitted, but try and do something creative instead of just filling the canvas with junk :^)<p>You can view the source code for the new back-end here: <a href="https://github.com/vkoskiv/nmc2" rel="nofollow">https://github.com/vkoskiv/nmc2</a>
You can also check out a recent time-lapse here: <a href="https://www.youtube.com/watch?v=FUmnUvTqn6M" rel="nofollow">https://www.youtube.com/watch?v=FUmnUvTqn6M</a>
The time-lapse gets generated from the server log output using this tool: <a href="https://github.com/zouppen/pikselipeli-parser/" rel="nofollow">https://github.com/zouppen/pikselipeli-parser/</a><p>(Note to HN staff: It wouldn't let me repost this unless it had a 'slightly different url', hence the sneaky redirect there. If this is a big no-no, I apologize, otherwise feel free to swap out the URL to the redirected one :^))
Show HN: We optimize your finances, for free - Uprise.us
Show HN: We optimize your finances, for free - Uprise.us
Show HN: We optimize your finances, for free - Uprise.us
Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
Hey there HN! We're a pair of devs looking to get feedback for our open-source project.<p>We're remote engineers who have contracted for many clients overseas. There's a problem that all codebases share: Onboarding devs to a new codebase is hard no matter what.<p>We're also open-source engineers and learned about the techniques used in OSS to tackle the problem. Please give us your feedback.<p>Homepage: <a href="https://watermelon.tools/" rel="nofollow">https://watermelon.tools/</a><p>Repo: <a href="https://github.com/watermelontools/wm-extension" rel="nofollow">https://github.com/watermelontools/wm-extension</a><p>Install: <a href="https://marketplace.visualstudio.com/items?itemName=WatermelonTools.watermelon-tools" rel="nofollow">https://marketplace.visualstudio.com/items?itemName=Watermel...</a>
Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
Hey there HN! We're a pair of devs looking to get feedback for our open-source project.<p>We're remote engineers who have contracted for many clients overseas. There's a problem that all codebases share: Onboarding devs to a new codebase is hard no matter what.<p>We're also open-source engineers and learned about the techniques used in OSS to tackle the problem. Please give us your feedback.<p>Homepage: <a href="https://watermelon.tools/" rel="nofollow">https://watermelon.tools/</a><p>Repo: <a href="https://github.com/watermelontools/wm-extension" rel="nofollow">https://github.com/watermelontools/wm-extension</a><p>Install: <a href="https://marketplace.visualstudio.com/items?itemName=WatermelonTools.watermelon-tools" rel="nofollow">https://marketplace.visualstudio.com/items?itemName=Watermel...</a>
Show HN: Watermelon – open-source VSC ext. to document code and view Git blame
Hey there HN! We're a pair of devs looking to get feedback for our open-source project.<p>We're remote engineers who have contracted for many clients overseas. There's a problem that all codebases share: Onboarding devs to a new codebase is hard no matter what.<p>We're also open-source engineers and learned about the techniques used in OSS to tackle the problem. Please give us your feedback.<p>Homepage: <a href="https://watermelon.tools/" rel="nofollow">https://watermelon.tools/</a><p>Repo: <a href="https://github.com/watermelontools/wm-extension" rel="nofollow">https://github.com/watermelontools/wm-extension</a><p>Install: <a href="https://marketplace.visualstudio.com/items?itemName=WatermelonTools.watermelon-tools" rel="nofollow">https://marketplace.visualstudio.com/items?itemName=Watermel...</a>
Show HN: React Routing in 120 lines (including comments)
Show HN: React Routing in 120 lines (including comments)
Show HN: Fruits – Sell digital products via your website, newsletter, etc
Hi HN!<p>Whilst trying to build an online community for content creators, we failed!
Taking the learnings and stripping down our product to a true MVP, we now started working on "fruits", which allows creators to sell files such as ebooks, designs, checklists, music and online coachings online in less than two minutes.<p><a href="https://fruits.de/en" rel="nofollow">https://fruits.de/en</a><p>It works as simple as this:<p>1. upload a file at "fruits" & set a price
2. you will receive your individual fruits-sales-link
3. share the link wherever your customers are (e.g. website, newsletter, social media)<p>In addition, we also take care of the tedious office work such as invoicing and VAT collection for you, and this is completely automated.<p>What do you think? We are looking forward to your feedback!
Show HN: Fruits – Sell digital products via your website, newsletter, etc
Hi HN!<p>Whilst trying to build an online community for content creators, we failed!
Taking the learnings and stripping down our product to a true MVP, we now started working on "fruits", which allows creators to sell files such as ebooks, designs, checklists, music and online coachings online in less than two minutes.<p><a href="https://fruits.de/en" rel="nofollow">https://fruits.de/en</a><p>It works as simple as this:<p>1. upload a file at "fruits" & set a price
2. you will receive your individual fruits-sales-link
3. share the link wherever your customers are (e.g. website, newsletter, social media)<p>In addition, we also take care of the tedious office work such as invoicing and VAT collection for you, and this is completely automated.<p>What do you think? We are looking forward to your feedback!
Show HN: Fruits – Sell digital products via your website, newsletter, etc
Hi HN!<p>Whilst trying to build an online community for content creators, we failed!
Taking the learnings and stripping down our product to a true MVP, we now started working on "fruits", which allows creators to sell files such as ebooks, designs, checklists, music and online coachings online in less than two minutes.<p><a href="https://fruits.de/en" rel="nofollow">https://fruits.de/en</a><p>It works as simple as this:<p>1. upload a file at "fruits" & set a price
2. you will receive your individual fruits-sales-link
3. share the link wherever your customers are (e.g. website, newsletter, social media)<p>In addition, we also take care of the tedious office work such as invoicing and VAT collection for you, and this is completely automated.<p>What do you think? We are looking forward to your feedback!
Show HN: A Full-Stack Web Framework for Go
Hey HN! I want to share my side project with you. It's called Bud and it's a full-stack web framework for Go.<p>I created a short video to show you how to create a minimal Hacker News clone with Bud: <a href="https://www.youtube.com/watch?v=LoypcRqn-xA" rel="nofollow">https://www.youtube.com/watch?v=LoypcRqn-xA</a>.<p>The framework is free, open source and MIT Licensed. You can find it on Github: <a href="https://github.com/livebud/bud" rel="nofollow">https://github.com/livebud/bud</a>.<p>I started working on Bud 2 years ago after watching the introductory Laracast videos about the Laravel web framework. I was just blown away by how productive you can be in Laravel. However, like many of you, I've been so spoiled by Go. I didn't want to go back to writing PHP, so I decided to try creating Laravel for the Go ecosystem.<p>At this point, I just had the following goal:<p>• Be as productive as Laravel in a typed language like Go.<p>I got the first version working in 6 months and tried building a blog from it... It fell flat. You needed to scaffold all these files just to get started. If you're coming from Rails or Laravel you may shrug, this is pretty normal. Unfortunately, I've also been spoiled by the renaissance in frontend frameworks like Next.js. What I love about Next is that it starts out barebones and every file you add incrementally enhances your web application. This keeps the initial complexity under control.<p>With these newly discovered constraints, I started working on the next iteration. Bud should:<p>• Generate files only as you need them. Keep these generated files away from your application code and give developers the choice to keep them out of source control.<p>• Feel like using a modern JS framework. This means it should work with modern frontend frameworks like Svelte and React, support live reload and have server-side rendering for better performance and SEO.<p>With these new goals, the Bud you see today started to take shape. But along the way, I discovered a few more project goals:<p>• The framework should be extensible from Day 1. Bud is too ambitious for one person. We're going to need an ambitious community behind this framework.<p>• Bud should be able to provide high-level APIs for developers while compiling down to performant low-level Go code for production.<p>• Bud should compile to a single binary. With platforms like Fly.io and Heroku, these days it's easy to not care about this, but I still cherish the idea that I can build a single binary that contains my entire web app and secure copy it up to a tiny server that doesn't even have Go installed.<p>It's still super early days. You can find the the Roadmap on Github: <a href="https://github.com/livebud/bud/discussions/9" rel="nofollow">https://github.com/livebud/bud/discussions/9</a>. I encourage you to contribute your thoughts.<p>And here's the current documentation for what's already in Bud: <a href="https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f9917c5033e5205c69" rel="nofollow">https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f991...</a>. Comments are enabled for anyone to chime in.<p>I have big plans for the framework. I hope you'll join me on this journey to build ambitious websites faster with Go!
Show HN: A Full-Stack Web Framework for Go
Hey HN! I want to share my side project with you. It's called Bud and it's a full-stack web framework for Go.<p>I created a short video to show you how to create a minimal Hacker News clone with Bud: <a href="https://www.youtube.com/watch?v=LoypcRqn-xA" rel="nofollow">https://www.youtube.com/watch?v=LoypcRqn-xA</a>.<p>The framework is free, open source and MIT Licensed. You can find it on Github: <a href="https://github.com/livebud/bud" rel="nofollow">https://github.com/livebud/bud</a>.<p>I started working on Bud 2 years ago after watching the introductory Laracast videos about the Laravel web framework. I was just blown away by how productive you can be in Laravel. However, like many of you, I've been so spoiled by Go. I didn't want to go back to writing PHP, so I decided to try creating Laravel for the Go ecosystem.<p>At this point, I just had the following goal:<p>• Be as productive as Laravel in a typed language like Go.<p>I got the first version working in 6 months and tried building a blog from it... It fell flat. You needed to scaffold all these files just to get started. If you're coming from Rails or Laravel you may shrug, this is pretty normal. Unfortunately, I've also been spoiled by the renaissance in frontend frameworks like Next.js. What I love about Next is that it starts out barebones and every file you add incrementally enhances your web application. This keeps the initial complexity under control.<p>With these newly discovered constraints, I started working on the next iteration. Bud should:<p>• Generate files only as you need them. Keep these generated files away from your application code and give developers the choice to keep them out of source control.<p>• Feel like using a modern JS framework. This means it should work with modern frontend frameworks like Svelte and React, support live reload and have server-side rendering for better performance and SEO.<p>With these new goals, the Bud you see today started to take shape. But along the way, I discovered a few more project goals:<p>• The framework should be extensible from Day 1. Bud is too ambitious for one person. We're going to need an ambitious community behind this framework.<p>• Bud should be able to provide high-level APIs for developers while compiling down to performant low-level Go code for production.<p>• Bud should compile to a single binary. With platforms like Fly.io and Heroku, these days it's easy to not care about this, but I still cherish the idea that I can build a single binary that contains my entire web app and secure copy it up to a tiny server that doesn't even have Go installed.<p>It's still super early days. You can find the the Roadmap on Github: <a href="https://github.com/livebud/bud/discussions/9" rel="nofollow">https://github.com/livebud/bud/discussions/9</a>. I encourage you to contribute your thoughts.<p>And here's the current documentation for what's already in Bud: <a href="https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f9917c5033e5205c69" rel="nofollow">https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f991...</a>. Comments are enabled for anyone to chime in.<p>I have big plans for the framework. I hope you'll join me on this journey to build ambitious websites faster with Go!
Show HN: A Full-Stack Web Framework for Go
Hey HN! I want to share my side project with you. It's called Bud and it's a full-stack web framework for Go.<p>I created a short video to show you how to create a minimal Hacker News clone with Bud: <a href="https://www.youtube.com/watch?v=LoypcRqn-xA" rel="nofollow">https://www.youtube.com/watch?v=LoypcRqn-xA</a>.<p>The framework is free, open source and MIT Licensed. You can find it on Github: <a href="https://github.com/livebud/bud" rel="nofollow">https://github.com/livebud/bud</a>.<p>I started working on Bud 2 years ago after watching the introductory Laracast videos about the Laravel web framework. I was just blown away by how productive you can be in Laravel. However, like many of you, I've been so spoiled by Go. I didn't want to go back to writing PHP, so I decided to try creating Laravel for the Go ecosystem.<p>At this point, I just had the following goal:<p>• Be as productive as Laravel in a typed language like Go.<p>I got the first version working in 6 months and tried building a blog from it... It fell flat. You needed to scaffold all these files just to get started. If you're coming from Rails or Laravel you may shrug, this is pretty normal. Unfortunately, I've also been spoiled by the renaissance in frontend frameworks like Next.js. What I love about Next is that it starts out barebones and every file you add incrementally enhances your web application. This keeps the initial complexity under control.<p>With these newly discovered constraints, I started working on the next iteration. Bud should:<p>• Generate files only as you need them. Keep these generated files away from your application code and give developers the choice to keep them out of source control.<p>• Feel like using a modern JS framework. This means it should work with modern frontend frameworks like Svelte and React, support live reload and have server-side rendering for better performance and SEO.<p>With these new goals, the Bud you see today started to take shape. But along the way, I discovered a few more project goals:<p>• The framework should be extensible from Day 1. Bud is too ambitious for one person. We're going to need an ambitious community behind this framework.<p>• Bud should be able to provide high-level APIs for developers while compiling down to performant low-level Go code for production.<p>• Bud should compile to a single binary. With platforms like Fly.io and Heroku, these days it's easy to not care about this, but I still cherish the idea that I can build a single binary that contains my entire web app and secure copy it up to a tiny server that doesn't even have Go installed.<p>It's still super early days. You can find the the Roadmap on Github: <a href="https://github.com/livebud/bud/discussions/9" rel="nofollow">https://github.com/livebud/bud/discussions/9</a>. I encourage you to contribute your thoughts.<p>And here's the current documentation for what's already in Bud: <a href="https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f9917c5033e5205c69" rel="nofollow">https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f991...</a>. Comments are enabled for anyone to chime in.<p>I have big plans for the framework. I hope you'll join me on this journey to build ambitious websites faster with Go!
Show HN: A Full-Stack Web Framework for Go
Hey HN! I want to share my side project with you. It's called Bud and it's a full-stack web framework for Go.<p>I created a short video to show you how to create a minimal Hacker News clone with Bud: <a href="https://www.youtube.com/watch?v=LoypcRqn-xA" rel="nofollow">https://www.youtube.com/watch?v=LoypcRqn-xA</a>.<p>The framework is free, open source and MIT Licensed. You can find it on Github: <a href="https://github.com/livebud/bud" rel="nofollow">https://github.com/livebud/bud</a>.<p>I started working on Bud 2 years ago after watching the introductory Laracast videos about the Laravel web framework. I was just blown away by how productive you can be in Laravel. However, like many of you, I've been so spoiled by Go. I didn't want to go back to writing PHP, so I decided to try creating Laravel for the Go ecosystem.<p>At this point, I just had the following goal:<p>• Be as productive as Laravel in a typed language like Go.<p>I got the first version working in 6 months and tried building a blog from it... It fell flat. You needed to scaffold all these files just to get started. If you're coming from Rails or Laravel you may shrug, this is pretty normal. Unfortunately, I've also been spoiled by the renaissance in frontend frameworks like Next.js. What I love about Next is that it starts out barebones and every file you add incrementally enhances your web application. This keeps the initial complexity under control.<p>With these newly discovered constraints, I started working on the next iteration. Bud should:<p>• Generate files only as you need them. Keep these generated files away from your application code and give developers the choice to keep them out of source control.<p>• Feel like using a modern JS framework. This means it should work with modern frontend frameworks like Svelte and React, support live reload and have server-side rendering for better performance and SEO.<p>With these new goals, the Bud you see today started to take shape. But along the way, I discovered a few more project goals:<p>• The framework should be extensible from Day 1. Bud is too ambitious for one person. We're going to need an ambitious community behind this framework.<p>• Bud should be able to provide high-level APIs for developers while compiling down to performant low-level Go code for production.<p>• Bud should compile to a single binary. With platforms like Fly.io and Heroku, these days it's easy to not care about this, but I still cherish the idea that I can build a single binary that contains my entire web app and secure copy it up to a tiny server that doesn't even have Go installed.<p>It's still super early days. You can find the the Roadmap on Github: <a href="https://github.com/livebud/bud/discussions/9" rel="nofollow">https://github.com/livebud/bud/discussions/9</a>. I encourage you to contribute your thoughts.<p>And here's the current documentation for what's already in Bud: <a href="https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f9917c5033e5205c69" rel="nofollow">https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f991...</a>. Comments are enabled for anyone to chime in.<p>I have big plans for the framework. I hope you'll join me on this journey to build ambitious websites faster with Go!
Show HN: A Full-Stack Web Framework for Go
Hey HN! I want to share my side project with you. It's called Bud and it's a full-stack web framework for Go.<p>I created a short video to show you how to create a minimal Hacker News clone with Bud: <a href="https://www.youtube.com/watch?v=LoypcRqn-xA" rel="nofollow">https://www.youtube.com/watch?v=LoypcRqn-xA</a>.<p>The framework is free, open source and MIT Licensed. You can find it on Github: <a href="https://github.com/livebud/bud" rel="nofollow">https://github.com/livebud/bud</a>.<p>I started working on Bud 2 years ago after watching the introductory Laracast videos about the Laravel web framework. I was just blown away by how productive you can be in Laravel. However, like many of you, I've been so spoiled by Go. I didn't want to go back to writing PHP, so I decided to try creating Laravel for the Go ecosystem.<p>At this point, I just had the following goal:<p>• Be as productive as Laravel in a typed language like Go.<p>I got the first version working in 6 months and tried building a blog from it... It fell flat. You needed to scaffold all these files just to get started. If you're coming from Rails or Laravel you may shrug, this is pretty normal. Unfortunately, I've also been spoiled by the renaissance in frontend frameworks like Next.js. What I love about Next is that it starts out barebones and every file you add incrementally enhances your web application. This keeps the initial complexity under control.<p>With these newly discovered constraints, I started working on the next iteration. Bud should:<p>• Generate files only as you need them. Keep these generated files away from your application code and give developers the choice to keep them out of source control.<p>• Feel like using a modern JS framework. This means it should work with modern frontend frameworks like Svelte and React, support live reload and have server-side rendering for better performance and SEO.<p>With these new goals, the Bud you see today started to take shape. But along the way, I discovered a few more project goals:<p>• The framework should be extensible from Day 1. Bud is too ambitious for one person. We're going to need an ambitious community behind this framework.<p>• Bud should be able to provide high-level APIs for developers while compiling down to performant low-level Go code for production.<p>• Bud should compile to a single binary. With platforms like Fly.io and Heroku, these days it's easy to not care about this, but I still cherish the idea that I can build a single binary that contains my entire web app and secure copy it up to a tiny server that doesn't even have Go installed.<p>It's still super early days. You can find the the Roadmap on Github: <a href="https://github.com/livebud/bud/discussions/9" rel="nofollow">https://github.com/livebud/bud/discussions/9</a>. I encourage you to contribute your thoughts.<p>And here's the current documentation for what's already in Bud: <a href="https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f9917c5033e5205c69" rel="nofollow">https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f991...</a>. Comments are enabled for anyone to chime in.<p>I have big plans for the framework. I hope you'll join me on this journey to build ambitious websites faster with Go!
Show HN: A Visual IDE for React
I made this because building UIs in a lexical medium like code is super annoying. I have to pre-render what I’m making in my head, and then jump between the browser and IDE to test. I was inspired by the developer console in chrome and safari since I end up editing css there because it’s ironically more convenient. Hope it’s useful!
Show HN: A Visual IDE for React
I made this because building UIs in a lexical medium like code is super annoying. I have to pre-render what I’m making in my head, and then jump between the browser and IDE to test. I was inspired by the developer console in chrome and safari since I end up editing css there because it’s ironically more convenient. Hope it’s useful!
Show HN: A Visual IDE for React
I made this because building UIs in a lexical medium like code is super annoying. I have to pre-render what I’m making in my head, and then jump between the browser and IDE to test. I was inspired by the developer console in chrome and safari since I end up editing css there because it’s ironically more convenient. Hope it’s useful!