The best Hacker News stories from Show from the past day

from

All Show

from the past*

day week month

with these search terms:

Create follow Go back

Latest posts:

Show HN: Homemade automated solar concentrator

Hi HN!<p>I quit my job two years ago to have more time to work on my side projects.<p>The main one is an automated solar concentrator.<p>I've just open-sourced it, it's not perfect nor finished, and I still have a lot of ideas for further development, but I'm interested in knowing what you think of it.<p>There are many applications where concentrated solar power could be a viable environmental and economic solution, I hope this technology will one day be more widely used.<p>Feel free to give any feedback and ask questions.

Show HN: Homemade automated solar concentrator

Hi HN!<p>I quit my job two years ago to have more time to work on my side projects.<p>The main one is an automated solar concentrator.<p>I've just open-sourced it, it's not perfect nor finished, and I still have a lot of ideas for further development, but I'm interested in knowing what you think of it.<p>There are many applications where concentrated solar power could be a viable environmental and economic solution, I hope this technology will one day be more widely used.<p>Feel free to give any feedback and ask questions.

Show HN: We ungated our product (no signup)–is it a good idea?

Users within our ICP were dropping off during or right after the signup process, never reaching that crucial “aha moment” where they truly see the value in our product. Typically, this moment happens when they’ve created an interactive demo they’re happy with.<p>We were like... "let's just do it". So, we decided to ungate our product—removing the signup step entirely at this stage of the user journey. Of course, users can still sign up if they want to continue using the product, but our aim was to reduce friction and align with the supposed future of product-led growth, where ungated experiences help users quickly grasp a product’s value.<p>We’re tracking key metrics—like increased engagement, faster time-to-value, and created demos—but it’s still early days, and the results are mixed. We’ve seen spikes in usage, but also some users creating “meaningless” demos, likely due to being overwhelmed by too many options.<p>I’m eager for your thoughts: - What do you think of this specific ungated experience? - Were you able to create your first interactive demo? - Any other ungated product you really like, and why?<p>Open to any feedback or discussions!

Show HN: Shed Light on Your Go Binary Bloat with Go Size Analyzer

I've created a powerful tool to help Go developers uncover the hidden giants in their compiled binaries. Go Size Analyzer is like an X-ray machine for your Go executables, revealing:<p>Which dependencies are eating up your binary size<p>Unexpected bloat from standard library or vendor packages<p>Size changes between binary versions with a visual diff<p>Key features that set it apart:<p>Interactive treemap visualizations (check out the demo: <a href="https://gsa.zxilly.dev" rel="nofollow">https://gsa.zxilly.dev</a>)<p>Slick terminal UI for deep diving into package hierarchies<p>Cross-platform support (works on Linux, macOS, and Windows binaries)<p>Export to SVG for easy sharing and documentation or just visualize the CI process<p>Whether you're optimizing for edge devices, reducing Docker image sizes, or just curious about what's really inside your Go binaries, this tool provides detailed insights. .

Show HN: Repo2vec – an open-source library for chatting with any codebase

Hi HN, We're excited to share repo2vec: a simple-to-use, modular library enabling you to chat with any public or private codebase. It's like Github Copilot but with the most up-to-date information about your repo.<p>We made this because sometimes you just want to learn how a codebase works and how to integrate it, without spending hours sifting through the code itself.<p>We tried to make it dead-simple to use. With two scripts, you can index and get a functional interface for your repo. Every generated response shows where in the code the context for the answer was pulled from.<p>We also made it plug-and-play where every component from the embeddings, to the vector store, to the LLM is completely customizable.<p>If you want to see a hosted version of the chat interface with its features, here's a link: <a href="https://www.youtube.com/watch?v=CNVzmqRXUCA" rel="nofollow">https://www.youtube.com/watch?v=CNVzmqRXUCA</a><p>We would love your feedback!<p>- Mihail and Julia

Show HN: Repo2vec – an open-source library for chatting with any codebase

