#computer architecture

[zephiris]

Being autistic feels like having to emulate brain hardware that most other people have. Being allistic is like having a social chip in the brain that handles converting thoughts into social communication and vice versa while being autistic is like using the CPU to essentially emulate what that social chip does in allistic people.

Skip this paragraph if you know about video codec hardware on GPUs. Similarly, some computers have hardware chips specifically meant for encoding and decoding specific video formats like H.264 (usually located in the GPU), while other computers might not have those chips built in meaning that encoding and decoding videos must be done “by hand” on the CPU. That means it usually takes longer but is also usually more configurable, meaning that the output quality of the CPU method can sometimes surpass the hardware chip’s output quality depending on the settings set for the CPU encoding.

In conclusion, video codec encoding and decoding for computers is to social encoding and decoding for autistic/allistic people.

[moastudiess]

CS jokes are so sad

I forget the context but I think it had something to do with how a friend of mine was on the verge of a C in processor design, but he clutched up last minute. For reference, he’s the head TA of a different course called computer systems. My boyfriend said “grades are temporary, but registers are forever”

The saddest part is that registers are temporary too, they’re used for temporary arithmetic in the manner of short term memory allocation in computer architecture

[a-fox-studies]

April 15, 2024 • Monday

A whole day of number system conversions . . . hexadecimals are very cute in my opinion :3

🎧 Overnight — Connor Price ft. Tommy Royale

[steviethebean]

random access memory

They are the outgoing friend. "Random access" refers to how the physical location of the data in the RAM does not significantly affect the speed of accessing it. Usually volatile (does not store data permanently).

[frog707]

Loving Travis

For most of my open-source software projects, I use the Actions platform built into GitHub for CI (continuous integration). GitHub Actions provides virtual machines to run workflows, so I don't have to administer build environments for Linux, MacOS, Windows, and so on. It's modern, convenient (if you use GitHub instead of, say, GitLab), fairly reliable, and (best of all) free (for public repos).

For me, the main limitation of Actions is that all their hosted runners use the x64 architecture. Sometimes I want to build and/or test on Arm CPUs---for instance my Libbulletjme project, which has a bunch of platform-sensitive C++ code.

For Libbulletjme, I still depend on the older TravisCI platform, run by a private firm in Berlin. In addition to a huge selection of build environments based on AMD CPUs, Travis also provides Arm-based Linux environments. (Officially, they're a "beta-stage" feature, but they've been in beta for years.) Like Actions, Travis is also free to open-source projects, though their notion of "open-source" seems a bit stricter than GitHub's.

I mention Travis because my experiments with the Vulkan API exposed a limitation in Libbulletjme, which led me to begin work on a new release of Libbulletjme, which led me to discover an issue with Travis's Arm-based build environments. A recent change to these environments caused all my Arm-based builds to fail. I could only go a bit further with Vulkan before I would have to make hard choices about how to work around the limitations of Libbulletjme v18.5.0 .

At 20:09 hours UTC yesterday (a Sunday), I e-mailed TravisCI customer support and explained my issue. At 12:25 hours UTC today, Travis announced a hotfix to solve my issue. That's pretty good turnaround, for a non-paying customer having issues with a "beta-stage" feature on a summer weekend.

Bottom line: I still love Travis. <3

[hindicomputer]

Learn Logic Gates in Hindi

[blank-dude2]

Taking Computer Architecture has only made me more sure computers are just magic.

Like before this semester started, if you asked me how computers worked, I'd give a vague answer along the lines of "Electricty flows through certain logic gates to produce outcomes that do whatever is needed. Now if you ask me, I'd answer. "Computers just kinda work. A bunch of mystery steps happen somehow, and then it manages to play a full ass video game. No idea how it doesn't just explode or shatter into a million pieces, but it doesn't."

[starmanleo]

Help.

[jaroeducationmba]

Computer Architecture

