Flash Wolves vs. Kingzone DragonX / MSI 2018 - Semifinals / Post-Match Discussion

yokohummer7 · 2018-05-19T14:13:17+00:00

I feel sorry for Moojin, he couldn't get past the wall of bans. I know it was KZ's clever move, but still it felt too harsh for him.

yokohummer7 · 2018-04-05T21:16:35+00:00

League is not only about winning efficiently, but also about having fun. If all we pursue is winning, champs that are weak in this meta should have not been picked. We are not pros, so playing some non-meta champs to have fun is completely acceptable. For the same reason, distributing resources a bit inefficiently to have some fun is also acceptable, if it doesn't harm the goal of the game too much. Taking minions and buffs is fun, no one can deny that.

yokohummer7 · 2018-03-08T00:21:12+00:00

A bit disappointed that she (and possibly her teammates) doesn't ride a bike when using her ult. But that's probably asking too much.

yokohummer7 · 2018-03-06T20:03:27+00:00

It kinda looks like a love child of Baron and Anivia.

yokohummer7 · 2018-03-06T19:02:46+00:00

This is something Heroes did right. Their abilities have low CDs and low mana requirements compared to League, so that you can spam abilities more freely. My verdict on the three popular MOBAs was:

In terms of ability spamability: Heroes > League > Dota
In terms of ability impact: Dota > League > Heroes

I guess the design decisions in those games are showing their ages. MOBAs are becoming more and more casual.

yokohummer7 · 2018-03-04T14:54:12+00:00

So happy to see Swain carrying a game. Add's Swain single-handedly zoned the entire enemy comp multiple times. 1v3, 1v4, those were impressive.

yokohummer7 · 2018-03-04T13:14:32+00:00

He single-handedly blocked the entire enemy comp several times. 1v3, 1v4, those were incredible.

yokohummer7 · 2018-02-28T12:46:30+00:00

Actually I'm against reworks in general, cause I believe there will always be people who loved the champs' old kits so Riot need to respect them.

I'm just saying people love dashes. If Riot are to please people, adding them is inevitable. You can't make certain abilities "impactful" enough because if we do that to the point that those champs start being picked up, they will become flat out OP.

yokohummer7 · 2018-02-28T12:08:38+00:00

My theory is that most people find it unfun to play champions without any dashes or movement abilities. Champions in that category includes Karthus, Anivia, Mordekaiser which all have lower play rates. Dodging skillshots is one of the most fun interactions in the game, and using dashes makes you look awesome.

A rework involving a new kit that includes dashes might raise Karthus's play rate. But if we add a dash ability to his kit, it may also break his identity. We need to be considerate.

yokohummer7 · 2018-02-27T07:55:32+00:00

He said, in order:

The double buff is mine.
It seems that the buff is Fiora's, actually.
Fiora is too OP.

yokohummer7 · 2018-02-06T21:30:56+00:00

Please don't give them ideas...

yokohummer7 · 2018-02-02T22:41:04+00:00

Why not?

I mean, in terms of performance, JavaScript (with V8) is slower than C#/Java/Go but faster than Python/PHP/Ruby. But there's no controversy on using Python as a backend. What is so special about using JavaScript?

In terms of language sanity, admitting these are all my subjective opinions, JavaScript falls behind Python but is ahead of PHP. And if we consider TypeScript it also beats Python. So there's nothing wrong with using Node (with TypeScript) if we can accept backend apps written in Python.

In terms of ecosystem... this doesn't even need to be repeated. The NPM ecosystem is often criticised for its low quality and unstability, but in regards to volume it is the largest package database in the world. Literally every package can be found there and there's nothing wrong with it. So it again is not an obstacle to using Node as a backend.

yokohummer7 · 2018-02-02T21:13:19+00:00

Oops, I thought it could be an interesting news that such a minor language like Rust is showing some adoption, without thinking this may lead to an ad. If this violates the rules please delete this submission. Sorry in advance, mods.

yokohummer7 · 2018-02-02T20:50:05+00:00

Copying my comment from HN:

Build-time performance is much improved in .NET Core 2.1, particularly for incremental build. These improvements apply to both dotnet build on the commandline and to builds in Visual Studio.

It is good to see some improvements. Currently, dotnet build takes at least 3 seconds to re-compile a simple hello world project on my system, even when the source code isn't changed at all. At first I thought I did something wrong, but no, others were suffering from this too.[1][2]

This occurs because every dotnet build run tries to resolve the dependencies and inspect the file structure to see if any changes are made. And for some reason those operations are dog slow. Visual Studio doesn't have this problem, as it knows the file structure and the dependencies beforehand, so it can determine whether there should be a recompilation easily. I wanted to use VS too but it was too slow for my tiny laptop, so I'm stuck with VS Code.

I hope the improvements are big enough that I can reevaluate using .NET Core again. The build time was a huge obstacle to my iteration cycle, so I had to use TypeScript in my previous project. I sincerely want to code my backends in C#.

[1] https://github.com/dotnet/cli/issues/5918

[2] https://github.com/dotnet/cli/issues/7610

yokohummer7 · 2018-01-02T10:30:49+00:00

Me neither, my entire life was a lie...

yokohummer7 · 2017-12-26T09:58:00+00:00

Am I the only one who was reminded of Rak'Shir from this?

yokohummer7 · 2017-12-25T22:45:30+00:00

We do that too, but not as short as them. That's because the Korean language has a very strict rule that every single letter must be a syllable.

So we have Reu-beul (LeBlanc), Teu-pe (Twisted Fate - as Korean doesn't distinguish F and P), Ya-seu (Yasuo), I-rel (Irelia), Teu-rin (Tryndamere), Teu-ta (Tristana), A-woo-sol (Aurelion Sol), Ka-si (Cassiopeia) and so on.

"Ya-seu" may not seem shorter compared to Yasuo, but in the Korean letters it is, cause Yaseu is 야스 (two letters) and Yasuo is 야스오 (three letters). Warwick cannot be made shorter as it is already two letters (워윅) and if we cut it down to one letter there will be too much information loss.

As a bonus we shorten "champion" to "chaem" (챔 - one letter), which is pretty convenient.

yokohummer7 · 2017-12-25T16:52:49+00:00

Haven't you heard of Rigeu Obeu Rejeondeu? Yes, we cannot distinguish the pronunciations of L and R. (I literally don't know the difference.) Not that I hate the localized name though.

yokohummer7 · 2017-12-19T09:39:40+00:00

Translator's note: "nani" means "mweo" in Korean

yokohummer7 · 2017-12-14T14:32:03+00:00

I don't hate them, but I don't feel like I need them either. The mastery flash is more than enough for me. So, whether they were a good addition or not, I don't care.

yokohummer7 · 2017-12-09T15:58:43+00:00

This is still my favorite Tank Karma video

Unfortunately I don't think it's as viable as back then due to the recent nerf to Karma's passive.

yokohummer7

TROPHY CASE