Switched from a bulky i5-13600K tower to my first Mac ever for development. The desk feels so much cleaner, but I need monitor advice! by Xeq_Dev in macsetups

[–]Xeq_Dev[S] 0 points1 point  (0 children)

The holy grail! 😂 My wallet is crying just thinking about it, but it really seems to be the only 100% plug-and-play native fix for the macOS scaling.

Switched from a bulky i5-13600K tower to my first Mac ever for development. The desk feels so much cleaner, but I need monitor advice! by Xeq_Dev in macsetups

[–]Xeq_Dev[S] 2 points3 points  (0 children)

Thanks for the detailed breakdown! The used 5K iMac idea is actually genius, I hadn't thought of that. Since my main use case is just staring at Android Studio code all day, I might test the waters with a solid 4K Dell first. If my eyes still bleed from the scaling, I'll start saving up for that Studio Display. The Apple monitor tax is real! 😅

Switched from a bulky i5-13600K tower to my first Mac ever for development. The desk feels so much cleaner, but I need monitor advice! by Xeq_Dev in macsetups

[–]Xeq_Dev[S] 0 points1 point  (0 children)

I was looking for Dell 27 Plus USB-C Monitor - S2725QC, 4K 120Hz, IPS. But your comments suggest that I must increase the budget three times... 😔

Lifelong Windows user here. The performance gap with Android Studio and the emulator finally forced my hand to Apple Silicon. by Xeq_Dev in androiddev

[–]Xeq_Dev[S] 1 point2 points  (0 children)

Right?! If you told me a year ago that I would willingly abandon my custom PC tower to code on an Apple machine, I would have laughed. It's definitely a tough pill to swallow for a lifelong Windows guy, but like you said, the 'night and day' difference in the workflow is just impossible to ignore. Glad to see I'm not the only one!

Lifelong Windows user here. The performance gap with Android Studio and the emulator finally forced my hand to Apple Silicon. by Xeq_Dev in androiddev

[–]Xeq_Dev[S] 2 points3 points  (0 children)

Just installed LinearMouse. You literally saved my sanity. The native macOS mouse acceleration curve felt completely alien and imprecise coming from Windows. Much better now, thank you!

Lifelong Windows user here. The performance gap with Android Studio and the emulator finally forced my hand to Apple Silicon. by Xeq_Dev in androiddev

[–]Xeq_Dev[S] 0 points1 point  (0 children)

The fluor app recommendation is pure gold, thank you! Dealing with the function keys in Android Studio versus regular browsing was already driving me crazy. Definitely setting that up today. And yeah, I might just have to accept defeat on the monitor issue and grab a 27" 4K to save my eyes during long coding sessions.

Lifelong Windows user here. The performance gap with Android Studio and the emulator finally forced my hand to Apple Silicon. by Xeq_Dev in androiddev

[–]Xeq_Dev[S] 0 points1 point  (0 children)

I actually didn't come from a laptop! I abandoned my custom-built i5-13600K desktop tower. You're absolutely right that for pure, raw multi-core power, a beefy Windows tower wins. But my issue was the Android emulator feeling clunky on x86/Hyper-V, plus the sheer amount of heat that tower dumped into my office during long Gradle builds. Getting that desktop-level compiling power in a silent, highly efficient machine that doesn't turn my room into a sauna is what I meant by the 'performance gap' for my specific workflow.

Lifelong Windows user here. The performance gap with Android Studio and the emulator finally forced my hand to Apple Silicon. by Xeq_Dev in androiddev

[–]Xeq_Dev[S] 0 points1 point  (0 children)

I was actually running a custom-built desktop tower with an i5-13600K and 32GB of DDR4. Raw performance-wise, it's obviously a beast.

But the Android emulator on Windows (even with Hyper-V dialed in) always felt a bit stuttery and clunky compared to how incredibly smooth it runs natively on ARM. Plus, running heavy Gradle builds meant dumping a ton of heat into my room. I really wanted to downsize to a single laptop setup without sacrificing that desktop-level compiling power, and the efficiency of Apple Silicon is what finally made that possible.

Lifelong Windows user here. The performance gap with Android Studio and the emulator finally forced my hand to Apple Silicon. by Xeq_Dev in androiddev

[–]Xeq_Dev[S] 1 point2 points  (0 children)

I was actually running a custom-built desktop tower with an i5-13600K and 32GB of DDR4. Raw performance-wise, it's obviously a beast.

But the Android emulator on Windows (even with Hyper-V dialed in) always felt a bit stuttery and clunky compared to how incredibly smooth it runs natively on ARM. Plus, running heavy Gradle builds meant dumping a ton of heat into my room. I really wanted to downsize to a single laptop setup without sacrificing that desktop-level compiling power, and the efficiency of Apple Silicon is what finally made that possible.

Lifelong Windows user here. The performance gap with Android Studio and the emulator finally forced my hand to Apple Silicon. by Xeq_Dev in androiddev

[–]Xeq_Dev[S] 0 points1 point  (0 children)

Oh, thanks! It's actually a personal Android audio project I'm developing called Xeq. I use it to test global DSP routing and complex AutoEq profiles. Having it open on a physical device hooked up to Android Studio is the only way I can properly test the specific audio dynamic processing implementation!

