HTML Templates Instead Of Reactivity | Prime Reacts
ฝัง
- เผยแพร่เมื่อ 9 ก.พ. 2025
- Recorded live on twitch, GET IN
/ theprimeagen
Become a backend engineer. Its my favorite site
boot.dev/?prom...
This is also the best way to support me is to support yourself becoming a better backend engineer.
Reviewed article: guseyn.com/htm...
By: Guseyn Ismayylov
MY MAIN YT CHANNEL: Has well edited engineering videos
/ theprimeagen
Discord
/ discord
Have something for me to read or react to?: / theprimeagenreact
Kinesis Advantage 360: bit.ly/Prime-K...
Hey I am sponsored by Turso, an edge database. I think they are pretty neet. Give them a try for free and if you want you can get a decent amount off (the free tier is the best (better than planetscale or any other))
turso.tech/dee...
"the DOM is slow"
> What if we had two of them?
These frameworks were meant for Single Page Applications, not the whole company website.
this is so true.... the feature creeping is so insane nowadays
100%. The JS community didn't lose me with React. They lost me when people started converting their blogs to React and locking themselves in to server-side javascript and proprietary cloud-products-build-on-other-cloud-products in order to use their front-end frameworks. But React is still a good solution for me when I need a highly interactive SPA. And yes, I have to develop it as a separate application from the server, both with a sensible API, state machines, etc. Pick the right tool 🤷♂
Yeah let me switch my company website to an SPA in some parts, sometimes, somewhere, oh wait the shitty technology can't support that and it barely integrates. What if we just SPA?Oh it works, cool.
react is a lib, not a framework
@@tri__yt I agree. People lose the distinction of website and app. And if you are in the middle (Nextjs), that seems to be the worst place to be
That article had the "He is confused but he has got the spirit" energy
I agree with his take that things have gotten so complicated over the past few years but whatever he was creating didn't make much sense.
Hi, I am the author of this article, you can checkout EHTML, hopefully it would make more sense for you. Cheers!
All of your videos are so jam packed with information and your character makes it so easy to ingest! Love it
This comes from the mind of someone who only knows frameworks.
We will forever repeat the mistakes of the past.
I don't know how to interpret this, but you got my attention. How would it be from someone who's only seen the framework light approach
@@theodorealenas3171 Managing state and dom was as total mess, so frameworks like Angular and React came onto the scene to try and manage those issues.
Arguably we've gone way too far the other way, but the younger devs won't have experienced the problems that led to those frameworks, so their new solutions may just end up taking us backwards.
However, maybe the platform as a whole is now so much better that those more direct solutions are now viable again.
I don't know xD
@@ReedoTV Bravo dude, they're reinventing PHP and then they will reinvent NextJS
im waiting for MVC and active records to be a think again
@@michalkowalik89 Right? A controller is nothing but a glorified switch statement. And framework people build entire vast hierarchies of the darned things!
Rumors out that this is what "Rick" was working on before getting fired.
Got 'em! 😆
And this is how EHTML framework has born.
I'm not joking, the author transformed this into a framework, I'm find it interesting and constructive, very cool article for just thinking things different
Thanks for the feedback. Actually I created this framework 4 years ago, just because I wanted to quickly make AJAX requests and map responses to HTML without the need to create elements in JavaScript. This article was written just to demonstrate the idea in vacuum. Also, I have ideas on how to introduce type safety via linter into this concept.
@@guseynismayylov1945 wait you created EHTML?
@@rajmajumdar5253 yes, I am creator of EHTML
his approach reminds me of these super verbose xml protocols where you had a hundred elements with a hundred attributes and all it did was "int i = 1; i = i * 2". Getting nightmares from his example but I like that he's trying. I myself have went back into pure html + js and tried to reimplement mechanisms that transform page layout and reactivity in a clean and concise manner without a 500kb framework in the background. it's a powerful learning experience and it's making me want to rewrite my website for the n-th time, without a framework.
This is the part I don't understand, how does a personal website benefit from reactivity and state?
@@theodorealenas3171it usually doesn’t. There’s generally no need to use something like React, Angular, etc. for a personal website and most people who do so seem to do it just because they stick with what they already know and try to use that for everything.
.NET maui go brrrrrrrr
JDSL ftw! Tom always knew
@@theodorealenas3171 You must lack imagination.
8:10 Read from the article, "You can already imagine how much easier it is to share state...." Imagine writing that as if it's a good thing lol. Shared state is basically the source of all spaghetti.
true, it ends up with a high coupling
Shared writable state is. Shared observable state isn’t.
One owner of data, multiple consumers of data
How spaghetti can my vet's About Me page be?
@@dripcaraybbx Not very spaghetti because that's a static HTML file that doesn't need or js or any mutable state at all. I don't really see how that's a fair comparison to a stateful application.
@@avwie132 This does not negate high binding. Your components depend on another component and wait for a value to be initialized. Also, if you want to change the state structure and don't know who is using what, you will break the application because of the high coupling. So this approach doesn't scale. But for small sites it will do fine.
I’ve been building web apps without front-end libraries for the past year. I don’t use this guy’s approach with the template tag, but for me I find it much easier to just append to the Dom as needed. This idea that the code becomes unmanageable is a self fulfilling prophecy, not an actuality.
Working directly on the DOM is jQuery all over again. What's old, is new.
@@Niosushonestly I'd take jQuery over these heavy modern frameworks and npm package hell any day.
Remember when you could just add jQuery as a script tag from a CDN and be done with it?
You don't even need jQuery to do it any more now that modern JS has more features and IE is dead, you can just use vanilla JS easily
I made my site's menus with JavaScript, while the rest was hand written HTML.
Then I was sorry that Emacs' web browser couldn't render it and I redid it in PHP. But how: the PHP tag opens inside of the markup, to give attributes to the elements.
It took several iterations before I accepted there's only going to be 4 menu elements anyway
@@georgehelyar yeah I was thinking the same thing. I know Jquery is still around but it’s kinda obsolete with modern js updates. Also jquery syntax is awful to look at.
you should learn C
Btw, what the author proposed is actually a lot how oldschool AngularJS used to do things. You would include the AngluarJS in script section, define a template element, create a service that would hold some state, and bind it to the template html.
I am the author of this article. You should checkout EHTML
This idea is the core of EHTML framework/library.
I used Handlebars or Mustache with template tag and vanilla js so you can inject js variables and you have a decent template language with if, foreach, etc... It works and it is pretty straightforward
Look up Mark Turansky's "Better JavaScript Templates." ASP-style templates that support native JavaScript without a template language. Sometimes less is more.
I love Handlebars but I feel like I need to move onto something like React for the future?
bro cooked, and then overcooked... i agree with the cooking, just not what actually ended up on my plate
Just checkout EHTML if you want to see a good example. I am the author of this article.
PHP i the answer and no one realizes.
reluctant like
And JQuery if you want your pages to have fancy dynamic elements
PHP so old
PHP way of developing websites is not that bad actually. It's just the syntax and stdlib of PHP that's bad, infinitely worse than TS.
@@igorordecha I know but with Laravel i can create a fully fledged backend with workers, queues, caching, dashboard and metrics in about 2 hours
The solution is pretty straight forward, accept that html and http are stateless environments and stop trying to put a square peg in a round hole.
Careful, or I'll put my peg in your square.
The solution is accepting this is a client server model and state needs to be synced just like any other client server implementation.
http also defines we should send all username and password in (almost) plain text and i don't see the engineers recommending that
Hey, I read a book and finally understands what this sentence means. Curious, will there be a push one day for new hypermedia controls to fill in the gaps that client side stuff is doing rn?
So you want to go back to the olden days where doing literally anything will refresh the page?
And this guys how we got to 30 javascript frameworks!
Cue XKCD "Standards" comic: 30+1 frameworks, or as JS sometimes processes it...301 frameworks. ;)
and you are the reason i have a crap code base at work
“He is low key inventing a new framework” 😂
I am the author of this article, you can take a look at EHMTL
This idea is the core of EHTML framework/library.
congrats guys, they reinvented forgotten knockout js
mxml and actionscript was the best front end language ever.. databinding both ways, treeviews, treetables, accordion, they have them all you name it.. unfortunately it needed a flash plugin to run in the browser.. and now its dead.. thing is html is like 30 years old and was never meant to build UI.. so what we have now is like a tech soup just to have something decent running in the front end.. i think its time they reinvent the wheel so browsers support better languages so we can use 1 language to build the UI.. i dont understand that they dont understand the problem here..
If we let bro cook any longer, Gordon Ramsey's going to burst down the door and scream "IT'S FUCKING RAW"
Every passing day I get ever more grateful I don't work with web.
Indeed, Webdev is such a convoluted mess of misery and tangled frameworks! Then again... developing for Windows UI, with Microsoft continuously reinventing Windows UI programming in ever worse ways isn't much better. Then you've got the multiheaded abstracted monster that is modern C++... I guess the ticket is: just stick with embedded programming in nice beautiful simple C!
@@ScienceAfterDark The trick is to make your own product and work for yourself so that you can use the tools you want to :)
@@hamm8934 and then you become Rick hahahha
@patorasco6266 i laughed too hard
The web is great, the problem is it's every script-kiddies first exposure to programming so there is going to be a lot of stupid shit.
That said if you are the one setting the rules it's just as fun as any other platform because you can use the smart and throw out the stupid.
The more complex a solution is, the more unlikely it should be the default approach.
According to this logic React doesn’t stand a chance
@@guseynismayylov1945 Sadly, the realms of ought and are, are rarely converging.
Not a fan of this approach. I've never once needed to rely on an element's attributes to manage my state except maybe for styling purposes. I'm not the biggest fan of React either but even hooks aren't as unwieldy as this.
You’re not a fan because you’ve never done this? Interesting approach to software development 😄
@@EdwinMartin I have, when I was a noob. Great argument btw. I've never driven with my back to the wheel either; I still know it's a sh#t way to drive.
I am the author of this article, if you want to see good examples, you should check EHTML
This idea is the core of EHTML framework/library.
Omg, here it comes we’re going back to good ole HTML/CSS
Omg
That's roughly how I make use of templates where I can't make use of frontend frameworks, but the articles arguments are not really correct because they didn't even solve what those frameworks solve. It's fun to replicate what these frameworks do and I did so myself to understand how Vue, for example, achieves their reactivity.
This idea is the core of EHTML framework/library.
And they joked about me as a programming language - HTML
Specifically, application state (ie the domain model) should be parallel to the view model. Embedding state within the components that isn't totally isolated to the components is OOP goop all over again.
Allow the components to access/bring in the application state, but don't embed that state within the components
Always funny to see backend guys talking about frontend.
Every time I look at the discussions around front end dev, it just makes me even happier I chose the SRE route.
This idea is the core of EHTML framework/library.
“You can come back to the good old days and simply enjoy writing HTML”. To me those were never good old days and I absolutely hated writing HTML/CSS. So glad that there are frameworks out there taking care of all that, so I can focus on writing functionality.
Also, the HTML the author was writing was not "good old days html"
i think this days html/ja/css are not so bad because all the features works the same way on each browser
Best conclusion ever !
This idea is the core of EHTML framework/library.
Looks like AlpineJS.
It’s EHTML
You did not like the idea in the end but you gave the author credit and treated them fairly. I have much respect for you not going the easy route and just roast the guy but instead approach the topic with positivity ❤
you can cast an int by just adding a plus sign before the string
Re: 10:55 - Virtual DOM is meant to win against `el.innerHTML = ''; el.innerHTML = renderTemplate(data);` (which it does), not against pinpoint data manipulation to do exactly what you need.
Generally, it's more desirable to distribute work and memory requirements to clients I think. Not everyone is a company that has resources to stream _videos_ to viewers globally
I'm more a designer than a dev today. but my background is in Front End. last time I was doing just. a favor for a friend to help him launch their startup. It was just a website, just a F# website. not an application. it was being dealed by their front-end team. I'm pretty good at HTML/CSS (I know its not programming) so I can draw then build what I done. gosh, how much EASIER would be if I could not use NEXT JS there!!! build processes are horrible. it it was just a static site, they would not be "screaming" at me because THEIR SERVER had an incompatibility with next 14, and I need to go back to 13 and change everything I done just. to help a friend (I'm questioning if it's still my friend btw).
HTMX and etc. seems like a breath of fresh air. a fixing on the hell developers look like they have conspired to make. definitely DONT use these to make just simple websites! it's painful.
This idea is the core of EHTML framework/library.
It is okayish, but lacks foundation and the template should not say what happens and where but I think it’s totally fine to subject those topics. The framework hell is not a good solution. I am awaiting the proposals that are there for ES to come like the NodeParts, placeholder in templates and the new redesigned html imports.
Yeah. I wonder why they didn't go for LaTeX macros too btw. To define a li with an a and preset attributes. But maybe these will do
I am the author of this article, you can check EHTML to see a really good examples where I am mapping AJAX JSON responses on html templates just using HTML.
Thanks for reminding me how good React is
or any major frameworks.
Noob question but if htmx has to make server requests for html, what happens to a user in Australia using a website which has servers in the US? Isn't it just slow and unresponsive
That'd be an architectural issue. No front-end technology can make that data arrive faster across the globe.
??? It doesn't have to render everything server-side. It's not like every partial update to the DOM must be driven by ajax requests.
No, the difference is the client asking the server for html snippets vs the client asking the server for json. You keep the delay between request and response, but you reduce the javascript overhead. You likely even get a more responsive website with htmx because there is no need any more to have consecutive ajax requests for loading a single page.
Yep - you're hoping that the devs set up infrastructure near Australia
@@basione But you don't need data arrival across the globe if you store the state client side, do you?
If you want to convert a string to a number instead of doing times one. Just add the plus symbol at the start of it. `+variable`
Yeah this is the way I knew how :)
You forgot? @@dandogamer
Without benchmark results from a low level debugger, who is to say which way is better?
@@mkvalorI'd like to see the receipts but I would assume they are similar in cost.
If you consider that all mathematical operations in a computer are just addition operations then adding zero and multiplying by one should end up being the same operation.
The actual conversion that happens before the mathematical operations will probably vary in time but should be consistently tied to the features of the inputted values (like the length of the input).
I hate both. I prefer the code the speak for itself. Unless the programmer is well read on the quirks of Javascript's insane type system. I prefer to just see a parseInt or parseFloat. He's not being clear and concise with his code. He's just being a smartass.
I love templates! I used them in production multiple times now.
I wrote this article. You should check EHTML, it’s a template language based on the ideas in this article
I've made a couple projects with web components and wish more developers left frameworks and started using native controls.
This idea is the core of EHTML framework/library.
This feels very close to AlpineJS to me.
It’s coming from EHTML. I am the author of this article.
For anyone still worried about the job market: These are the type of articles that will ”educate” our next generation programmers. You’ll be fine.
For the next 10 years says Robert Martin. That's before I'll retire so I may get to see the sunrise
@@theodorealenas3171 I don't trust Bob to watch over a painted sheep
@@gileee I don't trust you to ship a painted watch
@@theodorealenas3171how are you going to retire, tell a secret
nothing like typing html inside multi line strings and appending them to the DOM with jquery, good old days
This idea is the core of EHTML framework/library.
Im surprised that a channel called Prime Reacts would even consider to read an article against reactivity.
LOVE seeing the move toward Native JS! The APIs are SOOO easy these days that there's almost no need to use a framework so long as you just have good code organization habits. A senior has virtually NO problem working in that environment. BTW, most frameworks STARTED OUT as proprietary systems that eventually became abstracted enough to use across any project. (Pssst!... The framework giants don't want you to know this)
4:58 that's not true. state = {count:0} puts state on window but const state = {count:0} does not
It meant global in terms of scope, but you're right
There's a JS library called reef.js, it adds the concept of signals to vanilla ja and works well with web components because the author is a vanilla js/web component fan
is there a reason not to do
parseInt(button.getAttribute('data-Count'))
?
Less to type? :D
try this:
parseInt("0.00000005")
parseInt(0.00000005)
I once worked at a company that used a custom framework that was actually based on php + templates + jQuery, worked pretty much like this. It worked I guess, but all the tags are still in the inspector even though they dont show up on the page. that alone killed it for me, coding for it was a mess.
Really? I also did something like template elements that only show up on inspector, in a previous iteration of my site, I liked it. You could see how templates expanded over time by looking at inspected eelments
@@theodorealenas3171 I mean I wasn't a fan of showing the user code that he shouldn't have access to yet and in a raw form. But it's far from the worst thing I ever worked with lol
@@refeals Shadow DOMs are still accessible to the user so I'm not sure where the concern is of "showing the user code that he shouldn't have access to". Anything client side is inherently viewable.
@@RaveYoda good point. Idk just felt weird i guess
At that point just create a server side PHP application with a competent framework and require a few extra refreshes.
As a veteran programmer with +30 years experience, the entire JavaScript eco system is the biggest pile of shite in the history of computing.
the fact he did not propose any solution for change detection says a lot about why it seems "less complex"
I am the author of this article. You don’t need a change detection, you need to solve real problems. This is why I created EHTML
These people are the motivation why I'm intending to learn HTMX and I really hope the rest of the world will do the same. This madness has to stop. Now.
HTMX is popular because of memes. It’s not “that” good yet, I like it, but full stack devs anyway will fuck up CSS
I am the author of this article, you can check my solution EHTML
@@MissViolettaBI think the philosophy of using http like it was intended is the selling point. The actual library seems like more of a proof of concept. I think you could very easily employ the philosophy of htmx into your vanilla app without actually using the htmx script.
Hot take: Everyone in the comments saying "use this or that framework instead" needs to learn JavaScript.
I feel like the issue with most modern frameworks being they let applications grow in a natural way.
Using templates and traditional backend services without the need for dependencies generates understanding while developing.
It's like leveling your way to max level instead of using an xp scroll. If you use the scroll you miss out on understanding how the skills work and lose the understanding of how to generate a "symphony". Like my embedded experience relates to writing linux components which relates to writing web servers which informs security and how to write large software projects. I can make a course graph if needed. The reason why "jumping into the deep end" is probably not a wise decision.
A framework i love that is using templates and a way to integrate state into the templates is Lit. I find it to be a more elegant solution and its a very small framework, but not very popular
Initially it was an idea similar from your video called Polimer (the first version of Lit)
This idea is the core of EHTML framework/library.
All I can say is "hallelujah"! I never understood replicating all the state on the client with complicated frameworks. Sure, it works great for Facebook, but most apps aren't Facebook. So much easier to just bring down the HTML with SSR, and adjust the pages as needed with vanilla js. Btw as a C#/vanilla JS/Azure programmer about 3/4 of Prime's stuff goes right over my head. OK, maybe 7/8....
I am the author of this article, you should check EHTML, probably you would find it very useful
Whew, that first paragraph is the hottest of takes. I do agree that while React is useful, we should all still know vanilla JS.
React is harmful. It solves non existing problems.
Reinventing the wheel for no reason.
Isn't Vue doing similar things like this, but way better?
I've learned Vue during covid and I'm such a fan,
and I feel Vue is doing what this person is trying to do. But better.
Yup :) with the powerhouse of Evan You leading us to the promised land
A number in string form * 1 basically does Number(stringnumber). It's faster to type, that's all.
Move to the Phoenix Framework and Liveview and all the js madness goes away, true server side state ... on the server, and handle updates via tiny websocket data calls to make the dom reactive. After 20 year writing JS... Liveview is just so much better
This is objectively terrible, but I learned something so nice article. We need more people like this in the world.
I am the author of this article. If you want good use cases, check out EHTML
How does HTMX solve the problem of syncing client & server-side state?
It seems like you're right back in state co-location hell the second you have a client-side action that changes server-side state, but can't wait on HTTP w/o killing UX.
It solves it by not having client side state in js, the state is the html markup. Every click is basically sent to the server, which modifies it's state, and sends back the appropriate html fragment. If you have some highly interactive components like maps or sheets, you need to implement it by vanilla js or some framework. But for any basic state change like count++ or appending a row, it's perfect.
@@peterszarvas94 And if the client's has bad internet, how would you do optimistic updates with HTMX?
@@peterszarvas94what happens when the server decides the state change, and not the client
@@jaeger2278 you can do polling with htmx
I am the author of this article, you can check out EHTML to see a real good examples.
These minimal frameworks are and always will be a bad idea.
After almost a decade of trying out all the frameworks under the sun and attempting to make my own probably a dozen times these are my conclusions:
- most websites do not need a framework, npm, or a build system of any kind
- the best libraries are usually the ones that are just a single js/ts file you can hotlink or copy into your project
- forking said minimal libraries to add your own features is the correct approach, don't hack an abstraction layer or plugin system ontop
- typescript is worth it, but only when you're creating libraries
- webcomponents kinda suck, but they are great for implementing progressive enhancements
I can’t imagine the sheer horror of a large codebase that has had 20 odd developers hacking pieces on to this over 4 years.
“Global state is fine” is completely ignoring the realities of software development.
fr
Global 'window' is legacy. But that doesn't mean we have to reference it every single time. You can ask window as argument in every function and that's what I prefer to do. This creates the annoying problem of prop passing which I consider a good problem to have because this forces to think about application design.
This guy just built his own crappy framework with 1 user. Why not instead use a proven, battle tested framework that thousands of people use daily, that can help each other out and improve the collective knowledge?
I also built whole application based on it. If I could find a framework that could do what EHTML can, I would not bother.
Because it's a deadlock to getting out an application, in some settings.
You know the "build your stack" obsessors? Who basically do what Skyrim modders do (99% configuration, 1% playing)?
Programming languages are already so powerful. It's easy to take a few hours to write a few functions to do exactly what you need for your specific application. And, then you'll understand everything going on, instead of adopting some hyped-up black box.
Frameworks make anything that's not in the scope of the framework way harder. Simple example: basic canvas animation in React vs raw JS.
But if you want me to give you a simple example: consider getting out a JSX / frameworked-up app as fast as possible, vs pumping out a slaw of PHP as fast as possible.
In my experience, the first takes ages for people to figure out how to tame their dependency dragon; often longer than it takes for some PHP loser to pump out some garbage functions that do exactly what he needs.
Wait, so you're telling me the things I've been doing for the last two decades, because I hate the state of web dev, might suddenly become hip again? Maybe I better break out that pair of Jenkos and oh! That one t-shirt I still have with the picture on the back!
He will quickly learn that his idea is not really an idea and that it is BS when he get's more expirience in building frontent libraries.
next post from this author: "honey i made another js framework"
I did, it's called EHTML
Wow I actually invented this at a company that refused to allow us to use third party libraries. It was a decent solution imo
I hate how the author dismissed the name collision problem. Naming is one of the 2 hardest problems in programming (right besides caching and off-by-1 errors).
"Just name better" bro that only works with a counter button page.
The point of components (doesnt matter if its web-components or JS frameworks) is that I can have a 100 separate counters without bloating the global namespace with counter-1, counter-2 etc.
I also can use a "counter" state in an other component and don't have to worry if it's already been taken in this particular page.
And I can create a component library that matches the company design and build a website like lego. I don't have to copy-paste 10s of lines of complicated markup every time I want to render a datepicker (that argument is pretty weak actually because its solvable by server side templates or whatever this thing he proposes. It's just an argument against vanilla HTML+CSS+JS for more complex sites).
I'm not advocating for a heavy JS framework but I'm saying we need a good system for creating semi-isolated(with access to both global and local state), reusable components. Web components suck, React is a bloated mess and HTMX is just an utils library for vanilla HTML so that you can modify parts of markup without reloading (it doesn't really solve my main issue). There's no good solution.
Also, React has no real alternative in the mobile app world. And btw on mobile you can throw your HTMX mindset of sending hydrated HTML to the client out the window.
4:54 Wrong. Global constants do not become properties of the window object, unlike var variables. You can confirm in in the browser in 2 seconds, have a look at window.constantYouSet - its not on there my guy.
It meant global in terms of scope, but you're right
Still waiting for the template demo that shows how it allowed them to build better interactive user interfaces for the user and not the developer
Insted of str * 1, there is also +str. cleaner. am i missing some con here?
Not just about what convivences we choose to develop with, these are the crappy performing behaviors making websites we end up being users on.
React , tailwind et al encourage bloat and soppy architecture.
It's obnoxious waiting for a frame to load that then fetches the content, then has to render that content, then update that content, then finally display that content and wait for interactivity; and that that isn't something that occurs only for the first load on a lot of "websites".
Meanwhile memory usage skyrockets and if your one a phone you now have a heater with a dying power source in your hand.
And userscripts and userstyles to fix these sites become harder and harder to make and maintain because of generated html divitis soup because more and more developers are given up on learning how to name things.
"...only to then turn around and use a library which calculates diff between DOM and Virtual DOM and does those direct manipulations anyway."
First thing, it is not calculating difference between DOM and Virtual DOM, rather it looks for difference between old Virtual DOM and new copy of Virtual DOM that has changes, confirms what the changes are and then updates only what is needed on real DOM. Second, it's not direct manipulation because it's not us directly manipulating it, automatic system does it based on how state changed and that's the whole point of these libraries.
I still believe that jails-js is a better alternative about "diferent way to think".
There are too many solutions full html or full js, and very less alternative like Jails which is use html and write logic on top of that without losing your mind...
It´s not because I thought about it, but I can´t see anything alike... and I wanted to see more... Not a React/Angular fan... not a htmx fan either... they live too much in the extreme edge for me...
4:59 while const state is "globally" accessible it still doesn't define it on the window object.
Then do it yourself lmfao
true, but you can also do window.state = ...
No, var at the top level of a script is on the window, const and key are block scoped see codepen DOT io SLASH anthonybullard SLASH pen SLASH RwdrGrR (thanks YT for making me do weird stuff to make url appear).
It's not even global in the sense that it's shared across modules if using a script tag with type="module", as modules have their own scope.
@@peterszarvas94 We can use var state instead. I was just clarifying that const is not the same behavior as stated in the video.
I love his first snippet. But I do have beef with the "1"*1. He's being a smartass and sacrificed readability in the process.
SHOTS FIRED!
The guy just reinvented Alpine.js... In a way.
What a convoluted way of saying you became old.
Looks like what would happen if HTMX and Alpine had an illegitimate child ✨
It would be EHTML. I am the author of this article
I did nearly the same, but with webcomponents, but I did create also a Designer for the templates
This idea is the core of EHTML framework/library.
Like HTMX but just native
Progressive Enhancement 2024
I'm an anarchist. I fight the state.
Just watched the video about "The truth about htmx" then this pops up lmao nice transition 4 months later
Why reinvent the wheel? AlpineJS does this and more!
looks cool, did know about that. I am the author of this article, I created EHTML, it works in a similar manner, but also allows you to fetch JSON and map it to the tamplate.
All this really needs is an LSP and it could work.
really missed the opportunity to end it on "try-agen"
I hate when my server returns html. Html response means that you don't have any control of your data on the client side at all. Also, all of your endpoints began to look ugly. Also, it oddly separates logic- and logicless parts of your html. I want my APIs to return some helpful format (mainly json, of course).
But I found the perfect solution for me: use htmx alongside nunjucks in case I need some data manipulations on the client side or use mustache otherwise.
Is it worth it trying to use Astro with HTMX? What would be the benefit? Or should you just use HTMX on it's own?
garbage. 😒
"look, we can just use template tags!"
the first thing he hasn't even addressed at all is updates - anything you clone from a template becomes just DOM elements with all the same difficulties. updating a single text node, sure. now try updating a list? ha ha. try adding or removing elements from a list. try getting portions of UI to get added or removed on the fly. this is where the fun starts and pretty soon you've built yet another half-baked framework.
if you've been here for long enough, you've been there. 😅
I remember doing something similar way back in the jQuery days - before but we would just put the templates in nodes. no big difference - as soon as you start adding interpolation syntax to your tags, you've gone outside native HTML, you're building your own template engine anyway.
sorry, but there is no idea here. get back to work. 😉
I am the author of this article. If you need update list of elements you use forEach template. You just release templates with new mapped data, you don’t need to create anything. Check EHTML, you will find more valid examples
*1 to force number conversion so the next + won't try a string concat I guess