zlatko

joined 1 year ago
[–] zlatko@programming.dev 2 points 3 days ago (1 children)

considering where the garbage came from, maybe we should stop shitposting :)

[–] zlatko@programming.dev 1 points 4 days ago

(sorry for the late response, I have to get in the habit of checking my Lemmy account)

No, I get that - a stylesheet denotes a class by having a dot. A JavaScript API for adding a CSS class omits this redundancy.

I was saying that the author might not be wrong to want to avoid the redundancy in rust example as well (since it explicitly mentions CSS classes).

[–] zlatko@programming.dev 3 points 2 weeks ago (2 children)

I mean, it is not embarrassing for you. In the browser, the CSS's "native platform", you add classes, via the JavaScript API, without the dot. It's not a stupid assumption.

To have to add the dot in the CSS class name seems a bit of an oversight in the gtkrs API.

[–] zlatko@programming.dev 2 points 3 weeks ago

Actual programmer

[–] zlatko@programming.dev 1 points 3 weeks ago

I wonder if JJ anonymous branches would be something that solves this. I've only read about it, have not used JJ yet.

[–] zlatko@programming.dev 2 points 3 weeks ago

Or meet old ideological dogs like me :P

[–] zlatko@programming.dev 4 points 3 weeks ago (1 children)

Much better integrated refactoring support. Much better source code integration support. Much better integrated debugging support. Much better integrated assistive (but not ai) support.

Vscode can do many things IntelliJ can, but not all, and many of them require fiddling with plugins.

Usually, JB is also faster (if your dev machine can run it, but in my experience most devs have beefy machines).

[–] zlatko@programming.dev 1 points 3 weeks ago

Zed is also lightspeed fast compared to either vscode or JetBrains' stuff.

[–] zlatko@programming.dev 1 points 3 weeks ago

I would expect it to rise. I still think it's worth it, if it's a good tool for you. IntelliJ is really a good product, even if they do have their downsides. In a commercial environment, it's totally worth it to buy a licence per developer, if it makes them more productive.

[–] zlatko@programming.dev 1 points 3 weeks ago

I don't mind paying for tools that help me do my job. For several years I even had a personal licence for "all products pack" thing. Their IDEs do a decent job.

There are better tools for specific things, but overall as an IDE, it's pretty good and makes you effective. And especially if you have to use Windows, it's integrating enough tools that you don't have to mess with the Windows crappy tooling that often.

That said, it's still a big fat slow IDE. For a while now I've been using neovim my modernized Linux toolkit and for the most part, I'm happier with it then I was with IntelliJ and Goland and the rest. Happier enough to not having a licence for JetBrains any more.

And recently I've looked into Zed. Zed looks pretty neat so far, but it's still under development. Once things stabilise there, I might commit to it and switch full time to Zed. It's got a few nice things that I miss from IntelliJ, but it's way, way more responsive.


Back on topic: I wanted to say I don't mind paying for IDEs, if they're good tools. But this is more of an ideological challenge and I'm always trying to keep myself from overreacting. So while I don't agree with you in general ("don't trust paid IDEs"), I might agree with you specifically ("don't fall for JetBrains' lure and Microsoft-like tactics").

[–] zlatko@programming.dev 2 points 3 weeks ago

JetBrains git integration is a known mess, true.

[–] zlatko@programming.dev 10 points 3 weeks ago (2 children)

Even this is forum-like though. It's a forum of people talking about a topic that interests them. It just happens to be distributed.

 

I'm building a NAS for the first time on my own, so I wanted to share the story so far here.

I'm not a stranger to custom builds, in fact I don't think I ever bought an assembled PC (not counting second hand 386 box a million years ago). But this is my first small, low power build, so it's not perfect, I already ran into a wall (more later).

I base the build on an AsRock mini-ITX board, the CPU is included, it's passively cooled, low power consumption but still powerful for a NAS. I'm sticking it into a Node 304 Fractal Design case. Here's the full list of parts I got:

  • AsRock J4125-ITX board with a Celeron 4125 (4-core CPU)
  • 8GB DDR4 RAM (a Crucial kit)
  • a 500GB NVMe SSD (which I can't use)
  • a couple of Seagate IronWolf 4TB drives
  • 90W PicoPSU and some no-name power brick
  • Fractal Design Node 304 mini-ITX case.

I planned to have an SSD for OS, these two disks for my photography and media, and then later on expand with more storage (preferably SSD, when I can afford it).

As mentioned, I messed up: the M2 slot on the motherboard is a "Key E" slot. I never bothered with these keys before, so I didn't know that a Key E slot does not have a SATA protocol, it won't take my SSD.

Another thing, the PicoPSU is a 20-pin power supply, and the board has a 24-pin slot. It should still be fine, the specs say that this is still okay, but I'll have to see. According to my back-of-the-napkin calculations, 90 Watts should be enough power for the mobo and CPU, the SSD and the two spinning disks.

Anyway I'll get a regular SATA SSD tomorrow and see how it's shaping up. Let me know if you want me to post more on my progress/end result or if you have any questions.

 

What would be a good investment now? I want no-frills Linux support, good CPU, lots of RAM, decent screen. If I'm actually working, I'm almost always docked, but when not, I would not mind a good battery as well. I want this primarily for personal use. I don't mind upgrading parts myself (if that's still possible), like getting a stronger SSD or something.

I used to own a T420 (and some other ThinkPads as well, but this one was used). It was an incredible investment at the time, used laptop price, build quality and feature on par with laptops 6, 7, 8 years younger. I wonder if this is still something you can get away with.

view more: next ›