161–170 of 172 posts
Earlier quoted context omitted.
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.
Any closed ecosystem is annoying but I'm not going to complain very hard while their desktop market share is below 20-25%.
Earlier quoted context omitted.
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.
Hadn't heard of qemu (in this context), I'll take a look, thank you!
Earlier quoted context omitted.
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…
> 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 spe…
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.
Why do these kinds of articles essentially refuse to admit RISC-V exists?
> 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-performanc…
Veyron releases later this year. Ascalon next year.
It's going to get exciting.
Earlier quoted context omitted.
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.
1. Build a pipeline with macOS in mind (because "All engineers I know have Macs") 2. Complain when the macOS-oriented process doesn't work for everyone.
Earlier quoted context omitted.
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.
Tried WSL?
Earlier quoted context omitted.
>chips like the 6502 have still been in active use (almost 50 years now) Also 8051 cores can still be found in modern products
8051s are just now getting phased out as control cores of IP blocks, which is pretty wild. The 32-bit ARM and RISC-V cores are small enough and easier to program.
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
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.
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 qua…
>chips like the 6502 have still been in active use (almost 50 years now) Also 8051 cores can still be found in modern products
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).