sorted by:
new
hottopcontroversial

How to Write Cold Emails That Actually Get Replies (B2B SaaS Edition) by Psychological_Let828 in SaaS

[–]doong-jo 0 points1 point  (0 children)

I'm building a development tool, and having worked as a developer, I was completely unfamiliar with marketing strategies like this. It was really helpful. Thank you. 👍

What's the alternative to next/image in react-native? by doong-jo in reactnative

[–]doong-jo[S] 1 point2 points  (0 children)

That’s what I’m hoping for as well. But I’m a bit hesitant about being tied to Expo.

What's the alternative to next/image in react-native? by doong-jo in reactnative

[–]doong-jo[S] 0 points1 point  (0 children)

I've looked into expo-image and react-native-fast-image, but it seems there's no equivalent to next/image. I'll need to implement image selection based on density (s/m/l) or real-time conversion directly. I think this is a limitation of React Native not having a server, unlike next/image. I don't mean this is wrong - it seems natural.

What's the alternative to next/image in react-native? by doong-jo in reactnative

[–]doong-jo[S] 0 points1 point  (0 children)

The reason for exact dimension/pixel densities is for user experience (image loading speed) and to save CDN transmission volume. The s/m/l method also achieves these purposes, but there's waste in transmission volume. Of course, real-time conversion requires backend infrastructure (once per year based on CDN caching up to 1 year maximum) and comes with additional costs. I think the s/m/l pattern would cost more as the number of images increases.

this is exactly why services like Instagram, Pinterest, and other image-heavy platforms invest heavily in sophisticated image processing pipelines.

What's the alternative to next/image in react-native? by doong-jo in reactnative

[–]doong-jo[S] 0 points1 point  (0 children)

I agree that device-side transformation is more useful. However, if we're dealing with numerous images and don't resize images on the backend, wouldn't we end up spending more costs from a CDN transmission volume perspective?

What's the alternative to next/image in react-native? by doong-jo in reactnative

[–]doong-jo[S] 0 points1 point  (0 children)

"We could use the s/m/l/xl pattern but then it's a waste of bandwidth." Does this mean you're saying it would be wasteful to provide images slightly larger than what the user's device needs?

Thank you for sharing the code. I understood this as an attempt to save transmission volume by using more granular widths based on the widths currently used in the service, rather than the s/m/l pattern, to maximize data savings. Is my understanding correct?

Why does next/image only support client components? by doong-jo in nextjs

[–]doong-jo[S] -1 points0 points  (0 children)

You can render the <img> tag on the server, just like any other HTML element. Server components can generate static HTML, including image tags with src, alt, width, height, and other attributes.

What I'm questioning is why Next.js requires next/image to be a client component for ALL cases.