Programmer Humor

32442 readers

891 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

[email protected]

What if we tried designing C a second time? (lemmy.ml)

submitted 1 year ago by [email protected] to c/[email protected]

21 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago (1 children)

I 100% think it would. Android Studio is hot garbage. Not just the compiler, but the whole build process.

Gradle configuration syncing takes over a minute for the most minor of changes when building a project. Importing a new package in Go takes less than a second in most cases.

Changing a version of any imported package in Android Studio has a 50-50 chance of breaking everything. Heck, even creating a new project in Android Studio has a 50-50 chance of working.

The reasons why Android Studio can't achieve similar speeds are plenty, but here are some:

The whole thing is a patchwork of randomly assembled pieces, with a complete mess of UI and unbelievably confusing settings.
It is also being developed by Google and JetBrains, so no single entity is responsible for the product.
The fact that it’s developed in Java doesn’t help, sometimes you can almost see the monstrous garbage collector having to swipe away the memory while the IDE freezes and you have to wait 30 seconds for the app to become responsive again.
Android Studio is a resource hog, requiring at least 4 GB of RAM to work properly. I had to buy another 8 GB RAM stick just for it to function properly. Also, no matter what CPU you have, it's still going to use it 100%.

[–] [email protected] 1 points 1 year ago

Those are fair points about Android Studio - I've never used it, or made apps, and was thinking simply that the compiler wouldn't make much of a difference in a large project; hadn't considered all the environmental disaster about Java and Android development.