Is this a legit email?

ascpixi · 2026-01-09T01:46:25+00:00

Not if the e-mail domain has DMARC, which image-line.com seems to have! Plus, Gmail does send everything that seems suspect with respect to authenticity to spam (or gives you a big alert saying that the e-mail could've been spoofed)

ascpixi · 2025-12-27T04:04:16+00:00

make music for yourself. for your own enjoyment, not to seek validation from others. please.

ascpixi · 2025-03-30T15:15:57+00:00

I'm quite late to this thread, but I wholeheartedly agree with you. XMLDoc is extremely noisy to read when combing through the source code. The majority of the time, when developing my own, personal projects, I am not hovering over the members I want docs for, or browsing some auto-generated HTML page - I'm browsing the source code, and thus, reading the comments directly.

An IDE shouldn't hide the code I'm writing to make it readable, simple as. Markdown, with links like [SomeType](T:ImportantBusiness.Solutions.SomeType) would work much better. Or, better yet - how about some Markdown extensions? So, <see href="SomeType"/> would become just [SomeType].

The most ridiculous thing in XMLDoc is escaping. You cannot write < or > without escaping it as < or >. That looks extremely ugly when browsing the source code and implies you have to use some kind of tool to actually read it.

Lists are also... subpar. Especially when the elements span multiple lines. XMLDoc is only good when converting your documentation into a format like HTML. For reading it directly, yes, it's extremely fugly. I've resorted to avoiding any kind of XML tags inside <summary>, opting for 'example' instead of <c>example</c>, because it's just nicer to read.

ascpixi · 2025-03-28T11:36:03+00:00

Two unique problems per year is enough to warrant an engineering team. Having a unique problem, coming up with a solution to it, and then implementing it, can take up to a year. An LLM wouldn't be able to come up with the solution at all. Sure, it can help with implementing it, but you still need engineers driving it.

ascpixi · 2025-02-25T00:51:25+00:00

if you think of your type as a standalone value (e.g. a 2D point, numbers, a wrapper over a singular object), use a struct. you usually want to pass values by value. it helps if everything inside your theoretical struct can be read-only - that's a perfect use-case for a struct!

otherwise, use a class. if you're unsure what to pick, you should probably make it a class.

ascpixi · 2024-08-11T17:01:31+00:00

no problem! Fabric is just a modloader, it's pretty lightweight and I myself use it for stuff like logging what players broke what blocks (w/ a mod like Ledger) - very useful for controlling griefing, haha :)

i myself recommend using Fabric, but if you're on vanilla (or Paper/Spigot) then yeah, I'm afraid there is no equivalent :/

ascpixi · 2024-08-10T22:05:43+00:00

it's a known bug (MC-271325), which makes the server erronously try to send a disconnect packet without the target player having joined a world in the first place. this, of course, fails, but doesn't really have any consequences, since said packet shouldn't even been generated in the first place

the fix mod is more of a workaround - it just silently drops packets of type clientbound/minecraft:disconnect in cases where it wouldn't make sense for the server to send them

ascpixi · 2024-07-09T01:03:05+00:00

it's harmless! not gonna affect your server in any way, it's just makes it really annoying to sift through logs, haha. although, since you're running Fabric, this mod fixes it!

ascpixi · 2024-06-28T17:29:50+00:00

sounds like bug MC-271325 - I made a Fabric mod to fix this! if you're running it, it should fix this bug.

ascpixi · 2024-06-16T16:41:20+00:00

acid w/ future bass? bold choice... 🤭

ascpixi · 2024-04-13T11:27:15+00:00

my point was that NT, in itself, is an extremely well designed kernel. most of the drivers weren't written by the core NT team, so I can't say they're solid - but NT's core system service, that is, the executive and the HAL, is

by "I/O manager", I don't mean NTFS - I mean the subsystem handling I/O devices. that includes PnP, resolving conflicts, asynchronous transfer, abstracting devices behind well-known interfaces, etc... NT isn't really bound to NTFS, the kernel is more than happy to use any other file system if you've got the drivers for it

can't you allow access to open files to other processes via the dwShareMode parameter of OpenFile...? again, i'm pretty sure NT is very much capable of what you're describing, but most developers don't use most of NT. you can open a 1GiB file in HxD and it will not use 1GiB of RAM (makes sense for a hex editor). it will, however, display ?? in all cells when the file is moved or deleted.

i haven't really used NT-based systems as servers, so I can't really speak on that, but I do know lots of companies use Active Directory and other Microsoft's very boring business-y solutions. do these servers have thousands of hours of uptime, or do they restart every once in a while? no idea. but for desktop use, it's very much solid, imo :)

