Ugh, why would a company switch to Maven in 2019 instead of Gradle. You'll come around though, don't be a monkey, automatic dependency management is amazing once you get the grip of the tool you're using.

Amazing how such openly racist talks are possible in 2019.

Hehe. Hearing Kotlin delights me in a similar way as MongoDB, cause "Kot" means "shit" in German.

Sorry those aren't buzzwords it's just a bunch of languages/frameworks. And some of them are super boring enterprise trash like Hibernate.

(Unit) testing Firebase (or any other 3rd party service) does not make much sense - they should be tested by their own development teams.

What you should be unit testing is your own application logic, using mocks or similar replacements for any external services.

You got it all backwards. Oracle did a terrific job in making Java more open source than it was before. Before raising the licensing fees, they commited most parts of the Hotspot VM to openjdk. Now there are tons of different, free, Java VMs to choose from in a much easier way.

Here's a chart that might help you in your future discord api adventures: https://s.gus.host/flowchart.svg

Both gateways are "https" (wss) gateways that create a websocket connection. Actual voice data is sent as udp packets, that's true.

Why not use one of the million api libs?

Did that bitch just assume your gender?

Not sure about reporting. After all, I don't want my subjective judgment to be forced on all the other users.

It's true, I can stop reading devRant all together any time, but I would prefer not to. I enjoy it quite a lot when having some idle time. However I've noticed some low quality/overall negative content coming from a few usual suspects, would be nice to be able to put them on a shitlist.

> synchronously

You're doing something wrong, not JavaScript.

ORMs suck. SQL is a 4th generation language and does not lend itself well to being abstracted into patterns of 3rd generation languages. But that's not all: most ORMs also try to support many databases, and therefore make it hard to use database-specific features. Sure some ppl love ORMs - because they are their job security. ORMs might make a few already simple use cases even simpler, but I've never seen one that was actually helpful with more advanced queries, on the contrary - instead of learning SQL properly (a valuable and transferable skill) you end up learning the quirks of some shitty framework entirely useless for all projects that use a different one.

Here's a great link about one very notorious ORM: https://hackerfall.com/story/...

Play Mass Effect

Fuck entity frameworks.

Berlin is a shithole lol.

You call yourself and other programmers experienced, but are focusing on which language each of you is fanboying? Lol ur not experienced at all.

about tree fiddy

@nitwhiz
>python
>rule free

What universe are you living in? Python's white space awareness makes it one of the least free languages out there.

I smell static abuse.

Is there a better alternative to git for the average use case?

Yeah it's much easier to write new legacy code for the future than deal with the result of others having the same sentiment.

Unpopular opinion: dealing with meh legacy code is on average no harder than writing really good* future proof code.

*bug-free, maintainable, extensible, edge cases covered

ll -h usually does it for me /shrug

Hahaha! Don't forget the onions!

Touché. :)

I like your attitude. Many ppl want to rewrite and throw away code but forget that while it may be ugly, not all things that look crap do so due to incompetence. Legacy code usually also contains many bugs fixed and workarounds for weird shit and edge cases.

Yes please I need a new Mass Effect!

When you see someone ranting about someone trying to get upvotes to get a free 1$ stress ball because of the free shipping.

Dealing with database integrity errors on 4 databases!

@ScriptCoded Use a proper formatter. If your IDE does not support formatters, use a proper IDE. Also a team not using a common formatter sounds horrific.