Пікірлер

• 
  @DanielTSasserII5 сағат бұрын

  I Am enjoying the HTMX, Alpine,Astro, tailwind stack with nestJS for all sensitive rest api stuff.

• 
  @chaitram414111 сағат бұрын

  Can we work while doing 42 and how many months course is it?

• 
  @KodapsAcademy10 сағат бұрын

  You need to finish the core of the course within a year, otherwise you are out If you're fast it might be feasible to work part time while doing the course. And from there on you choose your path and your subject matter, so it can be as short or as long as you like (within reason).

• 
  @morrning_group12 сағат бұрын

  🌟 Wow, this video was incredibly insightful! Thank you so much for breaking down the pros and cons of HTMX vs React in such a clear and practical way. 🚀💻 💬 I have a question: Do you have plans to make more videos comparing different web technologies for specific use cases? It would be awesome to see more in-depth analyses like this! 📊🤔 Keep up the great work! Can't wait to see more content from you! 🎥👍

• 
  @brendanalexander6053Күн бұрын

  Objective fact: Angular is the GOAT

• 
  @ishanpareek7150Күн бұрын

  Great stuff!! The efforts you took in giving subtitles is incredibly admirable. The content of the video was of course top notch.

• 
  @KodapsAcademyКүн бұрын

  Thank you very much :)

• 
  @JatinKhatri25Күн бұрын

  Loved the way you explained man!

• 
  @zunnoorainrafi5985Күн бұрын

  Make video on Remix Vs Nextjs

• 
  @science_trip2 күн бұрын

  I m using jQuery, and In some Rect projects I ve destractured the ajax module from jQuery import { ajax } from 'jquery' I m chaotic evil 🤣🤣🤣🤣🤣🤣

• 
  @HiltonFernandes2 күн бұрын

  Great video ! Amazing clarity and conciseness. I'll keep it in my "Watch again" playlist.

• 
  @ubucux2 күн бұрын

  in full english, la grande classe ;)

• 
  @KodapsAcademy2 күн бұрын

  To be perfectly honest … English is my mother tongue :P

• 
  @ubucuxКүн бұрын

  @@KodapsAcademy ah ouais, je me disais aussi... Bravo pour la qualité de tes vidéos ;)

• 
  @KodapsAcademyКүн бұрын

  Merci :) (j’attends que YT m’active le multilingue pour faire en 2 langues sur cette chaîne :D)

• 
  @vittoriuz2 күн бұрын

  You don't learn Go, you just start writing in it

• 
  @codokit2 күн бұрын

  Hotwired Turbo plus AlpineJS have brilliant balance.

• 
  @giovan74822 күн бұрын

  the editing on this video feels like a schizophrenic episode.

• 
  @KodapsAcademy2 күн бұрын

  That’s outside my field of knowledge so I’ll gladly bow to your superior knowledge :P

• 
  @elcsie56793 күн бұрын

  Zig

• 
  @miindaugas4 күн бұрын

  Touched both for long time trying to avoid Angular projects.. at the end of the day

• 
  @muhammedalikosen94694 күн бұрын

  Valuable infos. Perfect ambiente. Above a huge hidden experience. 👍

• 
  @huw16764 күн бұрын

  That's a fair assessment. I really like Angular, having used it since 2014. React is one I want to learn. Wiz sounds very interesting. Thank you

• 
  @aleksandarstanisic18484 күн бұрын

  I quit both 😮

• 
  @user-rs7fz4qu9u5 күн бұрын

  Prisma dsl is very easy and intuitive and it is way easier than writing your own database schema yourself I like it

• 
  @JohnJohnson-ch6xq5 күн бұрын

  Which one is beginer friendly ?😊

• 
  @KodapsAcademy5 күн бұрын

  React is probably easier to get started with :)

• 
  @jobiej74166 күн бұрын

  This is a better use case for web components.

• 
  @meka49966 күн бұрын

  In short, if you have existing C projects, use Zig to fix it. If not, use Rust for new projects.

• 
  @DionsTravels6 күн бұрын

  I keep hearing this guy mention agility, but what good is the agility when you need to rewrite your react components 20 times 😂 😂

• 
  @KodapsAcademy5 күн бұрын

  This guy is wondering why exactly you find yourself needing to rewrite the react component 20 times ; it kind of feels like blaming your tools :)

• 
  @VishalTheK7 күн бұрын

  This is the best explained video on youtube.... Angular vs React.

• 
  @dryphresque71138 күн бұрын

  Thank you for this video. With signals and zoneless angular is th best for me 👍

• 
  @bayelrey80288 күн бұрын

  Lua is nice! I use it to make plugins or write small scripts for Q-SYS. Q-SYS is QSCs control AV control platform. Each controller is a DSP and you can add behavior to the audio programming, control a display, control video switching devices, etc. I recently wrote some Lua to control a Denon network recorder via IP, an Epsom projector, Extron presentation switch, change the GUI behavior/layers/text/button behavior/css properties, etc. It's simple but really really powerful

• 
  @kuthub19898 күн бұрын

  Laravel (Vue/React) Inertia

