Monday, 3 April 2023

New Show Hacker News story: latest news

Show HN: Ycinterview.ai – Practice the YC Interview with Cloned AI Partners
3 by KianHooshmand | 0 comments on Hacker News.


New Show Hacker News story: latest news

Show HN: Pubnix.pink, a public-access Void Linux system
2 by DakotaR | 0 comments on Hacker News.
This is a hobby project I've been working on, any feedback is greatly appreciated!

New Show Hacker News story: latest news

Show HN: Tomatotree.tv – Find your next series to watch using Rotten Tomatoes
2 by hauxir | 0 comments on Hacker News.


New Show Hacker News story: latest news

Show HN: Goru, an experimental, Go-inspired concurrency library for Ruby
2 by bryanp | 1 comments on Hacker News.
Hey folks, wanted to show this off and get feedback. Still early/experimental but there are quite a few concepts I'm excited about here. This project came about while writing a program in Go and loving its approach to concurrency. Being a long-time Rubyist I immediately started to think about what similar concepts might look like in Ruby. I set out with two main design constraints: 1. Lightweight: I didn't want routines to be backed by fibers or threads. Having been involved some in the async project ( https://ift.tt/x1VdmSO ), I had some experience using fibers for concurrency but was curious if they could be avoided. 2. Explicitness: Routine behavior must be written to describe exactly how it is to behave. I always felt like concurrent code was hard to fully understand because of the indirection involved. On the spectrum between tedium and magical I wanted to err more on the side of tedium with Goru. Goru routines are just blocks that are called once for every tick of the reactor. It is up to the developer to implement behavior in terms of a state machine, where on each tick the routine takes some action and then updates the state of the routine for the next tick. This fulfills both design constraints: 1. Because routines are just blocks, they weigh in at about ~345 bytes of memory overhead. 2. Routine behavior is explicit because it is written as a state machine inside the block. Couple more features worth noting: * Goru includes channels for buffered reading/writing (similar to channels in Go). * Goru ships with primitives for non-blocking IO to easily build things like http servers. Curious your thoughts!

Sunday, 2 April 2023

New Show Hacker News story: latest news

Show HN: I Got ChatGPT to Write Complete Programs
4 by strnisa | 1 comments on Hacker News.


New Show Hacker News story: latest news

Show HN: Shhhbb, an SSH BBS
2 by lagniappe | 2 comments on Hacker News.
Hello all :) I made this BBS for fun and thought you all would enjoy it. It's not perfect, but it's been a fun exercise! see it: https://ift.tt/mdhWqcv try it: ssh -p 2223 shhhbb.com host it: https://ift.tt/PztVyLW why? Every year I challenge myself in some new way, this year it is to push one project per week. You might recognize my static site generator [0] or my releaser for go [1] from previous posts as one of these weekly projects. If you want to join me in doing this, it's been a blast and I highly recommend it! Maybe we can chat on the bbs about it :) [0] - bearclaw tiny static generator - https://ift.tt/30qtf5p [1] - release.sh release builder for go - https://ift.tt/30qtf5p need: I'd love a few co-conspirators, or even some new friends for the bbs software or the bbs itself. A lofty nice-to-have goal is meeting a few other similarly motivated people to conspire with on a weekly basis. If that's you, drop me a line! goals: I have about half of an admin interface endpoint pushed up, which I'd like to finish. I realized mid-commit that I'd lacked some other material in a previous commit, and in pushing it up, I ended up pushing half the admin feature. Stay tuned for that. I'd also like to implement a feature where I surrender the socket to a new process so I can upgrade the binary without dropping all of the connected users. I'm not sure on the feasibility of this, but all the words fit together, so it'll be tried.

New Show Hacker News story: latest news

Show HN: Reward open-source contributors with bounties & tips
9 by zcesur | 6 comments on Hacker News.
Hey HN! We’re Ioannis & Zaf, building Algora.io to help open source projects reward their contributors & grow their communities. The Problem: open source has a lot of work to be done, but not enough contributors. Introducing rewards for product development can help bridge this gap. However, today, paid contributions in open source are scarce, low trust & high friction Our Solution: we built an app that streamlines open source bounties on Github • workflow: /bounty & /claim commands on issues and pull requests to create & solve bounties • discovery: README shields, badges and leaderboards, Github bot notifications, in-app bounty boards • tipping: /tip command on issues and pull requests to reward contributions retroactively • payments: Stripe Connect to onboard contributors & simplify payments, invoices & reporting • bounties API (SDK coming soon) to create bounty portals on your website Our first customer was Remotion.dev (15.6k stars, Typescript/React) in November 2022, whose feedback helped us ship our Github app & iterate through our bounty workflow. To date, Remotion.dev has rewarded 17 open source bounties. Since then, we’ve been fortunate to also welcome Cal.com (17.6k stars, Typescript/Next), IHP (3.9k stars, Haskell), Qdrant.tech (5.4k stars, Rust), erxes.io (2.8k stars, Typescript) and shuttle.rs (YC S20, 2.1k stars, Rust). With Algora, OSS projects have rewarded bounties to contributors in the US, Europe (Germany, France, Norway), Canada, Nigeria, India, Egypt, UAE, Brazil, Colombia, Philippines and Australia — we hope this list keeps growing! In an effort to learn more about open source, understand the experience of maintainers and share lessons & advice for building commercial open source companies, we also started a COSS founder interview series. You can find the full interviews & highlights on our youtube channel: https://youtube.com/@algora-io We are really excited to hear your feedback/questions and connect further: our emails are ioannis@algora.io & zafer@algora.io Thank you in advance for all your input!