Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tales of the M1 GPU

asahilinux.org

Post reply on HN
Print view View original

381–390 of 390 posts

Re: Tales of the M1 GPU

#381

Post by olddustytrail »

ethbr0 wrote: post #301
dwringer wrote: post #247

Earlier quoted context omitted.

I was shocked to read this comment because I interpreted your original comment as meaning a Philip K Dick novel would be optimistic compared to the cyberpunk dystopia in which we find ourselves now. lol Anyway it's pretty fair to confuse the two I think, there can't be any way Johnny Mnemonic wasn't influenced by Blade Runner (I'm guessing it's true of both the movies and of the books). Very similar themes and protag…

Johnny Mnemonic was dead tree published in 1981. (I have the issue of OMNI) Blade Runner, the movie, was released in 1982. And PKD's DADoES was published in 1968. Honestly, IMHO, Blade Runner in movie form shares more DNA with Alien than proto-cyberpunk. They're both character studies rather than world-building exercises, albeit with massive credit to Ridley Scott and the design team that their "background" world is…

Well, Blade Runner and Alien are set in the same universe.

Re: Tales of the M1 GPU

#382

Post by irae »

embedded3 wrote: post #377
dagmx wrote: post #371

Earlier quoted context omitted.

I have such a love hate relationship with Swift. It genuinely has some great ergonomics and I see it as a sister language to rust. I just wish it was more cross platform (I know it technically works on Linux and windows…but it’s not a great experience) and that it didn’t have so much churn (though they’ve stopped futzing with the core components as much with Swift 4+). I also wish it was faster. I did an Advent of Co…

>The rust code was running circles around their Swift ones even when we tried to keep implementations the same. I've done Advent of Code a few years -- even Javascript implementations, if using a good (optimal) algorithm, are highly performant, so I'm suspicious of the claim. In most AoC problems, if your code is observably different between languages, it's the fault of the algorithm, regardless of language. But perh…

That is not the first time I want to understand a bit better the performance difference today between the approaches of Rust, without a garbage collector, ARC on Swift with the reference counting and other garbage collected languages, such as Javascript.

I know Javascript have an unfair advantage here, since the competition between V8 and the other javascript cores is huge over the years and garbage collection on JS is not often a problem. At least I see more people struggling with the JVM GC with its spikes in resource usage.

I've also heard that the erlang VM (be it written in elixir or erlang itself) implements GC on a different level, not to the global process, but on a more granular way.

Is there a good resource that compare the current state of performance between those languages or approaches?

Re: Tales of the M1 GPU

#383

Post by ge96 »

throwntoday wrote: post #333
ge96 wrote: post #181

Earlier quoted context omitted.

Yeah... I was hoping to passively watch it, maybe gleam something but yeah. The other thing too, watching other people code is kind of not fun like George or Rene. More fun to see some screeching video with no actual info just the end result of a robot pissing in a cup. Also goes to show how much work goes into writing code/having some end result. Maybe it will get more exposure since there is a growing trend for vtu…

You don't like watching George? His coding streams always get me hyped enough to work on my own projects.

The stuff he works on and OP above is beyond my current level/field. I wouldn't really watch it to follow along rather just for the company/background noise. Maybe learning something in the process. Currently I don't watch anyone regularly for code.

I get it though, I used to watch Social Network or Silicon Valley to hype myself up to pursue something. Now my problem is too many projects ha.

Re: Tales of the M1 GPU

#384

Post by ge96 »

ge96 wrote: post #383
throwntoday wrote: post #333

Earlier quoted context omitted.

You don't like watching George? His coding streams always get me hyped enough to work on my own projects.

The stuff he works on and OP above is beyond my current level/field. I wouldn't really watch it to follow along rather just for the company/background noise. Maybe learning something in the process. Currently I don't watch anyone regularly for code. I get it though, I used to watch Social Network or Silicon Valley to hype myself up to pursue something. Now my problem is too many projects ha.

I still am trying to figure out my own business though. I'm getting tired of writing code/constant upkeep. Soon there will be a library just to make a button with its own context manager.

Re: Tales of the M1 GPU

#385

Post by rasz »

ddingus wrote: post #369
rasz wrote: post #315

Earlier quoted context omitted.

No, VIC-20/1540 had hardware problem. C64 shipped with fixed chips. C64 cant even work with 1540. Commodore crippled it because of incompetence.

Too late for me to edit, but yes I did confuse the source of the bug. Please clarify the C64 drive scenario source of slowness. Was it VIC-20 backward compatibility, or? In any case, I maintain the engineering wasn't at fault, having a CPU etc. Fastloaders showed it to be just poor software, and that's a point I did not make clear enough.

Commodore wanted new C64 drives to be backward compatible with VIC-20 and vice versa. They failed the second goal, and C64 sold ~10x the number of units VIC-20 did making whole exercise pointless.

