go-rpio
joystick
Our great sponsors
| go-rpio | joystick | |
|---|---|---|
| 0 | 20 | |
| 1,874 | 79 | |
| - | - | |
| 4.3 | 9.4 | |
| 2 months ago | 7 days ago | |
| Go | JavaScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
go-rpio
We haven't tracked posts mentioning go-rpio yet.
Tracking mentions began in Dec 2020.
joystick
-
GraphQL Is a Trap?
Yes. It overcomplicates what can be a simple process using a bit of ingenuity and good ol' fashioned REST endpoints: https://github.com/cheatcode/joystick#customizing-outputs
-
I fell in love with low-JS
This is exactly why I’m building Joystick (full-stack, UI framework + Node backend, full SSR out of the box—think Meteor w/o data bottlenecks and dependency traps). JavaScript doesn’t have to be a nightmare: https://github.com/cheatcode/joystick.
-
Ask HN: Have we screwed ourselves as software engineers?
> Will industry move towards simple solutions after experiencing this churn down the line or are we doomed forever?
That depends on the individual developer. For example, I'm working to clean up the mess that has become app dev w/ JavaScript (https://github.com/cheatcode/joystick), but I expect many will dismiss it short-term because it's not "what everybody else is doing" (despite being far simpler and clearer than the state-of-the-art).
And therein lies the problem: groupthink. There are very few people asking "how do we simplify this" or "how can we make this more clear" and a whole lot of people trying to impress each other with their galaxy brain knowledge of unnecessary tech.
The good news is that it's not a technical problem, but a cultural one. People are afraid to think independently and so they just go along with whatever the "best and brightest" say to do (which is usually an incentivized position due to existing relationships/opportunities).
-
I don't miss React: a story about using the platform
Come on over rovers: https://github.com/cheatcode/joystick.
I promise you'll love it if you're switching from React. And it's full-stack so no more stitching together frankenstacks. Good ol' isomorphic JS for devs who value their time/productivity.
-
Entire website in a single JavaScript file
The truth I learned building my own SSR JavaScript framework is that it's not that complicated, it's just made complicated.
1. Get some data from a database/source.
2. Pass that data to a template/component.
3. Convert that template/component to HTML (using the given framework's version of renderToHTML()).
4. Return the HTML to your HTTP request.
For example, here's the SSR for my framework: https://github.com/cheatcode/joystick/blob/development/node/.... It blew my mind when I wrote it because I was under the impression it would be more difficult.
-
Ask HN: What is something exciting you're working on?
Working on a full-stack JavaScript framework: https://github.com/cheatcode/joystick.
Currently splitting my time between framework improvements in prep for a 1.0 (wrapping up a PostgreSQL integration today) and working on a deployment automation tool.
-
Back-end languages are coming to the front-end
I do use a virtual DOM but I only use it to patch the HTML in the browser (no synthetic events or anything like that). The meat of it starts here: https://github.com/cheatcode/joystick/blob/development/ui/sr....
My focus for v1 is on developer ergonomics and solidifying an API (this will be frozen after v1 with the only changes being additions if absolutely necessary—a component you write today will look identical to one you write in 10 years).
All future major versions will be solely focused on performance and security (my way of saying: I haven't stress-tested renders, but for the time being it will work well for the majority of use cases).
-
Ask HN: Freelancer? Seeking freelancer? (February 2022)
SEEKING WORK - Freelance/Contract, Remote, Tennessee, U.S. (Central Time)
I'm a full-stack JavaScript developer and UI designer, working primarily with React.js, GraphQL, and Node.js.
I run https://cheatcode.co and recently launched a new full-stack JavaScript framework: https://github.com/cheatcode/joystick.
Looking for 3-6 month freelance and contract opportunities. Best suited for working with small teams (standalone or embedded in bigger co's) and individuals looking to ship:
- Web apps (internal or customer-facing)
- Command line tools
- REST APIs (private and public) -- can do GraphQL APIs on request
- Technical documentation
Email: [email protected]
-
Ask HN: Freelancer? Seeking freelancer? (January 2022)
I'm a full-stack JavaScript developer and UI designer, working primarily with React.js, GraphQL, and Node.js. I run https://cheatcode.co and recently launched a new full-stack JavaScript framework: https://github.com/cheatcode/joystick.
Looking for 3-6 month freelance and contract opportunities.
Email: [email protected]
-
From Node to Ruby on Rails
For those looking for a legit Rails-like experience in Node: https://github.com/cheatcode/joystick
What are some alternatives?
react-use - React Hooks — 👍
goroslib - ROS client library for the Go programming language
arduino-cli - Arduino command line tool
SvelteKit - The fastest way to build Svelte apps
netlify-plugin-nextjs - A build plugin to integrate Next.js seamlessly with Netlify
emgo - Emgo: Bare metal Go (language for programming embedded systems)
svelte-native - Svelte controlling native components via Nativescript
sysinfo - Sysinfo is a Go library providing Linux OS / kernel / hardware system information.
joystick - Go Joystick API
ghw - Golang hardware discovery/inspection library
go-osc - Open Sound Control (OSC) library for Golang. Implemented in pure Go.
concise-encoding - The secure data format for a modern world