Mazen Khiami

Web software everything..👨🏻‍💻

[Mazen Khiami @sgaawc]

Stop passing database transactions down 15 levels of function calls! 🛠️

I wrote about how to ditch "parameter plumbing" in #nodejs

In this guide: • Implicit transactions 🔄 • The "Un-effect" context escape 🚫 • Event Loop boundaries 🌀

https://t.co/flIpA6Z7gq

[International Cyber Digest @IntCyberDigest]

❗️🚨 BREAKING: Researchers used Mythos Preview to find the first public macOS kernel memory corruption exploit on Apple's M5 silicon, they give a glimpse into Mythos say it’s really powerful.

Apple spent five years and an estimated several billion dollars building Memory Integrity Enforcement (MIE), the hardware-assisted memory safety system built around ARM's MTE. It was the flagship security feature of the M5 and A19, designed specifically to kill the entire memory corruption bug class.

Researchers from Calif built a working exploit in five days.

According to Apple's own research, MIE disrupts every public exploit chain against modern iOS, including the recently leaked Coruna and Darksword kits. Calif walked into Apple Park this week and handed over the report in person.

Full 55-page technical report drops after Apple patches the vulnerability.

[Mazen Khiami @sgaawc]

@FuegoQSTP Congrats Fuego and Karl

[Daniel Glejzner @DanielGlejzner]

Rx Visualizer Beta V1 out now.
Link in comments.

#rxjs #angular

[Mazen Khiami @sgaawc]

@nxtlvl @TheCryptoLark But it will come one day, they cant keep holding forever!

[Mazen Khiami @sgaawc]

@k7ybnd99 Just keep it singular, since the enemies of your enemies are not necessarily your allies

[Mazen Khiami @sgaawc]

The boring side of the Web
Inbox: you have received an email from seller
Email: click to read message
Chrome: 10 redirects for page to come
Page: login to see message
Login form: enter username/password
Password: incorrect! Try again
Store inbox: promotion crap!

[Manz 🇮🇨⚡👾 @Manz]

Backend developers

[Mazen Khiami @sgaawc]

@BlackStarDiva @rickygervais @chrisrock Stupid joke and an overreaction!

[Mazen Khiami @sgaawc]

@Vonster @Adobe Good catch.. eagle eyes

[Mazen Khiami @sgaawc]

@duncanfaulkner Remove any polyfill from your main.ts, keep working on dev mode, disable any reversed proxies running via ng cli, if applicable

[Mazen Khiami @sgaawc]

@duncanfaulkner Can you try isolating the problem by slimming down your app and comment out everything, just let the outer shell works app.component.ts maybe.. that depends on your app, and gradually include back other modules/cmps.. you will definitely spot something on the way

[Mazen Khiami @sgaawc]

Finally!

[Mazen Khiami @sgaawc]

@simey @spierala Thats a good way of thinking, always put that at the top when writing down the logic

[Mazen Khiami @sgaawc]

@simey @spierala I am not sure your pattern works, the service might be constructed once, and stays there as long as the app is working, so waiting for the service to destroy itself might not really happen, that event should stay in the rendered cmp instead, but yes API is unpleasant I can say.

[Mazen Khiami @sgaawc]

@simey @spierala In paging example, the docs listen to the paging emission without any unsubscribe. Thats like a memory killer if applied in many diff cmps where the paging is taking part

[Mazen Khiami @sgaawc]

@simey @spierala Well, thats the case when you need to pick the right observables to listen to. If you feel a dire need for the unsubscribe, yea sure. Not to list down all possible scenarios, but to make it clear, easy to understand.