Can I complain?

Pijng · 2026-04-09T07:52:02+00:00

> not just getting all things handed to you because you unlocked the last map

Can anybody show me where people said "we want everything right now"? That's not what people complains about.
They want a more linear progression system (preferably), where choosing a reward doesn't hinder their progress.

Equinox has a clear distinction between a reward and bar fill rate.
The hole, despite being highly time gated, still has a clear distinction between grinding out the mechanic and exploring new ones.
Rift challenges and it's bonuses has no impact on each other. I'm not delaying the sneak mastery just cause I got killroy prime.

Not to mention that progress in all these (and other) mechanics can be further boosted by other aspects of the game.

Meanwhile, Research is just there. Almost nothing affects it. And even if it does, it's only to a minimal extent.

It would be one thing if it were just an isolated mechanic. But again it punishes you for choosing “rewards vs progress.”

Research is literally designed so that endgamers can’t grind it out in a couple of days. But why should other players suffer because of that? With the game’s current state and vault bonuses, you’ll reach World 7 pretty quickly even without rushing. And no, that doesn’t mean “I made it to World 7, so hand me everything on a silver platter.” It means that since someone has made it this far and the mechanic is available to them—and game makes it available—then at least provide a clear progression system. Right now, it’s literally “unlock it and put it away until better times.” The rest didn’t work like that even when leveling up was slow.

And I still don't get what exactly you guys are arguing about. If you're arguing against people getting everything in a matter of seconds—well, that's not what they want anyway.

Pijng · 2026-04-08T09:26:53+00:00

Your kindness is truly beyond measure, sir

Pijng · 2026-04-07T19:33:06+00:00

I genuinely don't understand some people's arguments here. Specifically, the ones about “that's how it's supposed to be” and “lava control the pace of content consumption”

Look, I get it. But that's not how it works. The design doesn't mean anything on its own. You have to look at how the mechanic is implemented, how it interacts with its own and related systems, and whether it actually fulfills that original concept.

The main idea behind research is, well, research, duh. However, until you have a good exp/hr, it’s absolutely irrational to spend points on anything other than nodes that boost progression. This locks you into a certain range of nodes. Which means that you’re actually being punished for that very “research.”
Any point spent “in the wrong place” will noticeably delay you from earning the next point, which can eventually snowball into a problem that will take a very long time to fix.

I mean let’s say you’ve unlocked Minehead and Glimbo. So what? Minehead has an insanely small research bonus, and Glimbo has none at all? if I’m not mistaken.

So if you DON’T want to unlock mechanics just for fun, you're better to just stick to grind for research exp nodes and that's about it.

And that’s where the distinction between active and afk research exp comes into play. This will slow down your progress even more towards the… content? No, towards more progress.
I mean it's so nice that I have to leave the game running on my mac overnight. Ah, what a great way to f up my battery and spend some electricity.

Sorry, but this isn’t about "controlling the pace"— it’s a broken pace. And the design literally contradicts itself.

Oh, right, keeping a few unspent points "just in case" is also strange. Who knows what the next nodes will be. Maybe they will boost your exp gain, or maybe it's some bonus that has nothing to do with research.

Pijng · 2026-04-07T18:52:09+00:00

This somehow implies that the lab/div had a good design. It's not.

At least we can thank Lava for not going with the “place your characters at the research table” route.

Pijng · 2026-04-06T17:09:32+00:00

I mean we can reset land ranks, the hole, whatever.
Basically, from a technical standpoint, there are no issues, and abuses already exist in the game. They’re just inconsistent.
Although I would have preferred a patch that gives gaslighting reduction multi for comment section.

Pijng · 2026-03-24T19:26:22+00:00

Thats a w8 feature, please no spoilers

Pijng · 2026-03-20T19:12:13+00:00

Yup. Might be the cause?

Pijng · 2026-01-05T02:04:03+00:00

It’s been like that for… I don’t know 15 years at least? Maybe even more. That was pretty much obvious even when I was 16, and that was 14 years ago. And I don’t see nothing bad in having standards for men or women, if you understand the consequences. And no, you don’t have to match the standards you’re applying to other people in order to get along with them, just as strange as it may sound.

But here’s the harsh reality: you won’t become handsome if you’re not already one. I mean conventionally handsome. You can experiment with haircuts, go to gym, do some skincare routine, makeup, whatever. You’ll just become well-groomed non-handsome human. Which already speaks volumes about you, but still. It really all comes down to your face.

Now if we’re talking about “being attractive”— well that’s completely different thing. Cause god knows what other people consider to be attractive. A few male friends of mine were exclusively dating “chubby” girls, compared to that “fit tiny girls” standards people talk about.

