Earlier quoted context omitted.
You might actually expand "Apple likes open standards when it is weak" to "companies likes open standards when they are weak." Generally speaking you get standards consortiums when there is a clear winner that is mopping up the space. Here's an example that's happening right now: Nvidia-NvLink-Infiniband. Nvidia owns the highspeed interconnect inside the chassis (HGX), the NICs (Mellanox), the inter-host interconnect…
> they are also routinely about the losers joining together to compete. That is the greatness of it. It reminds me of democracy: The less powerful join together to give everyone an equal vote, rather than having one vote per dollar.
The first conformant M1 GPU driver
671–680 of 699 posts
Re: The first conformant M1 GPU driver
#672Earlier quoted context omitted.
FWIW, Apple does release _some_ patches for previous iOS versions, but there absolutely are mitigations that are not back ported to older versions. If you care deeply about security, I’d recommend having a phone that actually is using up-to-date OS.
I do care, that's why I'm thinking of getting a new one. But still, ios 16, the first which didn't support the iphone 7, came out in September 2022. The iphone 7 came out in September 2016. I'm not aware of any Android phone with such a long support cycle.
Re: The first conformant M1 GPU driver
#673Earlier quoted context omitted.
> Publishing someone's real name online isn't doxing when his real name is already publically available online. You're being deliberately obtuse. It's the connecting (obviously) that's the issue. It's like saying, "publishing someone's address online isn't doxing when their address is already publicly available online." Yeah I only care if you say it's my address. > I don't "feel strongly" about it at all. > also con…
>I usually try to be cooler on HN than this, but this is super toxic. I am responding in kind, based on the way you are talking to me. If you were polite, there would be no issue. Instead, you make nasty psychologising comments and then pretend that you're a victim when someone responds in kind. >You're being deliberately obtuse. It's the connecting (obviously) that's the issue. It's like saying, "publishing someone'…
I've yet to insult or condescend to you, whereas you've condescended to me ("Grow up"). I'm not "psychologising" you, I've said that you're pushing an issue that affects you not at all but is harmful to others, and that you should probably figure out why you're doing that (or, why you refuse to accept you're doing that). Maybe me being polite while pointing it out makes it seem like I'm "psychologising" you, so let me rephrase: you clearly can't keep yourself from harassing people who live life in a totally harmless way, that's real weird, and you might not know how weird it is.
> and then pretend that you're a victim when someone responds in kind
Again I've not insulted or condescended to you so you're not actually responding in kind, but that aside I don't at all feel like the victim here.
> Publishing someone's address online when it's already publicly known what their address is isn't doxing!
This analogy doesn't fit, because--again--the connection isn't publicly known. How do I know it's not publicly known? Because I didn't "know" and I looked. I went to marcan's various social media sites and his website, to Asahi Lina's various social media sites and her website, and came up bupkis. So to be honest, I can't corroborate your claim based on what I've seen, and it's not for lack of looking. Could I probably find something? Sure. Do I care to? Not even a little.
Basically your argument boils down to: "someone already doxxed this person, so it doesn't matter if someone does it again". I think any reasonable person would think that's wrong.
Re: The first conformant M1 GPU driver
#674I really wish nerds would stop supporting Apple hardware and software. It is so closed and everything is a giant pain. Its one thing for the average non-techie that does not want to do anything advanced and just wants to swallow the blue pill. But for an actual techie to support a system that is the antithesis of general purpose compute...Can you even be considered a true techie anymore? I just don't get it.
Re: The first conformant M1 GPU driver
#675Earlier quoted context omitted.
> A lot of dev companies force their employees to use bacbooks in part as a result of their locked down practices and the only way to actually compile and test for "everything", because of how much easier it is to cross compile to other platforms and markets. A lot of devs are also choosing them because they are insanely good machines. Simply because ARM64 is a good architecture and there is pretty much no competitio…
My personal experience: - MacOS user experience: Terrible. It feels like Linux did 10 years ago. Bugs and inconsistencies everywhere. But hey, they are competing with W11 so, no need to improve it either. Forced updates and restarts. And, did I mention bugs and inconsistencies everywhere? - M2 Computational performance: It feels like my laptop 10 years ago. - M2 Batterly life performance: It is absolutely brilliant,…
Re: The first conformant M1 GPU driver
#676Earlier quoted context omitted.
Granted, I'm just massively struggling with the idea of excluding a whole radically diverse community (with some of the most civilized and self-moderating discourse on the internet) in the name of inclusiveness. To me, it's as ironic as it gets. On that end, I can't find any fault on HN's end enabling their 99.99% of their interested readers who didn't do any wrong to be included in the discourse around these ideas,…
> the idea of excluding a whole radically diverse community (with some of the most civilized and self-moderating discourse on the internet) in the name of inclusiveness. To me, it's as ironic as it gets. Not really more ironic than almost every non-trivial societal discussion, à la "if you want peace prepare for war". Anything non-trivial is multifaceted, and anybody who has an absolute opinion is probably missing mo…
(OK, there’s also the argument that HN will engage with people whose opinions the usual Asahi folks consider reprehensible—even if not necessarily often—and should thereby be treated as equally reprehensible unless they kick them out[2]. But, I don’t know. I’m a couple decades too young to have seen organized ostracism at the meetings of the Komsomol, but still, the only reaction I have when these kinds of social-isolation penalties are proposed is base animalistic terror. This includes people a decade younger in my own social circles proposing it, which is not even rare.)
[1] https://slatestarcodex.com/2016/04/04/the-ideology-is-not-th...
[2] “Parable of the Nazi bar“, etc.
Re: The first conformant M1 GPU driver
#677Earlier quoted context omitted.
It's not going to work because they are too late. HPC cluster builds are complex enough due to the presence of multiple networks (2x moderate-scale infiniband chassis and 2x ethernet chassis as a minimum) without introducing unknown vendors. At that point, if you're doing IB, why not just go Mellanox since you will almost certainly buy 200GE Connectix NICs and not the 100G NICs from these guys. UEC will - like most s…
Idk, I personally did it for a HPC cluster two years ago. 2x100GbE + OmniPath was a sensible way to reduce cost, especially as the cluster was very light on GPU power and mostly focussed on CPU-bound jobs. Last I heard everyone there is still very happy with what we built.
Modern HPC mostly means GPU compute and tons of data shuffling, but point taken. CPU bound jobs aren't going to stress the i/o, so you probably could have done 100GE for less. I'm curious what you did for storage but I'm guessing with CPU-bound that is again much less of an issue.
Re: The first conformant M1 GPU driver
#678Earlier quoted context omitted.
Swiping along the bottom of the screen goes to the last used app.
It works but I prefer Android's intent based transition system.
Re: The first conformant M1 GPU driver
#679Earlier quoted context omitted.
> Apple was part of the patent pool for FireWire Apple is listed first as the designer, then second the IEEE1394 working group. Indeed, there's some indication that Apple's development started in the 80's and it wasn't until later it was presented as a standard.[1] Funnily enough, they wanted it to replace SCSI, another technology you noted as a counter to Apple not liking standards they don't control. > is also part…
What exactly is your complaint? That Apple only uses standards that it contributes to? What other computer maker was going to move technology forward? Should Apple have used the PS/2 connector instead? > That said, they make moves away from it where they could for protocols they had some level of control and or steering of (FireWire, Thunderbolt, etc). What were they going to use instead of FireWire? USB 1 was painfu…
My complaint? I'm just calling into question your counterpoint exampkes supplied when someone stated that Apple only likes standards they control. Whether it's warranted or they have good reason to in some cases is somewhat besides the point, they have a long history of developing their own standards, sonetimes because they are addressing a problem that isn't solved by another technology, and sometimes just because they would rather have something they control whether the market segmentation and user confusion it causes is best for the customer or not.
Re: The first conformant M1 GPU driver
#680I wonder if support for OpenGL, Vulkan, etc will improve now that Apple is partnering with nVidia, Adobe, Autodesk, Microsoft, etc around the OpenUSD rendering/animation/CAD/3D-scene format? Considering the whole schtick of OpenUSD is "one file format that renders consistently everywhere" (paraphrasing), I would be surprised if Apple doesn't use it as a means to cement more 3D software vendors into macOS land. It's r…
Apple's strategy for cross-platform GPU is WebGPU, which they are actively involved in. OpenGL has been obsolete for a while and Apple has no interest in supporting Vulkan (for multiple reasons). The core philosophy of Vulkan — which is designed as a least common denominator abstraction to facilitate fast driver development, with no regards to end developer convenience — is at odds with what Apple wanted (a compact,…
I can tell you have strong opinions on Vulkan. I don't disagree with your general view that it's hard to work with development wise as it's very tied down to driver and hardware implementation specifics.
What I can say though, is that I've met several pipeline rendering engineers (think folks who invent render engines for film and write low level game engine code) who seem to love Vulkan. They appreciate being able to really get down to the bare metal of the drivers and eek out the performance and conformity they need for the rest of the game or render engine.
A lot of the frustration with OpenGL/DirectX from these specialists was their inability to "get in there" and force the GPU to do what they really wanted. Vulkan apparently gives them a lot more control. As a result, they are able to accomplish things that were previously impossible.
All that being said, I think WebGPU will be far more popular for 99% of developers. Only a very few folks like getting down into the nitty-gritty of libraries like Vulkan. At the same time, there is huge money to be made knowing how to make a game eek out another 10 FPS or properly render a complex scene for a film group like Pixar who wants to save days on a scene render.