今日已更新 256 条资讯 | 累计 20726 条内容
关于我们

标签:#us

找到 1032 篇相关文章

AI 资讯

Why SCORM Refuses to Die — And What AI Finally Changes About That

SCORM was built in the early 2000s for a world of CD-ROMs and Flash. It's 2026 and it still runs 80%+ of corporate e-learning. Here's why, and why generative AI might be the thing that finally breaks the cycle. SCORM Is Everywhere, and Nobody Is Happy About It If you work anywhere near corporate learning, you've encountered SCORM — the Sharable Content Object Reference Model. It's a set of standards that lets e-learning content talk to a Learning Management System: track completion, record scores, resume where you left off. SCORM 1.2 was released in 2001. SCORM 2004 followed a few years later. That's it. The spec hasn't meaningfully evolved in two decades. And yet, almost every LMS on the market — Moodle, Cornerstone, SAP SuccessFactors, Docebo, Absorb — still supports SCORM as a primary content format. Most Fortune 500 compliance training runs on it. Every major authoring tool, from Adobe Captivate to Articulate Storyline to Lectora, exports SCORM packages. It's the TCP/IP of corporate learning: unglamorous, creaky, universally understood. Why It Won't Die: The Network Effect Nobody Talks About People love to write "SCORM is dead" articles. I've been in e-learning engineering for 11 years and I've read that headline at least once a year since I started. SCORM isn't dead because it benefits from one of the strongest network effects in enterprise software. Consider the ecosystem: Authoring tools export SCORM because LMS platforms expect it. LMS platforms support SCORM because authoring tools export it. L&D teams require SCORM because their procurement processes mandate it. Procurement mandates SCORM because it's the only format every vendor supports. Breaking this cycle requires everyone to move simultaneously. That doesn't happen in enterprise software. It especially doesn't happen when "good enough" works and switching costs are invisible but enormous (repackaging thousands of courses, retraining content teams, renegotiating vendor contracts). xAPI (Tin Can) was su

2026-06-12 原文 →
AI 资讯

Pokémon Go Scans Trained Military Drone Navigation Tech

Pokémon Go Scans Trained Military Drone Navigation Tech Meta Description: Discover how Pokémon Go Scans Trained the Navigation Tech for Military Drones — the surprising data pipeline from your phone to the battlefield. (158 characters) TL;DR: Niantic, the company behind Pokémon Go, collected millions of 3D environmental scans from players worldwide through its AR scanning features. That same spatial mapping technology and data infrastructure has now been linked to navigation systems used in military drones — raising serious questions about informed consent, dual-use technology, and the hidden value of "free" mobile apps. Key Takeaways Pokémon Go players unknowingly contributed to a massive real-world 3D mapping dataset through Niantic's AR scanning features. This spatial data and the underlying technology stack have been connected to navigation systems used in autonomous military drones. The pipeline from consumer app to defense application is a textbook example of dual-use technology — civilian tools repurposed for military ends. Users were not clearly informed their scans could be used beyond in-game features. This story has major implications for data privacy, tech ethics, and how we think about "free" apps. Regulatory frameworks around dual-use data collection remain dangerously underdeveloped. Introduction: The Game That Mapped the World When Pokémon Go launched in July 2016, it looked like a harmless — if slightly chaotic — augmented reality game. Millions of people wandered parks, city squares, and college campuses, phones raised, hunting virtual creatures overlaid on real-world environments. But beneath the Pikachus and Poké Stops, something far more consequential was happening. Niantic was building one of the most detailed, crowd-sourced 3D maps of the physical world ever assembled. And as reporting has surfaced in 2025 and 2026, the revelation that Pokémon Go scans trained the navigation tech for military drones has ignited a firestorm of debate among tech

2026-06-12 原文 →
开发者

I’ve found the Goldilocks of portable MIDI controllers

I have tested more portable MIDI controllers than I can keep track of, and I will tell you right now: 37 keys is the ideal size. While Arturia's 25-key MiniLab MK3 is a solid controller that easily fits in a backpack, it feels a bit claustrophobic. The new $149 MiniLab 37 adds another octave, giving […]

2026-06-12 原文 →
开发者

Looking to connect with fellow C++ learners and developers

Hi everyone 👋 I'm currently learning C++ and looking to connect with other people who enjoy programming. I'm interested in improving my coding skills, building small projects, and learning from more experienced developers. If you're also learning C++ or are willing to share advice with a beginner, I'd be happy to chat and learn together. Happy coding! 🚀

2026-06-11 原文 →
AI 资讯

Elon Musk is encouraging race riots on the eve of SpaceX’s IPO

Elon Musk, on the verge of becoming the world's first trillionaire, is whipping up anti-immigration tensions amid ongoing riots in Belfast, Northern Ireland. Following a knife attack in the city on Monday, Musk declared support for Restore Britain, a hard-right populist political party that advocates for large-scale migrant deportation in the UK. He reposted statements […]

2026-06-11 原文 →
AI 资讯

The Microsoft Interview Question I Keep Thinking About

A few months ago, while interviewing for a Cloud Solutions Architect role at Microsoft, one of the interviewers asked me a question that stuck with me long after the interview ended. Not because I couldn't answer it. But because I kept thinking about whether I had answered it well. The question was: "What's the hardest part about working on mainframe technology?" At the time, I was still relatively new to the world of mainframes. And by "relatively new," I mean embarrassingly new. Before joining my current company, I didn't even know something called a "mainframe" still existed. If you'd asked me what COBOL was, I probably would've guessed it was a Pokémon. Okay that is an exaggeration but you get what I mean. I still remember early on hearing terms like KT (Knowledge Transfer) being thrown around and quietly wondering if everyone had received some secret corporate dictionary except me. The good news is that I've never been particularly afraid of looking stupid. So my strategy is simple: Ask the question. Then ask the follow-up question. Then ask the question that reveals I didn't understand the previous answer either. Surprisingly, people were usually happy to explain. Anyway, after a few KT sessions and what I'd generously describe as a "bare minimum amount of research," my brain went where most developers' brains probably would've gone. The technology The age The tooling The learning curve The fact that some of these systems were designed before I was even born All perfectly reasonable answers. But while I was sitting there in the interview, another thought appeared: "This feels too obvious." Interviewers at that level usually aren't asking for the first answer that comes to mind. They're trying to understand how you think. And the more I reflected on that question afterwards, the more I realized something interesting. The hardest part isn't the technology itself. Before I started working around large enterprise systems, my mental model of old technology was pret

2026-06-11 原文 →