Jeremy's classification of developer tools has always impressed me:
I've mentioned two types of web development tools, but I'm still not sure how to call these categories. Interior and external? For developers and users?
The first category includes build tools, version control, translators, preprocessors, and code inspectors. These tools run on your machine—or on the server—take the code you write and convert it into raw materials for the web: HTML, CSS, and JavaScript.
The second type of tools is composed of raw materials for the Web: CSS framework and JavaScript libraries.
This is a good way to think, and of course there are some subtleties. Sass belongs to the first category because it will not be delivered directly to the user, it only generates CSS delivered to the user. But it will still affect the user because the size of the CSS it generates will vary depending on how you use it.
Jeremy calls Svelte a library, whose goal is to compile as much as possible before the code is delivered to the user. There will still be some JavaScript code, but it does not contain the overhead of the developer-oriented API. The subtlety here is that Svelte can be used in a way that completely removes all JavaScript code. For example, SvelteKit can turn off its hydration function completely and pre-render the page, creating a completely JavaScript-free website (or at least only use it if you need it).
About React:
I know there are ways to make React behave more like the first type of tool, but this is definitely not the default behavior. And the default behavior is really important. For React, the default behavior is to assume that all the code you write—and the tools you use to write it—is sent to the end user.
I think this is reasonable, but the story seems to be slowly changing. I think widespread use is far from the way it is, but server components are worth paying attention here because they come from the React team itself, just as SvelteKit comes from the Svelte team itself.
About Astro:
[…] Unlike Svelte, Astro allows you to use the same syntax as existing framework React. So if you've learned React -- because you need to learn it to find a job -- then you can use Astro without learning new syntax.
I know you may not be able to convert an existing React website to Astro in one click, but there is at least a clear upgrade path.
This is not only correct in theory, but also in practice!
I just converted our small serverless micro website from Gatsby to Astro. Gatsby is based on React, so all components are built as React components. Pull Request is a bit messy, but it's here. I converted some of it into a .astro file, but left many components basically the same as .jsx React components. But React will not be sent to the user's website. The JavaScript code on the website has been almost completely removed, leaving only some handwritten native JavaScript code for very simple interactions.
So here are some coin tossing things happening. Coins merge? To me, Astro feels very much like a developer-oriented tool. It helped me . It uses the Vite compiler, which is very fast and enjoyable to use (Astro certainly has some shortcomings as it is not yet reached 1.0, but DX is largely implemented). It scopes my style. It allows me to write SCSS. It allows me to write components (using many different frameworks). But it also helps users. There is no JavaScript package on the website at all.
I guess this means Astro hasn't changed the category - it's a developer-oriented tool. It just happens to turn an originally user-oriented tool (even Svelte) into an almost entirely developer-oriented tool.
Since I still have a few links about Astro that have been in my pocket, Flavio has a great tutorial on getting started, and here is Drew McLellan and Matthew Phillips discuss Astro on the recent Smashing Podcast.
Here are some websites Dave and I discuss with me recently remade with Astro:
The above is the detailed content of Inertia. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.

To deal with CSS browser compatibility and prefix issues, you need to understand the differences in browser support and use vendor prefixes reasonably. 1. Understand common problems such as Flexbox and Grid support, position:sticky invalid, and animation performance is different; 2. Check CanIuse confirmation feature support status; 3. Correctly use -webkit-, -moz-, -ms-, -o- and other manufacturer prefixes; 4. It is recommended to use Autoprefixer to automatically add prefixes; 5. Install PostCSS and configure browserslist to specify the target browser; 6. Automatically handle compatibility during construction; 7. Modernizr detection features can be used for old projects; 8. No need to pursue consistency of all browsers,

Themaindifferencesbetweendisplay:inline,block,andinline-blockinHTML/CSSarelayoutbehavior,spaceusage,andstylingcontrol.1.Inlineelementsflowwithtext,don’tstartonnewlines,ignorewidth/height,andonlyapplyhorizontalpadding/margins—idealforinlinetextstyling

Use the clip-path attribute of CSS to crop elements into custom shapes, such as triangles, circular notches, polygons, etc., without relying on pictures or SVGs. Its advantages include: 1. Supports a variety of basic shapes such as circle, ellipse, polygon, etc.; 2. Responsive adjustment and adaptable to mobile terminals; 3. Easy to animation, and can be combined with hover or JavaScript to achieve dynamic effects; 4. It does not affect the layout flow, and only crops the display area. Common usages are such as circular clip-path:circle (50pxatcenter) and triangle clip-path:polygon (50%0%, 100 0%, 0 0%). Notice

Setting the style of links you have visited can improve the user experience, especially in content-intensive websites to help users navigate better. 1. Use CSS's: visited pseudo-class to define the style of the visited link, such as color changes; 2. Note that the browser only allows modification of some attributes due to privacy restrictions; 3. The color selection should be coordinated with the overall style to avoid abruptness; 4. The mobile terminal may not display this effect, and it is recommended to combine it with other visual prompts such as icon auxiliary logos.

To create responsive images using CSS, it can be mainly achieved through the following methods: 1. Use max-width:100% and height:auto to allow the image to adapt to the container width while maintaining the proportion; 2. Use HTML's srcset and sizes attributes to intelligently load the image sources adapted to different screens; 3. Use object-fit and object-position to control image cropping and focus display. Together, these methods ensure that the images are presented clearly and beautifully on different devices.

The choice of CSS units depends on design requirements and responsive requirements. 1.px is used for fixed size, suitable for precise control but lack of elasticity; 2.em is a relative unit, which is easily caused by the influence of the parent element, while rem is more stable based on the root element and is suitable for global scaling; 3.vw/vh is based on the viewport size, suitable for responsive design, but attention should be paid to the performance under extreme screens; 4. When choosing, it should be determined based on whether responsive adjustments, element hierarchy relationships and viewport dependence. Reasonable use can improve layout flexibility and maintenance.

Different browsers have differences in CSS parsing, resulting in inconsistent display effects, mainly including the default style difference, box model calculation method, Flexbox and Grid layout support level, and inconsistent behavior of certain CSS attributes. 1. The default style processing is inconsistent. The solution is to use CSSReset or Normalize.css to unify the initial style; 2. The box model calculation method of the old version of IE is different. It is recommended to use box-sizing:border-box in a unified manner; 3. Flexbox and Grid perform differently in edge cases or in old versions. More tests and use Autoprefixer; 4. Some CSS attribute behaviors are inconsistent. CanIuse must be consulted and downgraded.
