I understand the confusion, given the existing terms but it seems the intent behind the name 'VanJS' is to highlight the simplicity and 'bare-bones' nature of this new framework, aligning it with the 'vanilla' aspect.
While it might lead to some confusion initially, with clear and transparent communication about what 'VanJS' offers, it could still work as a brand that distinguishes itself by simplicity - or pivot to Van rentals
Might ?? Come now, be an adult and a thinking person ! Go down the hall find 10 js/frontend programmers. Ask them what do they think "Vanilla JS" might mean ?
Speaking as a dude who loves legacy Lisp - I once wrote an interpreter for it in Elm. I was disappointed to find there wasn't enough parenthesis in Elm! Sometimes the bell and whistles get in the way of my creativity and flow
It seems like we're living in the era of the 'Netflix Paradox' - the more our content gets decentralized - the more subscriptions we're expected to manage on our credit cards - but, unlike Netflix, there's no 'one size fits all' for news for most people.
A gaming would've been a good example - there's Steam and there's everything else, but is this the case for video streaming? One either shells out a noticeable sum for Netflix/Hulu/Disney+/ESPN+/HBO Max/Amazon Prime Video/Apple TV+/Paramount+/Peacock/... combo (with a number of those free on some year-long promotion), or, I've heard, as the those year-long trials come to end, fragmentation progresses, and diversity and quality of media on any single individual platform declines, people are simply starting to sail back to the high seas.
Maybe if this stream dies (and companies stop blaming it on password sharing or whatever, but realize no one is paying because it's not worth it anymore) there will be some partnerships and larger package deals. But I'm skeptical, as no one had solved how to slice the pie. Microtransactions were proposed to solve this but any attempts at those had ultimately failed.
So if I'm getting this right, the Steam Deck is shaping up to be less of a gaming console and more of a portable DevOps station with a gaming side gig. Guess we're approaching the era where one can fill out an expense report for the boss and sau "I bought this gaming console for development" with a straight face.
Loving the trend, though. Between Distrobox and Docker, containers seem to be the inescapable "Matryoshka dolls" of the tech world.
But all jokes aside, the flexibility this provides is impressive. If you told me a few years ago that I'd be able to run a full Ubuntu environment on a handheld gaming device, I would've raised an eyebrow
No, the Steam Deck is a gaming console. It just isn't deliberately locked out and the fact that it's a computer underneath is left there for you to use if you want.
If you want a portable DevOps station, you want a cheap laptop. You don't want to use the default Steam Deck keyboard for much more than entering a login name or something. A Steam Deck with a keyboard plugged into it is much closer to a desktop setup than anything I'd call portable.
But portability is the only question. It's still a full computer. It just isn't a very convenient one for anything other than games.
I personally do use it a lot like a Nintendo Switch, though. You can easily have a desktop-like setup at home behind a dock, and then pop it out and carry it off portably. It's not quite as slick as a Switch but it works. But, again, this is a desktop setup with the Deck standing in as the computer, not a portable setup.
Close but I'd say it's more like a handheld console with a Chromebook attached.
Steam Deck apps (mostly) have to come from a Flatpak repo to install correctly but Flathub (the default repo and therefore defacto app store on the Steam Deck) has lots of the common apps for daily use, even if they are largely unofficial/unsupported versions. So for 95% of people, it's definitely usable as a laptop/desktop replacement, but if you want to develop or want stuff outside the Flatpak repos, it's a bit of a hassle.
The idea of using Go and Alpine.js together for building reactive web apps seems promising. As you mentioned, Fir is targeting devs with moderate HTML/CSS & JS skills.
How does Fir handle more complex scenarios such as nested components, handling form submissions with client-side validation, and integrating third-party APIs or libraries?
Does the toolkit offer any built-in functionality or guidelines for handling these cases, or is the developer expected to handle them using custom code and Alpine.js plugins?
This example has most of the scenarios you have called out: https://github.com/livefir/fir/tree/main/examples/fira. Fir aims to limit itself to rendering templates on the server and making it available for all subscribers as a browser CustomEvent which is consumed by alpine.js for more complex interactivity. The expectation is the that the developer handles it via either alpine.js plugins or standard JS code.
[edit] This is still a work-in-progress so I will certainly add better guides and documentation moving forward. Although its good to get feedback that this approach might be interesting for at least some people.
I think this is adding unnecessary complexity. One of the reasons developers gravitate towards a framework like Alpine or HTMX is to write less JS and go back to enjoying HTML. Of course there are a lot of use cases that require custom JS scripting. But bootstrapping a project with another Go web framework and adding Alpine is also trivial. But keep going and follow your vision. I love these types of projects. Check this one out:
Hey. I have checked out pushup before. Its great. I guess I am taking a niche approach which not many would find useful. To clarify: What is adding more complexity? alpinejs ?
As devs we could create an app that sets a timer for social media use and then shocks you with a mild electric shock every time you exceed your set limit!
We'll call it the Zapchat or the Zapper and we guarantee it'll be SHOCKING how effective it is at keep us from looking at our screens every 5 min
Syncthing is like the reliable, quiet roommate who always does their dishes, whereas dealing with different file systems feels like trying to figure out who left their half-eaten pizza on the couch.
iOS literally doesn't have "just there for storage" directories that are not icloud. Either you use the photos pool, or you use icloud, or you use per-app directories that are local to each app. But then those directories cannot be accessed by other apps. Even if access to individual files is implemented, it's often very buggy.
Say you have a pictures directory shared via Möbius Sync. Then you want to edit one of the pictures with a pictures editing app that is not the builtin photos app. The app crashes, or cannot save an edited copy of the file into the same directory. I encountered this in real life.
Apple has a “files” app that lets you access your “home directory” on the phone. It def has “just there for storage” space. It’s literally the best way to access/delete some log files.
That directory doesn't work with Möbius Sync however. It gives an error when you try to set it as the local path for sync. Also, I can't figure out how to access that from Linux via ifuse: https://github.com/libimobiledevice/ifuse/issues/58
> iOS literally doesn't have "just there for storage" directories that are not icloud. Either you use the photos pool, or you use icloud, or you use per-app directories that are local to each app.
Isn’t this no longer the case
for the last 5 years or so?
‘Files’ allows to access local non iCloud folders and every app with the right entitlement can write/read there.
You can even integrate your own cloud service into ’Files’ making in indistinguishable from iCloud (in some ways at least).
Working copy has some of doing this. I had it syncing my logseq notes and it worked fine (other than merge conflict type things). The setup was fairly convoluted though.
iOS effectively blocks all background apps from accessing the internet except a few kb per sec. You are forced to pay apple for the convenience of a cloud backup. Walled garden dark pattern
- Syncthing is available in the Play Store. If it wasn't, I could use F-Droid or simply download the app from Github.
- It works in the background and it has access to my folders. I can take a picture and few seconds later it's on my PC without having to change or move anything.
Not saying that iOS is bad, but I felt tied when I had to use it. It's not for me.
I just found out it's a regulation from France regarding encryption (mostly declarative paperwork), so it's not an Apple App Store thing. Seems like Apple's App Store enforces it, but maybe not Play Store? And so either it may be published but may not be in compliance with regulations, or SyncThing did the paperwork but Mobius Sync did not.
Ah, the classic dance between regulatory agencies, lobbyists, and the cuteness of babies. It's fascinating how the lack of standards for certain toxins in food can lead us to lean on the water-based standards, even though it might not be the most accurate comparison.
I suppose it is a decent fallback -but it's a reminder that regulatory frameworks could use some refinement!
Cute that your response to endless collusion is that it's "decent" but “needs some refinement”. Have fun advocating for that with your vote at the polling station.
While it might lead to some confusion initially, with clear and transparent communication about what 'VanJS' offers, it could still work as a brand that distinguishes itself by simplicity - or pivot to Van rentals