The best Hacker News stories from Show from the past day
Latest posts:
Show HN: An in-browser text editor to easily create static HTML
Show HN: An in-browser text editor to easily create static HTML
Show HN: Hibiki HTML – New frontend framework – no scaffolding, no Webpack
Source <a href="https://github.com/dashborg/hibiki" rel="nofollow">https://github.com/dashborg/hibiki</a> | Interactive Tutorial <a href="https://playground.hibikihtml.com/tutorial/" rel="nofollow">https://playground.hibikihtml.com/tutorial/</a><p>I love JavaScript, but for many projects -- especially internal tools and prototypes -- setting up a full frontend JavaScript stack (npm, webpack, babel, create-react-app, redux) and all of their configuration files, folders, and scaffolding is overkill.<p>Hibiki HTML incrementally plugs into any backend, using any template language (even static HTML files) with a single script include. It includes a built-in frontend data model, Vue.js-like rendering, built-in AJAX integration, and a full component/library system.<p>It is also <i>fully scriptable</i> from your backend AJAX handlers. Anything that Hibiki HTML can do on the frontend can be done with a remote handler by returning specially formatted JSON <i>actions</i>. This allows you to write frontend logic (that would normally be JavaScript code) in your backend handlers.<p>Background -- Hibiki HTML is a standalone, open-source, more powerful version of the frontend language that I had built for my internal tools startup Dashborg over the past year. It is a reaction against the extreme amount of scaffolding and configuration required to set up a new frontend project, especially when you're a backend/devops/data engineer who isn't a JavaScript expert. As more Hibiki libraries are written, the advantages will hopefully become even more clear.<p>I'd love to get all of your feedback, questions, and comments. Would love a star on Github if you like the idea. Also, feel free to email me, and/or join the Slack workspace I set up (contact info on Github or the tutorial).
Show HN: Hibiki HTML – New frontend framework – no scaffolding, no Webpack
Source <a href="https://github.com/dashborg/hibiki" rel="nofollow">https://github.com/dashborg/hibiki</a> | Interactive Tutorial <a href="https://playground.hibikihtml.com/tutorial/" rel="nofollow">https://playground.hibikihtml.com/tutorial/</a><p>I love JavaScript, but for many projects -- especially internal tools and prototypes -- setting up a full frontend JavaScript stack (npm, webpack, babel, create-react-app, redux) and all of their configuration files, folders, and scaffolding is overkill.<p>Hibiki HTML incrementally plugs into any backend, using any template language (even static HTML files) with a single script include. It includes a built-in frontend data model, Vue.js-like rendering, built-in AJAX integration, and a full component/library system.<p>It is also <i>fully scriptable</i> from your backend AJAX handlers. Anything that Hibiki HTML can do on the frontend can be done with a remote handler by returning specially formatted JSON <i>actions</i>. This allows you to write frontend logic (that would normally be JavaScript code) in your backend handlers.<p>Background -- Hibiki HTML is a standalone, open-source, more powerful version of the frontend language that I had built for my internal tools startup Dashborg over the past year. It is a reaction against the extreme amount of scaffolding and configuration required to set up a new frontend project, especially when you're a backend/devops/data engineer who isn't a JavaScript expert. As more Hibiki libraries are written, the advantages will hopefully become even more clear.<p>I'd love to get all of your feedback, questions, and comments. Would love a star on Github if you like the idea. Also, feel free to email me, and/or join the Slack workspace I set up (contact info on Github or the tutorial).
Show HN: Hibiki HTML – New frontend framework – no scaffolding, no Webpack
Source <a href="https://github.com/dashborg/hibiki" rel="nofollow">https://github.com/dashborg/hibiki</a> | Interactive Tutorial <a href="https://playground.hibikihtml.com/tutorial/" rel="nofollow">https://playground.hibikihtml.com/tutorial/</a><p>I love JavaScript, but for many projects -- especially internal tools and prototypes -- setting up a full frontend JavaScript stack (npm, webpack, babel, create-react-app, redux) and all of their configuration files, folders, and scaffolding is overkill.<p>Hibiki HTML incrementally plugs into any backend, using any template language (even static HTML files) with a single script include. It includes a built-in frontend data model, Vue.js-like rendering, built-in AJAX integration, and a full component/library system.<p>It is also <i>fully scriptable</i> from your backend AJAX handlers. Anything that Hibiki HTML can do on the frontend can be done with a remote handler by returning specially formatted JSON <i>actions</i>. This allows you to write frontend logic (that would normally be JavaScript code) in your backend handlers.<p>Background -- Hibiki HTML is a standalone, open-source, more powerful version of the frontend language that I had built for my internal tools startup Dashborg over the past year. It is a reaction against the extreme amount of scaffolding and configuration required to set up a new frontend project, especially when you're a backend/devops/data engineer who isn't a JavaScript expert. As more Hibiki libraries are written, the advantages will hopefully become even more clear.<p>I'd love to get all of your feedback, questions, and comments. Would love a star on Github if you like the idea. Also, feel free to email me, and/or join the Slack workspace I set up (contact info on Github or the tutorial).
Show HN: Hibiki HTML – New frontend framework – no scaffolding, no Webpack
Source <a href="https://github.com/dashborg/hibiki" rel="nofollow">https://github.com/dashborg/hibiki</a> | Interactive Tutorial <a href="https://playground.hibikihtml.com/tutorial/" rel="nofollow">https://playground.hibikihtml.com/tutorial/</a><p>I love JavaScript, but for many projects -- especially internal tools and prototypes -- setting up a full frontend JavaScript stack (npm, webpack, babel, create-react-app, redux) and all of their configuration files, folders, and scaffolding is overkill.<p>Hibiki HTML incrementally plugs into any backend, using any template language (even static HTML files) with a single script include. It includes a built-in frontend data model, Vue.js-like rendering, built-in AJAX integration, and a full component/library system.<p>It is also <i>fully scriptable</i> from your backend AJAX handlers. Anything that Hibiki HTML can do on the frontend can be done with a remote handler by returning specially formatted JSON <i>actions</i>. This allows you to write frontend logic (that would normally be JavaScript code) in your backend handlers.<p>Background -- Hibiki HTML is a standalone, open-source, more powerful version of the frontend language that I had built for my internal tools startup Dashborg over the past year. It is a reaction against the extreme amount of scaffolding and configuration required to set up a new frontend project, especially when you're a backend/devops/data engineer who isn't a JavaScript expert. As more Hibiki libraries are written, the advantages will hopefully become even more clear.<p>I'd love to get all of your feedback, questions, and comments. Would love a star on Github if you like the idea. Also, feel free to email me, and/or join the Slack workspace I set up (contact info on Github or the tutorial).
Show HN: MockRocket – 3D app mockups and animations in the browser
Hey HN,<p>I've spent a lot of time over the years building mockups and demo videos for my apps with tools like Photoshop and After Effects, always frustrated by how tedious it was.<p>For the past year and a half, I've been working on building a better way.<p>MockRocket makes it easy to show off your app, right from your web browser–no experience required. Choose a template, drag and drop a screenshot or video and display it on a realistic 3D device model. You can even animate it to create a video.<p>You can customize as much or as little as you want, and export in up to 4K resolution. All rendering is done in the browser, not on a server–using WebGL and WebAssembly–so your imported designs stay 100% private.<p>This is the first release! Please let me know if you have any feedback or questions!
Show HN: MockRocket – 3D app mockups and animations in the browser
Hey HN,<p>I've spent a lot of time over the years building mockups and demo videos for my apps with tools like Photoshop and After Effects, always frustrated by how tedious it was.<p>For the past year and a half, I've been working on building a better way.<p>MockRocket makes it easy to show off your app, right from your web browser–no experience required. Choose a template, drag and drop a screenshot or video and display it on a realistic 3D device model. You can even animate it to create a video.<p>You can customize as much or as little as you want, and export in up to 4K resolution. All rendering is done in the browser, not on a server–using WebGL and WebAssembly–so your imported designs stay 100% private.<p>This is the first release! Please let me know if you have any feedback or questions!
Show HN: Simple Zero-Knowledge Proof Treasure Hunt Game
Show HN: Simple Zero-Knowledge Proof Treasure Hunt Game
Show HN: Simple Zero-Knowledge Proof Treasure Hunt Game
Show HN: Simple Zero-Knowledge Proof Treasure Hunt Game
Show HN: SPyQL – SQL with Python in the middle
SPyQL (<a href="https://github.com/dcmoura/spyql" rel="nofollow">https://github.com/dcmoura/spyql</a>) is SQL with Python in the middle, an open-source project fully written in Python for making command-line data processing more intuitive, readable and powerful. Try mixing in the same pot: a SQL SELECT for providing the structure, Python expressions for defining transformations and conditions, the essence of awk as a data-processing language, and the JSON handling capabilities of jq.<p>How does a SPyQL query looks like?<p><pre><code> $ spyql “
IMPORT pendulum AS p
SELECT
(p.now() - p.from_timestamp(purchase_ts)).in_days() AS days_ago,
sum_agg(price * quantity) AS total
FROM csv
WHERE department.upper() == 'IT' and purchase_ts is not Null
GROUP BY 1
ORDER BY 1
TO json” < my_purchases.csv
</code></pre>
In a single statement we are 1) reading a CSV (of purchases) with automatic header detection, dialect detection, type inference and casting, 2) filtering out records that do not belong to the IT department or do not have a purchase timestamp 3) summing the total purchases and grouping by how many days ago they happened, 4) sorting from the most to the least recent day and 5) writing the result in JSON format. All this without loading the full dataset into memory.<p>The Readme is loaded with recipes and there is also a demo video: <a href="https://vimeo.com/danielcmoura/spyqldemo" rel="nofollow">https://vimeo.com/danielcmoura/spyqldemo</a><p>Any feedback is welcomed! Thank you.
Show HN: SPyQL – SQL with Python in the middle
SPyQL (<a href="https://github.com/dcmoura/spyql" rel="nofollow">https://github.com/dcmoura/spyql</a>) is SQL with Python in the middle, an open-source project fully written in Python for making command-line data processing more intuitive, readable and powerful. Try mixing in the same pot: a SQL SELECT for providing the structure, Python expressions for defining transformations and conditions, the essence of awk as a data-processing language, and the JSON handling capabilities of jq.<p>How does a SPyQL query looks like?<p><pre><code> $ spyql “
IMPORT pendulum AS p
SELECT
(p.now() - p.from_timestamp(purchase_ts)).in_days() AS days_ago,
sum_agg(price * quantity) AS total
FROM csv
WHERE department.upper() == 'IT' and purchase_ts is not Null
GROUP BY 1
ORDER BY 1
TO json” < my_purchases.csv
</code></pre>
In a single statement we are 1) reading a CSV (of purchases) with automatic header detection, dialect detection, type inference and casting, 2) filtering out records that do not belong to the IT department or do not have a purchase timestamp 3) summing the total purchases and grouping by how many days ago they happened, 4) sorting from the most to the least recent day and 5) writing the result in JSON format. All this without loading the full dataset into memory.<p>The Readme is loaded with recipes and there is also a demo video: <a href="https://vimeo.com/danielcmoura/spyqldemo" rel="nofollow">https://vimeo.com/danielcmoura/spyqldemo</a><p>Any feedback is welcomed! Thank you.
Show HN: SPyQL – SQL with Python in the middle
SPyQL (<a href="https://github.com/dcmoura/spyql" rel="nofollow">https://github.com/dcmoura/spyql</a>) is SQL with Python in the middle, an open-source project fully written in Python for making command-line data processing more intuitive, readable and powerful. Try mixing in the same pot: a SQL SELECT for providing the structure, Python expressions for defining transformations and conditions, the essence of awk as a data-processing language, and the JSON handling capabilities of jq.<p>How does a SPyQL query looks like?<p><pre><code> $ spyql “
IMPORT pendulum AS p
SELECT
(p.now() - p.from_timestamp(purchase_ts)).in_days() AS days_ago,
sum_agg(price * quantity) AS total
FROM csv
WHERE department.upper() == 'IT' and purchase_ts is not Null
GROUP BY 1
ORDER BY 1
TO json” < my_purchases.csv
</code></pre>
In a single statement we are 1) reading a CSV (of purchases) with automatic header detection, dialect detection, type inference and casting, 2) filtering out records that do not belong to the IT department or do not have a purchase timestamp 3) summing the total purchases and grouping by how many days ago they happened, 4) sorting from the most to the least recent day and 5) writing the result in JSON format. All this without loading the full dataset into memory.<p>The Readme is loaded with recipes and there is also a demo video: <a href="https://vimeo.com/danielcmoura/spyqldemo" rel="nofollow">https://vimeo.com/danielcmoura/spyqldemo</a><p>Any feedback is welcomed! Thank you.
Show HN: Infracost (YC W21) – Open-source cloud cost policies
Hi, we’re Ali, Hassan and Alistair, co-founders of Infracost (<a href="https://www.infracost.io/" rel="nofollow">https://www.infracost.io/</a>). Infracost shows engineers the cost of each Terraform change in CI/CD before resources are launched. When something changes, it posts a comment with the cloud cost impact. e.g. you’ve added 2 instances and volumes, and have changed an instance type from medium to large, this will increase your bill by 25% next month from $1000 to $1250 per month.<p>We launched the first version of Infracost just under a year ago (<a href="https://news.ycombinator.com/item?id=26064588" rel="nofollow">https://news.ycombinator.com/item?id=26064588</a>). As we said in our first release ‘the people who are purchasing cloud resources are not shown costs upfront, so they don’t know how much the resources will cost before launching them’. Our assumption was that because we are open source and engineers are flying blind, they (the engineers) would pull us into their workflow. Actually, something different is happening:<p>The engineers are not pulling us in - it turns out to be the senior DevOps, SREs and platform teams. One of their challenges is figuring out how their small team of 7 people can fulfill the infrastructure requirements of hundreds of engineers. To solve this, they have created and put in place processes for engineers to provision infrastructure when they need. Now they want to implement cost policies and guardrails so that these hundreds of engineers don’t blow past all budgets. For example, if a change will result in a higher than 15% increase, leave a warning. If a change results in a >25% increase in costs, block the change till a team lead has reviewed it.<p>This has two implications for us. First, we need to create an output that isn’t only used by humans but is also digested into other systems to make further decisions. The second is the people we have been speaking to are not our end users. We need to figure out how we can get introduced to our end users, and create a different set of questions for each persona.<p>We’d really love your feedback around the cost policies use-case. We've created examples with standard policy tools like Open Policy Agent (OPA), HashiCorp Sentinel and Conftest. Check out the repo for GitHub Actions at <a href="https://github.com/infracost/infracost" rel="nofollow">https://github.com/infracost/infracost</a>. Our other CI/CD integrations are listed here: <a href="https://www.infracost.io/docs/#4-add-to-cicd" rel="nofollow">https://www.infracost.io/docs/#4-add-to-cicd</a>.<p>We'd love to hear how you think about policies and guardrails for containing cloud costs!
Show HN: Infracost (YC W21) – Open-source cloud cost policies
Hi, we’re Ali, Hassan and Alistair, co-founders of Infracost (<a href="https://www.infracost.io/" rel="nofollow">https://www.infracost.io/</a>). Infracost shows engineers the cost of each Terraform change in CI/CD before resources are launched. When something changes, it posts a comment with the cloud cost impact. e.g. you’ve added 2 instances and volumes, and have changed an instance type from medium to large, this will increase your bill by 25% next month from $1000 to $1250 per month.<p>We launched the first version of Infracost just under a year ago (<a href="https://news.ycombinator.com/item?id=26064588" rel="nofollow">https://news.ycombinator.com/item?id=26064588</a>). As we said in our first release ‘the people who are purchasing cloud resources are not shown costs upfront, so they don’t know how much the resources will cost before launching them’. Our assumption was that because we are open source and engineers are flying blind, they (the engineers) would pull us into their workflow. Actually, something different is happening:<p>The engineers are not pulling us in - it turns out to be the senior DevOps, SREs and platform teams. One of their challenges is figuring out how their small team of 7 people can fulfill the infrastructure requirements of hundreds of engineers. To solve this, they have created and put in place processes for engineers to provision infrastructure when they need. Now they want to implement cost policies and guardrails so that these hundreds of engineers don’t blow past all budgets. For example, if a change will result in a higher than 15% increase, leave a warning. If a change results in a >25% increase in costs, block the change till a team lead has reviewed it.<p>This has two implications for us. First, we need to create an output that isn’t only used by humans but is also digested into other systems to make further decisions. The second is the people we have been speaking to are not our end users. We need to figure out how we can get introduced to our end users, and create a different set of questions for each persona.<p>We’d really love your feedback around the cost policies use-case. We've created examples with standard policy tools like Open Policy Agent (OPA), HashiCorp Sentinel and Conftest. Check out the repo for GitHub Actions at <a href="https://github.com/infracost/infracost" rel="nofollow">https://github.com/infracost/infracost</a>. Our other CI/CD integrations are listed here: <a href="https://www.infracost.io/docs/#4-add-to-cicd" rel="nofollow">https://www.infracost.io/docs/#4-add-to-cicd</a>.<p>We'd love to hear how you think about policies and guardrails for containing cloud costs!
Show HN: Infracost (YC W21) – Open-source cloud cost policies
Hi, we’re Ali, Hassan and Alistair, co-founders of Infracost (<a href="https://www.infracost.io/" rel="nofollow">https://www.infracost.io/</a>). Infracost shows engineers the cost of each Terraform change in CI/CD before resources are launched. When something changes, it posts a comment with the cloud cost impact. e.g. you’ve added 2 instances and volumes, and have changed an instance type from medium to large, this will increase your bill by 25% next month from $1000 to $1250 per month.<p>We launched the first version of Infracost just under a year ago (<a href="https://news.ycombinator.com/item?id=26064588" rel="nofollow">https://news.ycombinator.com/item?id=26064588</a>). As we said in our first release ‘the people who are purchasing cloud resources are not shown costs upfront, so they don’t know how much the resources will cost before launching them’. Our assumption was that because we are open source and engineers are flying blind, they (the engineers) would pull us into their workflow. Actually, something different is happening:<p>The engineers are not pulling us in - it turns out to be the senior DevOps, SREs and platform teams. One of their challenges is figuring out how their small team of 7 people can fulfill the infrastructure requirements of hundreds of engineers. To solve this, they have created and put in place processes for engineers to provision infrastructure when they need. Now they want to implement cost policies and guardrails so that these hundreds of engineers don’t blow past all budgets. For example, if a change will result in a higher than 15% increase, leave a warning. If a change results in a >25% increase in costs, block the change till a team lead has reviewed it.<p>This has two implications for us. First, we need to create an output that isn’t only used by humans but is also digested into other systems to make further decisions. The second is the people we have been speaking to are not our end users. We need to figure out how we can get introduced to our end users, and create a different set of questions for each persona.<p>We’d really love your feedback around the cost policies use-case. We've created examples with standard policy tools like Open Policy Agent (OPA), HashiCorp Sentinel and Conftest. Check out the repo for GitHub Actions at <a href="https://github.com/infracost/infracost" rel="nofollow">https://github.com/infracost/infracost</a>. Our other CI/CD integrations are listed here: <a href="https://www.infracost.io/docs/#4-add-to-cicd" rel="nofollow">https://www.infracost.io/docs/#4-add-to-cicd</a>.<p>We'd love to hear how you think about policies and guardrails for containing cloud costs!
Show HN: A simple Wordle clone in 60 lines, using Hyperscript
Hello HN!
I've been playing a lot with <a href="https://hyperscript.org/" rel="nofollow">https://hyperscript.org/</a> recently (not to be confused with the other hyperhype hyperscript). I threw together a quick Wordle clone in an evening to see what it would look like using this language. The main functionality that is missing is checking for invalid words. The word dictionary is also very small, so it's very easy.<p>The goal here wasn't really to create a good version of Wordle, it was to build 80% of Wordle in a different language to see what it looks like. Turns out, it looks pretty good! Stuff like using CSS rule precedence to highlight the squares, CSS selectors to figure out which key to highlight, and using the DOM to keep state are all really natural in Hyperscript. I highly suggest going to the site and viewing the source!
Show HN: A simple Wordle clone in 60 lines, using Hyperscript
Hello HN!
I've been playing a lot with <a href="https://hyperscript.org/" rel="nofollow">https://hyperscript.org/</a> recently (not to be confused with the other hyperhype hyperscript). I threw together a quick Wordle clone in an evening to see what it would look like using this language. The main functionality that is missing is checking for invalid words. The word dictionary is also very small, so it's very easy.<p>The goal here wasn't really to create a good version of Wordle, it was to build 80% of Wordle in a different language to see what it looks like. Turns out, it looks pretty good! Stuff like using CSS rule precedence to highlight the squares, CSS selectors to figure out which key to highlight, and using the DOM to keep state are all really natural in Hyperscript. I highly suggest going to the site and viewing the source!