off the top of my head: ip kvms, keyboards, 3d printers, home assistant, cameras, zwave or zigbee. Their moat is superb software support and established ecosystem. I think their most challenging competition would be ESP32s or mini pcs. Source: my ahh
No, it stems from a lineage of Tegra chips that pre-date the M-Series.
This chip was called GB10. One of its predecessors, GV10 was shipped in 2018.
It was a 256 bit, unified-memory system on a chip with a Volta GPU and 12 ARM Cores. GB10 is a 256 bit, unified-memory system on a chip with a Blackwell GPU and 10+10 ARM cores.
the maintainers seem happy, especially now that CI is actually working how it's supposed to. but a non-rare complaint in the Zig discord is how slow Codeberg can be, and other things like the lack of codesearch hurt as well.
> and made several videos of the furnace attempting to start and gave it to gemini
I assume recorded videos and uploaded them in the Gemini phone on their app; and then probably said "what's wrong?"
Gemini is very good at those kinds of things. I recently got some ratcheting straps and needed to use them, but at the time I didn't know what they were called, so I didn't know what to search for on Google. I opened the Gemini app, pushed the button to take a picture (just like in text messages,) and included a message that was similar to "what is this and how do I use it?"
Yes, here is my prompt. It also contained a video: "I have a furnace that will not heat when I reset the power to this unit. It makes some noise within its fan system for about three or four minutes and then I get an error light. Can you help me figure out what may be wrong here?" This prompt is not the best but I was freezing and in my attic.
> Multiple people I know were rebalancing their portfolios way from the big index funds
Hypothetically, let's say the SpaceX IPO is a wild success. Will those people be disappointed on missing out in the returns? In other words, did they rebalance away because of financial numbers they didn't believe in or did they rebalance away because of emotional or philosophical reactions to the company? If they just don't like the company (likely company leadership) then i would guess they don't care how much return they miss out on, they want nothing to do with SpaceX period.
I made a long drawn out comment up thread but i feel like a lot of this drama is due to an emotional response to SpaceX because of Musk, and the possibility of him becoming the first trillionaire, and Anthropic/OpenAI because of AI's risk to labor.
No, it's definitely financial. Something along the lines of SpaceX's valuation only making sense if it replaces the entire productivity of white collar workforce of the entire USA with its AI ventures. If it ends up reaching escape velocity anyway, sure they would be disappointed, who isn't at least a little when they miss some opportunity.
E.g. This is for B2B marketers who need a tool to create social content.
Congrats though for launching. 99% of people don’t even do that. But now the hard work starts, and 99% of user adoption is now marketing (not the product itself).
/mnt/c is a mounted C: drive in WSL2, that allows WSL2 guests to read/write files on the Windows host.
The mount is fine and speedy enough, but the underlying reads/writes turn into native NTFS reads/writes through Windows. NTFS file API is incredibly slow - high fixed overhead for initial file access.
So patterns like node_modules with many small individual files (or compiling code in general) are much much slower on Windows or WSL2 /mnt/c due to the fixed overhead adding up over a large number of files.
It's a ridiculous problem that has plagued Windows for years.
File access is significantly slower on Windows compared to Linux on the same hardware. You can run Linux inside a VM and it will easily beat the host OS in filesystem performance.
If the problem is not NTFS, then it is in how the Windows OS uses it
eBPF has opened the door to such bloatware on Linux. Previously there was no easy, stable way for enterprise bloatware vendors to maintain complex file and subsystem filter and analytic modules. Now that market is exploding because of eBPF, and it's a big reason there's so much work around growing eBPF's capabilities.
Could you expand? I never understood why this was considered acceptable, how is windows filesystem so slow compared to linux?
I am familiar with the issue, doing any sort of ruby development is a nightmare on windows because each require loads a file becoming increasingly slow at boot time
WSL2 operates through a file-level translation layer, not unlike NFS in Linux, which can be a huge performance problem for programs that manipulate lots of tiny files, like git or npm.
WSL2 is a VM based on a Windows virtual disk file (VHD). inside that VHD IO is quite fast , a couple degrees worse than native. /mnt/c is how you access your windows files, but it's slow like NFS (socket based). anything needing high IOPS will be dog slow e.g. compiles, file scanning, etc.
the rule of thumb without the newest features is to copy work to/from /mnt/c into $HOME as needed.
One example is that if you have a node modules folder on Windows and you try to delete it from WSL it can take 10 plus minutes whereas if you deleted it directly in Windows it would have just taken a few seconds
Also if you try running Next js from files on Windows from WSL it takes minutes for each page to compile to the point that any local development is impossible so you would have to either run the Next JS server on Windows or move the files to WSL
Anything with node_modules takes ages on my Windows machine, whether it is through WSL, Docker or direct, largely in part due to corporate filters, checks, anti-virus and malware protectors and endpoint control.
Although the stuff you mention is true, it is not the only reason. NTFS is just notoriously bad at reading/writing tons of small files.
It also has a lot of problems with locking files that are open by a process, if you have a rogue process reading your node_modules npm install or rm node_modules can hang until that process finishes.
yarn2 keeps dependencies as tarballs instead of extracting them to disk, imported files get loaded from the tarball at runtime. Makes a massive difference in windows.
Since most of the R&D are done on the iPhone side, Neo's margin is actually quite good. The R&D for M5 and M5 Pro etc have to be amortised by Air and MacBook Pro.
The percentage should be similar. In the old days of Apple pricing, Apple margin is nearly fixed and you could literally work out their BOM by doing reverse calculations. Things changed with Tim Cook but it is still largely similar.
Lower margin, but higher volume. Plus a subset of the buyers will subscribe to Apple Music, buy apps from the App Store, etc.
I am surprised that they only do it now, since Mac marketshare growth has stagnated for a long time and it's even hard to grow the iPhone marketshare. Growing the Mac marketshare by making very competitive models is one of the best ways for them to grow and to grow services fees.
I think the problem was Apple management was too obsessed with the iPad, believing they would replace laptops.
Apple's advantage is that they design a large share of their own parts, and their partners build them at a very high volume since they are used in more than one product line.
They don't have to pay a margin to so many component vendors in addition to economy of scale gains.
At a lower Neo volumes, they were using already manufactured iPhone Pro chips that were binned due to a bad GPU core, but they reportedly have already blown through that supply.
They also came up with a new process that uses extruded recycled aluminum for the case, which needs much less CNC time to clean up.
For most people in the Apple ecosystem, the iPhone is central and the Neo is another useful (but secondary) companion device. Not unlike the Watch and Airpods.
Leaving money on the table, as opposed to losing it. They make a decent buck on the hardware, but could have charged more (though likely would have sold fewer units).
But I can’t understand what are the use cases to be selling 73M units.
Would anyone mind sharing what are the broadly applicable use cases, because selling 73M units is well beyond hobbyist fun.
https://investors.raspberrypi.com/
reply