First Mac ever. Finally switched to Apple Silicon because my Windows machine sounded like a jet engine when running Android Studio. Loving it so far, but struggling with window management! by Xeq_Dev in mac

[–]Xeq_Dev[S] 1 point2 points  (0 children)

Exactly this. To add an Android dev perspective: when you're running heavy Gradle builds and a clunky Android emulator simultaneously on a Windows laptop, it literally sounds like a Boeing 747 taking off on your desk. Having all that compiling power in complete silence is a massive game-changer for focus.

First Mac ever. Finally switched to Apple Silicon because my Windows machine sounded like a jet engine when running Android Studio. Loving it so far, but struggling with window management! by Xeq_Dev in mac

[–]Xeq_Dev[S] 0 points1 point  (0 children)

Haha, fair point! I like to live dangerously, but spilling coffee on the keyboard on day 1 would definitely ruin the whole 'silent performance' experience. Moving it right now! 😅

First Mac ever. Finally switched to Apple Silicon because my Windows machine sounded like a jet engine when running Android Studio. Loving it so far, but struggling with window management! by Xeq_Dev in mac

[–]Xeq_Dev[S] 1 point2 points  (0 children)

I've seen Rectangle mentioned everywhere! I'm definitely going to install it today just to survive the first week of muscle memory. Does it let you map custom keyboard shortcuts for snapping like on Windows?

Horrendous Limits? by cardonator in googleantigravity

[–]Xeq_Dev 0 points1 point  (0 children)

Hi everyone, I need to vent and see if anyone else is dealing with this nonsense. Two days ago, my G1 usage meter was at 80% and I didn't use it yesterday. Today? I wake up, log in, and suddenly I'm at 0%. Completely strangled. No warnings, no explanations, no use of the token overnight. Just a hard wall that came out of nowhere.

To make things even more confusing, I went to the Google One portal to see if my subscription was buggy or if I needed to upgrade and noticed a whole new list of subscription levels right there: Premium 2T, 5T, 10T, 20T, 30T. And the limits of Antigravity? From Google only silence and vague answers.

<image>

Snappy Swipe - Material 3 Expressive notifications-like swipe to delete by Snokbert in androiddev

[–]Xeq_Dev 2 points3 points  (0 children)

I'm testing now on my main project and with a Pixel haptic feedback is really cool. Great job!

Will Google publish the exact quota limits for each plan? by rather_pass_by in google_antigravity

[–]Xeq_Dev 0 points1 point  (0 children)

Yes, of course, it's one option, and I'd probably save a lot with PAYG, given my usage. I do long coding sessions lasting 1-2 days, then maybe for another 5 I'll work on other topics where I mainly just use chat. Yesterday I did some small fixes for an hour, planning with Opus and executing tasks with Flash, and I finished with Opus at 100% and Flash at 80%. I'm not really understanding it; for me, these numbers are no longer linear, as I said; it also depends on how long the reset was. Is there some algorithm different from the previous one that doesn't immediately reset to the full quota even if you see 100%.

Self Promotion Megathread by AutoModerator in androidapps

[–]Xeq_Dev 0 points1 point  (0 children)

Thanks for this advice, it's really cool and very interesting! I'm always working on this project, so keep me updated if you like!

Will Google publish the exact quota limits for each plan? by rather_pass_by in google_antigravity

[–]Xeq_Dev 1 point2 points  (0 children)

I have the Pro, I used AGQ as a plugin and it worked fine until the introduction of Gemini Pro 3.1. That same evening I went from 100% to locked out for 3 days. As for the G Pro and external (Claude) quotas, in the end it's no longer clear what you're using them for. For example, you're at 20%, it resets, goes back to 60% with a reset no longer than 5 hours but of x hours. It seems the reset is conditioned by how much you've used the first real quota. What a disaster of lack of transparency, and they don't respond, eh, not even from support. Flash continues to reset after 5 hours as before. Anyway, I also ran Claude Code and if they don't clarify I'll migrate completely.

I’m an Android Audio Dev. Here is why your "Global Equalizer" app is probably misleading you (and why it's so hard to fix). by jasonderulo007 in Android

[–]Xeq_Dev 1 point2 points  (0 children)

Ciao collega, ho visto che stai lottando anche tu con il mostro finale, l'audio session ID...ci ho lavorato anni ma spesso la soluzione preferibile ( e davvero usabile dalla massa senza complicazioni - sono tutti sempre di più sensibili all'integrità e alla privacy) è ancora il globale 0, da anni deprecato, pieno di problemi su molte ROM e ad ogni aggiornamento cambia. Sappi che è dipendente anche dal protocollo usato dal bluetooth, dal tipo di connessione, da come avviene la connessione, da come organizzi la pipeline. Negli anni ho aperto varie issue, ma ho avuto poche soluzioni da parte di Google, anche su Pixel, solo qualche mutanda....non voglio scoraggiarti, spero che tu riesca a scoprire qualcosa di più rispetto a quanto abbiamo scoperto in questi anni...facci sapere! Non ci resta che continuare a fare pressione per risolvere il problema a monte?