Pannoniae

8 ms·

1.
by Pannoniae 4d ago
Until some kind anon hopefully leaks it...
2.
by Pannoniae 4d ago
>LLMs haven't created a I don't think this is true. They very well might have, but a specific one, not a generic reusable version you find on GitHub or whatever.
3.
by Pannoniae 6d ago
that would only be true with a perfectly expressive language with both high-level and low-level features, perfect support for any kind of metaprogramming and a godly optimiser. ofc we don't have that, so code is compressible, and c
4.
by Pannoniae 6d ago
No, rapid development is essential when you're making games. It's not a "solved science", sure you can code something up and slap some programmer art on it then ship it but you very well know that won't be usable. Y
5.
by Pannoniae 6d ago
Sadly it still feels like it's one of the languages where the language doesn't trust you, it tries to force you to do things "the right way". I do love quite a few of its design like how traits are, not forcing every met
6.
by Pannoniae 8d ago
Only the ones you could ask afterwards;) This is propaganda pretending that suicide is an impulsive decision. That's a category error because in many cases, it is not. If there was more focus on screening for impulsive thoughts and d
7.
by Pannoniae 8d ago
Thank you for opening my horizons :)
8.
by Pannoniae 8d ago
You're so close to getting it. If you could somehow shelter people from the idea of ending it, you'd have created the torment nexus. People who do so usually do it because they see negative things coming up and they're too ti
9.
by Pannoniae 8d ago
"It is difficult to get a man to understand something, when his salary depends on his not understanding it." - Upton Sinclair
10.
by Pannoniae 9d ago
I wholly agree, processors are strongly typed, even if there are holes like using integer instructions on floating-point values in XMM regs, very insightful comment:) btw a bit of nitpick: to be fair basically no one uses x87 anymore, it&
11.
by Pannoniae 10d ago
Being decent at music has definitely made me a worse programmer because I just do many things - software design, structure, names, you name it - on the vibes instead of sticking to the rules to the chagrin of others :D
12.
by Pannoniae 10d ago
This is why open source is rapidly becoming obsolete ;) There have been source-available/fair source/whatever-you-name-it approaches before. They were attacked by OSI zealots every time because it's not real open source. Whic
13.
by Pannoniae 14d ago
I also expect some kind of reaction in the future though! Just like how people generally got tired of broadcast TV in favour of YouTube or shorts, there's only a certain amount of slop someone can read and write without getting sick of
14.
by Pannoniae 14d ago
looks like we've circled back to the good old #ifdef FEATURE_AI_V2 ;)
15.
by Pannoniae 17d ago
He made middleware used by countless games over at RAD. I'd say that counts as contributing to game development.
16.
by Pannoniae 17d ago
"He didn't fully understand or appreciate the quote about premature optimization, so no one did." He ain't wrong though.... most people definitely don't get the jive for sure. Knuth was talking about a massively d
17.
by Pannoniae 17d ago
Yes, VTune is good. I'm on AMD and uProf isn't that good (it often fails to match PDB to source, it's slow / crashy, stuff like that) so I mostly use Superluminal myself (has godly UX) and only drop down to uProf when I
18.
by Pannoniae 17d ago
Sure, but there are performance issues no profiler will catch in a straightforward flamegraph reading. Some examples: 1. Your hottest loop is spilling registers which only shows up as non-local cache thrashing (i.e. some other random code b
19.
by Pannoniae 17d ago
Being I/O bound is usually a result of bad engineering practices though. If you're I/O bound, that either means the problem doesn't require much computation - which is possible but fairly rare, or more likely that your
20.
by Pannoniae 22d ago
no, you can also call ntdll (or even syscalls although those aren't stable), there's plenty of documentation on the internet but also why would you, not much point except for very niche functionality
21.
by Pannoniae 24d ago
Do you really care if it works?
22.
by Pannoniae 27d ago
>Most mainstream languages guarantee stability, certainly Rust. That's their mistake, right there... When you're upgrading software, you presumably want a better version. You can't have something better without changin
23.
by Pannoniae 27d ago
Who said a standard library can't make breaking changes? That used to be a norm some time ago. There are upsides, your program is smaller, better security because a random kid can't pwn your deps, quality and interoperability. W
24.
by Pannoniae 27d ago
The fallacy is assuming that standard != unchangeable. One can very simply....make breaking changes. Yes it will require some work to update but that's already the case when you upgrade library versions. The dependency hell doesn'
25.
by Pannoniae 27d ago
What's wrong with treating it as biology though? Even large software systems have biological aspects, their behaviour is emergent and if you want to observe how they work, a holistic approach is needed, you can't really reason abo
26.
by Pannoniae 1mo ago
1. This isn't true whatsoever. You can easily do better than std::vector (trivial relocation support, non-inlined grow), better than C# List<T> (ref T accessor, batch add API, maybe even an add-uninitialised API or in-place const
27.
by Pannoniae 1mo ago
I admit I have a hard time following this logic. If an agent has a baseline intelligence, you can... instead of using boring technology, just DIY/NIH the simplest custom solution which fulfills your requirements. And you'll usuall
28.
by Pannoniae 2mo ago
you can always combine it with a bunch of racial slurs (for western models), insert 1989/winnie the pooh references, insert a bunch of paragraphs from the anarchist cookbook then namedrop the steps to synthetise a bunch of drugs for go
29.
by Pannoniae 2mo ago
It's kind of full circle... dependency management was invented because consuming libraries or common code was hard, everyone kept reinventing the wheel and if you had some vendored code, updating it was a nightmare due to the build int
30.
by Pannoniae 2mo ago
Well yeah, for example I'm working on a codebase written mostly in 2003. The assumptions in the original code are at best tangentially relevant (stuff like "LUTs are cheaper than using ALU" or "CPU power is cheap, GPU po

More ›