Rocket.Chat vs GitHub
Side-by-side trajectory, velocity, and editorial themes.
Rocket.Chat hardens for regulated buyers: phishing-resistant MFA, ABAC governance, and a quiet client-architecture pivot.
The 8.4 line is finishing its RC cycle while 8.5.0-rc.0 lands, carrying a server-side OAuth rewrite with CSRF/PKCE, 2FA-on-OAuth flows, and four new admin permissions for the ABAC panel. Around those headline items sits a layer of plumbing work — an opt-in SDK-over-DDP transport behind a meta-tag/localStorage/URL flag, a room-scoped text-index toggle for large workspaces, and image-URL sanitization closing an XSS vector — alongside the usual stack of patch fixes.
Two trends dominate. First, security and enterprise governance are the gravitational center: ABAC keeps gaining surfaces (panel visibility, app reads, Virtru as a Policy Decision Point in 8.4), OAuth is being rebuilt server-side, and 2FA is being enforced even through identity providers. Second, the team is modernizing the legacy Meteor underbelly — an SDK transport that bypasses Meteor's DDP layer is shipping dormant, and a flag is staging for Babel's removal in 9.0.0.
Expect 8.5 to graduate to GA with the OAuth/MFA hardening as its headline, and for the SDK-over-DDP transport to become the default in 9.0.0 once the dormant period exposes incompatibilities. ABAC will keep accreting admin controls until it's a coherent enterprise governance story alongside SSO and audit logs.
GitHub turns Copilot into a routing layer, with Eclipse client now open source
GitHub's recent shipping cadence centers almost entirely on Copilot, with the product shifting from model choice to routing intelligence — auto model selection in VS Code, a narrowed web chat model picker, and a Gemini 3.5 Flash GA all landed within 72 hours. Outside Copilot, issue fields in public preview and expanded OIDC support for Dependabot continue the slower enterprise workflow consolidation. The Eclipse client going MIT-licensed marks a deliberate widening of Copilot's IDE footprint beyond VS Code without GitHub having to build each integration in-house.
The direction is clear: Copilot is being repositioned as an automatic, model-agnostic agent layer rather than a code-completion product with a model picker. Open-sourcing IDE clients suggests GitHub wants ecosystem-led IDE coverage while concentrating its own engineering on the routing and model layer. Issue fields and Dependabot work feel like quieter platform consolidation around structured metadata and identity, likely to feed Copilot context down the line.
Expect the model picker to keep receding behind 'auto' defaults, and for more Copilot client surfaces (JetBrains, Neovim) to follow Eclipse into the open. The semantic issues index will almost certainly resurface as a Copilot tool, not just a chat-only search feature.
See more alternatives to Rocket.Chat →
See more alternatives to GitHub →