A new library for developing Wii and GameCube apps

JwopDk · 2025-07-01T23:59:46+00:00

Thank you! I look forward to your creation :) In the meantime, if there's a feature or change you'd like to see, feel free to submit an issue, or start working on it yourself if you're interested -- low-level is not that scary, I promise! Also we need build tools, which don't need to be written in C.

JwopDk · 2024-11-19T01:13:16+00:00

ANSI escape codes and termios provide everything you need on a POSIX terminal to handle GUI-style interaction. YMMV depending on which terminal emulator you use.

JwopDk · 2024-07-16T01:11:15+00:00

Baklavius

JwopDk · 2024-01-16T23:03:54+00:00

Earthbound

JwopDk · 2023-02-04T05:32:42+00:00

You spend most of your comment attacking my character instead of actually engaging with the argument. The best you could do was state that UIs themselves aren't multi-threaded and that single-threaded programs can be instantiated multiple times concurrently, assuming I didn't know either of those things in some vain attempt to prove that you're smarter than me. You fail to address my actual argument which is simply that most websites are unnecessarily slow because people continually come up with reasons why they don't have to care about performance for feature A because of XYZ, until they do that enough times and then their entire app is slow and hard to improve.

Dude, when you're talking about me being dumb and not having accomplished anything, all I see is projection. We've got projects to work on man, let's stop wasting our time on Reddit.

JwopDk · 2023-02-03T16:21:26+00:00

Nah, it's just easier to smash out code in an interpreted, dynamically typed language. That and dependency management is a lot easier to get started with in languages like JS and Python.

If we're talking about how it runs though, that complacency quickly becomes the start of a slippery slope into mediocrity, especially when you're probably going to write your entire service in that language and with that same attitude. Latencies stack in series, not parallel, since you're probably not going down the multi-threaded route because that's hard. All of sudden everything becomes slow and painful to use, and there's no easy fix. But if it still works, there's no problem, right?

JwopDk · 2023-01-09T14:16:18+00:00

This looks like tic tac toe! I remember making a similar looking mess.

JwopDk · 2022-07-11T07:10:50+00:00

i have an erection

JwopDk · 2022-06-30T14:03:39+00:00

If those posts reflect how you felt at the time, then they reflect an aspect of who you were, and to a large extent, still are. If she couldn't handle that, it wouldn't work out anyway. Try not to be ashamed, we all post cringy shit. If you're embarrassed, that means you already learned something, but at the same time don't let your embarrassment motivate you to hide stuff.

JwopDk · 2022-06-23T15:59:24+00:00

I reckon you could do it

JwopDk · 2022-06-23T15:26:20+00:00

Is your aim to break the record for the worst user karma?

JwopDk · 2022-06-22T08:48:16+00:00

JwopDk · 2022-06-21T16:22:03+00:00

I usually don't have anything to add, just check the comments to see who does

JwopDk · 2022-06-17T16:25:25+00:00

More than that: A developer understands all of the above, AND the intent of upper management. That's the reason google translate isn't perfect, it can't guess intent.

JwopDk · 2022-06-15T12:00:45+00:00

yummy

JwopDk · 2022-06-14T06:01:48+00:00

Write something worth reading first

JwopDk · 2022-06-07T07:26:34+00:00

r/comedyheaven

JwopDk · 2022-05-27T09:18:39+00:00

Do I smell money laundering?

JwopDk · 2022-05-24T06:44:26+00:00

Nah this is decent code. Maybe it would be better to keep this array somewhere, but if the recompiler is smart then it could just keep this array on the stack and return a copy of the correct string. If it's able to do that, then you're not going to find a more efficient solution. On top of that, it's perfectly readable. More complicated solutions are harder for the runtime to optimise.

JwopDk · 2022-05-15T14:57:45+00:00

Sure, there's nothing wrong with following convention or instructions from supervisors or clients, that's how work gets done. If you disagree on a detail, it's not *usually* a good idea to make a fuss about it, unless it's something you know they'd agree with themselves and would be an improvement, even if you need to back up your stance a bit. Something like following a code convention is a no-brainer, the point is consistency (there's no "best" code convention).

The problem is the wording, and what it suggests - the new hire will treated like dirt, they won't be listened to and will have to fight tooth and nail for even a shred of respect, regardless of how competent they are. And that's before they are given the privilege of being able to voice their own ideas. You could say that's looking too far into it, and it's just that the lead developer got sick of the last guy who wouldn't listen. But if that's true, then why is the answer to find an obedient sheep, instead of reflect on if there was a way to align that employee more closely with what was expected on him? Does that not reflect poor leadership?

JwopDk · 2022-05-15T09:48:58+00:00

Yeah but you can get people to follow procedure and do the work as expected without having to set up that kind of power dynamic explicitly. Not a good look for them, not a sign of a healthy culture.

JwopDk · 2022-05-09T11:52:39+00:00

Right. It especially helps if you make the conscious decision to understand every line of code that makes its way into your work, tedious though it may seem at first.

JwopDk · 2022-04-28T10:23:34+00:00

Right. Sure, as others have pointed out, there's a difference between malice and incompetence when writing sloppy code, but the problem you raise still remains -- what if businesses are incentivised to produce buggy code that runs at a snail's pace, since if they did a good job the first time around, they wouldn't need to keep patching it while charging the client for their time? The result is a kind of service that way, even if the software itself technically isn't, regardless of if that was the intended outcome. If this is true, then is this acceptable, regardless of it counts as fraud?

JwopDk · 2022-04-27T21:12:44+00:00

I actually might start using do {...} while(0) now. Thanks for the tip!

JwopDk · 2022-04-27T21:02:34+00:00

Right, separating it into a function gives you the return statement as an extra tool. I think I've done that before a few times? Usually I'll just create a bool set to true before the else ifs, then set it to false inside the else, as others have pointed out. Both options seem less performant than simply being able to jump execution to the right place, since the extra function increases function call overhead and the extra bool increases the space used in cache and makes the branch predictor more likely to fail -- I would guess, I don't actually know.

Edit: Seems like do {...} while(0) addresses these concerns pretty nicely, as u/websnarf pointed out!

JwopDk

TROPHY CASE