pianojacq
joystick
pianojacq | joystick | |
---|---|---|
3 | 49 | |
- | 194 | |
- | 4.1% | |
- | 9.9 | |
- | 11 days ago | |
JavaScript | ||
- | GNU General Public License v3.0 or later |
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.
pianojacq
-
Modern SPAs without bundlers, CDNs, or Node.js
As someone who does this too: it depends. If you take time out every now and then to completely refactor your code base it can actually be surprisingly effective. I've done exactly that on my last project and I'm pretty happy with the end result, you can have a look for yourself:
https://gitlab.com/jmattheij/pianojacq/-/tree/master/js
This project will likely never be finished, there are always nice new things to add or requests from people, there is no commercial pressure because it is a hobby project and I don't have a boss to answer to. And even if such refactoring operations take me two weeks or more (this one I did while I was mostly just working on a laptop without access to a keyboard so it was sometimes tricky to ensure that nothing broke) in the end it is worth it to me because I am also paying the price for maintaining the code and if it is messy then I would stop working on it.
The project moves forward in fits and starts, sometimes I work on it for weeks on end and sometimes it is dormant for months. In a commercial setting or in a much larger team I don't think this approach would work.
-
Ask HN: What happened to vanilla HTML/CSS/JS development?
Two things:
- adding interactivity to a web page vs building an application. Those are not the same thing, and what you read applies to the first
- there's a widely accepted belief that vanilla js is not suitable to build apps. I don't buy in this belief. I have a built networked Scrabble game written in vanilla js. Both the backend and the frontend. This simplicity allowed external contributors not well versed in the modern web stack to contribute. I also was able to enter the code of Pianojacq (from jaquesm) [1] and contribute quite easily because he also chose vanilla js. This simplicity is very valuable, and lost with modern framework, and nobody is really concerned about this.
I've done some React development, so I know my way in a modern app. I've also contributed to a frontend written in Vue. I think they solve problems but bring complexity to the table, in particular the tooling (bundlers, minifiers, etc), the dependencies and the debugging being much harder.
It seems DOM manipulation through native browser API scares many people, but when it's what you are familiar with, your usual "framework", it's manageable. You need to be disciplined to avoid things getting messy (a discipline frameworks partially enforce), but I really believe you can go far with vanilla js.
I believe React & Co are often picked to ease beginners' contribution, but they actually do require expertise. I'd rather touch vanilla js code from a beginner or an experienced developer than a React code from a beginner.
It's a matter of taste. Vanilla JS has the taste of fresh air to me. It's zen. You write the code and it runs. No tools, no slow compilation, no minification that complexifies the debugging. Minification which is only useful because with those framework you bundle an awful quantity of code in the first place. Yes, source maps exists but they don't do everything.
But today you won't have access to the whole ecosystem of existing React components with vanilla JS. It might be a curse or a benediction.
[1] https://gitlab.com/jmattheij/pianojacq
-
Lots of progress on the piano practice software
As for 1) yes, I can do that, the reason it is set where it is right now is because very soft keypresses on real pianos with sensorbars installed are typically fingers brushing keys on the way to other keys and these false triggers leave a lot of errors that aren't really errors. I'll make that setting configurable.
2) yes, if you look in the 'midi' directory on the gitlab site ( https://gitlab.com/jmattheij/pianojacq/-/tree/master/midi , but also linked from the application) there are whole bunch of them that all should work well
joystick
- Show HN: Joystick – A Full-Stack JavaScript Framework
-
Ask HN: Freelancer? Seeking freelancer? (April 2024)
SEEKING WORK, Tennessee, United States
Remote: Yes
I'm a full-stack, JavaScript/Node.js developer and designer. I'm the creator of the Joystick JavaScript framework [1], Push deployment service [2], and Mod CSS framework [3].
I also have experience with MongoDB, PostgreSQL, and MariaDB (limited but competent) and devops (K8s + Docker and bare-metal linux admin, the latter preferred for simplicity/stability).
Currently looking to take on clients who are open to using Joystick, Push, and Mod to design and develop their app. Because it's still at a pre-release version, I'm willing to work out deals around pricing to get some more test-cases under my belt. Ideal client is a solopreneur w/ funding or entrepreneur with previous experience + funding. Open to working with startups (early or established), but only on greenfield projects where use of Joystick is ok.
Email: [email protected].
[1] https://cheatcode.co/joystick
[2] https://cheatcode.com/push
[3] https://cheatcode.co/mod
- Ask HN: Freelance website builders/maintainers, what's in your 2024 toolkit?
-
Web Components Eliminate JavaScript Framework Lock-In
There is. I was frustrated by all of the chaos and built a solution [1]. Not too far of from an RC1 and then a 1.0 (which is being done slowly so I can freeze APIs and avoid the typical JS rug pulls).
[1] https://github.com/cheatcode/joystick
- Web Components Will Outlive Your JavaScript Framework
-
We should start to add “ai.txt” as we do for “robots.txt”
I've been (slowly) writing a new type of OSS license around this exact concept so it's easier to (legally) stop LLMs hoovering up IP [1] (under "derivative works not permitted").
[1] https://github.com/cheatcode/joystick/blob/development/LICEN...
- GitHub - cheatcode/joystick: A full-stack JavaScript framework for building web apps and websites.
- Joystick: A full-stack JavaScript framework for building web apps and websites
-
React is a fractal of bad design
Joystick [1] will let you go. No Stockholm syndrome. No lotion in the basket.
[1] https://github.com/cheatcode/joystick
-
The Great Gaslighting of the JavaScript Era – The Spicy Web
If you share the sentiment of the author and want to get on the road to recovery, I submit Joystick [1]. I had similar frustrations to this and decided to do something about it [2].
[1] https://github.com/cheatcode/joystick
[2] Please give it an honest a look and save the XKCD "muh standards" comic and accompanying snark for after you've taken it for a spin.
What are some alternatives?
zynthian-sys - System configuration scripts & files for Zynthian.
SvelteKit - web development, streamlined
prehistoric-simulation - Simulator in browser
react-use - React Hooks — 👍
systemjs - Dynamic ES module loader
concise-encoding - The secure data format for a modern world
modern-todomvc-vanillajs - TodoMVC with Modern (ES6+), Vanilla JavaScript
svelte-native - Svelte controlling native components via Nativescript
yhtml - Tiny html tag function for rendering Web Component templates with event binding
next-runtime - The Next.js Runtime allows Next.js to run on Netlify with zero configuration
arduino-cli - Arduino command line tool
htmx - </> htmx - high power tools for HTML