text
stringlengths
14
502
[3493.10 --> 3493.30] Anyway.
[3493.92 --> 3495.72] Um, there was runes and stuff.
[3496.12 --> 3496.48] Ruins.
[3496.66 --> 3496.98] Ruins.
[3497.04 --> 3497.18] Yeah.
[3497.22 --> 3498.08] Not those kinds of ruins.
[3498.32 --> 3500.04] I was like, this is getting pretty crazy.
[3500.04 --> 3510.78] Um, and he kind of stands up there and declares AMD's graphics business to be a software business.
[3511.56 --> 3515.10] And remember this was, was he wrong?
[3515.56 --> 3519.10] How programmable have GPUs become in that time?
[3519.28 --> 3519.40] Yeah.
[3520.98 --> 3529.04] And that's effectively what that's, that's one piece of this, of the puzzle of the direction
[3529.04 --> 3536.32] that we are moving overall and Intel missing a node and your applications getting faster
[3536.32 --> 3542.84] and your graphics in your games getting better anyway is sort of an indication of what is
[3542.84 --> 3543.30] to come.
[3543.92 --> 3551.74] Software tomfoolery, like with VR, the way that they will inject extra frames to accommodate
[3551.74 --> 3556.02] that graphics cards haven't gotten a lot faster or more, certainly not more affordable.
[3556.98 --> 3560.50] Software tomfoolery may just be the way it's going to have to be.
[3560.78 --> 3561.16] Go ahead.
[3561.18 --> 3564.94] I think it might be the way it's going to have to be for a little while and then we will
[3564.94 --> 3566.64] change how we're doing things.
[3567.28 --> 3570.50] Like, I mean, risk five could come along and really change the game.
[3570.64 --> 3570.86] Yeah.
[3570.94 --> 3574.74] Like, like there, there could be completely different architecture styles.
[3575.38 --> 3576.90] But that's going to take time.
[3577.02 --> 3577.36] Yes.
[3577.36 --> 3577.80] Okay.
[3577.80 --> 3583.74] I will agree with your stance probably for like a little while, but I think I could see
[3583.74 --> 3584.48] it doing that.
[3584.60 --> 3584.94] Five years?
[3584.94 --> 3585.24] For sure.
[3585.52 --> 3586.22] Yeah, I could see that.
[3587.04 --> 3592.06] But I think eventually we're going to change how we do things and then we'll see advancement
[3592.06 --> 3596.78] again in, in, in hard way or whatever it is at that time.
[3596.86 --> 3598.08] Because like the challenge here.
[3598.08 --> 3598.28] Organics even.
[3598.92 --> 3599.68] Is that if we could just.
[3599.68 --> 3600.74] Organic computing is a really cool.
[3600.74 --> 3605.28] If we could just keep pushing clock speed higher, it would be easier to compensate for
[3605.28 --> 3609.74] some of the, some of the trickery that has already made its way into the hardware products.
[3609.80 --> 3611.60] I mean, you look at what happened with Spectre and Meltdown.
[3611.92 --> 3612.14] Yeah.
[3612.46 --> 3618.28] Anything that requires a branch prediction, for example, which dramatically accelerates the
[3618.28 --> 3618.56] CPU.
[3618.70 --> 3623.46] I mean, if you don't have good branch prediction in your CPU, your performance basically sucks
[3623.46 --> 3624.32] these days.
[3624.32 --> 3629.80] And now all of a sudden there's these exploits that are making it so that it's becoming more
[3629.80 --> 3631.22] challenging to implement these features.
[3631.36 --> 3635.72] I mean, SMT, there was a, there was a group that came out and basically said hyper threading
[3635.72 --> 3636.84] is insecure.
[3637.20 --> 3639.10] We just like shouldn't use it anymore.
[3639.30 --> 3640.44] Meanwhile, poor AMD.
[3640.88 --> 3643.38] Oh man, we finally got it.
[3644.52 --> 3646.12] We just added this.
[3650.62 --> 3651.10] So.
[3651.10 --> 3655.48] It's like, it's like everyone tells you about this party and you show up and you show up
[3655.48 --> 3656.38] and everyone's leaving.
[3656.56 --> 3657.22] It's like, oh.
[3658.16 --> 3660.60] So thoughts on Intel missing the 10 nanometer node.
[3661.24 --> 3665.28] I don't think that Intel, I don't think people are going to stop needing computing devices.
[3665.28 --> 3669.86] And I think Intel is going to continue to be a player in that space, whether it's through
[3669.86 --> 3673.90] innovating their own things or acquiring others or just marketing the heck out of themselves
[3673.90 --> 3674.30] again.
[3674.30 --> 3682.92] But the industry as a whole has gotten less exciting to me.
[3683.04 --> 3683.26] Oh yeah.
[3683.26 --> 3684.14] I'm not going to hide it.
[3684.26 --> 3688.94] And I think that Intel is a symptom as opposed to the problem.
[3689.58 --> 3691.16] I hope that answer is helpful.
[3691.16 --> 3696.38] I can't read your username, but you said Fortnite is for children.
[3697.72 --> 3698.08] Warboy.
[3698.58 --> 3699.44] Please make a video.
[3699.56 --> 3703.66] We saw this PC case in half and put it back together with the power of flex tape.
[3704.46 --> 3704.86] No.
[3706.28 --> 3706.68] Hetriu.
[3706.82 --> 3707.18] Hi.
[3707.54 --> 3707.90] Dax.
[3708.40 --> 3708.80] Hi.
[3709.76 --> 3710.16] Johnny.
[3710.88 --> 3711.28] Hi.
[3711.68 --> 3711.98] Wow.
[3712.06 --> 3712.60] Genzy boy.
[3713.38 --> 3713.96] I need a new phone.
[3714.02 --> 3714.78] Is the Vivo Next worth it?
[3714.80 --> 3716.08] I wouldn't go Vivo Next personally.
[3716.18 --> 3717.44] I would go with something with a better camera.
[3717.88 --> 3719.78] Mikel says, ordered your coffee.
[3720.16 --> 3721.32] Should be here in a few days.
[3721.86 --> 3725.96] You're going to be trying it the same time I am because I actually haven't tried it yet.
[3726.12 --> 3726.42] Really?
[3726.52 --> 3729.30] Well, I don't really drink coffee, as you know.
[3729.42 --> 3729.68] Yeah.
[3729.98 --> 3734.64] And I wasn't actually in office when they were doing all the testing of the different blends
[3734.64 --> 3736.34] that they concocted for us and stuff.
[3736.68 --> 3740.32] But we had just about a dozen people here try it and like it.
[3740.64 --> 3740.78] Cool.
[3741.30 --> 3742.58] What is the blend?
[3743.34 --> 3743.84] Do we know?
[3744.40 --> 3744.76] Can you say?
[3744.78 --> 3745.64] Well, I haven't tried it.
[3745.70 --> 3746.12] Oh, okay.