Comments by "Ozzy Perez" (@OzzyTheGiant) on "I built a JavaScript framework" video.

  1. Nowadays, with a static site generator and a headless CMS, it's much easier to build static websites with custom layouts. I feel they just need more exposure. Would like to see Wordpress decline in favor of this method.
    2
  2. No experience with Hugo, but in Astro, I use Svelte components whenever I need a part of the page to have JS functionality. Astro does use JS/TS but this is only for build time functionality (like css class properties, fetching data to render the page ahead of time). This JS gets stripped out when building the final site. To preserve JS, you need a <script> tag or components from a framework. These components can then be reused throughout your site (like forms, cards, etc.). You can take it a step further by writing these components in a separate repository, compiling them to web components and then reusing them in any project or framework.
    2
  3. Can't speak for Fireship but I stopped using Angular for many reasons: - File Hell - even though Single File Components technically are supported, it's not to my liking (prefer Vue html tags over Component config properties). - I want to use Vite for all projects now. Angular uses webpack with a heavily configured build system that feels like it takes too much time to learn. - Template syntax is ok but I feel like third-party components force you to write a lot of boilerplate stuff instead of using sensible props and a Slots API like Vue. For example, using Angular Material's Table component required a lot of explicit table row, custom table cell, and secondary row definitions written in html through the use of directives, but in Vuetify, that same table only requires the component itself and just a few modifier properties, and maybe one slot element; the size of the resulting HTML on Vuetify was significantly smaller. Everything else in Angular is pretty good, but I do think its time they slimmed down on these features.
    1
  4. I've tried a few of them. Directus shines when you have an existing database with a custom schema that you don't want the CMS to alter, but you can always start from scratch too. The admin panel can be extended with custom plugins/pages made with Vue components. Strapi works primarily with data models but has an opinionated way of creating the database tables; I would say it's the best one for people who want to replace Wordpress. It also has a plugin system, but this one is based on React. Both Directus and Strapi support Markdown editors. Then there's Wagtail if you prefer a Python backend. That one is decent and can be customized with Django configurations, but the admin interface can be confusing on your first try; took me a while to figure out how to actually set up the API routes for my SSG, which are not available out of the box. Finally, if you must use PHP, there's SilverStripe, which is neat because it actually can be coded like a normal OOP back end framework, or you can just use the admin panel instead. Strapi also has the ability for you to code your data models instead of using the admin panel. SilverStripe, Strapi, and Directus also allow you to define custom API controllers like you would use in a normal web framework.
    1
  5. If only people put this much effort into other languages that need a larger ecosystem (Dart, Go, etc.)
    1