Hi HN, We're excited to share repo2vec: a simple-to-use, modular library enabling you to chat with any public or private codebase. It's like Github Copilot but with the most up-to-date information about your repo.<p>We made this because sometimes you just want to learn how a codebase works and how to integrate it, without spending hours sifting through the code itself.<p>We tried to make it dead-simple to use. With two scripts, you can index and get a functional interface for your repo. Every generated response shows where in the code the context for the answer was pulled from.<p>We also made it plug-and-play where every component from the embeddings, to the vector store, to the LLM is completely customizable.<p>If you want to see a hosted version of the chat interface with its features, here's a link: <a href="https://www.youtube.com/watch?v=CNVzmqRXUCA" rel="nofollow">https://www.youtube.com/watch?v=CNVzmqRXUCA</a><p>We would love your feedback!<p>- Mihail and Julia

Show HN: Every open source tool from the "What's HN working on" thread

Show HN: Claude Artifacts but creating real web apps

Hey Hacker News!<p>Launching gptengineer.app into beta today.<p>It's like Claude Artifacts, but:<p>- you can edit the code in your fav IDE (two-way github sync)<p>- installs npm packages<p>- automatically picks up build and runtime errors and fixes them<p>- very fast, built with rust<p>The full stack capabilities are built on supabase (prefer to not have to handle auth + user data at this point so this is owned by the user)<p>The seed for this project was an open source experiment, posted about that previously here:<p><a href="https://news.ycombinator.com/item?id=36422730">https://news.ycombinator.com/item?id=36422730</a><p>Would love feedback if you give it a try!

Show HN: Claude Artifacts but creating real web apps

Hey Hacker News!<p>Launching gptengineer.app into beta today.<p>It's like Claude Artifacts, but:<p>- you can edit the code in your fav IDE (two-way github sync)<p>- installs npm packages<p>- automatically picks up build and runtime errors and fixes them<p>- very fast, built with rust<p>The full stack capabilities are built on supabase (prefer to not have to handle auth + user data at this point so this is owned by the user)<p>The seed for this project was an open source experiment, posted about that previously here:<p><a href="https://news.ycombinator.com/item?id=36422730">https://news.ycombinator.com/item?id=36422730</a><p>Would love feedback if you give it a try!

Show HN: Claude Artifacts but creating real web apps

Hey Hacker News!<p>Launching gptengineer.app into beta today.<p>It's like Claude Artifacts, but:<p>- you can edit the code in your fav IDE (two-way github sync)<p>- installs npm packages<p>- automatically picks up build and runtime errors and fixes them<p>- very fast, built with rust<p>The full stack capabilities are built on supabase (prefer to not have to handle auth + user data at this point so this is owned by the user)<p>The seed for this project was an open source experiment, posted about that previously here:<p><a href="https://news.ycombinator.com/item?id=36422730">https://news.ycombinator.com/item?id=36422730</a><p>Would love feedback if you give it a try!

Show HN: IPA, a GUI for exploring inner details of PDFs

Show HN: Skip – Build native iOS and Android apps from a single Swift codebase

