The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Simula One – Portable Linux VR Computer
Hi HN, My name is George, and I am helping build an office focused VR headset called the “Simula One”. It was discussed recently here: <a href="https://news.ycombinator.com/item?id=28695455" rel="nofollow">https://news.ycombinator.com/item?id=28695455</a>. We have just opened our store for preorders (<a href="https://shop.simulavr.com" rel="nofollow">https://shop.simulavr.com</a>), so that we and our backers can help people replace their old PCs/laptops with more capable VR headsets.<p>We call our headset a “VR Computer” (or a “VRC”) to distinguish it from gaming headsets. When Simula was founded, most people thought the future of VR was in games & entertainment. The truth is that VR offers a superior way for performing knowledge work, but until now there haven’t been dedicated VR computing devices available on the market. While existing headsets are optimized for gaming, ours is optimized for productivity: it features bleeding edge high-resolution displays, has a detachable compute pack with specs comparable to a premium office laptop (x86 architecture), and runs a VR specialized Linux distro optimized for clear text.<p>VRCs offer several advantages over Laptops & PCs: they provide unlimited screens of any size, improve work focus & immersion, are usable outdoors (no laptop glare), improve privacy (no one around you can snoop your screen), and their compact design frees up desk space. They also promote better posture and freedom of movement: with a VR computer you can change positions, sit up, lean back, stand, lie down, or even walk while you compute.<p>Our project started out as an open-source VR window manager (<a href="https://github.com/SimulaVR/Simula" rel="nofollow">https://github.com/SimulaVR/Simula</a>), which you can try out today on the Valve Index or HTC Vive. It's built over Drew Devault's wlroots and the Godot game engine. Once our compositor became relatively stable, we ran into the issue of “no other manufacturer wanted to offer us Linux support” (thinking there was no market for something so niche, I imagine?). So we decided to build our own =] We are happy to answer any question (technical or otherwise) about our project.
Show HN: Simula One – Portable Linux VR Computer
Hi HN, My name is George, and I am helping build an office focused VR headset called the “Simula One”. It was discussed recently here: <a href="https://news.ycombinator.com/item?id=28695455" rel="nofollow">https://news.ycombinator.com/item?id=28695455</a>. We have just opened our store for preorders (<a href="https://shop.simulavr.com" rel="nofollow">https://shop.simulavr.com</a>), so that we and our backers can help people replace their old PCs/laptops with more capable VR headsets.<p>We call our headset a “VR Computer” (or a “VRC”) to distinguish it from gaming headsets. When Simula was founded, most people thought the future of VR was in games & entertainment. The truth is that VR offers a superior way for performing knowledge work, but until now there haven’t been dedicated VR computing devices available on the market. While existing headsets are optimized for gaming, ours is optimized for productivity: it features bleeding edge high-resolution displays, has a detachable compute pack with specs comparable to a premium office laptop (x86 architecture), and runs a VR specialized Linux distro optimized for clear text.<p>VRCs offer several advantages over Laptops & PCs: they provide unlimited screens of any size, improve work focus & immersion, are usable outdoors (no laptop glare), improve privacy (no one around you can snoop your screen), and their compact design frees up desk space. They also promote better posture and freedom of movement: with a VR computer you can change positions, sit up, lean back, stand, lie down, or even walk while you compute.<p>Our project started out as an open-source VR window manager (<a href="https://github.com/SimulaVR/Simula" rel="nofollow">https://github.com/SimulaVR/Simula</a>), which you can try out today on the Valve Index or HTC Vive. It's built over Drew Devault's wlroots and the Godot game engine. Once our compositor became relatively stable, we ran into the issue of “no other manufacturer wanted to offer us Linux support” (thinking there was no market for something so niche, I imagine?). So we decided to build our own =] We are happy to answer any question (technical or otherwise) about our project.
Show HN: Simula One – Portable Linux VR Computer
Hi HN, My name is George, and I am helping build an office focused VR headset called the “Simula One”. It was discussed recently here: <a href="https://news.ycombinator.com/item?id=28695455" rel="nofollow">https://news.ycombinator.com/item?id=28695455</a>. We have just opened our store for preorders (<a href="https://shop.simulavr.com" rel="nofollow">https://shop.simulavr.com</a>), so that we and our backers can help people replace their old PCs/laptops with more capable VR headsets.<p>We call our headset a “VR Computer” (or a “VRC”) to distinguish it from gaming headsets. When Simula was founded, most people thought the future of VR was in games & entertainment. The truth is that VR offers a superior way for performing knowledge work, but until now there haven’t been dedicated VR computing devices available on the market. While existing headsets are optimized for gaming, ours is optimized for productivity: it features bleeding edge high-resolution displays, has a detachable compute pack with specs comparable to a premium office laptop (x86 architecture), and runs a VR specialized Linux distro optimized for clear text.<p>VRCs offer several advantages over Laptops & PCs: they provide unlimited screens of any size, improve work focus & immersion, are usable outdoors (no laptop glare), improve privacy (no one around you can snoop your screen), and their compact design frees up desk space. They also promote better posture and freedom of movement: with a VR computer you can change positions, sit up, lean back, stand, lie down, or even walk while you compute.<p>Our project started out as an open-source VR window manager (<a href="https://github.com/SimulaVR/Simula" rel="nofollow">https://github.com/SimulaVR/Simula</a>), which you can try out today on the Valve Index or HTC Vive. It's built over Drew Devault's wlroots and the Godot game engine. Once our compositor became relatively stable, we ran into the issue of “no other manufacturer wanted to offer us Linux support” (thinking there was no market for something so niche, I imagine?). So we decided to build our own =] We are happy to answer any question (technical or otherwise) about our project.
Show HN: Simula One – Portable Linux VR Computer
Hi HN, My name is George, and I am helping build an office focused VR headset called the “Simula One”. It was discussed recently here: <a href="https://news.ycombinator.com/item?id=28695455" rel="nofollow">https://news.ycombinator.com/item?id=28695455</a>. We have just opened our store for preorders (<a href="https://shop.simulavr.com" rel="nofollow">https://shop.simulavr.com</a>), so that we and our backers can help people replace their old PCs/laptops with more capable VR headsets.<p>We call our headset a “VR Computer” (or a “VRC”) to distinguish it from gaming headsets. When Simula was founded, most people thought the future of VR was in games & entertainment. The truth is that VR offers a superior way for performing knowledge work, but until now there haven’t been dedicated VR computing devices available on the market. While existing headsets are optimized for gaming, ours is optimized for productivity: it features bleeding edge high-resolution displays, has a detachable compute pack with specs comparable to a premium office laptop (x86 architecture), and runs a VR specialized Linux distro optimized for clear text.<p>VRCs offer several advantages over Laptops & PCs: they provide unlimited screens of any size, improve work focus & immersion, are usable outdoors (no laptop glare), improve privacy (no one around you can snoop your screen), and their compact design frees up desk space. They also promote better posture and freedom of movement: with a VR computer you can change positions, sit up, lean back, stand, lie down, or even walk while you compute.<p>Our project started out as an open-source VR window manager (<a href="https://github.com/SimulaVR/Simula" rel="nofollow">https://github.com/SimulaVR/Simula</a>), which you can try out today on the Valve Index or HTC Vive. It's built over Drew Devault's wlroots and the Godot game engine. Once our compositor became relatively stable, we ran into the issue of “no other manufacturer wanted to offer us Linux support” (thinking there was no market for something so niche, I imagine?). So we decided to build our own =] We are happy to answer any question (technical or otherwise) about our project.
Show HN: Simula One – Portable Linux VR Computer
Hi HN, My name is George, and I am helping build an office focused VR headset called the “Simula One”. It was discussed recently here: <a href="https://news.ycombinator.com/item?id=28695455" rel="nofollow">https://news.ycombinator.com/item?id=28695455</a>. We have just opened our store for preorders (<a href="https://shop.simulavr.com" rel="nofollow">https://shop.simulavr.com</a>), so that we and our backers can help people replace their old PCs/laptops with more capable VR headsets.<p>We call our headset a “VR Computer” (or a “VRC”) to distinguish it from gaming headsets. When Simula was founded, most people thought the future of VR was in games & entertainment. The truth is that VR offers a superior way for performing knowledge work, but until now there haven’t been dedicated VR computing devices available on the market. While existing headsets are optimized for gaming, ours is optimized for productivity: it features bleeding edge high-resolution displays, has a detachable compute pack with specs comparable to a premium office laptop (x86 architecture), and runs a VR specialized Linux distro optimized for clear text.<p>VRCs offer several advantages over Laptops & PCs: they provide unlimited screens of any size, improve work focus & immersion, are usable outdoors (no laptop glare), improve privacy (no one around you can snoop your screen), and their compact design frees up desk space. They also promote better posture and freedom of movement: with a VR computer you can change positions, sit up, lean back, stand, lie down, or even walk while you compute.<p>Our project started out as an open-source VR window manager (<a href="https://github.com/SimulaVR/Simula" rel="nofollow">https://github.com/SimulaVR/Simula</a>), which you can try out today on the Valve Index or HTC Vive. It's built over Drew Devault's wlroots and the Godot game engine. Once our compositor became relatively stable, we ran into the issue of “no other manufacturer wanted to offer us Linux support” (thinking there was no market for something so niche, I imagine?). So we decided to build our own =] We are happy to answer any question (technical or otherwise) about our project.
Show HN: Constructor – simple issue tracking for small teams, inspired by Trello
Hi, we’re Seth & Andrew (Aalk4308), founders of Constructor, the newest contestant in the issue tracking thunderdome.<p>TL;DR - we’re building a lightweight-yet-powerful tool that aims to minimize friction and improve clarity for both developers and managers alike, mostly by modeling things differently. We’re aiming for an out-of-the-box experience as simple as Trello, but designed completely from scratch for software teams, with enhancements like threaded comments, blockers, and integrations with GitHub and devops tools. You can take it for a spin with our instant, no-signup demo at <a href="https://try.constructor.dev" rel="nofollow">https://try.constructor.dev</a> – please let us know what you think!<p>Really, another tracking tool? Why?<p>Yes, another tracking tool, because nobody’s done it right yet, not even the recent entrants. We think the friction and complexity everyone hates about tracking tools are largely rooted in flawed models. Dev tracking tools both model the software development process and participate in it, and if they can’t model it in a lightweight way, then their participation adds friction and complexity. This wastes the team’s time and makes management more difficult. For over a decade as an engineering leader I struggled to capture my teams’ run-of-the-mill dev processes in a satisfyingly lightweight way; our solutions were always either inadequately simple or much too complex (Jira) and couldn’t strike a good balance between the needs of management and staying out of the team’s way. We’re building Constructor to solve this problem.<p>How is Constructor different from other dev tracking tools?<p>Abstractly: we differ in our product philosophy and our approach to modeling. Concretely: we’re redesigning lots of familiar features in novel ways, for example:<p>- Comments are threaded, assignable, and resolvable so you can keep discussions in the context of the work, have multiple going at the same time, and keep clutter to a minimum. Most importantly, they provide a lightweight mechanism for keeping track of small ad hoc tasks that might otherwise get lost in Slack, without requiring the overhead of a separate ticket.<p>- Blockers are first-class objects modeled as free-form text, so anything can be a blocker, not just another ticket – and are built on comment threads so you can easily have discussions around them.<p>- Checklists are provided for each stage in your workflow. So you can have one checklist for design, a different one for coding, one for QA, one for UAT, etc. We love checklists because they’re flexible and provide a ton of value with a minimum of hassle.<p>- In the near future, checklist items can be pointers to tickets and thus be used to create completely user-defined work structures. So you can build any structure you like, e.g. milestone -> epic -> story, or have no structure at all. Tickets can be in multiple projects/features/epics at once, since it’s a DAG. This may sound complicated, but we think it will prove to be lightweight and powerful. (And before you say “that’s great for devs but no non-technical PM would ever understand that” – this design was suggested to us by a non-technical PM customer.)<p>If you’re curious about how we differ in philosophy:<p>* We view complexity as enemy #1 for software development teams and pursue simplicity with an almost unwholesome zeal.<p>* We believe a tracking tool should be a great solution for many teams straight out of the box and provide solid value with virtually no configuration or learning curve.<p>* We don’t think a tracking tool should tell you how you ought to run your team. We don’t buy the idea that there’s one “best process”, certainly not during rapid team growth and change. We think everyone should do what works for their team and adjust it as they grow and circumstances change. It’s Constructor’s job to support that growth and evolution as well as possible.<p>* We think a tracking tool should never stand in the way of you getting your work done; if you want to do something, you probably have a good reason, and Constructor should let you do it. We can’t stand being blocked by simpleminded validation rules; our approach to consistency checks is more akin to linting.<p>* Avoid manager footguns. E.g. we’ll probably never report “velocity” even if it’s computed internally because it’s so commonly abused as a dev productivity measure (when in fact there’s no such thing). We know this is in tension with letting teams work however they want, but every rule has its limits.<p>We have a lot of cool stuff in the works but wanted to get feedback on what we’ve built so far. Please take it for a spin at <a href="https://try.constructor.dev" rel="nofollow">https://try.constructor.dev</a> and let us know what you think.<p>Thanks!
Show HN: Keep your bookmarks clean and up-to-date
Show HN: I rolled my own simple support / Helpdesk SaaS aimed at Indie Hackers
Show HN: I rolled my own simple support / Helpdesk SaaS aimed at Indie Hackers
Show HN: I made a tool to create product tutorials
Show HN: I made a tool to create product tutorials
Show HN: The Brutalist Report – A rolling snapshot of the day’s headlines
Hi HN. I was inspired by so many other folks also longing for a return to the old web that I put together a service to scratch my own itch: An extremely fast headline aggregator done in 1990s style HTML.<p>Sharing it with you all for those of you that also would enjoy this now esoteric style.
Show HN: The Brutalist Report – A rolling snapshot of the day’s headlines
Hi HN. I was inspired by so many other folks also longing for a return to the old web that I put together a service to scratch my own itch: An extremely fast headline aggregator done in 1990s style HTML.<p>Sharing it with you all for those of you that also would enjoy this now esoteric style.
Show HN: A new daily word puzzle
Show HN: A new daily word puzzle
Show HN: Prisma Python – A fully typed ORM for Python
I created this ORM to fill a gap in the Python ecosystem. Due to the nature of typing in Python there are no other Python ORMs that can provide correct type hints. Prisma Python manages to work around this by auto-generating python types.<p>Aside from static type checking, providing type hints means that you will get autocomplete suggestions for you which for me is the killer feature for this ORM (see the GIF in the README for an example).<p>It's also built on top of Prisma, a next-generation ORM for TypeScript which means that the core query building and connection handling has been battle tested, getting around a potential concern with adopting a new ORM.<p>Prisma Python also supports PostgreSQL, SQLite, MongoDB, MariaDB and more!
Show HN: Prisma Python – A fully typed ORM for Python
I created this ORM to fill a gap in the Python ecosystem. Due to the nature of typing in Python there are no other Python ORMs that can provide correct type hints. Prisma Python manages to work around this by auto-generating python types.<p>Aside from static type checking, providing type hints means that you will get autocomplete suggestions for you which for me is the killer feature for this ORM (see the GIF in the README for an example).<p>It's also built on top of Prisma, a next-generation ORM for TypeScript which means that the core query building and connection handling has been battle tested, getting around a potential concern with adopting a new ORM.<p>Prisma Python also supports PostgreSQL, SQLite, MongoDB, MariaDB and more!
Show HN: Google Drive to SQLite
Here's the repo: <a href="https://github.com/simonw/google-drive-to-sqlite" rel="nofollow">https://github.com/simonw/google-drive-to-sqlite</a><p>The README is using a trick I'm increasingly leaning on: parts of that document - the --help output and the example database schema - are automatically generated using Cog: <a href="https://nedbatchelder.com/code/cog" rel="nofollow">https://nedbatchelder.com/code/cog</a> and <a href="https://til.simonwillison.net/python/cog-to-update-help-in-readme" rel="nofollow">https://til.simonwillison.net/python/cog-to-update-help-in-r...</a>
Show HN: Google Drive to SQLite
Here's the repo: <a href="https://github.com/simonw/google-drive-to-sqlite" rel="nofollow">https://github.com/simonw/google-drive-to-sqlite</a><p>The README is using a trick I'm increasingly leaning on: parts of that document - the --help output and the example database schema - are automatically generated using Cog: <a href="https://nedbatchelder.com/code/cog" rel="nofollow">https://nedbatchelder.com/code/cog</a> and <a href="https://til.simonwillison.net/python/cog-to-update-help-in-readme" rel="nofollow">https://til.simonwillison.net/python/cog-to-update-help-in-r...</a>
Show HN: Google Drive to SQLite
Here's the repo: <a href="https://github.com/simonw/google-drive-to-sqlite" rel="nofollow">https://github.com/simonw/google-drive-to-sqlite</a><p>The README is using a trick I'm increasingly leaning on: parts of that document - the --help output and the example database schema - are automatically generated using Cog: <a href="https://nedbatchelder.com/code/cog" rel="nofollow">https://nedbatchelder.com/code/cog</a> and <a href="https://til.simonwillison.net/python/cog-to-update-help-in-readme" rel="nofollow">https://til.simonwillison.net/python/cog-to-update-help-in-r...</a>