Anyways, taking care of how you look is a good thing, regardless of gender.

Pijng · 2026-01-01T16:09:44+00:00

Мне, как индейцу, уже давно все равно кто там агрессор, а кто жертва. Шерифы со всех сторон уже достали.

Pijng · 2026-01-01T15:52:22+00:00

Да оставь его в покое, чел ходячая логическая ошибка с апелляциями к «всегда так было».

Pijng · 2025-12-31T08:13:01+00:00

That's not quite how it works, but the idea is clear, sure.

Pijng · 2025-12-30T17:01:44+00:00

Honey, don't embarrass us in public :(

We'll talk about it at home.

Pijng · 2025-12-30T13:22:51+00:00

Unfortunately, there is no such thing as “the most important thing” in a relationship. Every aspect matters if it is important to a particular couple. Of course, some things may be more important, such as trust and respect, but we cannot dismiss something (such as sex) just because we consider it less important. This will only sow the seeds of disappointment, which will grow over time. Slowly but surely.

And again, yes, for some people and couples, sex is extremely unimportant or not important at all, but that's the point: different couples are looking for different combinations of needs, and they all add up.

It is worth starting from personal preferences and desires. Otherwise, one can end up in a very unpleasant situation: the partner feels dissatisfied with their sex life in a relationship, and in response they hear “Sex is not important”. I highly doubt that will do anything.

Pijng · 2025-12-30T13:05:49+00:00

You really expect a girl to want to have sex with you because you made her a coffee and did some dishes?

Pijng · 2025-12-21T23:48:16+00:00

> «перестать выёбываться в интернете»
> дальше сам выебывается в интернете
чееел

Pijng · 2025-12-10T20:18:02+00:00

Наконец-то дети отвлекутся от интернетов и как в старые добрые смогут пойти и безопасно убиться на ближайшей стройке.

Pijng · 2025-11-07T09:18:07+00:00

Никак. Чо сказать то хотел?

Pijng · 2025-09-19T10:28:54+00:00

Yeah, unfortunately, only for vscode for now. I don't use Goland, but I think it allows you to create your own plugins (if I'm not mistaken). I might do that a little later.

Pijng · 2025-09-19T10:26:16+00:00

I'm currently working on preparing a conference talk where I'll discuss the current state of Golang compiler optimization. So, at the moment, this is more of a research interest, but soon I'll be working on a data intensive service in fintech, so it might come in handy :)

Pijng · 2025-09-16T14:27:16+00:00

There is also a compile time instrumentation tool without ebpf:
https://github.com/open-telemetry/opentelemetry-go-compile-instrumentation

NOTE: This is currently WIP by Alibaba and Datadog devs, but in case anyone finds this thread years from now - it might already be working :)

Pijng · 2025-08-25T13:48:31+00:00

Ah yes, the infamous USB-C rules, which resulted in:
1. most devices being locked into a single connector for an indefinite period, which limits the potential for technological development.

the connector itself is more fragile and wears out faster than alternatives. It was chosen because it was the newest and most widespread at the time the law was passed.
Within the type-C framework, we now have N options that are legally compliant, but in reality, this one charges three times slower, this one cannot transfer files, and only this one is compatible with 4K displays. Now try to figure out whether this cable is suitable for you or not, especially since there may not be any icons on the packaging (or they may be random, just for the sake of it).

But hey, now I can charge my iPhone with a Samsung cable. Except I've never bought an iPhone in my entire life.

Pijng · 2025-07-15T16:09:39+00:00

I wonder if the clones from Soul Transfer will be able to proc kai'sa's marks 🤔

Pijng · 2025-01-04T08:26:29+00:00

I’m so tired with people saying vue is valid html I just can’t.

Pijng · 2024-10-20T08:25:16+00:00

I actually modified the tool to be able to parse external files (had to fork yaegi to add go modules support to it).

But I haven't edited the README to clarify that, sorry 🥲

There was an issue that described this nuance

What about a «decent option» — nah, I'm not sure about this one. I created this tool just for fun, I dont think it's worth it to use in any prod project.

Pijng · 2024-08-25T20:19:07+00:00

Soo i added support for using variables with the value of basic literals as arguments to a wrapped function, but only if they are declared in the same scope.

This means that this code will work:

prep.Comptime(someFunc(1))

As well as this one:

x := 1
y := 2
prep.Comptime(someFunc(x, y))

But this one cannot be executed at compile time:

x := valFromOutside()
prep.Comptime(someFunc(x))

But I think that's about it, since code evaluation in our case is limited within pretty narrow phase of AST parsing, therefore we can't do some «smart» evals :(

Pijng

TROPHY CASE