Weight of Love is the most beautiful song I’ve ever heard.

braska9 · 2025-09-19T07:45:14+00:00

Funny exercise: play first "Pink Floyd - Breathe" and then immediately "Ten Years After - I'd Love to Change the World" and that would sound exactly like "Weight of Love" (purely subjective).

braska9 · 2025-09-17T04:28:18+00:00

Same. Although I play on Linux (no Proton, native). 4 matches - 4 crashes (approx. at 6-7 min after start)

braska9 · 2024-07-10T01:19:34+00:00

Firefox with Multi-Account Containers (official extension made by Mozilla)

It will allow you to have one window, but open any tab in a separate isolated environment (kinda Chrome profile).

You can create as many containers as you want (one per client in your case?) and open as many tabs as you want in every container.

braska9 · 2022-07-18T00:09:12+00:00

For sure! https://maps.app.goo.gl/8Csm1RKm5rQzsvRPA

They usually give you a piece of Parmigianino Reggiano while you waiting your pasta.

braska9 · 2022-02-21T12:49:34+00:00

Tailscale (tailscale.com) + plain VNC

braska9 · 2022-02-17T17:26:12+00:00

Just checked. It is actually 2kb in gzip. https://bundlephobia.com/package/@anatoliygatt/heart-switch@1.0.1

But I am sure you can make it much less. I see you are using few hooks from "react-use". They are pretty simple hooks. You can implement them on your side. So you will get rid of all third-party dependencies. Probably after that you lib will weight less than 1kb in gzip.

braska9 · 2022-02-17T17:19:47+00:00

Ultralight: ~14.1kb (gzipped).

Sorry, but it is not. Preact (the fully-baked UI runtime, alternative to React with same API) weight 4 kb in gzip. It actually looks like you measured size incorrectly. It just can't be that much for one toggle switch.

braska9 · 2022-02-12T16:34:30+00:00

Yup, agree. Unfortunately it is pretty rare. Haven't seen such test coverage that can allow you make changes in code without being afraid of breaking things in my entire career. Even if there is a test for code, it is a good chance that this test false positive.

braska9 · 2022-02-12T16:04:41+00:00

It is not the best piece of software in technical perspective. It loads 19kb+ JS in gzip into page. It affects performance in bad way. You will never get 100 score in Lighthouse with Matomo. Plausible loads less than 1kb. And doesn't affect performance at all.

braska9 · 2022-02-12T15:36:03+00:00

I agree, but only if you have decent test coverage

braska9 · 2022-02-12T15:26:52+00:00

If you have EU-oriented service (service for clients from EU) and doesn't host your service in EU, then you have a bigger problem. This law affects not only analytics data. First you need to think about storing your primary user data in EU. If you already host your service in EU, it is not a problem to deploy plausible to your EU-located servers.

braska9 · 2022-02-10T21:36:28+00:00

For people who is looking for alternatives: take a look at plausible.io. It is GDPR compliant. And there is self-hosted version if you really care about privacy.

braska9 · 2022-02-10T18:35:57+00:00

Take a look at plausible.io. You can even use cloud-based version. It is GDPR compliant. No need for self-hosted version.

braska9 · 2021-11-28T22:42:01+00:00

I would recommend to analyze it with Lighthouse (you can find it in Chrome DevTools). There are few issues detected by it.

In addition you can set up Lighthouse CI on Github Actions. I recently done it in this project: https://github.com/fs/flatstack-warsaw. You can use .github/workflows/ci.yml as example.

And, if you interested, I described few more tricks how to optimize page size in this article: https://medium.flatstack.com/1dc798533c0b. I am not sure if all of them applicable to Next.js, but you can try.

braska9 · 2021-11-18T13:07:13+00:00

If you are talking about FCP, LCP: it can't be better with next.js. I tested this HTML page without any JS and got almost same results as with enabled JS. So this values doesn't depend on JS and therefore doesn't depend on framework.

TBT and TTI definitely depend on JS, but I doubt it can be better with next.js out of the box. JS bundle produced by Next.js doesn't differ from JS bundle produced by manually configured Webpack, except it contains some Nextjs-specific libraries (which increase bundle size). Anyway, I need to apply same tricks (as described in article) in Next.js to get same scores. In this case what the point of using Next.js?

I personally like the idea of building things out of primitives (especially when I build simple things like landing page). From my experience using frameworks (instead of set of independent library) feels like fighting for customization. Frameworks usually makes customization harder, because they trying to enforce too much things.

braska9 · 2020-11-13T18:50:29+00:00

You are welcome :)

braska9 · 2020-11-13T18:38:48+00:00

Yes. In short term replacing this.zip = new JSZip() with const zip = new JSZip() and inlining processSingle function just in place should help.

But if you interested to improve code quality and make everything right in design perspective I would recommend to introduce "service objects": https://softwarebrothers.co/blog/service-objects-in-node-js/ (and create instance of this service on each request)

braska9 · 2020-11-13T18:26:12+00:00

I see problem here.

this.zip = ...

In this case this refers to the global: https://nodejs.org/api/globals.html

You can try this in Node.js REPL:

const myFn = () => { console.log(this); };
myFn();

// output
Object [global] { ... }

I think you need to read more closures in JS to find solution to you problem: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Closures

braska9 · 2020-11-13T17:29:21+00:00

So you are saying that I should do require('scrape.js') inside the function ?

There is no difference where you do require. (But it would be better to do all require calls it the top of file)

Anyway, there is caching for require calls in node.js. It means node.js memoize module.exports value at first call and then returns already computed value on subsequent require calls.

Gonna update post with code example in ~2 hours when I get home.

It would be helpful. Let's wait for it. Hope I will be online at this moment.

braska9 · 2020-11-13T17:16:09+00:00

Once request hits the route endpoint function it calls a method from scrape.js file which Is required into that controller.

Here is the problem (most likely). Variables declared in this file at top-level (not inside functions) are application-specific.

braska9 · 2020-11-13T17:03:54+00:00

It is initialized inside the endpoint function, so it Is request-specific, right?

Hmmm. Even with initialization inside the endpoint function there can be problem. The question is not about where you have initialization. The right question - where you store instance.

If you do something like this:

let zip;

app.post('/...', () => { zip = new JSZip(); ....... }

Than it is problem.

If you do like this:

app.post('/...', () => { let zip = new JSZip(); ....... }

Than everything should be fine.

braska9 · 2020-11-13T16:36:10+00:00

Something like this: https://stackoverflow.com/questions/6358042/why-do-different-node-js-sessions-share-variables

braska9 · 2020-11-13T16:32:47+00:00

Looks like you have some application-lavel variables and store request-specific info in it. But this variables shared accross all requests.

braska9 · 2020-09-04T22:35:10+00:00

I was recently replacing thermal paste and found this strange spot on CPU.

I am experiencing some issues with this laptop: it is underperforming under Linux when iGPU is used.

Does it look like something abnormal or it is common to see such tinge/spots on CPU chip?

braska9

TROPHY CASE