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

Apple's M4 has reportedly adopted the ARMv9 architecture

wccftech.com

Post reply on HN
Print view View original

71–80 of 250 posts

Re: Apple's M4 has reportedly adopted the ARMv9 architecture

#71

Post by rbanffy »

aaomidi wrote: post #68
heroprotagonist wrote: post #38

Earlier quoted context omitted.

Every character you type results in some sort of hit to their telemetry server. It will include the actual letter you typed, if you or your org are not configured to be in EU. With their EU configuration option (pulled from server every launch) it will only report the fact that you typed _something_. Now if that's not fun enough, their telemetry also covers mouse movements. Go ahead and watch your CPU as you spin you…

This is so stupid. They are the sender and receiver of the messages. They can backfill their telemetry using batch processes offline ffs.

Unless someone really complains loudly enough large orgs switch to a competitor, it's tech debt and not a bug they need to fix.

Re: Apple's M4 has reportedly adopted the ARMv9 architecture

#72

Post by xnx »

bluGill wrote: post #64
treyd wrote: post #32

Earlier quoted context omitted.

Why is that not at least done asynchronously? I thought part of the whole narrative of shipping these new terrible pieces of software as standalone Google Chrome instances was that it makes it easier to spawn async JS workers for background tasks and whatnot?

async is still difficult. There is no getting around data synchronization issues. either you need to spend a lot of time in design or will get constant problems with things like not having a mutex when you should, mutex deadlock, holding a mutex too long, locking/unlocking too often. I haven't done async JS, but I've done enough async elsewhere to know that language cannot work around bad design.

I thought this was mostly/fully solved with CRDTs?

Re: Apple's M4 has reportedly adopted the ARMv9 architecture

#74

Post by aaomidi »

zamadatix wrote: post #73
aaomidi wrote: post #67

Earlier quoted context omitted.

It’d be trivial to MITM it with wireshark

What's the easiest way to get the Teams app to accept the MITM on TLS?

I believe it just uses your systems rootstore. So adding the signer cert in there should probably be enough.

Re: Apple's M4 has reportedly adopted the ARMv9 architecture

#75

Post by zamadatix »

heroprotagonist wrote: post #59
Aaargh20318 wrote: post #48

Earlier quoted context omitted.

I’m in the EU and should have the EU configuration. The problem mainly occurs when I mention someone in a reply to a thread. Once I type @ the text input just slows down so much I can type much faster than it can render the text.

It's still going through the same telemetry action, it just omits the actual character you typed. And yes, it is character by character. That collection (eg, the timestamp you hit the character, channel/person it was to, etc) is the inefficiency causing your typing to slow. If it was a straight text box that they polled contents of _occasionally_ or after you hit 'send', it would be a much better user experience.

As much as I dislike overbearing telemetry in the context of an M4 or even an N95 the computer should be more than capable of logging a few kb of telemetry about inputs per second without even a notice on the performance statistics. The problem remains that every single thing in the app is just implemented god awful slow and would still be regardless if it's also recording telemetry on the input data or not.

Re: Apple's M4 has reportedly adopted the ARMv9 architecture

#76

Post by zamadatix »

aaomidi wrote: post #74
zamadatix wrote: post #73

Earlier quoted context omitted.

What's the easiest way to get the Teams app to accept the MITM on TLS?

I believe it just uses your systems rootstore. So adding the signer cert in there should probably be enough.

Ah, that's right, Chrom* based things look at the system store by default and it's the Firefox based things that don't (without configuration at least). Thanks.

Edit: and that reminds me I should probably run this test on new Teams, where it now uses the built in WebView2

Re: Apple's M4 has reportedly adopted the ARMv9 architecture

#77

Post by plorkyeran »

alberth wrote: post #41
ko27 wrote: post #23

It seems that M4 was overhyped. Almost of all of the performance improvements, in Geekbench for example, comes from new instructions that most apps won't use, and even if they do they might end up using the faster GPU/NPU for those tasks. https://twitter.com/toniievych/status/1788596920627118248

I truly never understood why Apple deprecated Bitcode. It was a super great idea because it allowed recompilation on the App Store to take advantage of new instructions.

Bitcode did not allow recompilation to take advantage of new instructions. They dropped bitcode because they never actually managed to do anything with it other than the armvk7 to arm64_32 recompilation, and that required specifically designing arm64_32 around what was possible with bitcode.

Updating apps to use new vector instructions is far more complicated than upgrading to a new compiler version and having it magically get faster.

Re: Apple's M4 has reportedly adopted the ARMv9 architecture

#78

Post by jandeboevrie »

Aaargh20318 wrote: post #18

The most incredible thing about the new iPads is that even with the crazy fast M4 chip MS Teams manages to crawl to a halt. Clearly it takes all the engineering skills of the largest and most valuable software company in the world to make text entry go at about 1 fps on a chip as powerful as the M4.

Try Pidgin with the excellent ms teams plugin: https://github.com/EionRobb/purple-teams - less than 100mb ram usage and notifications that still work after an hour. Only for (video) calls you need to open teams..

Re: Apple's M4 has reportedly adopted the ARMv9 architecture

#79

Post by Klonoar »

heroprotagonist wrote: post #59
Aaargh20318 wrote: post #48

Earlier quoted context omitted.

I’m in the EU and should have the EU configuration. The problem mainly occurs when I mention someone in a reply to a thread. Once I type @ the text input just slows down so much I can type much faster than it can render the text.

It's still going through the same telemetry action, it just omits the actual character you typed. And yes, it is character by character. That collection (eg, the timestamp you hit the character, channel/person it was to, etc) is the inefficiency causing your typing to slow. If it was a straight text box that they polled contents of _occasionally_ or after you hit 'send', it would be a much better user experience.

...do you have any source verifying this? Setting aside how insane of an issue it'd be network-wise/privacy-wise/etc, this is like a day one "debounce the call" fix.

I'm not even saying I doubt you, I'm just curious how you ascertained this exact behavior.

Post reply on HN