Hello Hacker News. I'm Marc, one half of the team that created skip.tools. Skip is a tool that transpiles your SwiftUI iOS app into a Kotlin Jetpack Compose app, and enables you to use a single language to create a complete app that reaches the entire mobile marketplace.<p>What it is: Skip stands in contrast to other cross-platform development tools like Flutter, React Native, and Xamarin, in that it enables the creation of genuinely native applications for both of the dominant mobile platforms. It doesn't embed a separate engine or runtime into your app, but instead lets you use pure Swift and SwiftUI to create the iOS side of the app (as per Apple's recommended best practices for creating iOS apps), and transpiles it into a pure Kotlin and Jetpack Compose app for the Android side (which is Google's recommendation for building Android apps). So your application will use platform-native controls and will automatically have all the affordances provided by the platform vendor: animations, accessibility, and future-proof evolution alongside OS updates.<p>How it works: you build a Skip app using the same tools that you use to create a standard iOS app: Xcode, Swift, and SwiftUI. Skip augments this workflow with a Swift Package Manager plugin called "skipstone", which transpiles your Swift into Kotlin each time you build your app, and launches the Android app side-by-side with the iOS app each time you run the app. The transpilation works not just on your primary app module, but also transitively processes all your dependent SwiftPM modules, so you can break complex projects down into individually testable sub-modules containing business logic or UI code. In fact, this is how our own adaptor modules for the standard frameworks are structured: SkipFoundation adapts the Foundation framework and SkipUI adapts the SwiftUI framework, so the same familiar API can be used when building the app. And there's a GitHub ecosystem of open-source modules supporting popular frameworks, including SQLite, Firebase, Lottie, and many other common building blocks of modern apps.<p>Over the past year Skip has evolved into a fully-capable solution for creating best-in-class apps for both iOS and Android. And today we are delighted to announce the release of version 1.0, meaning that it is ready for production use.<p>We have a wealth of videos and documentation available at <a href="https://skip.tools" rel="nofollow">https://skip.tools</a>, and I'll be around to field any questions that any of you might have. Thanks in advance for taking a look!<p>Home: <a href="https://skip.tools" rel="nofollow">https://skip.tools</a><p>FAQ: <a href="https://skip.tools/docs/faq/" rel="nofollow">https://skip.tools/docs/faq/</a><p>GitHub: <a href="https://github.com/skiptools/">https://github.com/skiptools/</a>

Show HN: Skip – Build native iOS and Android apps from a single Swift codebase

Hello Hacker News. I'm Marc, one half of the team that created skip.tools. Skip is a tool that transpiles your SwiftUI iOS app into a Kotlin Jetpack Compose app, and enables you to use a single language to create a complete app that reaches the entire mobile marketplace.<p>What it is: Skip stands in contrast to other cross-platform development tools like Flutter, React Native, and Xamarin, in that it enables the creation of genuinely native applications for both of the dominant mobile platforms. It doesn't embed a separate engine or runtime into your app, but instead lets you use pure Swift and SwiftUI to create the iOS side of the app (as per Apple's recommended best practices for creating iOS apps), and transpiles it into a pure Kotlin and Jetpack Compose app for the Android side (which is Google's recommendation for building Android apps). So your application will use platform-native controls and will automatically have all the affordances provided by the platform vendor: animations, accessibility, and future-proof evolution alongside OS updates.<p>How it works: you build a Skip app using the same tools that you use to create a standard iOS app: Xcode, Swift, and SwiftUI. Skip augments this workflow with a Swift Package Manager plugin called "skipstone", which transpiles your Swift into Kotlin each time you build your app, and launches the Android app side-by-side with the iOS app each time you run the app. The transpilation works not just on your primary app module, but also transitively processes all your dependent SwiftPM modules, so you can break complex projects down into individually testable sub-modules containing business logic or UI code. In fact, this is how our own adaptor modules for the standard frameworks are structured: SkipFoundation adapts the Foundation framework and SkipUI adapts the SwiftUI framework, so the same familiar API can be used when building the app. And there's a GitHub ecosystem of open-source modules supporting popular frameworks, including SQLite, Firebase, Lottie, and many other common building blocks of modern apps.<p>Over the past year Skip has evolved into a fully-capable solution for creating best-in-class apps for both iOS and Android. And today we are delighted to announce the release of version 1.0, meaning that it is ready for production use.<p>We have a wealth of videos and documentation available at <a href="https://skip.tools" rel="nofollow">https://skip.tools</a>, and I'll be around to field any questions that any of you might have. Thanks in advance for taking a look!<p>Home: <a href="https://skip.tools" rel="nofollow">https://skip.tools</a><p>FAQ: <a href="https://skip.tools/docs/faq/" rel="nofollow">https://skip.tools/docs/faq/</a><p>GitHub: <a href="https://github.com/skiptools/">https://github.com/skiptools/</a>

Show HN: Skip – Build native iOS and Android apps from a single Swift codebase

