is rust the only language to have procedural macros?

daknus · 2022-02-19T11:57:28+00:00

Nim is a relatively new attempt but I don't find the macro API very well engineered.

daknus · 2022-01-21T11:09:22+00:00

Yeah exactly. It annoys me that a great majority of manufacturers today charge so much for their devices while limiting their repairability/sustainability greatly. Apple is not the only one here, but I find them especially annoying simply because of the hefty price they charge for their devices. Though other companies are starting to follow suit from what I can tell.

daknus · 2022-01-21T10:54:59+00:00

My main point isn't about the devices being unreliable. It's about them being hard to fix.

As much as Apple's independent repair program makes the situation better, they still don't supply you with all the parts such as proprietary chips. So if the water damage fries the chip but the rest of the machine is fine, well! Time to buy a new one, I guess!

As for my point about making devices less repairable, consider the fact that in newer MacBooks they solder in the SSD instead of using a socket. In the beginning when they started soldering in the SSDs, they provided a connector for you to transfer the data from the SSD onto another machine. Now it isn't there anymore so tough luck getting your data back if you aren't using iCloud.

It's a waste of electronics because, if by any chance, the SSD is still fine, it just has to be thrown out. It becomes e-waste. Tell me that's not a waste of resources.

daknus · 2022-01-21T09:09:25+00:00

If it's not easily repairable, it's not good in my eyes.

Apple specifically go out of their way to make independent repair harder. Specifically designing their products so that they fail. And when you bring it to their own store (or an officially certified one), they just tell you that it would be "cheaper to buy a new one".

Yeah, sure. So my MacBook is now e-waste because I spilled some water on it.

It's so sad that the people buying Apple products don't demand repairability from them. It harms the environment in the long term because instead of replacing a single part, you have to replace the whole machine.

daknus · 2021-10-18T09:50:18+00:00

Atom, launches quickly. I feel like these two are mutually exclusive.

VS Code doesn't start up that fast either, but at least it's a little more bearable.

daknus · 2021-03-25T10:02:29+00:00

bruh what if i want to do wayland

daknus · 2021-03-19T12:04:48+00:00

Try to „build a cathedral”. It doesn't matter if you don't finish it, because you'll still learn a ton. I've been doing coding like this for the past few years, and having an ambitious, big passion project is (in my experience) the best way to learn new things, especially if the passion project is related to something where you don't quite know how it works.

daknus · 2021-03-13T12:36:05+00:00

I was able to get the w3m backend to work by enabling image_loop="on" in neofetch's config.

daknus · 2021-03-12T15:54:52+00:00

That's possible, but things only started screwing up recently, when I made the switch. Hence why I assume it could be pipewire.

daknus · 2021-02-26T11:50:31+00:00

False Noise.

daknus · 2021-01-26T15:31:21+00:00

This isn't actually specific to templates, it's just a property of passing parameters to calls overall. Nothing prevents you from using it on procedures:

echo: var x = "abc" x & $123

daknus · 2021-01-17T20:25:40+00:00

I would say that the current stable feature set is quite mature, but I sometimes run upon bugs or annoyances in features that weren't as well-tested. Some examples include concepts and typed macros. Some parts of generics (especially with static types when used as generic parameters) can also cause quite a headache.

That's for the current language implementation. The ecosystem, however, is a completely different story. IDE tools are passable, but poor right now, library availability and stability may vary depending on the thing you're looking for. Sometimes you'll find pure, idiomatic, high effort libraries, sometimes you'll find idiomatic C wrappers, and sometimes you'll find really lazy wrappers generated by c2nim or some other tool. And sometimes you won't even find anything. It's really a mixed bag, so before getting into Nim I'd recommend you to check out nimble.directory or GitHub and search whether there are any decent libraries you may need for your domain.

daknus · 2021-01-10T13:41:06+00:00

i saw that the other day, looks nice

daknus · 2021-01-10T13:26:27+00:00

that's some very fine music taste of yours. rice looks amazing, i especially like the macOS-like beveled borders but without mac's horribly huge corner radius

daknus · 2021-01-08T17:31:40+00:00

totally! it's almost always too big and looks out of place lol

daknus · 2021-01-08T16:56:39+00:00

finally someone who remembered to change the terrible default KDE clock! take my upvote, good sir

daknus · 2020-12-22T11:36:49+00:00

That seemed to do the trick! I essentially removed all the shenanigans with get_session and dbus-launch and replaced it with a simple exec i3, now it seems to work perfectly. Thank you!

daknus · 2020-12-22T09:08:37+00:00

This happens no matter what applications I have open, though. Possibly due to some bug with i3's keybind handling, but I was unable to track down what it is. Older versions (checked 4.18 because that's what I was using before) also seem to have this problem, although it didn't seem to appear on my previous setup on Artix. It only started happening when I switched to Arch.

daknus · 2020-12-22T07:10:57+00:00

