Reject Web technologies - embrace native mobile app development
Compose feels like React but without the bad JavaScript parts, really pleasant experience!
Ah, yes, let’s have thousands of specialized apps, each with uniquely expiring dependencies and vulnerabilities, instead of one browser that can work with apps that are standardized for OSS, UI, accessibility, performance, inspection by humans and machines, and security.
I love Compose, creating UI is actually fun. The whole ViewModel thing though I don’t love
I love Compose, creating UI is actually fun.
It’s a good time, for sure. That being said, I’ve stopped working with UI, and I don’t really miss it. I still do some side projects in Compose though, and it’s always way better than XML.
The whole ViewModel thing though I don’t love
When it clicks, it’s actually not that bad imo. I think the main problem is that Google aren’t really explicit enough about how to leverage them effectively, and as such they can be pretty hard to get right.
If you know HTML and Python already I would recommend going for something like jinja2 + flask or fastapi and try some htmx stuff no need to use everything you can just refresh the site at the beginning. This should be pretty beginner friendly. It really depends on what you want to do. I don’t know much about Hugo or Publii. If you want to make an interactive website and not just a blog or static website I would advise you against using either of the two. If you want to get a job in frontend webdev I would advise you to learn javascript (https://javascript.info/) and some framwork like react also learn tailwind or css.
I’ll check those out and see if I can get a good workflow going for it.
I wanted my first web project to be a static site since I really only need a blog at this point in time. The use case for my blog really would be to write about chemistry and chemical engineering stuff I think is cool. Having a worksheet repository for my students as well that they could access with some encryption so the access is restricted. I’d love to try the fancy stuff on websites, I just need to get the poison of “JavaScript is spyware” out of my head.
It’s pretty disorienting to figure out the “right” way of learning web development after the loads of slander I’ve seen in memes. Im sure youve seen the same about React, JavaScript, and something about “NodeJS”. I wasn’t really too aware of software other than doing calculations on data collected from DAQs. Any resources you’d recommend to check out?
I guess I should ask the question, what exactly is all the fuss about surrounding some of the frameworks? I definitely can see the argument about adding more layers of abstraction can obfuscate the underlying mechanisms of the codes thus increasing the amount of potential vulnerabilities. Particular companies and developers turning evil is also. But some of the rhetoric becomes “They’ll put a miner for your crypto” “They’ll siphon every facet of information about you”. The most bizarre I read was how to figure out the outline of 3D objects surrounding the user via the pattern in white noise detected by an interference pattern.
Histrionics aside, is there a good resource that I can read that dismisses common falsehoods that is generally reflective of what constitutes a " good" framework? Thanks for the help!
https://hypermedia.systems/introduction/ maybe this is a good read if you do want to go a bit against the current webdev mainstream. Disclaimer: I have not read it yet but i will.
I thought HTMX was a joke, but they’re serious.
C’mon, what’s not to like about bonding every UI action against a remote server? What’s a few milliseconds anyway? I’m sure it works fine over cellular networks. I mean, it works great on my dev machine! /s
What kind of you UI action are you talking about? Most of the time you need data from the server and if you want have some animations with css it will be client side anyway also it’s not like you cannot write JS. I mean downloading thousands of lines of js for some web framework over cellular does not sound better tbh.
That’s a strawman. I don’t need 1000s of lines of JS to swap a UI. I can do it in 1 line with Web Components: oldElement.replaceWith(newElement). And those modules can be lazy loaded like anything else.
This is just DX in name of UX, which is almost never a good idea.
And maybe you’re fine with throwing a server computation for every single UI change, but I’m not made of money and I much rather have stuff on a CDN.
I personally don’t like the htmx style of coding. It often feels like having to explain what I want to do to someone else using only a limited set of custom words, instead of just doing it myself.
I understand you but for me it’s the opposite I am not bound to using js for everything and can just return html from the server like I want. Also everything else still works I can write js if I want to. Htmx gives me more words I can use in html not less. Also I can manage the state via the url and the server. In other frameworks I often had the problem that I was writing the same logic twice in backend and frontend.
I’m good with my Vue, thanks. I hate React though. I can see htmx simplifying some things and being adopted by front-end frameworks. The same way improvements in HTML and CSS have been adopted.
When you say “and”, do you mean together?
I love Vue, first time I’ve heard of AlpineJS. From my quick searching, they seem pretty similar. What advantages does one have over the other? Thanks :)
Ah, sorry, that was a bit confusing on my part. I use them entirely separate. Here are some real world examples:
Vue: new projects that will require multiple components, state management, etc.
AlpineJS: when I have a tiny project/demo that needs reactivity, or if I have an existing HTML setup that needs state management and reactivity bolted on after the fact (like an old site or something like that).
Fellow Vue enjoyer! I love Vue, it’s so friendly. Maintaining a complex React app feels like getting dragged behind a truck down a one way road.
(Did you like my two way data binding joke there?)
