When I think about how long chips like the 6502 have still been in active use (almost 50 years now), it is hard to conceive of a world where there isn't a significant presence of x86 activity for the rest of my life.
The majority of 'the market' may go elsewhere, but for a gazillion reasons, x86 will not be disappearing for quite a while. At this point it would honestly surprise me if we didn't at least have high quality emulation available until the end of the human race as we know it.
Sure, we've probably lost most of the software ever written on it, but a whole lot of interesting artifacts from a key transition point for our species still remain locked up in this architecture.
Given the new 128-core AMD server parts are on-par with ARM in terms of power efficiency and capable of more raw compute, it may even grow a bit.
I think there's lots of room for ARM, Risc-V and x86_64 in the future. There's reasons to support any of them over the others. And given how well developer tool are getting support across them all, it may actually grow a lot. I think the down side is a lot of the secondary compute accelerators, such as what intel is pushing and what the various ARM and Risc-V implementations include in practice.
The further from a common core you get, the more complex porting or cross platform tooling gets. Even if for big gains in some parts. For example, working on personal/hobby projects in ARM boards that aren't RPi is sometimes an exercise in frustration, with no mainline support at all.
> I think the down side is a lot of the secondary compute accelerators, such as what intel is pushing and what the various ARM and Risc-V implementations include in practice.
I’m curious why this is a downside. The current trends in computing is that we’re long past the point of single threaded compute. The first step of that was multi processor and multi core and that’ll continue with more and more dedicated and specialized computing sub-processors. Energy prices are more and more becoming a major determining factor as is the area needed for cooling. By having more separated subprocessors you get both efficiency and easier ability to cool the parts.
The specialized sub-processors are implemented differently, not always available, and not available 1:1 to compute nodes. If you're offering, for example, cloud compute... you can offer 4 cores pretty easily... but if there are 2 specialized sub-processors, then do you offer them, does this queue across all users/clients on that system or do you just block and pretend it doesn't exist. For Zen 4c, they're all general compute.
This means, practically speaking, you're only going to really have 1 host on a server that wants/needs these specialized sub-processors. Which means more space/heat/power for a single user/service. It's probably fine for some things, but far from ideal. This also doesn't get into software optimization and alternative paths where not available.
This gets far worse in the ARM space, as it seems every SOC does something different, which means it's often broken, or unusable if you're using a mainline OS/kernel and even then most software won't be optimized for it. At best, you can maybe playback 4k compressed video. At worst, you can't at all. Just speaking to the most common instance in that space, which is video compression, which is often built around closed drivers that mainline OSes (Ubuntu Server, Debian, etc) don't have in the box, and the vendor only supports a single version of a distro fork with no upgrade path.
I'm not a hardware designer, so quite possibly wrong.
My understanding for the push for energy efficiency is not for cost reasons, but for performance and stability. At a certain power level, the chips just can't dissipate enough energy, especially on smaller nodes.
If amd could double the performance at double the power, they would.
Cost is obviously a marketing/client-value thing too.
Plausibly we're headed for a world where feature size decreases stall out but manufacturing improvements continue to lower the price of transistors over time. In a world like that throwing in a few x86 cores even if the dominant ISA shifts might be worth it from a backwards compatibility standpoint even if other ISA become dominant.
There's lots of complications to address there (strict x86 memory ordering versus loose ARM ordering, for instance) but I expect they're solvable.
Yeah, I'm actually thinking something like a socket integrator buying an 8 core chiplet from AMD or Intel to connect via CXL or whatever to the ARM/RISC-V/GPU/Tensor cores in the other chiplets from different manufacturers.
It used to somewhat work for humans, until about the mid-19th century (in Europe, other places vary). A newborn was unlikely to reach an age of 5, a 5 year old had better chances but might still die from illness in childhood, but someone who reached an age of 20 could be expected to reach an age of 40, and if you reached 40 you might well make it to 80.
ARM vs 8051 is a licensing fee thing usually. 8051 license terms are extremely generous compared to ARM as far as I know. RISC is a being explored more readily, but toolchains are not nearly as robust as arm/8051.
Just a few years back, I checked out datasheet for an IC encountered in an USB card reader (newly bought).
Turns out a 8051 core was included (iirc clocked @ ~30 MHz, to control jobs like light busy LED on card read/write ops, some bus arbitration / priority settings, power management or the like).
Made total sense to encounter an ancient, 'fast', tiny 8-bit core there, even though unexpected.
There must be (and will be) an endless list of products including tiny CPU cores like that (eg., RFID tags come to mind).
I'm reminded of the Vernor Vinge novel where a character hacking some fleet's automation hundreds of thousands of years in the future casually mentions that the tech stack is so old that the system time stamp is still the Unix Epoch
“And via a million million circuitous threads of inheritance, many of the oldest programs still ran in the bowels of the Qeng Ho system. Take the Traders’ method of timekeeping. The frame corrections were incredibly complex—and down at the very bottom of it was a little program that ran a counter. Second by second, the Qeng Ho counted from the instant that a human had first set foot on Old Earth’s moon. But if you looked at it still more closely…the starting instant was actually about fifteen million seconds later, the 0-second of one of Humankind’s first computer operating systems.”
I mean a thousand years are very hard to imagine, and how many changes there are.
But the cynical operator in my head could just laugh. We as a tech community are still running MS-DOS productively. Just wait, someone will run the door controls of our first space ships on some x86 chip. Or some similar system you just need, but that never gets time to be updated properly. Just wait, the new cruise liner spaceship of the milky way republic is going to run some x86 emulator for their window control.
Maybe this is because we're mostly a Apple computers household, but a few months ago I realized the only x86 device my household own is our NAS (and frankly it's the worse device we own). Was pretty wilded out when I figured that one out.
I wouldn't know. I just watched a talk a couple of years back about reverse engineering tamagochis, and they turned out to run on some 6502 compatible chip made by a company that - IIRC - sells to toy makers mostly.
I was surprised to learn a few months ago that 6502's are still in production, so there must be some use for it. Perhaps replacement parts for industrial equipment from the 70s-90s?
8051 was once big in industrial applications like PLCs.
Somehow I doubt much has changed. In such applications, reliability + maturity of hw/sw ecosystem is much more important than raw speed or design innovations a competing architecture might bring to the table.
So 8051 based parts may see the occasional process shrink, addition of new peripherals, or new IC packages, I/O pin counts, operating voltage etc.
But I'd doubt any designer worth their salt would dare touch that core architecture unless their life depended on doing so. :-)
8051 is quite popular in new designs as a low-cost embedded controller. You don't see it as often as a discrete component [1]; it's more frequently embedded in more complex devices, like as controllers for USB peripherals or even for startup sequencing in larger parts.
[1]: Although that is a thing too; there's a number of manufacturers like Silicon Labs with extensive lines of modern 8051-based mcirocontrollers.
x86 is now permanently a part of humanity. 1000 years from now, when we've transcended our physical bodies and exist only as streams of sentient data and energy traveling between the stars, I 100% guarantee x86 will be detectable somewhere.
Stuff like 6502s and Z80s are a bit like little single-cylinder engines - the world will move onto all sorts of interesting new places, but something somewhere will always be powered by a wee Briggs & Stratton that starts first pull of the string, and we'll be glad of it.
We'll always need tiny cores, but it's worth noting that RISC-V can squeeze down to pretty small sizes and is so much nicer to use. Notably you can go smaller than a 68k or 8086.
I suspect 32-bit RISC-V cores will become the minimum unit of processor for new designs. Not a meaningful cost increase over say a 6502 (or ARM) to build, but the convenience of having mainstream compiler support and that kind of thing does make a difference in the cost of building a product.
We did a migration from GCP's Intel based E2 instances to AMD's T2D instances and saw huge 30% savings in overall compute! It is similar amount of savings folks got from switching to AWS Graviton instances, so looks like AMD might keep the x86 ISA still alive
E2 is just extremely old. E2 are a mixed fleet that contain CPUs as old as Haswell. Haswell launched over 10 years ago. It makes sense that you get a better bang for your buck from using something that isn't gravely obsolete. You should also keep that in mind when benchmarking E2, since it's a grab-bag of CPUs you need to control for the actual CPU type, either by specifying the minimum one you require or assuming the worst.
That is true. But in cloud our hands our tied, we cannot really switch from one one generation to another so easily. GCP has so far never launched a new chip while keeping the price same or lower. We did same cost/perf analysis on newer generation chips like Ice Lake from Intel and even Milan from AMD in the form of N2D, but both are quiet expensive for the performance uplift they provide. The unique thing about T2D is that the price is competitive with 10 year old E2, which has been the case only for ARM based CPUs like Graviton and Ampere Altra (T2A from GCP)
ETA: Since you are using Go and targeting a specific modern CPU, you may also get a measurable benefit from setting GOAMD64=v3, so the go compiler generates code using AVX2, BMI2, LZCNT, etc.
I would just like to point out that that is not how the saying goes. When Queen Elizabeth died it would have been “the queen is dead, long live the king”, as the dead thing is the predecessor and the living thing is the one that follows it
In this case, the article is implying that Intel (x86) is dead to them and AMD (x86) is the successor. Whether Intel is dead or not is up for debate (I doubt they are), but the saying is used correctly.
If we're going to be that pedantic, we might as well just say that because Intel and AMD aren't living entities so they can't be "dead". Or we could just accept that the original meaning of the phrase has evolved and is flexible enough to be used in situations where it's not absolutely literal.
I’ve noticed that as well. It beggars belief that people are seriously arguing about applying a centuries-old foreign metaphors about kings to modern large corporations. That’s straight over Pedantic territory into the Obnoxious Contrarian wilderness. Sigh…
I'd guess it's a timing thing. This site likes to prioritize more highly the "current" discussions which are generating upvotes as long as they're not also generating a ton of downvotes.
Your point is about the factual statement (whether Intel x86 is actually dead).
But this subthread (as started by amusingimpala75), and your direct parent's question was about whether the idiomatic usage of "(old) X is dead, long live (new) X" was correct (given that the author believes AMD taking over Intel is the factual case). That is, not about whether the factual statement is correct or not, just whether it's expressed well idiomatically.
Perhaps it would be better phrased as "'intel x86'" vs "'AMD x86-64'". Specific sets of mandatory instructions and extension parameters - But AMD's set "won" at some point in the past, roughly corresponding to the launch of Intel's "Core" microarchitecture in 2006 when they started competing in the x86 space again
>When Queen Elizabeth died it would have been “the queen is dead, long live the king”, as the dead thing is the predecessor and the living thing is the one that follows it
And if a freshly dead king is replaced by a new king, it's "the king is dead, long live the king".
The predecessor and the living thing doesn't have to be of the opposite sex, or use a different term:
no, the "saying" is "the king is dead, long live the king", because the "saying" uses the apparent absurdity of the king being dead and alive to illustrate the stability of the royal system: the people don't need to worry, they are never without a king.
yes, in a particular circumstance, if there happens to be a queen involved (rarer within agnatic primogeniture), then it would be spoken as you say, but that's not "the saying" that people generally quote.
Rarer still, but 2 Queens would have the same form as the saying, "the queen is dead, long live the queen", which I mention to mention, when the king is dead, if it's "long live the queen", it's not generally the king's spouse even if she was styled "queen", but would be some direct blood relative of the king such as his daughter. I think his wife would become Dowager Queen. The Dowager queen might rule as Regent if her children were not adults yet.
It's really important to benchmark this stuff, because depending on the workload, a cheap VPS is the way to go (you're almost always idle, say) or getting some of the latest and greatest hardware under your desk can quickly pay for itself.
As a separate data point, I briefly switched one of our servers from an r6a.4xlarge (AMD Epyc) to a r6i.4xlarge (Intel Xeon) and saw a 30% speedup in our number-heavy compute task. I would love to find out why (MKL or AVX512? Do I need to recompile numpy?), but for the time being it pays to stay on Xeon.
We eventually switched to m-instances since that fits our compute/memory usage better when we’re at limits.
Yes, I point this out in the article too. Which CPU will perform better is heavily dependent on your workloads, so I refrain from relying 100% on synthetic benchmarks and directly ran canaries in production instead. It's definitely possible Ice Lake is superior for your workload than Milan
Because it essentially doesn't? At least when I tried looking a few months ago, it was really hard to find any commercially available RISC-V SoCs, let alone high performance ones. Sure there's little hobbyist boards going for $200>, but that's about it.
Probably because the article is looking at silicon that's actually available today, and big-iron RISC-V silicon akin to Xeon/EPYC/Graviton/Ampere is more of a hypothetical at this point.
Cloud world is really slow. Imagine writing about Zen3 Milan in Aug 2023 when AMD has already announced Zen4c Bergamo. Actually we were "ahead of the curve" since we got access to T2D before it was made publicly available in Tokyo region, and even then it took several months to get enough capacity in Tokyo to fully migrate our production Kubernetes cluster.
I really wish we could test out RISC-V SoCs from the likes of tenstorrent, but it's a long journey
It takes very long time for going from preview to actual production usage for anyone. We had T2D preview access more than a year ago, it took several months to get enough stock in Tokyo region (US always gets preference in such cases whenever a new machine type comes out). GCP already has Zen4 in preview for some US customers. Also, us being one of the largest GCP customers in Japan made things even slower
> Why do these kinds of articles essentially refuse to admit RISC-V exists?
Because as much as I like RISC-V myself, it hasn't built up the scale needed to supplant x86/64 or ARM. It's still a long way to go before the following are achieved:
- Similar/better performance to x86/64 or ARM, with at least 80% of their performance
- Similar/lower prices compared against x86/64 or ARM
- A win in either price-to-performance or power-to-performance against x86/64 or ARM at some point.
RISC-V is important, and I use it every day for work, but there are no mainstream mature server platforms using it and that's what this article is about.
Because in the great scheme of the universe, it doesn't matter.
It is an architecure cheered by FOSS folks, that ignore cloud offerings will be just as closed, and no one is selling RISC-V computers at the shopping mall down the street.
A few programmers on HN think only they use laptops (and specifically Macbooks). Not surprising.
If you just bother to open your eyes just a little bit wider you would notice that there is a huge market for Chromebooks, budget laptops, gaming laptops, mobile workstations, ultrabooks for students, gamers, business people, bankers etc. New things are happening every month. We are seeing more efficient laptops from Intel and AMD. Companies like Framework are doing actual innovations in the decade old laptop area. And there are workflows that can only be done on Windows.
Apple products are only dominant the US. For the rest of the world they are more of an luxury item.
That said, I am not terribly interested in ARM-based laptops for now. Yes, they may be more energy efficient and all but that hardly matters to me compared to just having the same x86 architecture I run on my desktop and servers. That sweet binary-compatibility means less headache.
People underestimate the advantages that CPU architecture monoculture gave us, though they are getting admittingly less important year by year. Maybe one day I am going to run an ARM laptop or even RISC-V.
> ... just having the same x86 architecture I run on my desktop and servers.
Yep! For me, it's the same ARM64 architecture I run on my desktop and servers[1]. :-)
Hetzner's offering is very competitive, cheaper than their already rock-bottom x86 offerings. Then there's AWS Graviton, Oracle with their free tier (not sure how expensive that gets if you actually have to load it) and both Azure and Google also have ARM offerings.
A key element to Apple and ARM and why you are right outside the us is this:
1. Apple's chips are so far beyond everything else that it makes obvious sense for Apple only. Snapdragon is at least 30% slower single core while having worse Performance per watt.
2. Apple wasn't playing fair with their translation layer. The Rosetta layer cheats a little because apple also made the chip. The secret sauce is that the M1 has a hardware compatibility mode (That technically breaks ARM spec) for x86 memory order that basically gives near 1:1 performance.
3. Microsoft heavily botched their ARM rollout (again. Hello, Windows RT). The translation layer on W10/11 is just bad, not because of bad coding but just the technical limits of what they were trying to do.
4. Google is in a great place with ARM compatibility in Chrome OS as the only consumer-facing apps are either built-in or on the play store...which was designed for ARM in the first place. Problem is that nobody will give them a good chip for ChromeOS and the focus is on low end, so Mediatek is just cruising.
ARM is a great arch...but right now it is Apple VS x86, not ARM.
Their cores break the ARM spec in other ways too. Added instructions for AMX, new guard privilege modes, HCR_EL2.E2H can't be disabled, GPRs are clobbered on WFI, etc.
>3. Microsoft heavily botched their ARM rollout (again. Hello, Windows RT). The translation layer on W10/11 is just bad, not because of bad coding but just the technical limits of what they were trying to do.
It's not bad at all, however Intel patents heavily restricted the initial implementation, to the point they couldn't ship the 64bit emulation. Apple decided to wait out the patents.
Unfair … strange use of phrase. Innovative would be a better use of word as nothing prepare others to do the same … it is good to have a vendor play differently not follow the slow and dominated by arm player c.
The conclusion is on the ball but only current. M1 has been a bit old now and if other arm vendor and the two major architecture (ibm power for mainframe … cannot be counted) it is at least x86-32 plus x86-64 vs arm vs apple.
The wording of unfair is more of a fun use of the word. Because Apple vertically integrated the whole product and software supply chain, they are singularly able to do things others cannot. In that context, if one is playing "fair" on the terms of everyone else when they could do more...they are losing.
ARM has a lot more market share in people's minds than in actual numbers. One research firm says that ARM has 15% of the laptop market share in 2023, expected to increase to 25% by 2027. (Surprisingly, Apple only has 90% of the ARM laptop market.)
In the server market, just an estimated 8% of CPU shipments in 2023 were ARM.
I keep meaning to research this, and maybe this isn't the right place, but how are things going for Linux executables? Last I tried Linux on ARM it seemed like application-level support for ARM was very spotty.
It doesn't seem like a Rosetta 2-like effort is making it into mainline Linux anytime soon, if ever.
For open source applications it's generally pretty good. Closed source: not so much.
qemu-x86_64 is probably the closest there is to Rosetta; it works fairly well and I think conceptually it's identical or similar to Rosetta, but I don't really know what the performance is like, and it's of course not as integrated/automatic as Rosetta.
I suppose it depends on the distribution but most I've used (Manjaro, Void, Alpine) are close to 1:1 with x86. Of course third party applications have to compile for ARM if they don't intend to distribute source code.
That is spot-on. The fact of the matter is that it is Apple VS x86, not ARM. The M1/2 have dominant mindshare due to being actually better.
On Windows, ARM products just suck. The product is just bad because there is no reason to use it. The chips available are worse than x86 and then the software issue is bad due to a whole set of reasons that Microsoft can't change on their own..\
Google has that last 10% probably, ChromeOS moves ARM devices all day, every day. Just cheap ones.
Based on what? I would never buy an Apple laptop and no one I know has one either. The Windows "gaming laptop" I got a few years ago for game dev is perfectly adequate and has features missing from Macbooks:
- ethernet port
- hdmi port
- multiple usb A and C ports
- solid keyboard
Same for my work laptop, again Windows/x86 and no one I know with a work laptop is supplied a Mac either.
We live in different worlds. All engineers I know have Macs and the ones that don’t have Linux. The one guy on my team who uses windows is a constant problem as he has to find work arounds for every process we have/service we build.
Every company I've worked for provided a macbook to us, and all my coworkers use a macbook. When I have the option, I pick PC. My last company gave me a choice between mac or PC, and I picked the thinkpad. My current company gave me a macbook pro, but I opted to use my personal Windows machines instead.
I'm the guy who has to come up with a workaround, but it's never a problem for others. Usually I'm translating some bash command into powershell, which takes maybe 2 minutes. Everything else runs just fine, and I don't even need to use WSL. Windows is a perfectly viable development platform, if you give a shit about learning the differences between a unix-like environment and windows instead of just copping out and using WSL
Apple is doing what people hated Microsoft for.
It's amazing that a closed ecosystem is so welcomed by Apple fans. But I suppose man has always been tribal.
I work on a split team, Windows and macOS. We do straightforward Java work and most of the problems that we have are related to installing command-line software on Windows.
Installing Postgres, Redis, etc. on Windows is wildly complicated compared to on macOS or Linux.
If your dev environment is meant to be multiplatform, it's sounds a lot more like the other developers are checking in things that don't work on anything but macs.
Yep. I work in an entire office of engineers with only Macs (mostly ARM ones now) and I only have a Mac at home, besides a very old ThinkPad running Ubuntu. (Aside from FFXIV on MacOS, I've moved any gaming to PS5 and Switch.)
I haven't actively used Windows since 2008. It's such an obnoxious OS to use, and I have never seen a Windows laptop with quality in the same zip code as a Mac. There's always a terrible touch pad, keyboard flex, plasticky trash fit and finish, mediocre display or something that just ruins the whole thing.
I like the aluminum bodies of macs, but I hate the flat keyboards. In my view, no laptop brand has had a good keyboard since the Thinkpad T420.
In terms of build quality, apple laptops are pretty good, but I can't stand macOS and apple keeps fucking with their ports.
My Inspiron 16 has a good glass screen and a pretty solid aluminum body. It's got all the ports I want (HDMI, USB-A 3.0, SD card reader, USB-C, and a 3.5mm headphone jack). Personally, the macbook pro my company issued me is one of my least favorite laptops I've ever used. I also had compatibility or performance problems with x86 based software when I got my first M1 macbook, I don't know if they're improved anything since then
I just received a brand new Thinkpad from work. I don't even mind Windows but holy crap is that thing an absolute chore to use. I don't understand how this is still an issue while Apple has been putting out what amounts to the perfect laptop for like 10+ years now.
>I don't even mind Windows but holy crap is that thing an absolute chore to use.
What are your issues? I have a T490 that is a few years old and its great for my use. But I keep it docked in to a monitor and external mouse and keyboard 90% of the time.
> I haven't actively used Windows since 2008. It's such an obnoxious OS to use
You might want to modernize your perception of it, holding on to 15 year old views is not a very smart move in the tech industry.
Windows 10 and 11 are a joy to use, and to develop. I used a Mac for 15 years and switched to Windows to develop 5 years ago, and now macOS looks extremely antiquated and creaky for development.
Sure are a lot of extreme opinions on operating systems when they all seem pretty damned similar to me on the fundamentals.
Development work strikes me as maybe the least distinguishing kind of task to compare them on. Very few hard choices to make unless you're developing for Mac or iOS.
The operative word is "actively." I've certainly touched it since then and am just as unimpressed. Windows is a chore to use, and the best they've been able to manage to close the gap is shipping a glorified Linux virtual machine. I'll take Homebrew over that any day, and leave the VMs to Docker.
The windows UI itself is an unpolished joke that's a hodgepodge of things that haven't been touched since Windows XP and half-baked new things, with sad window management (ironic) that lacks the perfection of Exposé and Spaces. To say nothing about laptop battery life, plugging in and removing multiple monitors several times a day.
I would strongly consider not working somewhere if they didn't use Macs
MacBook Pros have HDMI ports and many USB-C ports. I also don't know any issue with MacBook keyboards except the 2016-2019 model years.
I work for a large financial services company and receive a MacBook Pro for my work.
My work laptop battery can handle all-day IntelliJ & web browsing without charging, I've never heard the fan and the laptop stays cool. It has a Geekbench multicore score of 13,649.
My personal laptop also lasts that long and stays cool, and doesn't even have a fan.
I would never buy an Apple laptop. I have one for work and I hate it. Linux and Windows are by far more productive for me, so all I need to do is keep getting better PC laptops. While Mac hardware does have a slight edge on cost/benefit at that price point, macOS is just too cumbersome for my needs.
EDIT: It's funny to see this downvoted. I'm literally speaking of my particular use case and needs! Are there people who believe Apples are better in all scenarios?
The whole "click once on the app for it to wake up, click again for it to know which window you wanted" makes using Mac OS highly unpleasant on a daily basis. Yes, I'm on Mac OS, and no, I don't like it.
As a daily Mac user for about 13 years now I have no idea what phenomenon you're talking about.
For any program that is open, even if it hasn't been in use for a while, I click it once, and it comes to the forefront immediately.
For programs that are not open, I click it once, and then if I wait for it to launch, it appears in the forefront. If I immediately click back over to my web browser and begin using it before the program launches, it does not appear in the forefront... because I interacted with another program after starting the launch.
They might be referring to how clicks don't register with an app until it has focus (the first click being to focus it).
On Windows you can, say, click once to pause on a video playing in a browser window that doesn't have focus but is visible. On macOS, it's two clicks, because you have to focus the app first.
I don't care for the behavior but it's so minor to me that it carries essentially no weight.
Except for how there's no stable sort order for windows, even if you turn off the setting that's supposed to not rearrange it all the time. Mission control was probably one of the things I liked least about the Mac when I used one for work... To the point that I ended up using hammerspoon to create shortcuts to switch between my applications directly rather than deal with it.
Just chiming in to agree, I don't think we have a single mac in our entire company (100's of people). It's all just windows/x86 like every other business I've worked at.
MBP once again have HDMI ports and good keyboards. I wouldn't mind a single USB-A port but I don't particularly miss it, and 3 USB-Cs is plenty for my uses.
I haven't needed an ethernet port on a laptop since the mid 2000s troubleshooting why my newly installed stack of Cisco switches weren't working, and that sort of use cases is rare enough that having a dongle seems fine.
Conversely, about 80% of the people I know use Apple laptops for work.
I don't see ethernet ports making a comeback on thin laptops anytime soon though. They are handy for LAN parties, so bulky gaming laptops will keep shipping with them, but for everyone else it makes more sense to leave that functionality to a dock.
That's what's so great about capitalism: I'm not interested in any of those features on a laptop, so Apple is great for me.* You do, and several other companies compete for your business.
On a desktop (which these days isn't a tower) I do want some of those features, and I get them.
* except kbd, and I find the apple kbds just fine -- I even survived a couple of rounds of the infamous "butterfly" kbds. But I know some people were unhappy and eventually Apple got their act together.
> Based on what? I would never buy an Apple laptop and no one I know has one either
Yes because no one that you know buys an Apple laptop that must mean that Apple isn’t selling any…
> Same for my work laptop, again Windows/x86 and no one I know with a work laptop is supplied a Mac either.
I find the lack of self awareness…amusing.
Because no one you know uses a Mac laptop, that must mean no one uses one.
Well my anecdote from working at the second largest employer in the US that the vast majority of technical people prefer Macs even though they can choose Macs or Windows.
"Apple isn't selling any laptops" wasn't what was said. The original claim was x86 has "thrown in the white flag" and that Apple dominates the laptop market, which is a pretty ridiculous claim since x86 is still the vast majority of laptop sales and Windows is still the dominant laptop OS.
> Apple isn't selling any laptops" wasn't what was said
The parent poster said
> would never buy an Apple laptop and no one I know has one either
What relevance then was there in the statement that the original poster made?
> Apple dominates the laptop market, which is a pretty ridiculous claim since x86 is still the vast majority of laptop sales and Windows is still the dominant laptop OS.
Nor did I argue otherwise. I merely called out the silliness of the statement that because the parent poster “doesn’t know anyone who owns one” or that because every developer he knows uses a Windows laptop, that his anecdotal experience has any relevance.
I don't personally see MacBooks as a viable platform either right now, but I would say that this looks like a steady decline for windows x86 laptops until Chrome laptops take over or an arm-based windows replacement takes hold. "Hey this isn't a surrender, it's a war of attrition for the next five years!!!"
Given that 15-20 years ago almost all laptops were x86/Windows, "decline" is pretty much the only direction the platform could go in.
I don't expect either x86 or Windows to go away any time soon – in general I think x86 has been somewhat unfairly maligned, and for most applications (including laptops) it works pretty well and is even the best available choice. I would prefer to say "diversification" or "the existence of actual competition" rather than "decline", as that doesn't imply it's going away.
They're not arguing that Apple doesn't sell laptops, they're refuting that "Windows, Intel, AMD and Nvidia have [...] given the laptop market to Apple". Unless one thinks the laptop market only exists in the US, this idea simply can't match reality, not yet anyway.
Not if the anecdote contradicts an equally unsubstantiated generalisation, honestly. If you're going to complain about the quality of the discussion, do it with both sides, not just the argument you side against.
I've been hoarding apple devices too. I have a 12 inch macbook, recently brought it up to Ventura. But the blasted thing won't hold a charge. The battery is fine over 90% health but something is causing power drain while it sleeps even when I try to hibernate it.
It's impossible to find a use case for the thing. I might have to sell it.
The majority of 'the market' may go elsewhere, but for a gazillion reasons, x86 will not be disappearing for quite a while. At this point it would honestly surprise me if we didn't at least have high quality emulation available until the end of the human race as we know it.
Sure, we've probably lost most of the software ever written on it, but a whole lot of interesting artifacts from a key transition point for our species still remain locked up in this architecture.