141–150 of 296 posts
Page refresh also seems to reset scroll position but that might be unrelated.
Earlier quoted context omitted.
I completely agree except that I would say "full stack framework" instead of "frontend framework." Just add a db and you are good to go. I tried it out when building a couple of non-critical internal apps for clients (basic CRUD apps, but with some pretty complex business rules). SvelteKit is beautifully designed. It makes things that used to be a bit of a pain super easy to understand and implement. You can use pret…
> Just add a db and you are good to go What about validation, CORS, cookies, encrypted sessions, etc? A backend (or full stack) framework should at the very minimum include those kind of things. It's a major gripe I have with all the new full stack frameworks. The focus is on rendering and dealing with requests but they are quite sparse in bread and butter backend features. Other than routing you're basically on your…
Though I expect the situation improve a bit soon, as now SvelteKit 1.0 release is out from the door.
Earlier quoted context omitted.
If it's for your career: React + (Next or Remix). Maybe Angular or Vue if the specific company you want uses it If it's for yourself: Svelte. Amazing community, very likely to be here in 5 years, but I don't think it's been proven to work at large scales yet. If you want to twist everything upside down and see the full potential of what front-end dev work could be: Qwik or Elm (imho)
What would be an example of large scale for a front-end app or site?
many pages and lots of functionality with lots of data floating around like Reddit, Twitter
literally everything/anything like Facebook, GitHub, etc
For simple apps, I'd go with a PWA if possible. For single, mostly informational, pages you usually just need a static site. For a company blog, some of these tools could be used to make the frontend for a CMS, but you can also just get away with Wordpress, Squarespace, etc most of the time unless they want some really custom functionality. Then there's also micro-frontends and Astro and other related tools if you're trying to do a lot of different things and wanna mix and match different solutions to different problems
Earlier quoted context omitted.
Same, but with ASP.NET (which produces an OpenAPI specification) + Entity Framework on the server, React + TypeScript on the client (which consume that specification through openapi-generator). https://github.com/OpenAPITools/openapi-generator I chuckle every time I read claims about Go (or whatever) being amazingly productive. I don't think it's possible to beat this stack with regards to both productivity and ease…
Do you still need to pass around "Data Transfer Objects" to do simple parameter binding?
This is how I move fast and break nothing. By having fullstack type-safety from database all the way to the frontend with auto-completion. My current stack: + SvelteKit (could be Next, Nuxt, Solid or any other TypeScript framework) + tRPC (typed calls between frontend and backend, https://trpc.io ) + trpc-sveltekit (glues SvelteKit and tRPC, https://github.com/icflorescu/trpc-sveltekit ) + Prisma (ORM, https://www.pr…
I'd love to browse a sample codebase. Do you know of any non-trivial open source projects using this stack?
How so people feel about client side navigation? Browsing svelte.dev it appears back/forward navigation now requires a request each time as browser cache is no longer usable. Page refresh also seems to reset scroll position but that might be unrelated.
How so people feel about client side navigation? Browsing svelte.dev it appears back/forward navigation now requires a request each time as browser cache is no longer usable. Page refresh also seems to reset scroll position but that might be unrelated.
There is a plethora of javascript frameworks: React, Vue, Svelte, Remix, etc. If I know nothing about front-end development, and would like to learn one that is: - Intuitive - Suitable for small projects as well as large projects. - That is here to stay, i.e. either adopted by many companies, or its adoption curve is going up. Which one should I pick? Would Svelte be a good choice?
If it's for your career: React + (Next or Remix). Maybe Angular or Vue if the specific company you want uses it If it's for yourself: Svelte. Amazing community, very likely to be here in 5 years, but I don't think it's been proven to work at large scales yet. If you want to twist everything upside down and see the full potential of what front-end dev work could be: Qwik or Elm (imho)
> but I don't think it's been proven to work at large scales
i basically have this saved now:
notable companies now using svelte not just for internal apps but customer facing, critical stuff:
- huggingface (for everything, including gradio)
- alaska airlines (entire customer flow)
- razorpay (payment dialogs)
- schneider electric (many things)
- ikea (entire ecomm experience)
- riot games (league of legends client)
- Brave (search page)
- Square (developer portal)
- several YC startups
- and basically every notable data journalism outlet on the planet (Bloomberg, the Economist, Reuters, Les Echos, german and japanese publications, pudding.cool, and of course the NYT)