Computer Architecture refers to the design and organization of the components of a computer system. It focuses on how the CPU, memory, input/output devices, and storage systems interact to execute instructions and perform tasks. Key concepts in computer architecture include the CPU's instruction set, data paths, control units, and how components communicate through buses. Efficient computer architecture optimizes performance, energy consumption, and scalability. It is essential for understanding how hardware influences software efficiency.

For more details, check further resources -

[comicsanas]

"Hello, World!" in MIPS Assembly

[compsci-haikus]

The powers of two: crucial to computers now. They weren't, always.

You might have heard of 32-bit and 64-bit applications before, and if you work with older software, maybe 16-bit and even 8-bit computers. But what came before 8-bit? Was it preceded by 4-bit computing? Were there 2-bit computers? 1-bit? Half-bit?

Well outside that one AVGN meme, half-bit isn't really a thing, but the answer is a bit weirder in other ways! The current most prominent CPU designs come from Intel and AMD, and Intel did produce 4-bit, 8-bit, 16-bit, 32-bit and 64-bit microprocessors (although 4-bit computers weren't really a thing). But what came before 4-bit microprocessors?

Mainframes and minicomputers did. These were large computers intended for organizations instead of personal use. Before microprocessors, they used transistorized integrated circuits (or in the early days even vacuum tubes) and required a much larger space to store the CPU.

And what bit length did these older computers have?

A large variety of bit lengths.

There were 16-bit, 32-bit and 64-bit mainframes/minicomputers, but you also had 36-bit computers (PDP-10), 12-bit (PDP-8), 18-bit (PDP-7), 24-bit (ICT 1900), 48-bit (Burroughs) and 60-bit (CDC 6000) computers among others. There were also computers that didn't use binary encoding to store numbers, such as decimal computers or the very rare ternary computers (Setun).

And you didn't always evolve by extending the bit length, you could upgrade from an 18-bit computer to a more powerful 16-bit computer, which is what the developers of early UNIX did when they switched over from the PDP-7 to the PDP-11, or offer 32-bit over 36-bit, which happened when IBM phased out the IBM 7090 in favor of the the System/360 or DEC phased out the PDP-10 in favor of the VAX.

[designing-software-architecture]

The Role of Innovative Software in Designing Software Architecture

In the ever-evolving landscape of software development, the key to success lies in harnessing the power of advanced tools that go beyond conventional boundaries. Explore the realm of "Software to Design Software Architecture" and witness a paradigm shift in the way we build digital solutions.

Embracing Efficiency with Intuitive Software Design

Gone are the days of traditional methodologies; today, it's about embracing efficiency through purpose-built software design tools. Discover how these tools streamline the architectural process, fostering creativity and precision in every code structure.

The Power of Visualization: Transforming Concepts into Digital Realities

Unlock the potential of visualization in software architecture design. Dive into the world of tools that bring your ideas to life, providing a clear and comprehensive overview of complex systems. See how these visual aids elevate the design process, making it more intuitive and error-free.

Navigating Complexity: Simplifying Software Architecture Challenges

Delve into the strategies employed by cutting-edge software to simplify intricate architectural challenges. From modular design to seamless integration, uncover the secrets that turn complexity into an opportunity for innovation.

My Journey with SystemDraw: A Revelation in Software Architecture Learning

As the blog journey concludes, I share my awe-inspiring experience of learning from SystemDraw.net. The platform proved to be a game-changer, offering not just a learning experience but an immersive journey into the world of software architecture. From comprehensive tutorials to hands-on exercises, SystemDraw.net empowered me to transform my understanding into tangible skills.

Embark on this transformative journey with me and witness firsthand the impact of incorporating advanced software into your architecture design process. The future of software development is here, and it starts with the tools you choose.

[steviethebean]

memory access register, memory data register

They are respectively storing addresses and the data attached to those addresses. They are kind of troublemakers in this story.

[vintagehomecollection]

Living with Folk Art: Ethnic Styles from Around the World, 1991

[frog707]

It did an exa flop.

Cost half a billion a pop.

It never saw a NOP.

It did an exa flop.

[hindicomputer]

Learn Boolean Algebra In Hindi