• 
  @KodapsAcademy8 күн бұрын

  I’m not sure I understand the point you want to make ? Can you expand ?

• 
  @bonkers_dave9 күн бұрын

  Enormously helpful. Thank you.

• 
  @KodapsAcademy9 күн бұрын

  Glad to be of service :)

• 
  @boopfer3879 күн бұрын

  Yes and yes! Story of my last 5 years. Have you looked at phoniex?

• 
  @gungun9749 күн бұрын

  Great talk. Except I don't need React at all since WebComponent are not that bad that some people say and vanilla JavaScript is not just a step in the process to learn React.

• 
  @kamilziemian9959 күн бұрын

  Learn C, then Go, then C++, then Rust, then Zig. And Common Lisp!

• 
  @markyin30299 күн бұрын

  Your perspective is unique but very understandable.

• 
  @KodapsAcademy9 күн бұрын

  Thanks :)

• 
  @user-hj5mz4lz1x10 күн бұрын

  I think HTMX is a very elegant solution, but I use Livewire for Laravel in conjunction with Alpine JS. Is there an equivalent to Livewire for Symfony?

• 
  @KodapsAcademy10 күн бұрын

  Symfony has bundles that integrate directly with Turbo (search for « Symfony UX »)

• 
  @TheAliAhad10 күн бұрын

  Greate example!

• 
  @KodapsAcademy9 күн бұрын

  Thanks :)

• 
  @patilmayurn10 күн бұрын

  Also, Angular was NOT released in 2016, it was Angular 2 which was released back in 2016. Full of mis-information, you know it's a crime to spread one?

• 
  @patilmayurn10 күн бұрын

  React was initially released on May 29, 2013 and not in 2011 as mentioned in the video. It was Angular 1's era back then.

• 
  @pratikshares10 күн бұрын

  But, didn't answer the question: Why Zig pays more?

• 
  @VeitLehmann10 күн бұрын

  That's a perfect use-case for HTMX. But I guess sticking with jQuery (and replacing the old jQuery plugin with an alternative or with custom code) would have done the job equally well. There are some things that I don't like about HTMX: Being basically just written as custom HTML attributes makes editor support tricky which might be problematic with refactoring and cause bugs in the long run. I'm also not sure if there's a good testing strategy for HTMX apart from E2E tests. Also you can't use TypeScript with it. On the other hand, you don't have a build step, so it's a far leaner dev workflow. It just won't scale up very well. That's why you also have React. Did you often run into situation where HTMX (or previously jQuery) pieces became too complex so you had to completely reimplement them in React? I wonder what would be a good tech stack that scales from your HTMX use-case up to your React use-case. Maybe Astro with something like SolidJS for its interactive islands?

• 
  @yume664310 күн бұрын

  Why can't you use typescript????? Also why wouldn't you be able to test it? I'm pretty sure it's going to scale much more efficiently than react.

• 
  @VeitLehmann10 күн бұрын

  @@yume6643 No TypeScript because with HTMX there's no build step. You add the HTMX library to your HTML and then you add your HTMX attributes to the HTML. And this means you also don't have separated pieces of frontend logic that you could unit-test. So afaik you can only have E2E and integration tests. But tbh I haven't really worked with HTMX yet, it's just what comes to my mind when I look at it.

• 
  @theintjengineer10 күн бұрын

  Astro with SolidJS sounds like a very neat option. I'm learning SolidStart now, because I do like the way they don't bloatware everything, keep things as needed and it's also very performant. I'm a C++ Programmer, so Front-end stuff was never really my thing, I'm just learning a bit of it to create a portfolio/blog webapp. The first thing I realised was: there are sooooo many frameworks to choose from. How do you folks decide what to pick?

• 
  @VeitLehmann10 күн бұрын

  @@theintjengineer SolidStart is definitely really promising, especially now with the just released stable version 1.0! Deciding is really not easy. Usually companies already have settled on a stack. In this case, it takes a lot of experience and observation to establish a change. I usually discuss with other teammates when I observe problems like bad performance, misuse or repeating bad patterns that lead to hard to maintain code. Then we look different options, considering their popularity and stability, the experience of our teams, how hard or easy it would be to migrate etc. For personal fun projects, I just go with gut feeling.

• 
  @believelody55319 күн бұрын

  @@VeitLehmann htmx has nothing to do with the issue you mentioned. It's just a way to make easier ajax call. Don't bother you with that...I mean, it's the html partial view that you have to test or your api endpoints. This what makes htmx a good try. We used to frontend logic separated because of fronted framework...without that, many concepts become a little bit...useless !

• 
  @yume664310 күн бұрын

  I use HTMX with a golang backend and Alpine if I need interactivity. As a result compared to previous versions of my applications with Nuxt or Astro, it's lighter, faster and much more robust. Also I'm more productive as a backend developer as I don't have to bother with the whole js/react/[insert framework] ecosystem.

• 
  @lardosian10 күн бұрын

  Was gonna create a project with Nest on the backend and Next on the frontend, so you would recommend Htmx and Alpine instead of Next Js on the frontend?