Hello Hacker News. I'm Marc, one half of the team that created skip.tools. Skip is a tool that transpiles your SwiftUI iOS app into a Kotlin Jetpack Compose app, and enables you to use a single language to create a complete app that reaches the entire mobile marketplace.<p>What it is: Skip stands in contrast to other cross-platform development tools like Flutter, React Native, and Xamarin, in that it enables the creation of genuinely native applications for both of the dominant mobile platforms. It doesn't embed a separate engine or runtime into your app, but instead lets you use pure Swift and SwiftUI to create the iOS side of the app (as per Apple's recommended best practices for creating iOS apps), and transpiles it into a pure Kotlin and Jetpack Compose app for the Android side (which is Google's recommendation for building Android apps). So your application will use platform-native controls and will automatically have all the affordances provided by the platform vendor: animations, accessibility, and future-proof evolution alongside OS updates.<p>How it works: you build a Skip app using the same tools that you use to create a standard iOS app: Xcode, Swift, and SwiftUI. Skip augments this workflow with a Swift Package Manager plugin called "skipstone", which transpiles your Swift into Kotlin each time you build your app, and launches the Android app side-by-side with the iOS app each time you run the app. The transpilation works not just on your primary app module, but also transitively processes all your dependent SwiftPM modules, so you can break complex projects down into individually testable sub-modules containing business logic or UI code. In fact, this is how our own adaptor modules for the standard frameworks are structured: SkipFoundation adapts the Foundation framework and SkipUI adapts the SwiftUI framework, so the same familiar API can be used when building the app. And there's a GitHub ecosystem of open-source modules supporting popular frameworks, including SQLite, Firebase, Lottie, and many other common building blocks of modern apps.<p>Over the past year Skip has evolved into a fully-capable solution for creating best-in-class apps for both iOS and Android. And today we are delighted to announce the release of version 1.0, meaning that it is ready for production use.<p>We have a wealth of videos and documentation available at <a href="https://skip.tools" rel="nofollow">https://skip.tools</a>, and I'll be around to field any questions that any of you might have. Thanks in advance for taking a look!<p>Home: <a href="https://skip.tools" rel="nofollow">https://skip.tools</a><p>FAQ: <a href="https://skip.tools/docs/faq/" rel="nofollow">https://skip.tools/docs/faq/</a><p>GitHub: <a href="https://github.com/skiptools/">https://github.com/skiptools/</a>

Show HN: Skip – Build native iOS and Android apps from a single Swift codebase

Hello Hacker News. I'm Marc, one half of the team that created skip.tools. Skip is a tool that transpiles your SwiftUI iOS app into a Kotlin Jetpack Compose app, and enables you to use a single language to create a complete app that reaches the entire mobile marketplace.<p>What it is: Skip stands in contrast to other cross-platform development tools like Flutter, React Native, and Xamarin, in that it enables the creation of genuinely native applications for both of the dominant mobile platforms. It doesn't embed a separate engine or runtime into your app, but instead lets you use pure Swift and SwiftUI to create the iOS side of the app (as per Apple's recommended best practices for creating iOS apps), and transpiles it into a pure Kotlin and Jetpack Compose app for the Android side (which is Google's recommendation for building Android apps). So your application will use platform-native controls and will automatically have all the affordances provided by the platform vendor: animations, accessibility, and future-proof evolution alongside OS updates.<p>How it works: you build a Skip app using the same tools that you use to create a standard iOS app: Xcode, Swift, and SwiftUI. Skip augments this workflow with a Swift Package Manager plugin called "skipstone", which transpiles your Swift into Kotlin each time you build your app, and launches the Android app side-by-side with the iOS app each time you run the app. The transpilation works not just on your primary app module, but also transitively processes all your dependent SwiftPM modules, so you can break complex projects down into individually testable sub-modules containing business logic or UI code. In fact, this is how our own adaptor modules for the standard frameworks are structured: SkipFoundation adapts the Foundation framework and SkipUI adapts the SwiftUI framework, so the same familiar API can be used when building the app. And there's a GitHub ecosystem of open-source modules supporting popular frameworks, including SQLite, Firebase, Lottie, and many other common building blocks of modern apps.<p>Over the past year Skip has evolved into a fully-capable solution for creating best-in-class apps for both iOS and Android. And today we are delighted to announce the release of version 1.0, meaning that it is ready for production use.<p>We have a wealth of videos and documentation available at <a href="https://skip.tools" rel="nofollow">https://skip.tools</a>, and I'll be around to field any questions that any of you might have. Thanks in advance for taking a look!<p>Home: <a href="https://skip.tools" rel="nofollow">https://skip.tools</a><p>FAQ: <a href="https://skip.tools/docs/faq/" rel="nofollow">https://skip.tools/docs/faq/</a><p>GitHub: <a href="https://github.com/skiptools/">https://github.com/skiptools/</a>

