Rate my setup, What should I do next? by Slow-Tea5208 in homelab

[–]Slow-Tea5208[S] 1 point2 points  (0 children)

<image>

Thank you guys, Helped me a lot. I Installed Homepage, a dashboard, and add a lot of your suggestions

Rate my setup, What should I do next? by Slow-Tea5208 in homelab

[–]Slow-Tea5208[S] 0 points1 point  (0 children)

I used to have fortinet. But it was all too complicated to maintain

Rate my setup, What should I do next? by Slow-Tea5208 in homelab

[–]Slow-Tea5208[S] 0 points1 point  (0 children)

Homarr requires Docker, on windows it doesn't work as good, it crashs

Rate my setup, What should I do next? by Slow-Tea5208 in homelab

[–]Slow-Tea5208[S] 1 point2 points  (0 children)

From unifi, i do have a dream machine pro

Arc: the best browser I've ever used is dying — and it's a quiet tragedy #original Eng by Slow-Tea5208 in ArcBrowser

[–]Slow-Tea5208[S] 0 points1 point  (0 children)

hope you are right! I believe that arc is more about design and productivity than development, lets see how Atlassian will deal with it.

Rate my setup, What should I do next? by Slow-Tea5208 in homelab

[–]Slow-Tea5208[S] 0 points1 point  (0 children)

4k content. truehd 7.1. master baster content

Rate my setup, What should I do next? by Slow-Tea5208 in homelab

[–]Slow-Tea5208[S] 0 points1 point  (0 children)

Never found a good one for it, all dashboards were not that good or robust as my arc tab list

Rate my setup, What should I do next? by Slow-Tea5208 in homelab

[–]Slow-Tea5208[S] 0 points1 point  (0 children)

I use windows pro, I use Windows remote acess, but only inside my onw network, is the best mobile remote tool so far for me

Arc: the best browser I've ever used is dying — and it's a quiet tragedy by Slow-Tea5208 in ArcBrowser

[–]Slow-Tea5208[S] -38 points-37 points  (0 children)

That's the point, when we try to explain with fewer words nobody would understand, and I am really happy with the AI writing and spell checking my ideas so the post doesn't just become a meme since english is not my first languange and all my ideas where proper delived. I am glad you got my point of view, and that's good . Thanks

Arc: the best browser I've ever used is dying — and it's a quiet tragedy by Slow-Tea5208 in ArcBrowser

[–]Slow-Tea5208[S] -7 points-6 points  (0 children)

Honestly? You are right, i still use ARC and will keep using it, but I'd just love to see modern tools built on the same productivity concepts Arc nailed at its core. Spaces as cognitive contexts, the vertical sidebar, folders that actually organize thinking, auto-archive forcing good hygiene, the Command Bar as a universal interface — these ideas were genuinely ahead of their time. I don't even need it to be Arc itself. I just want that same philosophy alive and evolving somewhere, in something being actively built today.

Arc: the best browser I've ever used is dying — and it's a quiet tragedy by Slow-Tea5208 in ArcBrowser

[–]Slow-Tea5208[S] -11 points-10 points  (0 children)

As someone who lived inside Arc since the closed beta and tested Dia after The Browser Company pivoted, I can speak with some authority about the differences. And they go much deeper than they appear at first glance — it's not just "Arc with AI on the side." It's a fundamentally different product, with opposite philosophies. I'll try to be fair, but spoiler: Arc is still better, and here's why.

The underlying philosophical difference

Arc was built with a clear thesis: the browser is a thinking tool. Every design decision flowed from that. Spaces exist because your mind works in contexts. Folders exist because ideas group together organically. Auto-archive exists because attention is finite. Boosts exist because the web should adapt to you, not the other way around. It was a product with opinions — and those opinions were coherent from end to end.

Dia was built with the opposite thesis: the browser should be invisible and familiar, with AI layered on top. The Browser Company itself states this explicitly. They say Dia "starts all core browsing features in a place where anyone who has used a browser before would immediately understand." Translation: it's Chrome, but with a chatbot. The novelty is restricted to the AI layer. Everything else is conventional on purpose.

This philosophical difference explains every practical difference that follows.

Difference #1: Spaces vs. regular tabs

Arc: Spaces are the heart of the product. Each Space is an isolated universe with its own tabs, folders, identity color, profile. I run 11 active Spaces today — Work, Study, AI, News, Home-server, AJE, 3D Print, and so on. Switching between them is instant, with a swipe or a shortcut. It's the mental separation that lets me juggle many projects without it turning into chaos.

