Comments URL: https://news.ycombinator.com/item?id=50237712

Points: 191

# Comments: 127

And here's the PageSpeed Insights result: https://pagespeed.web.dev/analysis/https-bloffy-bloffy-blog-...

It's a long post with lots of images in different sizes, plus diagrams and math.

Images uploaded in the editor get a srcset with 4 widths, and the CDN compresses them to suit each browser. Since we know each image's original width and height, the layout doesn't shift.

Diagrams and math are rendered to SVG and MathML when you publish, so readers can load them quite fast.

I actually wanted to talk about this too, so I'm glad I got the chance to answer. Thanks.

(The SEO score there is low only because the sample blog is noindexed.)

1. You're right. I actually considered it, but I thought a demo would make the landing page quite heavy. Your comment gave me the idea of making a separate page where you can try a demo. Great suggestion, thank you.

2. Thanks. This was actually intentional. As a first target, I'd like Bloffy to appeal to developers who care a lot about SEO. Bloffy is also a bit different from typical blog products built to be easy for everyone. The goal is for it to grow, over time, into a blog customized to you. The first target is developers, but going further, SEO professionals who can handle HTML, CSS, and basic JS could be a target too.

3. You're right. I'll make the differences clearer on the landing page, and I'm also planning to write a separate post about how Bloffy differs from other blogging platforms.

4. I think you mean the demo video on the landing page? The pace does feel a bit fast. I was trying to keep it under a minute. I'll take that into account. Thanks!

I'm fixing this right now.

My native language is Korean, and by "your own blog" I meant something like "a blog that's truly yours." I was trying to sum up a few things in that one phrase: you can customize it freely, the platform interferes very little, it's friendly to raw HTML, and it allows JavaScript. I think that line could be misleading, so I'll need to reword it.

Thank you.

The confirmation email being sent in Korean does look like a real bug. I had set English as the default, but it seems I missed this part. Thanks for pointing it out.

You're right that the word "Translation" can be misleading. For now, translations are meant to be done manually, but I'm also considering automatic translation in the future. Automatic translation can change the meaning you want to convey, so I'd still recommend translating posts yourself. But for convenience, I'm thinking about adding automatic translation.

Thanks again.

I like running my blog, but I couldn't find a blogging platform I really liked.

First. I thought a blog had to be really lightweight. Fortunately, after a lot of effort, I was able to achieve satisfactory results. (99 to 100 score)

Here is a sample blog: https://bloffy.bloffy.blog/en

You can check it with PageSpeed Insights: https://pagespeed.web.dev/analysis?url=https://bloffy.bloffy...

SEO score of the sample blog is low because I blocked it from search engine indexing (noindex).

Second. I think bloggers should have control over their own blog. The blogging platforms I used had several problems.

Unnecessary JavaScript chunks. Ads that the platform inserted into my blog, not my own ads. Cannot manage multiple blogs. An editor that makes it hard to write semantic markup. Limited customization options. I was dissatisfied with the difficulty of placing my own ads.

And to solve this, I spent quite a long time researching and developing it on my own, and finally created it. I'm glad to share this launch with HN. I would appreciate any criticism, feedback, and interest.

Comments URL: https://news.ycombinator.com/item?id=50189175

Points: 30

# Comments: 26

- There is a widespread misconception that “React Native has been discontinued” or that “Meta has abandoned it.” - This is not true. React Native continues to receive regular updates and is actively discussed at major global conferences. - The confusion largely stems from Meta’s new product Threads being built with fully native technologies (Swift and Kotlin/Jetpack Compose). - The rumor that “even Meta has abandoned React Native” is only half true — Threads chose native for product-specific reasons, while React Native remains actively used across many products.

- *Instagram* - Adopted React Native starting in 2016. - Achieved 80–99% code reuse, significantly improving development speed. - Delivered better UX than WebView-based approaches and reduced build times.

- *Facebook Marketplace* - Core UI surfaces (Seller Hub, product detail pages, profiles, etc.) were built with React Native. - Implemented complex gestures and animations using tools like PanResponder. - Meta engineer Blair Vanderhoof: “React Native was key to Marketplace’s growth.”

Comments URL: https://news.ycombinator.com/item?id=47163161

Points: 1

# Comments: 1

- If you care about productivity, reducing mouse usage in Chrome makes a real difference. - Most frequently used features can be handled with a single keyboard shortcut. - Internalizing these shortcuts noticeably speeds up tab management, navigation, and development workflows.

### Essential Tab Management Shortcuts - Switch tabs: `Ctrl/Cmd + Tab`, `Ctrl/Cmd + 1–8`, `Ctrl/Cmd + 9` - Close / Reopen: `Ctrl/Cmd + W`, `Ctrl/Cmd + Shift + W` - New window / Incognito window: `Ctrl/Cmd + N`, `Ctrl/Cmd + Shift + N` - Search all tabs: `Ctrl/Cmd + Shift + A` → Especially useful when you have many tabs open - Open history: `Ctrl/Cmd + Y` → Perfect for “What was that page I just visited?” moments

### Basic but Essential - Back / Forward: `Ctrl/Cmd + [`, `Alt + ←` - Scroll: `Space` / `Shift + Space` - Focus address bar: `Ctrl/Cmd + L`

### Hidden Power of the Address Bar - Use it as a calculator (type expressions directly) - Perform instant unit conversions (e.g., cm → inch) - Type `@` to switch search modes (including AI mode) It’s not just a URL field — it’s closer to a quick command launcher.

### Developer Shortcuts - Open DevTools: `Ctrl/Cmd + Option/Alt + I` - Toggle element picker: `Ctrl/Cmd + Shift + C` - Hard refresh (ignore cache): `Ctrl/Cmd + Shift + R`