Show HN: Skip – Build native iOS and Android apps from a single Swift codebase

Hello Hacker News. I'm Marc, one half of the team that created skip.tools. Skip is a tool that transpiles your SwiftUI iOS app into a Kotlin Jetpack Compose app, and enables you to use a single language to create a complete app that reaches the entire mobile marketplace.<p>What it is: Skip stands in contrast to other cross-platform development tools like Flutter, React Native, and Xamarin, in that it enables the creation of genuinely native applications for both of the dominant mobile platforms. It doesn't embed a separate engine or runtime into your app, but instead lets you use pure Swift and SwiftUI to create the iOS side of the app (as per Apple's recommended best practices for creating iOS apps), and transpiles it into a pure Kotlin and Jetpack Compose app for the Android side (which is Google's recommendation for building Android apps). So your application will use platform-native controls and will automatically have all the affordances provided by the platform vendor: animations, accessibility, and future-proof evolution alongside OS updates.<p>How it works: you build a Skip app using the same tools that you use to create a standard iOS app: Xcode, Swift, and SwiftUI. Skip augments this workflow with a Swift Package Manager plugin called "skipstone", which transpiles your Swift into Kotlin each time you build your app, and launches the Android app side-by-side with the iOS app each time you run the app. The transpilation works not just on your primary app module, but also transitively processes all your dependent SwiftPM modules, so you can break complex projects down into individually testable sub-modules containing business logic or UI code. In fact, this is how our own adaptor modules for the standard frameworks are structured: SkipFoundation adapts the Foundation framework and SkipUI adapts the SwiftUI framework, so the same familiar API can be used when building the app. And there's a GitHub ecosystem of open-source modules supporting popular frameworks, including SQLite, Firebase, Lottie, and many other common building blocks of modern apps.<p>Over the past year Skip has evolved into a fully-capable solution for creating best-in-class apps for both iOS and Android. And today we are delighted to announce the release of version 1.0, meaning that it is ready for production use.<p>We have a wealth of videos and documentation available at <a href="https://skip.tools" rel="nofollow">https://skip.tools</a>, and I'll be around to field any questions that any of you might have. Thanks in advance for taking a look!<p>Home: <a href="https://skip.tools" rel="nofollow">https://skip.tools</a><p>FAQ: <a href="https://skip.tools/docs/faq/" rel="nofollow">https://skip.tools/docs/faq/</a><p>GitHub: <a href="https://github.com/skiptools/">https://github.com/skiptools/</a>

Show HN: An All in One AI Workspace with 200+ AI Models, Should We Apply to YC?

Show HN: Outperforming VByte for Large Integers Using Phi-Encoding

Show HN: Rabbit Holes

Built a way to spatially explore wikipedia topics!<p>Enter a topic of your choice and dig into the rabbit hole. All content is from Wikipedia—related topics are generated with GPT based on the summary.<p>Spacebar to expand a topic inline, arrow keys to move around, and "J" to open journey view!

Show HN: Rabbit Holes

Built a way to spatially explore wikipedia topics!<p>Enter a topic of your choice and dig into the rabbit hole. All content is from Wikipedia—related topics are generated with GPT based on the summary.<p>Spacebar to expand a topic inline, arrow keys to move around, and "J" to open journey view!