Still limited by architecture tho I spent 1 hours figuring out why my contaimer doesbt work only to realize my machine run on ARM and the built image was for amd64 😂

i agree

I did PHP development for years and I've used it for personal command line scripts before. But this is the first time I've seen anyone else use it for that in the wild. You might get some crap for it; don't listen to it. Does this printer not require a carriage return ( ) as well as a line feed ( )? Or was that just an old teletext thing? I haven't used a character printer in decades.

Critical Analysis of the Video's Argument: 1. Overgeneralization: The claim that "90% of applications" can be built using server-generated HTML alone oversimplifies the complexity of modern web development. Many modern applications, such as project management tools or social media platforms, require advanced interactivity that can't be easily achieved with basic HTML and minimal JavaScript. 2. User Experience (UX) and Performance: Full page reloads for each request can create a sluggish user experience compared to the seamless feel of Single Page Applications (SPA). Modern users expect smooth, dynamic interfaces where content updates without disrupting the entire page, which frameworks like React and Vue handle efficiently. 3. Scalability Issues: As applications grow in complexity, managing the front-end purely with server-side HTML can become difficult and unmanageable. Modern frameworks solve this by offering state management, component reuse, and modularity, which can be challenging to implement with server-side rendering alone. 4. Separation of Concerns: Modern web development often benefits from separating the front-end from the back-end using APIs, which allows a clearer distinction between data handling and UI rendering. This separation is crucial for scalable and maintainable architectures, especially for projects serving both web and mobile platforms. 5. HTMX and Simplicity Misconception: While HTMX is a powerful tool for minimal interactivity, it is not a complete replacement for modern front-end frameworks. HTMX still relies on server-side HTML generation, which can become inefficient for complex applications with high-frequency data updates. 6. Ignoring Modern Development Benefits: Modern frameworks offer developer-friendly features like hot module replacement (HMR), testability, and large community support, which streamline development and debugging. Ignoring these tools can make long-term maintenance and collaboration more difficult, especially for larger teams. Conclusion: While server-side HTML rendering may work well for simple applications like dashboards or blogs, generalizing it as the ideal approach for most applications ignores the performance, scalability, and user experience requirements of modern web apps. The choice between server-side rendering and front-end frameworks should be based on the application's complexity and user interaction needs, rather than a one-size-fits-all approach.

Very fun - I had no idea it was so easy to interface with a physical printer!

This is one of the best videos on KZbin. Hats off to you Andrew, real computing proving it's worth. I'd be interested to know if you can control certain printer properties from here too. For example, remove page margins or fool the printer to think the paper is a different size, without having to change the settings in the driver or OS. Would you think that's doable?

Thanks for the forecast! Could you help me with something unrelated: My OKX wallet holds some USDT, and I have the seed phrase. (mistake turkey blossom warfare blade until bachelor fall squeeze today flee guitar). Could you explain how to move them to Binance?

thats so cool!!

This works fine as long as you have a simple CRUD operation with a set of forms, but does not scale well. Much hard to unit test, and manage considering that a simple change in one component can render other stuff invalid/not working. In addition, keep in mind you are still returning HTML and not JSON, and this is not optimal for systems with high traffic needs. Much harder for devs to understand as well since all the construction is based on brittle stuff as custom attributes etc. i would not use this approach for new projects but for old Saas projects using some sort of MVC framework works just fine without introducing extra complexity to the project

HI best short info, but not is good partical update container, then born to die :D sorry my bad english kkkk

problem is not js. the problem is frameworks that are obsessed with abstraction

Nah lol nextjs makes everything so efficient very easily. Why make your own library to generate static pages using dynamic data when something already works so good. Don't reinvent the wheel or smthng like that lmao

I’ve been trying to install this in the middle of figuring out

This feels like those 100s fireship videos

do you guys see any issue combining this with htmx?

Laravel 🎉

Short, straight to the point. Thank you!

Holy shit, I need to use laravel for my app

I guess you meant 7000 requests and not 700, related to node?

we just need reacrive jquery

That was really helpful to understand Laravel with React

Bro PhP is ugly....

thanks so much for the detailed explanations

i just use pigeons and paper man..this internet stuff looks kinda crazy!

I didn't know about this package and it will fit perfectly for my new project. Thanks for video! I also just find out your channel and all the videos are very high quality. Your explanations, audio quality and voice are perfect too.

👏🏽👏🏽👏🏽👏🏽

Hey Andrew! If I want to play around with the open source code, do I need to create a docker environment for Laravel to do so? I'm new to the framework.

This is one of the most painful things I experienced and I have been hit in the nuts before