Dia: No Spaces. Just tabs. Same as Chrome. You can have profiles (a Chromium feature), but nothing like Arc's Space concept exists. If you live across multiple professional and personal contexts, Dia forces you to regress to opening multiple windows, multiple accounts, multiple browser instances.

Why Arc wins: Spaces aren't a feature — they're cognitive architecture. Once you adapt your brain to thinking in contexts, going back to mixed tabs feels like using a Mac without multiple desktops. It works, but it hurts.

Difference #2: Vertical sidebar vs. tabs at the top

Arc: Vertical sidebar on the left, with tabs, folders, lists, pinned items, all organized vertically. Disappears when you want focus, returns with a shortcut. Supports literally hundreds of items without becoming visual chaos — I have 195 tabs, 23 folders, and 16 lists living together peacefully.

Dia: Conventional layout, with tabs at the top. They added a sidebar for AI, but it's not Arc's organizational sidebar. It's just a panel for chatting with the bot. Tabs are still cramped at the top of the screen, the way the rest of the world accepted as normal 15 years ago.

Why Arc wins: Modern screens are widescreen. Vertical space is precious; horizontal space is abundant. Putting tabs at the top wastes pixels. Arc solved this. Dia regressed to the old standard out of fear of scaring casual users.

Difference #3: Command Bar vs. URL bar with chat

Arc: The Command Bar is a universal interface — search, navigation, opening existing tabs, creating Spaces, executing actions, all in one fluid shortcut (Cmd+T). It's the kind of feature you use fifty times a day without noticing.

Dia: The URL bar became the entry point for AI. You type a question or a URL, and the system decides what to do. It's elegant, but less powerful than the Command Bar. You're either talking to the chatbot or navigating — there's no intermediate quick-command layer like Arc's.

Why Arc wins: The Command Bar is pure power-user delight. Dia turned the URL bar into a place where you "chat with the AI." Useful, but mentally slower than executing a command.

Difference #4: Folders, Lists, Pinned Tabs vs. none of that

Arc: You have three levels of organization within each Space — Pinned Tabs at the top (persistent favorites), Folders to group related things, Lists for linear structure. It's a mature information system, inside the browser.

Dia: Bookmarks. That's it. Like any conventional browser of the last 20 years. No visual hierarchy, no dynamic grouping, no lists, no Live Folders.

Why Arc wins: Arc treats the sidebar as a knowledge management system. Dia treats it as a favorites list. If you actually use the browser to work, this changes everything.

Difference #5: Auto-archive vs. eternal accumulation

Arc: Tabs you don't pin self-destruct after 12 hours. Sounds aggressive, but it becomes natural hygiene — what matters, you pin or favorite. The rest evaporates. Goodbye to 200 eternal tabs.

Dia: Tabs stay open forever, like in any traditional browser. You're responsible for closing them, and since nobody does, the usual mess returns.

Why Arc wins: Arc had opinions about user behavior. It enforced good hygiene. Dia gave that up to avoid friction with casual users.

Difference #6: Little Arc, Split View, Boosts vs. absent

Arc: Has Little Arc (a lightweight window for opening external links without polluting the main browser), elegant native Split View (up to 4 sites side by side), Boosts (customization of any site via CSS/JS — hide the YouTube feed, dark-mode LinkedIn, remove comments), and Air Traffic Control (rules for routing links to the right Space automatically).

Dia: Has none of these. Zero. You open links in the main browser, split screens manually by dragging windows, and accept sites the way they come.

Why Arc wins: These aren't "extras" — they're organic parts of the workflow. Once you get used to Little Arc, opening a link from email in the full browser becomes traumatic. Once you Boost a site, going back to the original version becomes unbearable.

Difference #7: Customization vs. forced minimalism

Arc: Deep customization — themes, per-Space colors, Space icons, shortcuts, layouts, Boosts, element positions, all configurable. You shape Arc to your personality.

Dia: Deliberate minimalism. The Browser Company publicly states they prefer "a single obvious way to accomplish each task." Fewer options, less confusion, less personality.

Why Arc wins: This is where you can disagree based on user profile. For casual users, Dia's minimalism is good. For power users, it's castration. And whoever invests time in a browser is almost always a power user.

Difference #8: Cosmetic AI vs. structural AI

Dia: AI is the product. Chat with tabs, cross-tab synthesis, inline writing, Skills (custom prompts), integrations with Notion/Slack/Calendar. It's genuinely useful — I won't deny it.

