| Douglas Winslow's internet home page | updates | tech | games | art | community | parodies | e-mail | index |
Are computer operating systems art? I think maybe so, which is not a good mindset to have when we have serious things to think about. There is a boundary. There are boundaries. We don't want to have to deal with graphics all day if we're keyboard- and alpha-productive, and there is a middle-ground in how much junk to tolerate before reallocating resources to a more important task, either on- or off-line in the overall computing scenario system. Yes, if you have the computer in mind while you're off-line, you're still augmenting your session. That's my current interpretation at Douglas Winslow by way of Douglas Engelbart in NLS. Cumulative success is what I think we're all good at noticing. I've mirrored an interesting text-based operating system kernel called "Linux" from Linus Torvalds below for your simple understanding. It's a lot more complex today than it was when I started using it in the mid-1990s.
I've noticed elsewhere the lack of an international art system catalog that takes these concerns of complexity and confidence into account. There's reasons for this, likely self-referential when found, so keep in mind that we're not putting our faith in a network of art choices that haven't been unreviewed or untested, but most successes in the memetics of art that make it into the flexible canvas of the lightning-fast video screen (wow!) are going to survive the longest in effect closest at the site of the viewer's perspective, closest to the viewer (the user), and, yes, from the viewer's perspective, closest until otherwise cleared off as a problem, by time or other metric. Put simply, if it's been run in the art system by being published, it's already the user's concern to deal with, and, from their perspective, it can't change until someone arrives to change it. That's the user's mode. But there's always the overarching problem of interrupting what used to be there, which may be seen as an existensial concern. (Hint: the best accessible version of the aforementioned missing art system catalog is always hiding in plain sight somehow.) 💸
Here's an example. In design, maybe we'd rather use orange than red in interface design in certain stoplight-compatible scenarios in software. But when we start to consider the stigma around flow control versus the task in process, including its effects on the well-being of the user (keeping in mind healthy interaction), and other surrounding circumstances that affect from the art system, via the viewer, inbound toward the user, we'd perhaps rank software as not being the place we'd want to place hazard-bound colors. Therefore, now rather than disrupting a field that deals with hazards, maybe we'd rather use a monochrome display or interface to take the controversy away. Maybe the user was happy with monochrome in their first encounter with software before we even started changing things.. and shouldn't that have us being self-critics of how we've evolved the system? In page-bound and computing implementations of the system, we also have to deal with 2D. That's not an easy thing to express.
My off-hours schedule is full for the next few weeks while I get up to speed on some differences in various text editing servers such as gedit and emacs. I've been using GNU nano to do most of my text file editing for the past decade, and I'd been using UW pico since I started with Linux. BSD's ee is noteworthy, and so is joe, which I've used since around 1999 for block-shaped selection of text before pico was upgraded. See if you can find out how to do block selection in joe today without exiting the editor. What a mess. To think there used to be a sound penalty to using a lot of these utilities.
I've got a virtual buffer I'm working on provisionally named vt. It's been under-way since September 24th of 2022, but health setbacks have delayed it twice. You know how the computer can pull you into long hours sometimes. This isn't The Sopranos, but if the computer pulls you anywhere you aren't happy with, be sure to remember Control+C or whatever exit strategy seems to have been placed there to use in a crisis.
Likewise, I cannot release any software right now on terms that I find acceptable until certain businesses in the State of Maryland begin to honor my requests for employment seriously. Specifically, a reply overture from a local entry-level job provider in higher education suggested that instead of working and being happy in public situations like I've always done, that I should instead get back to working for $0 on the hypertext airport machine that briefly allowed the State to attach my concern to homelessness so it could fail and manipulate the market.
I visited Boston, home of the Free Software Foundation, via a quality American automobile some years ago to see if the area was more acceptable than Baltimore for my kind of work ethics, but the people I met were just too busy to want to talk. I'm still licensed for driving, much like other automobile enthusiasts, if that matters.
GNU is a very well protected system in and of itself, but darn if I don't have some buffers to wrangle to get productive again. gedit isn't how I thought I'd have to read kernel Changelogs, is what some might say.. 🛬
If you notice what I call "art system failures" (or even successes) pulling too much resources from your main thread of living a happy life, I'm sure you know when and how to reallocate your resources. The self-centric state-run art system is here to enforce status quo as soon as possible on the network as a "hit" to make sure there's an irrevocable element of affect or controversy. I think there's a Badfinger song that was rushed out in the proprietary song market of 1969 to make the point. But please think of this in context with popular long-standing protected art systems such as Buddhism which preach an easygoing lifestyle. I wish you happy usage of GNU/Linux on whichever side of that, state or author, that you think you are using at any given time. It's not easy being raised on Commander Data.
Warning: Local terminology does not imply network acceptance, and vice versa. Keywords subject to change.. (and how!)
| Copyright © 1996-2024 Douglas Rice Winslow III. All Rights Reserved. | E-mail Address: <winslowdoug@gmail.com> |