• 
  @believelody55319 күн бұрын

  @@lardosian oooohh yes !!!

• 
  @luka17909 күн бұрын

  ​@lardosian tbh, context really matters. Do you already know js/ts, maybe even js web frameworks? What kind of app is it? Is it ui heavy, think animations? Another plus for js is that the ecosystem is huge and it can save you a lot of time. But you have to choose wisely. I think a great usecase of htmx is when you dont no javascript and have no intention to learn / your team. Your app is just a basic crud or requires all the state to be on the server anyway. As js dev who actually likes to hope frameworks just to make coding more fun for myself i tried golang htmx aswell, but the dx was worse then solidstart and sveltekit.

• 
  @lardosian9 күн бұрын

  @@luka1790 Thanks, I have experience building a fairly big React app which I enjoyed, this one is a small side project so maybe I should stick to what I know for the moment.

• 
  @457Deniz45711 күн бұрын

  Best explanation so far 👌

• 
  @1lllllllll111 күн бұрын

  OMG this sounds awful. I’m at a point where I no longer use anything than DIV tags, very little CSS and everything data-related is in ES6

• 
  @galower40512 күн бұрын

  I like using HTMX, but for the React problem you mentioned of having different separate parts of the UI that need to be updated. Why not just use a state manager like Zustand which is around 1.2 kb compressed or Redux. I feel like the main advantage here of using HTMX is that the architecture of the server was already SSR and thus implementing HTMX wouldn't require much migration of the current services and it would save time. SSR is easily handled by React frameworks like NextJS or Remix but, for this case I see how it would have been overkill, double the time of work for an already working backend.

• 
  @KodapsAcademy11 күн бұрын

  Yeah if the backend was using Next we would clearly not have bothered with HTMX :D

• 
  @johnycache9 күн бұрын

  @@KodapsAcademy Yeh, I was understanding your video that way. i.e. Htmx being a good solution this case, because it's an update to an existing architecture - that's the idea here if I'm correct? ...great video by the way - I like this format/style. Nicely put together ;o,

• 
  @HikarusVibrator12 күн бұрын

  That approval rating statistic is complete BS

• 
  @KodapsAcademy12 күн бұрын

  Care to provide some more substance, ie a more solid argument as to why it “BS” ?

• 
  @nahidmubinkhan12 күн бұрын

  What if one use alpine js along with htmx to solve that transient ui state issue? Wouldn’t it be easier as the alpine js and htmx has the simillar philosophy and coding style?

• 
  @KodapsAcademy12 күн бұрын

  The transient state (e.g. if the dropdown is open or not) is simply managed by Bootstrap in our case :)

• 
  @codokit2 күн бұрын

  Alpine JS + Hotwired Turbo

• 
  @n4bb1212 күн бұрын

  Arguments like React is chaotic or Angular is for enterprise are total nonsense. Projects are as chaotic as the developers working on them. I have seen dozens of brutally chaotic and artificially complex projects in both camps. If you assume professional, competent developers, more choices and more freedom are good things. What is much more important about a piece of tech is how productive you can be with it and whether it fits the goal and the people.

• 
  @KodapsAcademy12 күн бұрын

  You kind of missed the point. The “chaotic” was in the context of D&D alignment, not in the sense you seem to have taken it to mean.

• 
  @n4bb1212 күн бұрын

  @@KodapsAcademy What do you mean by D&D?

• 
  @KodapsAcademy12 күн бұрын

  @n4bb12 Dungeons and Dragons (en.m.wikipedia.org/wiki/Alignment_(Dungeons_%26_Dragons) )

• 
  @n4bb1212 күн бұрын

  @@KodapsAcademy Oh, I didn't get that reference. Now it makes more sense.

• 
  @hwapyongedouard13 күн бұрын

  svelte and react

• 
  @mickomagallanes118514 күн бұрын

  wow this is superb and icing on the cake after researching this topic for days, finally I can sleep well. My question is Server Components are like Virtual DOM in the server? Like they are literally components in the React server who have its own virtual DOM?

• 
  @KodapsAcademy14 күн бұрын

  The whole point of the virtual dom is to track changes in the state, and there isn’t really any server-side state (useState only works client side). But RSCs are still components structured in to a component tree. It’s just the the idea of the Virtual DOM doesn’t really apply to the server side :)

• 
  @mickomagallanes118512 күн бұрын

  @@KodapsAcademy yeah the tree that's what I meant, like tracking the nodes (in this case, components in server) and changing only the specific node without having to re-do the entire tree

• 
  @3bdo3id14 күн бұрын

  you should have said I'll zig you in this next video instead of I'll C you in this next video

• 
  @KodapsAcademy14 күн бұрын

  Clearly a missed opportunity :D

• 
  @Tajdev14 күн бұрын

  drizzle

• 
  @nohox944414 күн бұрын

  I think it all depends on your skills. I can see why lots of people tend to prefer Angular because it works in a certain way out of the box. Personally I prefer to get some pieces and then think about how they fit best for the next project.