eis

26 ms·

241.
by eis 4y ago
Yes. So either way, Kuo cannot deduce that M2 Pro wont be on N3. If the revenue is realized later or if the numbers are too low to justify calling it a substantial contrubution to TSMC revenue... same result. Kuo's argument does not se
242.
by eis 4y ago
I guess that's where the misunderstanding comes from. I was not talking about CPU cores alone. Only M1, M2 as a whole. But I still am not sure if I can believe that the M2 CPU improved performance while at the same time cutting power.
243.
by eis 4y ago
Are you suggesting they might have produced millions of A16 chips on N3 during risk production phase and launched it before TSMC even reaches HVM? Highly unlikely. Risk production is a phase where they still make changes and fix issues. It&
244.
by eis 4y ago
The M1 Air launched at a price of $999. The increase to $1199 happened with the launch of the M2 Air. > With its sleek wedge-shaped design, stunning Retina display, Magic Keyboard, and astonishing level of performance thanks to M1, t
245.
by eis 4y ago
If the increase in power consumption comes from the additional GPU core, from increased frequencies in the CPU cores or other added parts to the chip imho is not that important for users (and depends on what they are doing). They see the sy
246.
by eis 4y ago
The report you quoted and linked to is about the A15 and not the M2. The M2 is based on the A15 but from what I've seen it does use quite a bit more power (~30%?) than the M1 when loaded. Anandtech did not analyze the M2 yet as far as
247.
by eis 4y ago
Of course nothing forces them to be ready within 2 years but alas, that's what Apple said they'd do. I agree the M2 numbers were not amazing. I guess after the big M1 shock it's hard to follow up with something that comes eve
248.
by eis 4y ago
M1 and M2 actually are not produced on the exact same process node. M1 is N5 and M2 is N5P, an optimized version of N5. I think Kuo might be misinterpreting the statement from TSMC regarding revenue from N3. The key is that they said it won
249.
by eis 4y ago
By that time it'll be far from bleeding edge. The Taiwan fab will be close to N2 while the Arizona fab will be able to produce 5nm generation chips, that'll be 4-5 year old tech then.
250.
Twitter staff exodus accelerates amid Musk battle, whistleblower complaint(reuters.com)
7 points by eis 4y ago|0 comments
251.
by eis 4y ago
A few more entries that might be of interest: * DynamoDB and the Dynamo KV store * LMDB (embedded kv) * Dgraph (distributed graph db) and its embedded kv store BadgerDB
252.
by eis 4y ago
There are plenty of data explorers for other databases, especially SQL DBs. I don't think it being built into the DB should be a make-it-or-break-it feature. I used RethinkDB back in the days because it was the first DB that had pretty
253.
by eis 4y ago
TiKV is not an embedded key-value store, it is distributed.
254.
by eis 4y ago
I believe the EU is on that one, let's see if and what comes out of that.
255.
by eis 4y ago
On the one hand we have a legend with impressive track record that is trying to bring to light serious issues at a large company and he has not much to gain but a lot to lose by making false accusations. On the other hand we have the Twitte
256.
by eis 4y ago
Isn't Matrix trying to be that?
257.
by eis 4y ago
> Wow, have to ask whether you're interested enough to contribute? :) Sorry but I don't have a lot of spare time. I think you have some ambition with this project and it'll be a good amount of work. > I rea
258.
by eis 4y ago
Cheers for the reply. > The protocol specifics (e.g. identifiers & types) aren't polished, because I focused on features in working code. Thanks for the feedback! Got it. IMHO it's better to start with a clean protoc
259.
by eis 4y ago
Seems like a poorly thought out protocol. 1. Inconsistences like the value for "op" being sometimes integer but then sometimes string. Why is this an integer anyways? We are already in inefficient JSON land and a lot of the re
260.
by eis 4y ago
Additional info: https://twitter.com/FatManTerra/status/1560553570814070784
261.
Hodlnaut fires 80%, lost $190M due UST depeg despite claiming no exposure(cryptobriefing.com)
4 points by eis 4y ago|1 comments
262.
by eis 4y ago
The iPhone 14 with A16 will be announced September 7th it looks like. People will have them within a month from now. There is no way it can be N3 as it takes months from HVM start to actual devices hitting the shelves. The iPhone 14 has alr
263.
by eis 4y ago
Yea normally we'd expect M2 Pro/Max etc to be on N5P like the M2. It can't be M3 because M2 was just released. A16 is way too far out. So what does that leave for N3 production? Either it's M2 Pro etc. or something compl
264.
by eis 4y ago
It wouldn't be the first time though that Apple used different process nodes in the same chip "generation". - A5(X) 32nm and 45nm - A9(X) 14nm and 16nm - A10(X) 16nm and 10nm If apple wanted to use N3 for the A15 or the M2 th
265.
by eis 4y ago
So I wonder if the M2 Pro/Max/Ultra will after all be on the N3 node. If N3 HVM starts next month, the A15 being on N5P and it being a year until the A16 on N3 will be released and Apple being the first to use N3... some other App
266.
by eis 4y ago
You could have a server that only sends to the network as well. Just block everything apart from outgoing UDP packets. For the price of development and launch of such a satelite you'd probably be able to afford to make a custom hardwar
267.
by eis 4y ago
How does using a satellite broadcasting differ from a server on the internet publishing the keys? Both are single points of truth that you'd have to fully trust.
268.
by eis 4y ago
> Yes and no: it's not a blockchain. It's relying on the fact that the drand network is producing distributed, verifiable randomness using a threshold scheme with distributed key generatio Hm ok, it's just that there is a
269.
by eis 4y ago
I was curious how this could work and spotted this sentence in the README: > In practice this means that if you trust there are never more than the threshold t malicious nodes on the network you're relying on, you are guaranteed tha
270.
by eis 4y ago
You correctly identified that with arbitrarily long transactions you can't GC the WAL that it is referring to so you will always have potentially arbitarily large WAL files. My suggestion was indeed not to prevent that (as you can&#x27

More ›