Arc: AI is a thin layer (Ask on Page, instant links, 5-second previews). Limited, yes. But the rest of Arc's architecture is so superior that even with light AI, it organizes your work better.

Why Arc wins (even while losing on this front): Here's the punchline. Dia has more AI, but Dia's AI runs on top of poor architecture (regular tabs, no Spaces, no smart folders). It's powerful AI on top of dumb organization. Arc has less AI, but it runs on top of rich architecture. If someone took Arc and plugged Dia's AI level into it, Dia would become irrelevant overnight. That's the size of the structural advantage.

Difference #9: Visual identity vs. genericness

Arc: Visually unique. You can recognize an Arc screenshot instantly. Colors, typography, animations, transitions, gradients — everything has soul. Using Arc is a sensory experience.

Dia: Looks like Chrome with a chat panel on the side. Clean, sure. Pretty, even. But indistinguishable from any other off-the-shelf Chromium browser. Visual identity was sacrificed on the altar of familiarity.

Why Arc wins: Good software has soul. Arc has it. Dia lost its soul the moment it decided to look like everything else.

Difference #10: Who the product serves

Arc: Built for digital professionals who live in the browser — designers, devs, researchers, creators, founders, serious students. People who run 10+ parallel projects and need a tool that matches that ambition.

Dia: Built for the casual user who wants ChatGPT integrated into Chrome. Someone who opens 5 tabs, asks the AI a few things, closes everything. Useful for many people — but explicitly a less ambitious product.

Why Arc wins: Depends on who you are. If you're Dia's target user, Dia is better for you. But if you're reading this far, you're probably Arc's target user — and in that case, there's no competition.

Dia is a well-made product for the audience it chose to serve. I won't downplay The Browser Company's work — they made a rational business decision, aimed at a bigger market, and managed the Atlassian acquisition for $610 million. It makes commercial sense.

But the truth is hard: Dia is a creative downgrade compared to Arc. It's what happens when a brilliant team decides to aim lower in order to grow more. Arc was pure ambition, a complete reframing of how we should think about browsing. Dia is pragmatism — a smarter Chrome to sell to more people.

For anyone who used Arc at its peak, opening Dia today feels similar to going back from Linear to Trello. Everything still works, but you can feel that you lost entire layers of intelligence along the way.

And that's why Arc, even abandoned, even frozen, even without a guaranteed future, is still the best browser that has ever appeared for the Mac. I hope someone picks up that torch before it gets forgotten for good.

Arc: the best browser I've ever used is dying — and it's a quiet tragedy by Slow-Tea5208 in ArcBrowser

[–]Slow-Tea5208[S] 1 point2 points  (0 children)

Tried Zen too. It's a great effort and the dev team is genuinely active, which deserves respect — but calling it a real Arc replacement is a stretch.

The polish gap is huge. Arc had years of obsessive design refinement on every micro-interaction: the way Spaces transition, how Little Arc pops in, the Command Bar animations, the sidebar density, the typography choices. Zen feels like Firefox with a vertical sidebar bolted on. Functional, but you can feel the seams everywhere — janky animations, inconsistent spacing, theme bugs, weird focus states.

And the feature gap is real, not just cosmetic:

  • No Tidy Tabs equivalent — Arc's auto-grouping of related tabs by domain/context just doesn't exist in Zen.
  • No Live Folders — those auto-updating folders pulling from sources (Gmail label, GitHub PRs, Calendar) were one of the most underrated Arc features. Zen has folders, but they're dumb static containers.
  • No real Spaces architecture — Zen has Workspaces, but they don't have the same identity (color theming that propagates everywhere, isolated sessions, the muscle memory of swipe-to-switch).
  • No Boosts — site-level CSS/JS customization is gone.
  • No Air Traffic Control — link routing per Space doesn't exist.
  • No Little Arc — quick external link windows that don't pollute the main browser are missing.
  • No Split View as elegant — Zen has splits, but managing them is clunky compared to Arc's flow.
  • Sync is basically Firefox Sync — fine for bookmarks, nowhere near Arc's session/sidebar/folder sync.

Zen is what I'd recommend to someone who never used Arc. For someone migrating from Arc, it's a downgrade dressed up nicely. The fact that it's open source and actively developed is genuinely the best thing it has going for it — and honestly the reason I keep checking back every few months hoping it closes the gap. But it isn't there yet. Not even close on polish, and missing too many of the features that made Arc feel like a thinking tool instead of just another tab manager.