@electrineer any powerful modern 8-core laptop will sound like a fucking airplane if you keep all 8 cores loaded 100% for 24/7. Seems like with M1 that will change. I do C++, so, I do need this piece of shit for work.

@electrineer if it had a bad cooler it would literally melt. It was spinning all the cores 100% and fan loud as a vacuum cleaner. We can also blame intel and hope M1 soon solve the problem, but we aren't there yet. Simply not taking all the cores when IDE is idle is kind of expected bare minimum

@Oktokolo the guy that made column mode for AS is an idiot. AS/ IntelliJ do have column mode edit with keyboard, but it's hideously fucked up. No idea what was running in the guy's head when the person was implementing that shit.
When I complained to them, I told them that with mouse it works, but with keyboard it's totaly shit and they said that they aren't going to fix because everybody is used to it. I guess, users simply don't use their messed up column mode edit with keyboard

@electrineer Last time I needed android specific IDE was when Android Studio was just some beta when Eclipse was main dev env. I wasn't a fan of Eclipse, but it did work, I don't recall major issues simply opening and building projects (I don't normally edit java or some gui stuff for android). Here I simply installed Android Studio and it melts my MBP

@Oktokolo I cannot use anything jetbrains. I prefer in random order: Notepad++, VsCode, VisualStudio, Xcode (No choice here for ios work). But I cannot use jetbrains: I use column mode edit a lot and these idiots cannot make proper column mode edit.

@WildOrangutan I just started it and after it loaded my project CPU was 0% and it was taking roughly 3GB of ram. 1-2 hours later ... surprise, it was already steady at 16% CPU, that is, two cores were fully consumed by studio64.exe. It's a clean install. I've installed it last week, no changes or customizations. Simply installed NDK 21 from studio manager, nothing else.

@bagfox it's their fault that they offloaded to some shit maker. If they are incapable making decent tools themselves, they should pay Microsoft for full fledged Android support in vsCode or Visual Studio.

@ScriptCoded yes, it's shit.

At least your CPU isn't 100%, seems like god really likes you.

I really want these things: cycle counter (or high res timer) as an int64_t, and a function that converts times to strings. I've done that soo many times and each time I want measure time I have to write tons of boiler-plate code. And to convert arbitrary durations to readable string is pure pain in the ass. That's what they should have added to std. Something that's usable, not some ikea-style set of bullshit tools for me to build my own tools.

@BigBoo but all the functions and the rest there is the same type of crap. I did c++ for 15 years (and I loved it). I did some nodejs for a couple of years and now each time I need to write that type of chrono shit in c++ I feel that this does not make sense in 3rd millennium, I feel those dudes in std committee waste their time to come with ways for me to waste my time when I want to write some code. It's the same as dysfunctional std::string: you cannot even check easily if a string ends with some suffix. Finally these dudes ub committee after 10+ years decided to add it (we'll have it in std++20). Still std::string is crap. It's just a string-like interface bolt-on for std::vector.

Just look at this disgrace:

std::chrono::high_resolution_clock::time_point t0 = std::chrono::high_resolution_clock::now();

runSomething();

std::chrono::high_resolution_clock::time_point t1 = std::chrono::high_resolution_clock::now();

std::chrono::high_resolution_clock::time_point::duration diff = t1 - t0;

std::chrono::microseconds micro = std::chrono::duration_cast<std::chrono::microseconds>(diff);

LOG("runSomething takes %llu microseconds", micro.count());

Yes, I know there is auto, but you cannot use it in class members. The point is: to represent timepoints, difference... all these basics suddenly became major pain in the ass when you really quickly want to measure some time

@BigBoo yes, that's what I do each time I need to access timers. I used to have wrappers for system specific clock APIs, now I do wrappers for std code. Why? It should be usable as-is. They should have provided int64_t time_ns() to get monotonic nanoseconds, or time_micro() or ms. That would cover 95% use needs that people have. All that moushfull::bullshit:chrono::talk is annoying as hell.

Regarding ego/asshole attitude: even if you are much better than your teammates don't act like asshole, try to help them instead so that they become better. In the end, the better your teammates the easier it is for you. Also, many companies specifically try hard to avoid people with ego issues and assholes, regardless if they are gods of software engineering. In interviews we try to spot these types of people and reject them if they are suspected of such ego problems.

For juniors I'd also give this advice:

- your boss/manager is not your friend. Don't be fooled.

- always work on self improvement and some personal side projects at your personal time.

- always be looking for better opportunities. Early in your career if you stayed more than 2-3 years at the same place switch to active mode of searching for a better place. Remember: making the right move may advance your career in a day to a new level whereas it would take you 5 or more years of your life to reach the same level at the old place.

#1 applies even more so for senior devs! If some dude asks me a question, I'll take a break and help them. I do c++ and in my case I have a very different idea about documentation: code is the documentation, I document unobvious/tricky things and some APIs that are meant to be used by others, other than that I try to keep code dense and not polluted by BS comments that do not have any value.

@phorkyas We don't build for linux. We run windows servers :) We use cmake for linux (non production) builds, we actually reuse same build scripts from our android build.

We are slowly switching to linux, but we will be using same linux version perhaps across tens of thousands of our servers. The reason for the swtich is obvious: you can guess what licensing fees we pay to run these tens of thousands of win servers

@Proximyst I've seen ninja (I've built chrome and I think they made ninja to handle chrome). No idea if these are any better. At least I know if I try to build cmake based project that I'll suffer and google for the same stuff again and again to be able to finally get VS project out of cmake.

@RememberMe I prefer to deal with VS directly (because I like it) and with xcode (because I have no other choice).

I really liked make-base original build system from android... I think it was well designed; however it seems that it's being replace by ... cmake

cmake is crap, no matter what.

CMake?.. it will convert your project at best to some convoluted crippled version of Visual Studio project (if that's your IDE of choice). How can this be even acceptable?.. I work on projects where literally heart of a billion dollar company's main project is a visual studio solution that you can open and... omg, build right away... build and run. Unbelievable. Every fucking project that uses cmake will take efforts to fucking get it converted to something that can build and if it's not a hello world project it just never works. Never. that's how it was 15 years ago, that's how it is now

Can you do that in cmake... yes, you'd need to do some weird moves to end up with fucked up version of VS project. What for?.. just to avoid having multiple projects for different targets (xcode, android etc). But if you chose cmake, you'll instead of having 3-4 different projects to maintain, you'll have 4-5 messed up projects and then only benefit is adding or removing a file becomes trivial.

Yes, Android Studio is epic pile of turd. Xcode is nice, but nothing comes even close to visual studio. Even if you take some 10 year old version.