找到 33311 篇相关文章
Microsoft is laying off 4,800 employees today, and more than 30 percent of the job losses are in the company's Xbox division. The significant gaming cuts will affect nearly every part of Xbox and also involve four game studios being spun off to be run independently from Microsoft. Today's layoffs, which are being described as […]
A year after cutting around 9,100 employees, Microsoft is making further layoffs today as it begins its new financial year. The software maker is laying off around 4,800 employees today, approximately 2.1 percent of its workforce. Most of the employees affected by today's cuts are in Microsoft's commercial sales business or the company's Xbox division. […]
They're for more than just fast charging.
GitHub热门项目 | git worktrees + tmux windows for zero-friction parallel dev | Stars: 1,708 | 62 stars this week | 语言: Rust
GitHub热门项目 | Open-source desktop app for downloading, organizing and studying media. Native cross-platform (Tauri + Rust + Svelte). PDF/EPUB reader with focus mode, timestamped notes and spaced repetition. Media downloads via yt-dlp (1.800+ sites). Extensible plugin system. | Stars: 6,293 | 96 stars today | 语言: Rust
GitHub热门项目 | A self-hostable bookmark-everything app (links, notes and images) with AI-based automatic tagging and full text search | Stars: 26,696 | 178 stars today | 语言: TypeScript
GitHub热门项目 | 📺 Cross-platform IPTV player application with multiple features, such as support of m3u and m3u8 playlists, favorites, TV guide, TV archive/catchup and more. | Stars: 6,463 | 21 stars today | 语言: TypeScript
GitHub热门项目 | Run Windows apps on 🐧 Linux with ✨ seamless integration | Stars: 21,861 | 14 stars today | 语言: TypeScript
GitHub热门项目 | The simplest, fastest repository for training/finetuning medium-sized GPTs. | Stars: 60,827 | 246 stars today | 语言: Python
Station F, the Paris-based startup hub founded by French billionaire Xavier Niel in 2017, is gearing up for a new edition of its selective acceleration F/ai program that will cement its role as a stepping stone for AI startups.
Bentley has confirmed that it will finally add an electric car to its exclusive lineup.
I have a folder on my laptop called side-projects . Most of them are Dockerized. Most of them will never see more than a handful of users. And for years, every one of them hit the same wall: getting the thing onto a cheap VPS without losing a weekend — and copy-pasting my own past mistakes forward every single time. Here's the opinion that eventually turned into a project: the part of a PaaS you touch most often should hold the least power over your server. Think of a deploy tool as two planes. There's a read plane — dashboards, logs, container health, the stuff you stare at — where you spend most of your time and which is your most exposed surface. And there's a write plane — deploy, restart, the actions that actually change the system — which is rare and should be gated. My frustration was that the thing I looked at all day and the thing that could rewrite my box tended to sit on the same pile of privilege. So I built Mooring to keep those two planes apart. It's an early, solo project, and this post is me showing it and asking for eyes on it. The mental model The whole thing, end to end: Install it as an unprivileged systemd service (not root). Connect a git repo. Write one mooring.yaml . Click Deploy. That's the loop. Everything below is what's underneath it. What it is Mooring is a small, security-first, self-hosted control plane for Docker — a tiny PaaS. You point it at a git repo, describe your app once, and it deploys and runs your containers on your own server. Same territory as Coolify, Dokku, CapRover, and Kamal — all genuinely good work. The difference I care about is the posture underneath. It ships as one static, CGO-free Go binary . It runs as an unprivileged systemd service — not root. State lives in SQLite (the pure-Go modernc driver). Every asset is embedded with go:embed , so there's no node_modules , no asset pipeline, nothing to build on the box. To be honest about the neighborhood: setting up a self-hosted PaaS, these tools tend to want broad ac
The story behind why we built a WhatsApp CRM that actually understands how WhatsApp works. There's one scene I can't get out of my head. A friend's desk. She runs an online store. On it sat three phones. Not for show. One for customer service, one for the admin, one for the number that was "just for resellers." All three buzzing, nonstop. And there she was, eleven at night, still replying to messages one by one, sighing: "It's the same questions over and over. But if I don't reply, they'll go to the competitor." That's not a rare case. That's the normal state of things for thousands of businesses. We all know one thing CRM software rarely admits: customers here don't live in email. They live on WhatsApp. They ask about prices on WhatsApp, complain on WhatsApp, close deals on WhatsApp, even ask for warranty support on WhatsApp. But the teams handling all of it? They use personal phones. No records, no context, no way to help each other when one person is drowning. Hallo Zetta was born out of that. What Frustrated Us About the Existing Tools Before building our own, of course we looked. Surely someone had solved a problem this simple? Turns out what existed fell into two camps, and both were maddening. Camp one: dumb auto-reply bots. Type "hi," get a template. But the moment a customer asks something slightly off-script, the bot freezes. It actually makes customers angrier, because it feels like talking to a wall. Camp two: bloated CRMs. Loaded with features, dashboards full of charts, but WhatsApp is bolted on as one small tab. As if WhatsApp were an afterthought, not the main battlefield. For most of our customers, WhatsApp is the battlefield. Nothing fit. So we decided to build it ourselves. The Hard Part Isn't "AI Can Reply to Messages" Let me be honest about this. Bolting AI onto WhatsApp is easy. Anyone can wire GPT to a webhook and ship it overnight. If that were the whole goal, this article wouldn't need to exist. The hard part, the thing that made us rethink