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

标签:#AR

找到 4422 篇相关文章

AI 资讯

Browse CVPR 2026 papers on PapersWithCode [P]

https://preview.redd.it/se5nr2z7tt4h1.png?width=3046&format=png&auto=webp&s=7db15b73afb749da236e5bb50ff96372f6a3239b Hi, Niels here from the open-source team at Hugging Face. It's been 2 weeks since I launched paperswithcode.co , a revival of the website we all loved. It allows us to keep track of the state-of-the-art (SOTA) across various domains of AI, from agents to computer vision and time-series forecasting. I've just added conference support as a new feature. The idea is that you should be able to easily browse all papers of major AI conferences like NeurIPS, CVPR, and ICML. As CVPR 2026 takes place next week in Denver, USA, I've indexed all papers with corresponding arXiv IDs. They are categorized by task, and tagged with linked GitHub and project page URLs, Hugging Face artifacts, and evals. You can also browse the papers which were accepted for an Oral presentation as well as the Spotlight papers. You can try it at https://paperswithcode.co/conferences ! Feel free to leave feedback. submitted by /u/NielsRogge [link] [留言]

2026-06-02 原文 →
AI 资讯

What are the best 10 \ 20 buck coding ais left?

So basically Claude at 20 buck sub is not much better than free. Chatgpt. It is pretty much shit. Gemini. It seems to have some reductions to its abilities in the last couple of months as well. The 20 buck price range used to have lots of good ais. Now they are all limited, downgraded. What would be the king in this price range? I have found myself using gemini ai pro with other ais as free on the top of that. submitted by /u/aluode [link] [留言]

2026-06-02 原文 →
AI 资讯

I wanna discuss medical ai researchs with major, and I improve my english skills. Please...discuss them helping my english skills

Hi, I'm prepare for a phd in the US in medical AI, so I want to improve listening and speaking skills. I warry about admission interview, and I like discuss research. I find male friends because I have a girlfriend. I don't want to make her worry. I find the friends online firstly. Please feel free to contact me. submitted by /u/CrazyIndependent7436 [link] [留言]

2026-06-02 原文 →
AI 资讯

I scraped over 2 million job postings across 100,000+ company career sites into a unified, daily-updated dataset. [P]

Over the past few months, I've been working on a high-scale scraping pipeline to aggregate listings directly from company job boards and applicant tracking systems. Mapping over 100,000 distinct companies to their career pages turned out to be a massive engineering headache, but it's finally stable. The result is a unified database of more than 2 million active job postings, which I'm opening up to everyone for free. I am running daily delta refreshes to keep it current. Dataset Overview Scale: 2M+ active job listings across 100,000+ unique companies. Format: Parquet. (To keep storage costs to minimum) Core Fields: job_title, company_name, company_website, job_description, location, post_date, and the original tracking URL. For more detailed info check here . Update Cadence: Refreshed daily straight from the source. View the stats here . (Currently it contains only minimal stats, but I plan on improving it based on the comments) Why I Built This Finding a clean, scaled, and up-to-date job dataset is surprisingly difficult. Most available options are either heavily gatekept by expensive subscription APIs or restricted to a single job board like LinkedIn. By scraping the actual employer sites directly, this collection sidesteps the noise and captures a much cleaner cross-section of the live market. How to Access It I set up a dedicated project space where you can grab the data directly: Open Job data Let me know what kind of analysis or projects you end up running with it. If you have questions about the engineering architecture behind handling this scale, or ideas for specific fields you'd like to see enriched next, let's discuss in the comments. submitted by /u/Invicto_50 [link] [留言]

2026-06-02 原文 →
AI 资讯

Why C is still dominates C++?