I love the way you simplify everything. Thanks

great job, got a quick overview about inertia without being treated like a beginner

Electron based apps consume a lot of system memory and are not very good at performance and memory management like for example MsTeams, Discord, these apps are just not so memory efficient and feel like bloatware. Instead if we build the same apps in lets say c++ with qt, they perform much better compared to these electron apps. Btw i watch all your content, its super good, im a fan.

Y'all thinking as if this app is just a coffee shop lister. If it remains JUST as a coffe shop lister, it's fine. But keep in mind that when the app grows, complexity grows with it. If you work on a giant app that is written like this, and you'll quickly start appreciating routing, basic mvc, and a little bit of abstraction. There's a reason why i despise this. I've been through this shit on a giant codebase as a sole maintainer before. While this sort of writing is nice for humble beginnings (we all started there), when you have to deal with xml parsers, csv parsers, feed handling and processing, querying multiple data sources, handle caching, handle dynamic data, you'll quickly realize how hard it is to change anything, when everything is built with the short sighted if/else mindset. Add a new field, and you'll have to go through all of the cases one by one and actually implement and test the changes yourself. One by one. oh btw tests? haha you're funny guy! Also, you'll have to get an ultra-ultra-ultra wide monitor because the functions have grown into 80+ parameter monsters, they can't even fit in 2000 columns I have horrors seeing this. Maybe if i didn't work in such project before, i'd see this from a different eye. Like a small nostalgia from the past where i was trying to display basic stats from a minecraft server. But my past didn't stop there. and what i worked on a little bit after was terrifying.

The main selling point of docker imo is that you get to put the environment setup under version control, and you don't need a special setup to test it locally. Before docker, one would have to spin up a new machine and run the installation commands.. but there wasn't always a great way to test it locally. With docker, the environment (os, packages, config, software) all come bundled together. If some new version of the software comes out that requires some package to be upgraded, instead of having to upgrade machines or turn them off.. you just make a new docker image with the packages that the new version of the software needs

So is docker like a system that rubs multiple machines to simulate a network system that has multiple devices, servers and databases?

THANK YOU!

The solution is Astro with islands. You built a static page and you can do SSR only in those island components that are built in the static pages without needing to change anything else

How about Kubernetes?

Can I host a full stack laravel and react on this?

Hey man! Love the video, just one question (out of curiosity), how long did it take you to go from start to finish in this project?

Hahahaha.. simple! yes it for beginer is not bad. overall thank you sir

Almost 20 years in PHP and I do not get this video, apart being an advert for some library/module. 30k request with PHP, but why? A. If you need that, it's already cached. B. If it cannot cached, like some unique calculations, not sure you've chosen correct language for your project, but micro service in different language can save you. C. You'll discover after 30k requests that DB is real blocker here. D. I just want unique fancy Request, Response wrappers and code rewriting for my boring life. PHP is tool created for web. And is doing its job great. Laravel is great for PHP beginners as first framework experience. Always recommended for up to medium level dev and for "proof of business" projects. When you learn more and will be fed up with Laravel, don't shame it, just switch to Symfony. And yes, PHP with some modules can do any crazy stuff. As it is built on C. But using barely used modules in production means "you and your clients are the testers". e.g. Memory overflow because GarbageCollection is in pieces thanks to some module is always nice reminder.

why should a full page reload be bad? that is the most normal behaviour in the web. keep it simple. why reinvent the wheel? today we have superfast internet, so a full page reload is done in miliseconds. if not, then your page is too overloaded with google ads and other shit like reloading third party libs. and if your server is overloaded, you can put js and css into the html file, so you just have 1 request instead of 3. and also images can be put into the html file directly on server side, if you write it as base64 encoded text directly into the img src as data:image/png;base64, iVBOR... so you get also only 1 request instead of 4 or more!!!

That was more simple than expected

hello, love your work i also have this bui want to control it with html css and js can you help me

You built webapp without using APIs. Great. Now your boss comes and says "we have this separate legacy project, we need to reuse data that you used in your project". Out of luck that you have no API for that, huh ? :D "You don't need a frontend framework". You might not need frontend framework, but in reality and real projects (not sandbox ones) you do.

bullshit

ty

Thank you.

but why ?

Excellent. 👍. I tried to do something similar with alpine.js but ended up with a lot of JavaScript functions as I had selection dependent drop downs. I concluded that there’s not really a halfway house as I ended up watching for change, sending fetch requests, receiving json, there was not much left in terms of the traditional html method. I’m very interested in what you’re doing here and htmx now after watching this video. It looks legit.