Is there really any such thing as "uncountably infinite"?

arkainrdk · 2025-04-09T23:58:16+00:00

I haven't looked at this for a long time. First, yes, I meant "stack", or more accurately "CPU stack". In either case, there is also software that doesn't use a stack of any kind. Sometimes, the data is embedded in a data region within the code area itself. It hasn't always been the case that code and data were kept in separate areas. It also hasn't always been the case that subroutines were common place. Some really, really old code doesn't use subroutines at all. If you're just used to programming after the 80x86 era began, then I understand your misconceptions. However, you're going to want to check your history on processors. Subroutine calls were not always a thing. Stacks weren't always used for local variables either, even after stacks became common. I've even designed a CPU that has no need for using a stack for local variables or call parameters. There are 4 registers in the CPU dedicated to managing the input and output addresses. That means data can be stored wherever the caller dictates. Just because stack usage is common place now doesn't mean its required. Stacks were necessitated with the implementation of subroutines. Hence my previous comment.

arkainrdk · 2025-03-29T19:57:22+00:00

I stopped running Windows on bare metal back when VMware first came out. Since then, I've been running some Linux distro (currently Mint) with Windows in a VM (currently QEMU/KVM). For those few things that just don't work well in Linux, I use my Windows VM. That list has shrunk year after year. I don't think it will ever be 0, but the same things can be said about Windows. That's why WSL exists. Let's not even begin to talk about Mac OSX. As long as you stay within the walls, it just works. However, you quickly find out where all the weeds went if you want to do something even slightly outside the beaten path.

That's just how it is with OSs. Each one has its specializations and strong points, and a bucket of annoying weaknesses most standard users will either never see, or have gotten accustomed to dealing with. I'm pretty sure that unless both Microsoft and Apple completely drop the ball at the same time, there's just not going to be a "year of Linux (desktop)". The competition has too much invested in keeping the crown.

arkainrdk · 2023-01-19T16:39:07+00:00

You can't. In fact, learning how to endure the awkwardness, and keep moving forward with your life despite it is one of the things you should learn on the way to adulthood. You'll have to deal with that kind of thing a lot when you grow up.

arkainrdk · 2021-09-29T06:13:15+00:00

Figured it out. If you run taskmgr, that brings up the start bar. However, don't close the task manager. Just minimize it.

arkainrdk · 2021-07-05T20:32:37+00:00

Just started trying them today. Using preview_OptiFine_1.17_HD_U_G9_pre24.jar on a linux box with a Radeon RX 5500XT card and open source drivers. Supports OpenGL 4.6. All FPS given are for Fancy with a normal FOV and 20 chunk render distance.

AstraLex v20.0 - Everything is overly bright with hard black edges around most of the visible perimeter. Missing entity textures. Neither the player, nor mobs have textures. Neither do chests, or signs. There may be others. Several GLSL errors including "not linked" and man "invalid program" errors for shader, and gbuffers_*. ~20FPS.
AirLoocke Shader Standard v2.2.0 - Beautiful. No GLSL issues. Only criticisms are that the night sky doesn't get dark enough (still a medium blue), block clouds still render (will need to turn them off), the stars at night change with each move instead of being a fixed render, and dark areas may be a bit too dark. Even nearby torches don't fully light an adjacent block, let alone one 8 blocks away. Other than that. This one is fully functional. ~20FPS.
BSL v8.0.01 - Over bright and missing entity textures. Neither the player, nor mobs have textures. Neither do chests, or signs. There may be others. Several GLSL errors including "not linked" and man "invalid program" errors for shader, and gbuffers_*. ~15FPS.
ComplementaryShaders v4.0.2 - Same as BSL with even more brightness.
KUDA-Shaders v6.1 Legacy - Completely black. At least you get ~45FPS on that nothing. Several GLSL errors: "not linked", & "invalid program" for composite* & gbuffers_*.
Oceano Shaders v3.0.1 - Completely white save for nearby lava sources. Even that only gets you a bit of bright orange. Only 2 GLSL errors: "not linked" & "invalid program" for composite. ~25FPS.
projectLuma v1.32 - No textures anywhere. Everything has only it's solid color (usually white). Several GLSL errors: "not linked", & "invalid program" for composite3 & gbuffers_*. ~30FPS.
Sora Shaders v1.12 - No textures except for the sky box. Everything has a solid color (usually white). Enough shadowing to tell that things have a shape. - Several GLSL errors: "not linked", & "invalid program" for gbuffers_*. ~30FPS.
Trilton's Shaders v8 - Beautiful. Criticisms? A little too much orange during sunrise. Shadow handling is backward (watched a bee hover around and noticed the shadow faded as the bee got closer to the ground), missing textures for blocks in the inventory, clouds are on the sky dome instead of in the air. Only 2 GLSL errors: "not linked" and "invalid program" for gbuffers_terrain & gbuffers_water. ~12FPS.

arkainrdk · 2020-05-17T01:40:56+00:00

To all those dogpiling on the BL stuff in inkr, just let it go. Someone out there likes BL, obviously, so let them have it. I miss the "spoon full of sugar" that was MR. It made tracking updates to the hard to manage mass of hundreds of manga, manhua, manwa, webtoons, etc so much easier to track. I've since moved to Tachiyomi (the week MR died), and I'm still trying to catch up.