Why C Is Still the GOAT (And Why People Like Me End Up Hating C++) Disclaimer: This is a personal opinion from a developer who enjoys simple tools, simple languages, and simple debugging sessions. The Eternal Question Every few months, somebody asks: "Why are you still writing C in 2026?" My answer is always the same: Because C knows exactly what it is. No hidden magic. No surprise abstractions. No template metaprogramming black holes. No compiler errors longer than my source code. Just you, a compiler, and a Segmentation Fault waiting patiently around the corner. C Is Honest One thing I love about C is that it never pretends to protect me. If I allocate 8 bytes and write 16 bytes? Boom. If I dereference a bad pointer? Boom. If I forget to free memory? Boom (eventually). But here's the important part: I know exactly why I got cooked. The language didn't hide anything from me. C basically says: "Here's the loaded foot-gun. Try not to shoot yourself." And honestly? I respect that. Meanwhile in C++ C++ often feels like this: template < typename T > concept SomethingComplicated = requires ( T t ) { // 300 lines of magic }; Then the compiler responds with: error: instantiation of recursive template ... required from ... required from ... required from ... required from ... ...followed by 14 pages of diagnostics. At this point, I'm no longer debugging my code. I'm debugging the language itself. My Personal Villain Origin Story I started using Visual C++. You know. The gigantic Microsoft ecosystem. The IDE. The project files. The build settings. The mysterious compiler flags. Eventually I found myself spending more time fighting tools than writing software. And somewhere along the way, I started associating that frustration with C++ itself. Fair or unfair? Probably unfair. But emotions aren't always rational. Modern C++ Feels Like Three Languages Wearing a Trench Coat Old-school C++? Pretty understandable. Modern C++? Sometimes it feels like: C Object-Oriented C++ Template

2026-06-02 原文 →
AI 资讯

NAT, SNAT, DNAT, PAT & Port Forwarding Explained Without the Networking Headache

Most people use these technologies every day. Almost nobody knows they exist. Every time you open YouTube, browse Instagram, join a Zoom meeting, or play an online game, your router is quietly performing a series of networking tricks behind the scenes. Those tricks have names: NAT SNAT DNAT PAT Port Forwarding They sound intimidating. They're actually much simpler than they appear. Let's break them down using something familiar: your home Wi-Fi. The Problem the Internet Had to Solve Imagine a family of five living in one house. Everyone owns a device: Laptop Phone Smart TV Gaming Console Tablet Each device needs internet access. The problem? Your Internet Service Provider usually gives you only one public IP address . Something has to manage all those devices sharing a single internet connection. That's where NAT comes in. NAT: The Receptionist of Your Network NAT stands for Network Address Translation . Think of NAT as a receptionist in an office building. People inside the building have room numbers: Laptop = Room 101 Phone = Room 102 TV = Room 103 But when communicating with the outside world, everyone uses the building's main address. The receptionist keeps track of who sent what. Your router does exactly the same thing. What Happens When You Visit Google? Inside your home: Laptop 192.168.1.10 Your router: Public IP 49.x.x.x When you open Google: 192.168.1.10 ↓ Router ↓ 49.x.x.x ↓ Google Google never sees your private IP. It only sees your router's public IP. That's NAT in action. SNAT: Changing the Sender's Address SNAT stands for Source Network Address Translation . The keyword is: Source It changes the sender's address. Before leaving your network: Source: 192.168.1.10 After SNAT: Source: 49.x.x.x The router replaces your private IP with its public IP. Without SNAT, websites wouldn't know how to send responses back to you. Real-Life Example Imagine mailing a letter. Instead of writing your bedroom number as the return address, you write the house address. Tha

2026-06-02 原文 →
AI 资讯

Stop picking a homelab mini-PC by TDP. The number that decides the power bill is idle watts.

A homelab box that never sleeps runs 8,760 hours a year. So the spec that decides what it costs you is not the one on the box. It is the one nobody prints: how many watts it pulls sitting at the login prompt doing nothing. I kept hitting this while shopping for a Proxmox node, so I put the measured numbers in one place. More on that at the end. First, why the spec sheet lies to you. TDP is a thermal budget, not a power reading TDP is the heat the cooler has to handle at full tilt. It is a design target for the heatsink, not a measurement of what the chip draws, and it says almost nothing about idle. Your homelab box spends 95%+ of its life idle, so the number that runs up the meter is idle wall power, and that number is never on the product page. The arithmetic is unforgiving. One watt running continuously is 8.76 kWh a year. So the gap between a 7 W box and a 35 W box is not 28 watts, it is about 245 kWh a year, every year, for as long as the box is on. Plug in your own rate to get the dollars; the point is the gap compounds. Where TDP actively misleads you A few measured results from the dataset I'll link below, all from third-party wall-meter readings, not vendor claims: The new N100 wave is genuinely low. A Minisforum UN100C measures 5 to 7 W at idle. Beelink, GMKtec and Trigkey N100 boxes land in the 6 to 10 W range. For a Pi-hole, a few containers and some light VMs, this tier is hard to beat on running cost. AMD mini PCs idle far higher than their marketing suggests. A Minisforum UM790 Pro measures 25 to 45 W at idle. A Beelink SER6 Pro lands at 20 to 35 W. These are fast little machines, but if you picked one expecting "small box, small draw," the meter disagrees, and over a year that delta is real money. Newer and higher-TDP is not lower-idle. A Dell OptiPlex 7060 Micro idles just over 18 W on its 65 W-TDP desktop chip. The older 7070 with a six-core part sits around 13 W, and the low-power "T" SKUs lower still. The CPU's TDP class predicted idle better tha

2026-06-02 原文 →