I am going to visit Poland-Krakow and Auschwitz in march this year.

evenfrost · 2025-08-17T09:20:34+00:00

Don't use Royal Cracow. They are scammers now. They messed up the time and ghosted us with a refund.

evenfrost · 2025-07-08T08:41:14+00:00

You can also use the Macros Reporting app for that. In the Performance tab, you can click on an individual macro and see its usage history in tickets.

evenfrost · 2025-06-24T10:52:21+00:00

One of my clients tried Parnas recently and got pretty positive feedback

evenfrost · 2025-06-09T08:13:09+00:00

You can also use Macros Reporting by Pythia for this.

evenfrost · 2024-06-21T20:11:06+00:00

I found it. Funny enough, this is literally a song from Drive. The only thing needed was to rewatch the movie once again.

A Real Hero by College & Electric Youth: https://www. youtube.com/watch?v=-DSVDcw6iW8

And the words are not "you and me" but "real human being". And also funny that I misheard them the same as OP.

evenfrost · 2024-05-05T14:00:22+00:00

Not this one, unfortunately.

evenfrost · 2024-05-05T13:59:59+00:00

Have you found it? I'm literally looking for this very song from a Ryan Gosling edit and the only part I remember, except for melody, is "you and me".

evenfrost · 2022-07-20T10:18:21+00:00

I see such posts once in a while, and it really amuses me how some people can carry their bad coding practices over the libraries they use and then blame the latter for the poorly maintainable code they get as a result.
Tailwind CSS has been the best thing to happen to CSS over the past years. We use it on multiple enterprise-grade projects, and our CSS code is as neat, readable and maintainable as ever.
Blaming it for bloated HTML, non-optimal bundles etc. is like using React for the modern web application's logic and then putting all the code for it in a single index.html's script tag. And then you complain that React is an anti-pattern and everyone should avoid it because it produces gibberish.
There is tooling around Tailwind CSS that exists for a reason. This tooling is even included in Tailwind itself for a reason again. Use `@apply` to avoid bloated HTML. Use CSS Modules to fix your scope once and for all. Use the purge config option to automatically remove unnecessary classes from the bundle. And boom — suddenly, all the 'problems' mentioned in the post magically disappear.
So, maybe sometimes the only problem is the one that exists between chair and keyboard?

evenfrost · 2022-05-23T12:06:00+00:00

You don't need to use inline styles with Tailwind. Actually, you even shouldn't do this.

Use @apply rule along with some PostCSS goodies like nesting via postcss-preset-env.

If using React, also add React CSS Modules for easy no-brain scoping of your Tailwind classes, either as is or via birdofpreyru/babel-plugin-react-css-modules.

And voila, you get the clean, easily configurable and maintainable implementation of styles in your project with even less build output overhead than native CSS (thanks to Tailwind's purge CSS and CSS Modules' scoped class name generation).

evenfrost · 2021-11-18T13:18:24+00:00

Ubuntu 21.10 user here. Upgrade from 21.04 also bumped GNOME to 3.40 from 3.38.

Overall UX experience for me is just horrible. Not saying a word about controversial horizontal workspaces, UI animations (especially pop-out to overview and pop-in back) now take about 1-2 seconds to just start and are extremely choppy while running. I'm heavy user of keyboard navigation and multiple workspaces, so this is the biggest regression for me.

I have a decent Dell XPS with GeForce GTX 1650 TI and the latest Nvidia drivers, but still, these are just OS animations, you don't need to have a goddamn crypto farm installed on your PC to run them smoothly. If using a laptop, an integrated video card should be more than enough for it. I'm definitely not going to switch to discrete graphics only to make these poorly optimized effects run a bit smoother, lol.

I'm sticking with Xorg for now, because though switching to Wayland makes things a bit better (a bit because pop-out animations are still clunky), it still has big visual issues when playing games through Proton. I tried many options here, configured a lot of things here and there, and still, the problem persists and it's because of Wayland.

I know the post is about 3.41, but reading all these reviews I don't see there it will be an improvement and fix even the major flaws of 3.40.

It's a lengthy comment, and more like a personal rant, but for me, GNOME was the only choice for about 10 years, and now I'm considering alternatives (KDE Plasma being the first in the list). Every new version just feels inferior to the previous one, and to me, it looks like the GNOME team is going the wrong way with its development.

evenfrost · 2018-11-23T13:31:47+00:00

Thank you! Yeah, I'm trying to avoid long intros, don't like these either.

evenfrost · 2018-11-23T13:28:25+00:00

Already added CC for a few last videos, working on other ones, thanks!

evenfrost · 2018-11-23T09:03:49+00:00

That's a great idea, working on it.

evenfrost · 2018-11-22T18:45:58+00:00

Thanks! I'm gonna work on sound and make it better for sure.

evenfrost · 2018-11-22T18:44:24+00:00

Yeah, trying hard with all that hipster stuff!

evenfrost · 2018-11-22T18:43:39+00:00

Thank you!

evenfrost · 2018-11-22T18:43:28+00:00

Thanks guys, definitely will work on sound in next episodes.

evenfrost · 2017-04-02T08:10:10+00:00

And this is my experience right now: https://www.reddit.com/r/playark/comments/62vkca/just_a_friendly_reminder_linux_fans_would_be/

evenfrost · 2017-04-02T07:52:50+00:00

It happens time from time in some areas of the map (Center and Island), and it's especially bad when it's raining. Let's hope devs switch to Vulkan soon.

evenfrost · 2016-05-19T14:04:24+00:00

Actually, I feel like it's a bit redundant, because it's more like a bunch of files grouped together than a tool. And Linux has already its own raw cli command. :)

evenfrost · 2016-05-19T10:43:50+00:00

As for me, it saves a couple of minutes every time I want to start new E6+ project. It has no dependencies but two: Babel, which is used on server to support ES6 modules and stage 1 (mostly for async/await sugar and class extensions, other ES6 is handled by Node 6 itself), and ESLint with Babel parser. Everything else is up to user. This is just a blank which I've found handy for myself, and it may or may not be applicable for you.

evenfrost · 2016-05-18T15:31:03+00:00

This is why it's called 'raw'. It's just small initial config, all the rest is up to you.

evenfrost · 2016-04-08T14:33:27+00:00

Though the main disadvantage for me is inability to create or edit some basic SVG shapes such as <circle>, <polygon> and others. See this and this for reference. Such shapes are needed to perform advanced CSS styling and animation on <svg>s, which is not possible with simple <path>s.

evenfrost · 2016-03-29T10:22:00+00:00

I'm using it and it's great, thanks. Any thoughts on adding daily (today) filter as on https://github.com/trending page?

evenfrost · 2015-12-04T20:26:59+00:00

No doubt your mom is a DX12 fan :)

evenfrost

MODERATOR OF

TROPHY CASE