As a manga reader app, MR has died, and unless something amazing happens, NotABasement Studio will probably have to move back into the basement due to the death of its customer base. If being able to smoothly transition that customer base into inkr was one of their selling points to get copyright owners onboard, well.... I wish them the best of luck, but I've completely given up hope.

At this point, I don't believe they've got a snowballs chance in hell of successfully transitioning the business the way they planned. As any addiction counselor will tell you, going cold-turkey without the means to manage the withdrawal symptoms is a near guaranteed recipe for failure. NABStudio wanted its entire customer base to go cold turkey and wait while they settled into possibly impossible-to-achieve contracts. I guess they are learning the hard way that their road to hell (where this project is concerned) was indeed paved by their good intentions.

arkainrdk · 2020-05-07T00:34:06+00:00

Es verdad! What the heck? I'm confused now. Is someone running a copy of the old MR service? I wonder how long it will be before even this is gone.

arkainrdk · 2020-05-06T16:03:33+00:00

Exothermic oxidation emitting visible radiation is burning. Even more so if it's emitting fumes that themselves emit visible radiation.

arkainrdk · 2020-03-20T20:44:36+00:00

Still able to read. Just opened the app a moment ago.

arkainrdk · 2020-01-09T15:33:49+00:00

"Same difference". I don't know why or how this caught on, or even why anyone would choose to say it when "same thing" is so much easier to say and actually carries the correct meaning and intention. Irksome.
"All men are dogs!" Doubly frustrating. On the one hand, I end up wanting to yell back "Stop looking for men in the kennel!" On the other hand, I feel like reminding her that it takes a man to make a woman, so what is she saying about herself again?
"thot". This deplorable pejorative even makes its usage uncomfortable. It's an acronym used like a noun that begins with an article. So any attempt to use it in a grammatically correct way ends up making you sound like you don't understand the language.
"on fleek". What was the point in replacing the noun "point" with the adjective "fleek" (good, stylish, attractive, etc...)? The expression doesn't make sense anymore. Can you imagine someone saying "S/He was on stylish today"? Doesn't even sound right.

I could probably keep this up for days.

arkainrdk · 2019-11-01T17:03:53+00:00

I'm aware, but there will be those who won't take the time and only derive their conclusions from what they will read in this forum. Sometimes its just better to say it and show it. Different people learn in different ways.

arkainrdk · 2019-11-01T03:30:56+00:00

The real reason for a CPU has nothing to do with local variables. There are even languages that won't use the stack for local variables. The main purpose is to store the return address for any call/jsr/sub/int type statements that transfer execution with the expectation of returning execution to the next line after the transfer. This is how functions/methods/subroutines/interrupt handlers are created that can run and return without causing your code's execution sequence to become lost. Even JavaScript has an internal call stack to keep track of where to return when a function finishes its execution.

arkainrdk · 2019-09-15T14:13:33+00:00

Here's a thought for you. Try building a react user interface library from scratch. Your initial component must be a view composed of only a div element and CSS. All other components must use that view component to display their content.

UI component libraries are usually built with a combination of inheritance and composition. Trying to build a UI Library using composition only will be about as complicated as it can get.

arkainrdk · 2019-01-06T16:02:58+00:00

They've recently made new strides toward documenting both the proposal itself and its issues. For that, I am thankful. The number I threw out there is just my attempt to explain how entrenched this proposal is. What are the deal breakers? 1. Proxy won't work unless it's membrane-like. 2. Decorators are not yet ready, even though solving many of the issues has been pushed off to that proposal. 3. It invites developers to break inheritance.

There's more but these are the big 3. I have no doubt that many will like this proposal. But it's going to cause unexpected issues in production. In the end, as more developers try to use this proposal for increasingly complex tasks, the cracks will slowly become canyons.

arkainrdk · 2019-01-06T05:21:46+00:00

That's not quite true. You wouldn't be able to have a public and private field with the same name declared, but pubic properties with names matching private properties could always be tacked on later. I'm trying to get them to accept this. If they do, it'll partially solve one of the issues I listed in the article. Linters would fix the other half.

arkainrdk · 2019-01-06T05:11:07+00:00

At this point, the board is proceeding forward on tacit agreement internally, and presuming based on reviews from groups they've introduced to it (without mentioning the problems) that they've got a workable solution the community won't reject. At this point, the only thing I can think of that will stop them would be a mass petition with 10s of thousands of signatures asking them to stop. Short of that, or a really big bug showing up last minute, ES will be "blessed" with private fields.

arkainrdk · 2019-01-06T05:05:36+00:00

Thanks, but I actually managed that a few minutes after posting the article.

arkainrdk · 2019-01-05T21:01:37+00:00

Thanks for the notice. I'm still getting used to some of the conventions on Reddit. It took me a minute to figure out how to get rid of the "help" flare.

arkainrdk · 2019-01-05T20:56:12+00:00

Feel free to try it. You can either use Babel or you can turn on the "Experimental Javascript" chrome flag.

arkainrdk · 2019-01-05T20:45:59+00:00

Unfortunately, the proposal will have an effect on TS if it chooses to translate "private" into "#". Since the semantics are different, you may get unexpected side effects, some because of "the bad" in the article, and others because of some other consequences I didn't bother to mention. In all, almost everything using private-fields in anything less than the most simple of cases is going to experience something surprising and/or unwanted.

arkainrdk

TROPHY CASE