News for hackers. Stuff that matters.

hishamk

Show HN: A headless Synergy server setup for niche use cases

https://github.com/hishamk/headlesssynergysetup

For someone with a bunch of retro machines that do not have a Synergy server port (and may not be near a machine that does or near one that I'd rather not run a Synergy server on) but do have a Synergy client port, using a headless Synergy server on a tiny SBC like the OrangePiZero makes for a slick, no frills setup to share a single mouse and keyboard among them.How do I use this? I've...

( Read More... | no comments | on HN )

Show HN: Jetstreamer – A Laravel Jetstream Dev Env with Docker+Makefile/Taskfile

https://github.com/hishamk/jetstreamer

Just wanted to share something I've been tinkering with lately. I've been playing around with setting up a dev environment for a project using Laravel Jetstream and PHP. It's been a while since I last used PHP (like, over ten years!), so a lot has changed.I went for a simple approach - no fancy stuff, just a combo of Makefile (or Taskfile) and docker-compose. Thought it might be cool to show...

( Read More... | no comments | on HN )
Re:Learn Electronics by Practice on Saturday July 08, 2023 @04:33PM (#36648435)
Analog, of course.
This looks real neat.
Thanks for the feedback. I've added a mermaidjs code generator for the ruleset.
Thanks for everyone's feedback. I've pushed out a few changes:

1- Regular slice instead of timestamp-keyed map. That didn't make sense in retrospect. 2- Better benchmarks. 3- Non-exported current state and transitions. Mutexed getters to avoid concurrency issues. 4- Variadic rule parameters. 5- Better example.

Thanks for the feedback.

The benchmark was for six transitions. I've now updated a few things and added new benchmarks.

I also got rid of timestamps for the map keys - it's back to a regular slice. In retrospect, that was a tad bit off, I agree.

Thank you so much for this head's up. I've just pushed out a new update that covers this and a few other changes.
Thank you. The focus was on simplicity and handling less complex scenarios. In my current projects the business logic lends itself to sitting outside the FSM/State Trooper. The logic dictates the transitions at arms length to the FSM. The FSM does not carry on any particular business logic, it just enforces the transition rules from one state to any number of possible states - hence why I've included the metadata aspect to embed info about the reason for a transition.

Re the visualization, I think that would be cool. I might give that a shot.

Ha! Not bad at all.
Thanks for this. You are indeed correct. I've pushed a fix and also added a race test to confirm the fix.
Thank you!
Re:Show HN: I made yet another Arduino clone on Saturday October 29, 2022 @12:28PM (#33385544)
I’ve spent the better part of my pandemic commute-free time learning a long standing interest of mine, electronics. This is my first MCU board.