All to sell more outdated garbage chips made by MOS instead of using proper FDC controller on CPU bus with cheap standard floppy.

Re: Tales of the M1 GPU

#386

Post by ddingus »

rasz wrote: post #385
ddingus wrote: post #369

Earlier quoted context omitted.

Too late for me to edit, but yes I did confuse the source of the bug. Please clarify the C64 drive scenario source of slowness. Was it VIC-20 backward compatibility, or? In any case, I maintain the engineering wasn't at fault, having a CPU etc. Fastloaders showed it to be just poor software, and that's a point I did not make clear enough.

Commodore wanted new C64 drives to be backward compatible with VIC-20 and vice versa. They failed the second goal, and C64 sold ~10x the number of units VIC-20 did making whole exercise pointless. All to sell more outdated garbage chips made by MOS instead of using proper FDC controller on CPU bus with cheap standard floppy.

Got it. Ty :)

Re: Tales of the M1 GPU

#387

Post by [deleted] »

catiopatio wrote: post #352
leidenfrost wrote: post #351

Earlier quoted context omitted.

Why is it that whenever gender and identity is mentioned in a technical community suddenly people start talking about "ham-fisted" and forced inclusions? There's nothing forced about people getting into programming and becoming relevant for it, that just by chance it turns out they are not cis+heterosexual. Nobody in the Asahi crew was "a ham fisted attempt to increase diversity". The only forced thing here is the "f…

> Why is it that whenever gender and identity is mentioned in a technical community suddenly people start talking about "ham-fisted" and forced inclusions? You answered your own question; it’s a technical community. Centering political activism is counterproductive to the fundamental telos of being a technical community. Existing members, unsurprisingly, push back against colonization of their community by those more…

[deleted]

Re: Tales of the M1 GPU

#388

Post by jcrash »

sneak wrote: post #329
calrizien wrote: post #242

Great work! Seems like Apple could make this a whole lot easier by giving even the slightest support...

It is irksome to me given how much Linux is used inside Apple (board bringup, debugging, etc). You benefit from these gifts, Apple, give back a teensy bit in return. Everybody wins.

https://opensource.apple.com/

Re: Tales of the M1 GPU

#389

Post by treesknees »

ddingus wrote: post #379
treesknees wrote: post #373

Earlier quoted context omitted.

It can in moderation, but there's a phenomenon that people (often women) in communications overuse exclamation points, trying to come across as friendly and not assertive [1][2]. It's something I've noticed in my professional career, and not me trying to make a stereotype. You start to tip that usage too far, like 149 of them in a technical document, and it detracts from your content. >A bunch of shader cores, which…

These meta discussions can be illuminating. The intent I got was the idea of all the GPU instruction sets being different is notable, and perhaps unexpected and at the least challenging. The latter being an exclamation in the context of reverse engineering makes some degree of sense to communicate the fundamental difficulty inherent in this effort. Now, we could go back and forth a few more times, invite friends and…

I'm not sure what your points are other than "people are different, get used to it." Surely there is room for different writing styles and perspectives in the world. That is really not what I was getting at. If that's what you took away from my comment, I would invite you to re-evaluate it.

>Finally, you mention women overusing exclamation points. Maybe they are just being women?

I did mention it, but I did not come up with this on my own. You can read the study I linked to. Calling it "women being women" sounds a bit like the old "boys will be boys" attitude, as if your gender defines your actions or is an excuse.

Instead I'd rather look at why a large group of people feel like they need to express themselves as upbeat and happy. If you read the study I linked to, it talks about this with explanation. I invite you to read some more.

Re: Tales of the M1 GPU

#390

Post by ddingus »

treesknees wrote: post #389
ddingus wrote: post #379

Earlier quoted context omitted.

These meta discussions can be illuminating. The intent I got was the idea of all the GPU instruction sets being different is notable, and perhaps unexpected and at the least challenging. The latter being an exclamation in the context of reverse engineering makes some degree of sense to communicate the fundamental difficulty inherent in this effort. Now, we could go back and forth a few more times, invite friends and…

I'm not sure what your points are other than "people are different, get used to it." Surely there is room for different writing styles and perspectives in the world. That is really not what I was getting at. If that's what you took away from my comment, I would invite you to re-evaluate it. >Finally, you mention women overusing exclamation points. Maybe they are just being women? I did mention it, but I did not come…

It's a bit more subtle than that. Understanding others is important. Blanket "there is too much x" or similar kinds of observations leave out the actual person writing and the context.

I read the stuff, and have read other stuff related to this discussion. Have had some conversations with others too. Those conversations are where "Maybe they are just being women" comes from.

Suppose my response was rooted in the exclamation not always being up beat and happy. That's context related.

Post reply on HN