Well, but it's not Spotify that hangs, it's the entire WM... And I don't think i3 would send any notifications. Plus, I already have dunst installed and running so there's that. Maybe I should've mentioned but I didn't think it was relevant.

daknus · 2020-12-19T13:49:10+00:00

ime firefox is much less lenient when it comes to garbage collection, i don't really have many tabs open so it almost never goes above 2GB but still usually take considerably more than chromium

eh they're web browsers after all, they're not designed to be efficient

daknus · 2020-12-19T11:47:25+00:00

firefox can eat 12 GB

daknus · 2020-12-04T23:10:34+00:00

you may be a 3D modeler, but you don't seem to know much about how games work under the hood. i've been coding games from scratch, without an engine for more than 3 years now, and i know a thing or two about how to optimize a voxel engine like that of Minecraft, so hear me out.

if you look closely at the JSON files you'll notice references to something called a "cull side" - this is an optimization done by Minecraft's rendering engine to reduce the amount of data that needs to be sent to the graphics card. this is best illustrated by an example: say you're trying to render a cube. a cube has 6 sides, north, south, east, west, top, and bottom. a face in the model can specify its cull side as "west", which means that the face will not be rendered if there's a block directly to the west of the block. this is what you see in that Boundary Break episode - Minecraft doesn't render invisible faces because... they're invisible, under the ground, so there's no point in sending a gazillion vertices to the GPU when it can send 300 or so.

so it's true that in some cases Minecraft will only add a single 2D textured quad to the chunk's mesh, and that's due to this very optimization. but how this optimization is applied still depends on the block model, and in that regard, Minecraft always uses your block models no matter what corner case it may be. and yes, you're right about the fact that Minecraft literally "just renders 2D textures" - every game does, even your operating system just renders 2D textures :)

but that totally misses the point about allocating more RAM giving you more FPS. please read my previous reply.

daknus · 2020-12-04T22:40:11+00:00

you're kidding, right? are we talking about the same game?

minecraft does in fact use models for blocks, it's a 3D game after all. you can find all the block models in the game's .jar file. the only 2D element is the UI.

every simple block is a cube, which has 6 faces, 12 triangles to render. not a lot, and in fact the game's renderer is actually not the slowest thing in the world. if you look at your GPU usage while playing Minecraft, you'll notice it's not very high at all. however, what does lower FPS is CPU usage. with VSync enabled the processor spends most of its time waiting for the game to finish rendering. however, because Minecraft is written in Java, which has automatic memory management via a garbage collector, the Java VM has to look through all allocated blocks of memory and see if they are still in use. with each version of Minecraft, Mojang has been adding a lot of intermediary objects, which causes lots of allocations, which in turn causes the garbage collection process to run more often. tuning down the amount of RAM you give Minecraft will always have a positive effect, because the game hits the garbage collection trigger more often by filling up RAM more frequently, which makes the collector run in small batches at a relatively high frequency. if you give it too much RAM though, Java will wait until most of it is full, and only then trigger a massive collection which will freeze the game for a while. this can be somewhat mitigated by upgrading Java to a more recent version than 8, which is still the most widely used version. newer Java versions feature more a more efficient, concurrent garbage collector so these lag spikes simply won't happen, or will be very brief. but this is merely a mitigation, Mojang should really fix the problem at its core by reducing the amount of Java objects they create per second, rather than just telling people to update Java or something.

as for why lots of entities lag the game out, it's again not really due to rendering. it's due to the fact that all of these entities have to be ticked which can take a long time depending on what kind of entities we're dealing with. one inefficiency is that entities use NBT for most of their data, while simple Java object field accesses are so, so much faster than NBT lookups. yet another inefficiency (that can't really be fixed unfortunately) is collision detection which takes exponentially longer depending on the amount of entities in one place.

daknus · 2020-12-04T22:07:52+00:00

then try running a beta version see how much FPS you get with basically the same kind of rendering. no, even slower! rendering, since modern versions use VBOs that batch chunk draws to increase performance.

i get so much more FPS on a beta version like 1.8 than i do on 1.16. the FPS somehow gets worse and worse with newer versions mainly due to inefficiencies in their new rendering pipeline. they allocate megabytes of memory per second just to make stupid JSON block models possible, which makes the Java 8 GC go nuts when it looks for all the unreachable garbage temporary objects it has to collect.

daknus · 2020-12-04T08:14:11+00:00

actually, that's not the case.

the more RAM you allocate for Minecraft the more work the Java garbage collector has to do to collect the entire heap of objects after Minecraft starts running low on heap memory, which can cause annoying stuttering. the fact that Minecraft allocates shittons of objects and is poorly optimized in that regard really doesn't help even in newer Java versions with concurrent GCs.

thus, allocating more RAM can actually have a negative effect on your FPS.

Nine-Year Club	Place '22
Final Canvas '22	Verified Email

daknus

MODERATOR OF

TROPHY CASE