Backbutton hijackingの件も含めてパブリッシャーは大変だ

Ever clicked back only to get stuck in a loop? Google's new spam policies aim to end frustrating browser back button hijacking. 🔍 #Google #BackButton #SpamPolicies #SEO community.designtaxi.com/top…

Most React developers misuse inheritance, and it slowly destroys their component architecture. The better approach? ✅ Composition. Here is the simple mental model 👇 Instead of creating large components and extending them… Break your UI into small and reusable building blocks. Then combine them. Example: You might start with a simple `Button`. Instead of extending it with inheritance: • `PrimaryButton` • `SecondaryButton` • `LoadingButton` You compose behavior. Example: • `<Button />` • `<LoadingButton />` • `<BackButton />` Each component adds behaviour without touching the base component. Why this matters: ↳ Inheritance forces you to create new subclasses for every variation. ↳ Composition lets you mix behaviours freely. That makes your components: • easier to reuse • easier to extend • easier to maintain Another way to think about it: Composition keeps your base components closed for modification but open for extension. This aligns perfectly with the Open/Closed Principle. Simple rule I follow when building React UIs: If you feel tempted to extend a component… Pause. Ask yourself: “Can I compose this instead?” Most of the time the answer is yes. And your codebase will thank you for it. —— 💾 Save this for later. ♻ Repost to help others learn React. ➕ Follow @petarivanovv9 turn on notifications.

like if people wanna keep writing without basic grammar and punctuation and causing readers to backbutton out without leaving comments or kudos who are we to stop them lol

Good afternoon Pack 🐺☀️ Quiet work. Real upgrades. Missions loot preview = clean (no ghost drops) Home rebuilt BackButton fixed Forge Shards craft = safe retries pity working ⚒️ Play today - you will feel it🧱 Block by block

Most React codebases don’t collapse because of bad devs. They collapse because everything becomes… specific. Specific buttons. Specific modals. Specific forms. Specific logic tied to one feature. Then business changes. And suddenly half the UI needs rewriting. I’ve worked on small e-commerce builds and large enterprise systems. The pattern is always the same: Tangled components Hard refactors Slow feature delivery So on one project, we changed the rule. We split our UI into two layers: → Generic components → Domain components Here’s what that actually means: Generic components → Pure UI building blocks → No business logic → Reusable across the entire app Examples: • Button • Input • Modal • Card Domain components → Built from generics → Contain business logic → Represent real product meaning Examples: • BackButton • CheckoutButton • UserSettingsForm Generic is about flexibility. Domain is about context. The magic happens when you stop mixing them. When your Button doesn’t know about checkout. And your CheckoutButton doesn’t rewrite UI from scratch. Result: • Faster feature changes • Cleaner refactors • Lower cognitive load • UI that survives business pivots Most teams don’t have a React problem. They have a component boundary problem. And once you see it, you can’t unsee it.

my physics prof has miu miu glasses on and a backbutton shirt with 3/4 sleeves. brazy…

Truecaller - (Garbage App) Whatsapp - (Runs absolutely pristine and thanks to ios has camera api) Backbutton - (Skill Issue) Call Reject Button - ( You gotta be blind)

If you are clean, no need to hide any thing. Iam happy on samsung s24 ultra. Iphone UI sucks big time, had iphone 15 plus couldnt use more than a week. Truecaller, Whatsapp, Backbutton, No Call reject button. etc..

Favor Composition over Inheritance when creating React Components. Here is why 👇 The main idea behind composition consists of two steps: 1/ Break the UI into many smaller reusable components. 2/ Combine these reusable components into more complex components. This way, you have multiple smaller building blocks that can be reused across the codebase to fulfill different use cases. Composition keeps core components unchanged and lets you add features via props or small wrappers. Inheritance forces new subclasses for each variant, leading to less flexible components and more code. By using composition, you can mix different behaviors like <LoadingButton />, <BackButton />, etc, without touching the core/base components. #React

Some dude: Why Samsung? Why not Apple like the rest of us? Me: This device chose me. It had a backbutton on its screen. We bonded over that. You wouldn't understand... 👀 #noseriously #ucantmakethisshitup #myINFAMOUSlife #imINFAMOUS #letsbeINFAMOUStogether #yerdoinitwrong

& if that's a turn-off for you, the door is just a backbutton away! my flock follows me for me. that will never change.

Haha yea True behavior when I used backbutton:)

1️⃣ Refactored for Reusability Made a proper reusable BackButton component 🔙 Defined color constants for consistent gradient usage Broke down parts of the UI for better maintainability Clean code = happy code 🧼✨

A fic from Jungkook's POV mentioned he hated doing laundry and I had to backbutton immediately. The mischaracterisation? 😤

why the fuck does the back button exit out of a tweet now?? it used to make my keyboard Go Down. which actually makes more sense because the ui still shows the backbutton as a down button. stupid ass software engineers

Feels nice but the price is hilarious. I think the lack of analog triggers makes it feel cheap, which exacerbates the price issue. The backbutton rebind feature is so barebones -- no combos; just bind an already active single button, which has literally no purpose whatsoever.

17. I have several ff pet peeves but I'll go with readers who feel they have the right to leave rude, hurtful, and mean comments on fics that aren't for them. Sometimes they're left as "help" but they weren't asked. Instead, I wish readers would just silently use the backbutton

I will never understand why people can't just quietly use the backbutton if a story isn't for them.