text stringlengths 11 441 |
|---|
[3408.04 --> 3410.88] So they did say no working transistors. |
[3412.30 --> 3413.70] So that could... |
[3414.36 --> 3414.64] No. |
[3414.82 --> 3415.32] You know what? |
[3415.34 --> 3415.60] No. |
[3415.74 --> 3416.56] There's no... |
[3416.56 --> 3418.40] I don't really think there's any way around this. |
[3419.58 --> 3424.40] As far as I can tell, these are... |
[3424.40 --> 3427.58] I don't know what they are. |
[3428.30 --> 3428.86] I just... |
[3428.86 --> 3433.14] What I don't understand is why they would come out and say something like that when they could have just said, |
[3433.52 --> 3436.00] Yeah, they're failed ones. |
[3438.20 --> 3438.60] Or they're... |
[3438.60 --> 3440.24] Well, you don't want the F word in your product launch. |
[3440.24 --> 3445.92] Yeah, but everyone talks about the process of binning. |
[3445.92 --> 3453.20] I think it's fairly well understood within the kind of enthusiast community that... |
[3453.20 --> 3454.42] Well, Intel already slammed... |
[3454.42 --> 3455.54] This happens. |
[3455.74 --> 3458.52] Intel already got to be smarmy by saying, |
[3458.94 --> 3459.98] Freadripper's glued together. |
[3460.32 --> 3461.36] So they could have said, |
[3461.70 --> 3463.58] It's just a bunch of failed chips glued together. |
[3464.02 --> 3465.78] Yeah, but Intel does the same thing. |
[3465.78 --> 3466.78] I mean, this is not... |
[3466.78 --> 3467.00] A little stab. |
[3467.36 --> 3471.12] Yeah, but it would come across really insincere. |
[3471.26 --> 3472.24] Completely meaningless. |
[3472.36 --> 3473.42] Because everybody does it. |
[3474.08 --> 3475.14] So are you confused? |
[3475.24 --> 3476.82] Or are you actually just kind of upset? |
[3476.92 --> 3477.68] Okay, so we've got... |
[3477.68 --> 3478.36] I'm just confused. |
[3478.46 --> 3479.24] Did they break your Chinese trust? |
[3479.24 --> 3481.06] Because here, we've got people saying... |
[3481.06 --> 3481.86] Warboy X says, |
[3482.04 --> 3483.04] If the cores were enabled, |
[3483.20 --> 3485.60] the CPU would have 6 or 8 channel memory also. |
[3486.10 --> 3486.80] No, it wouldn't. |
[3486.94 --> 3490.42] Because the socket and the motherboards wouldn't be wired up for it. |
[3491.12 --> 3494.20] Now, it's possible that AMD was... |
[3494.20 --> 3495.90] That what they were hoping to achieve |
[3495.90 --> 3498.90] was that nobody would run out and try to unlock cores. |
[3499.76 --> 3502.66] But then they couldn't possibly have thought |
[3502.66 --> 3505.06] that no one at any point |
[3505.06 --> 3506.92] was going to rip apart one of the dies |
[3506.92 --> 3508.42] once a Threadripper failed. |
[3508.42 --> 3510.42] They couldn't possibly have thought that. |
[3510.58 --> 3512.76] Because it is really easy to tell. |
[3513.16 --> 3513.98] Like, you can see. |
[3514.22 --> 3515.76] It's visible to the naked eye. |
[3516.24 --> 3516.78] If you... |
[3516.78 --> 3520.26] Okay, if you look at the video of the 7700K that we... |
[3520.26 --> 3521.40] Or 6700K, whatever. |
[3521.54 --> 3524.50] The chip that fell out of the vice when Burkle dropped it. |
[3525.00 --> 3525.78] It broke apart. |
[3526.08 --> 3527.42] You can clearly see... |
[3528.78 --> 3532.36] Like, the cache and the cores. |
[3532.54 --> 3534.08] It's visible to the naked eye |
[3534.08 --> 3536.18] that that's a CPU die |
[3536.18 --> 3538.40] once the top breaks off. |
[3538.42 --> 3539.30] You're looking at me, |
[3539.40 --> 3540.80] but all I can think of right now |
[3540.80 --> 3542.32] is that my stomach is a cauldron. |
[3542.92 --> 3545.50] They couldn't have possibly expected people |
[3545.50 --> 3547.30] to not look at it at some point. |
[3548.42 --> 3550.86] So, I don't know. |
[3551.24 --> 3554.76] This just seems super dumb and... |
[3555.34 --> 3557.18] It's up to us to get answers. |
[3557.68 --> 3559.54] Yeah, I mean, maybe they just didn't want... |
[3559.54 --> 3560.92] This is a good theory from... |
[3560.92 --> 3562.04] Also from Warboy X. |
[3562.54 --> 3565.40] Maybe they just didn't want people, you know, |
[3565.86 --> 3569.76] running Threadrippers and Epic Sockets or vice versa. |
[3569.92 --> 3573.24] Maybe they wanted to separate their consumer |
[3573.24 --> 3575.52] slash prosumer from their server. |
[3575.92 --> 3576.62] I don't know. |
[3576.96 --> 3577.46] I don't know. |
[3577.58 --> 3579.14] But I guess I'm over it. |
[3579.20 --> 3580.54] I just don't understand |
[3580.54 --> 3582.46] why they wouldn't be straightforward about this. |
[3582.46 --> 3584.92] Because they have nothing to gain |
[3584.92 --> 3587.82] and their credibility to lose. |
[3588.20 --> 3588.60] There. |
[3589.60 --> 3591.22] And there's a lot of times |
[3591.22 --> 3593.58] when you run into stuff like this in the industry |
[3593.58 --> 3594.76] where it just kind of goes, |
[3595.12 --> 3596.82] why would you deceive us about this? |
[3597.22 --> 3599.02] No one could possibly care |
[3599.02 --> 3600.44] that you were doing it this way. |
[3600.44 --> 3601.90] Like, the same way |
[3601.90 --> 3603.80] that everyone has made CPUs |
[3603.80 --> 3605.30] since basically the dawn of time. |
[3605.58 --> 3607.08] And by that I mean the last few decades |
[3607.08 --> 3608.76] because that's as long as we've had CPUs. |
[3610.02 --> 3610.98] Why not just say, |
[3611.06 --> 3611.86] yeah, we're doing it that way, |
[3611.92 --> 3612.86] same as usual. |
[3613.44 --> 3614.64] Unless you count the brain. |
[3615.38 --> 3615.64] What? |
[3617.28 --> 3618.88] Bluetooth has been hacked again. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.