211–220 of 256 posts
Might try this out at some point.
Earlier quoted context omitted.
Have you used React before? It's miles above HTML templating. I honestly don't use frameworks that have regular templating anymore, like Vue or Svelte.
I have used React. I'm a huge fan and I also prefer it over its most common "competitors" like Vue and Svelte. But React (like Vue and Svelte) are fundamentally about interactivity. If I had a project where I knew for sure that I only wanted to generate HTML sans JS on the server (or with a static build process) I wouldn't even consider using React. It barely even makes sense. Your "React components" would just be Ja…
They can also be async functions that process data independently. Whereas templates are commonly just passed in data from the controller.
I used Astro recently to rebuild my personal website/portfolio, and I really enjoyed it. I'm not a frontend dev and I quickly get overwhelmed by all of the choices and the breakneck speed that the web ecosystem changes at. Astro was exactly what I needed. It's optimized for spending most of your time writing content in markdown, but it gives you complete freedom to seamlessly add web code of any complexity you like.…
https://docs.astro.build/en/comparing-astro-vs-other-tools/
"Both XXX and Astro are frameworks for building websites. XXX does best with highly dynamic websites (like dashboards and inboxes) while Astro does best with highly static websites (like content and eCommerce websites)."
This explanation is used for every XXX framework, but i can't really see why. With components you can show high dynamic data, so for me there is no difference if i use XXX or Astro.
Did somebody has some real life examples, that could explain the difference?
Or why it could be better to stay with XXX and not use Astro.
Currently we want to switch our svelte project to SvelteKit, git rid of our custom fiddle (router, etc.). But when i see Astro now, i think about what speak against using Astro? But at the moment it seems that it has many additional benefits?
Earlier quoted context omitted.
I think it makes the tradeoffs that are ideal for content-oriented sites rather than web apps. > Next.js uses React to render your website. Astro is more flexible: you are free to build UI with any popular component library (React, Preact, Vue, Svelte, Solid and others) or Astro’s HTML-like component syntax which is similar to HTML + JSX. > Both Next.js and Astro are frameworks for building websites. Next.js does bes…
Also Astro sites can be hosted on CloudFront or any another static CDN. Next you’re kind of tied to Vercel no?
If you need backend api functions - https://github.com/serverless-nextjs/serverless-next.js/ AWS Lambda etc. Probably slightly more work I grant you.
Earlier quoted context omitted.
Not getting it tbh. Why would you go nuclear and develop a React or Vue app and then not actually use it on the browser side? For content-oriented websites there are much simpler workflows based on SGML and other classic markup processing and content management practices. I mean the point of "content-oriented" and web sites in general really is that an expert in the field, rather than a web developer, can achieve use…
Component-based UI frameworks and ecosystem has made building frontends much nicer, especially when you need some optional interactivity since you're already writing in JS. Having that productivity and flexibility without the SPA complexity and other JS cruft has real value.
I've been looking to make a simple website recently - landing page, user sign up, taking payments, then access to a simple react one-pager. It's all doable but with django you just have to do everything, even if you start with the cookicutter.
I just want something where I can pick from a good base template, then get started, not spend days plugging all the parts together. If this helps with that I'll check it out. What would you use for the user data? Firebase, etc.?
Earlier quoted context omitted.
The increase in value provided by these services is very much linear w.r.t. number of users. The 10x+ leap in cost with enterprise pricing is not at all justified by additional value provided. I don't mind paying a fair, pre-disclosed price for services that provide value. I do mind opaque enterprise sales tactics that try to take full percentage points off my available runway for no discernable increase in value whe…
Add me to the list of voices who are highly skeptical about Vercel. I recall watching a video on their YouTube account a few months ago where their head of devrel tried to interview a famous personality from the “cloud native” community (Kelsey Hightower) as a way to introduce their “edge functions” nonsense. The entire thing was a train wreck from about ten minutes in when he started asking questions about how it ac…
I cut out parts of the interview to make it shorter. If you’d like to verify what I showed, you can deploy an Astro site with Edge Functions for free: https://vercel.com/templates/astro/astro-edge-functions
Open to feedback on how we can do better next time. Would you prefer more discussion about tradeoffs?
TBH if it comes with some decent starter templates it's a massives step up from what the python world offers. I've been looking to make a simple website recently - landing page, user sign up, taking payments, then access to a simple react one-pager. It's all doable but with django you just have to do everything, even if you start with the cookicutter. I just want something where I can pick from a good base template,…