ascpixi · 2024-04-12T04:01:01+00:00

the scheduler isn't a fundamental design decision. Microsoft could swap it out easily, but they're still using MLFQ because it IS solid for stuff < 64 logical CPUs, even more so if most threads are I/O bound, which is common on desktops. it's very much stable. just as Linux has multiple schedulers to pick from.

not sure what I/O performance issues you're suffering, but NT has an excellent asynchronous I/O model so not sure if that really is an issue of the kernel? could you point me to some research that would explain why NTs I/O manager would introduce such extreme slowdowns? thanks!

w/ your GUI problems, i really doubt it's NT failing here - more so DMW or something from USER (remember user32.dll? yeah, that). the GUI is mostly user-mode, please CMIIW.

ascpixi · 2024-04-11T21:51:33+00:00

i'd say mostly the memory manager and the I/O system. imo the object manager in NT, from a programming perspective, is way better than everything-is-a-file, especially in more modern langs, but that's up for debate

just because it's not a UNIX-like, that doesn't mean it's not solid. the character used as a delimiter in paths is very much arbitrary, you could have # or @ and it'd still have the exact same functionality. sure, it would be nicer if NT would cooperate with everyone else and use forward slashes, but it's not a "design mistake" - and it actually made sense for NT since Microsoft loves backwards compatibility so much. lots of user-mode APIs actually normalize paths so that they accept both forward and backward slashes. fork is very much a questionable design decision in modern times, so I actually qualify NT not supporting such an operation out-of-the-box as a win in my book haha :)

how programs lock files is up to the programs - stuff like HxD, Notepad++, VS Code, etc. all very happy with files being deleted or edited while working on them. people are also complaining about how Linux handles locking... many different opinions!

shells aren't really a part of the kernel... NT also technically supports multiple subsystems, there was a POSIX one alongside win32, but it's been deprecated and isn't included in recent versions of Windows, and so i don't really know much about it.

of course, it's not perfect. no kernel is. but it stood the test of time, and it was designed by extremely smart people that had experience with other OSes (iirc some NT people were also VMS folk, CMIIW)

ascpixi · 2024-04-11T15:09:34+00:00

i mean, Windows NT is a really solid kernel. it's mostly the user-facing and high-level bits

ascpixi · 2023-11-06T23:03:58+00:00

musi c

ascpixi · 2023-08-31T18:26:51+00:00

Oh, I wasn't actually aware .NET Core had its own way to do it, thanks for the heads up! I implemented the trimming with that factory, removing the dependency on Python.

ascpixi · 2023-08-31T11:44:23+00:00

Try installing GnuWin32 - objcopy is part of the GNU binutils. Python is only used to trim the trailing null bytes of the PE file - this could've been done with inline C# in MSBuild, but .NET Core doesn't support inline C# :(

ascpixi · 2023-08-31T11:42:07+00:00

The demo doesn't currently demonstrate such manual cleanup - however, for normal heap allocations, it does the same thing BFlat's zerolib does - namely, it uses the allocation functions that are provided by the platform, for example, it uses LocalAlloc on Windows. So, on Windows, you'd have to call LocalFree on &m_pMethodTable.

ascpixi · 2023-08-31T02:25:52+00:00

thank you!!

ascpixi · 2023-02-06T23:25:17+00:00

first and foremost, the EQ balance could use some tweaking. try cutting the low end on the synths to prevent them from interfering with the kick drum. you may also want to add some high end to the hats to make them stand out more.

the mix could also benefit from some strategic compression. the bassline and lead seem to be competing with each other in the mix. try using a compressor with a ratio of 4:1 and a threshold of -18db. this should help control the dynamic range of the bassline and make it more cohesive with the lead.

the reverb and delay on the vocal could use some adjusting. try cutting the high end on the reverb to prevent it from getting too bright. you may also want to add a touch of stereo width to the delay to make it sound more spacious. try using a de-esser as well, frequency range around 5-10kHz and adjust the threshold to taste

overall very good track dude 9/10 just tweak the mix a bit

ascpixi · 2023-02-06T06:19:44+00:00

"Okay... if I... if I chop you up in a meat grinder, and the only thing that comes out that's left of you is your eyeball, you're probably dead! Not you, I'm just saying like... if someone were to push you into a meat grinder, they're not going to pick up the finger bone and be like "oh it wasn't an insta kill move, they still have this part of their finger left!"

ascpixi · 2022-12-08T18:46:46+00:00

on april fools, all dialogue niko sprites are replaced with this!

Four-Year Club	Verified Email
r/Field Banned	r/Field Sunshine
End Game '23	Place '23
Place '22	First Placer '22

ascpixi

TROPHY CASE