Abstract Concepts: Difference between revisions

From Resonite Wiki
Added a link for Cursed Knowledge in this page.
Added a new entry for a future page.
 
(One intermediate revision by the same user not shown)
Line 20: Line 20:
* '''[https://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency]''': The idea of code running after starting a task (in an attempt to prevent lockups from said task).
* '''[https://en.wikipedia.org/wiki/Concurrency_(computer_science) Concurrency]''': The idea of code running after starting a task (in an attempt to prevent lockups from said task).
* '''[[Defensive Programming]]''': The idea and implementation of code that prevents bugs, both from a security standpoint and user input checking.
* '''[[Defensive Programming]]''': The idea and implementation of code that prevents bugs, both from a security standpoint and user input checking.
* '''[[Asynchronous Safeness]]''': The idea of using async in ProtoFlux in a safe context. Along with examples on what makes it safe.
* '''[[Stateful vs Stateless]]''': Stateful systems remember past interactions, while stateless systems do not, treating each request as a new, independent event.


=== Social ===
=== Social ===

Latest revision as of 22:43, 8 November 2025

This article or section is a stub. You can help the Resonite wiki by expanding it.

Abstract Concepts are ideas that are not concrete as separate "things" in Resonite, but instead can be simple interactions between users, can be designed and built from or into projects, and can provide insight to problems that are desired to be solved. In contrast to Core Concepts, which are bound to the Engine, the Data Model, or in some way tangible and usable at the moment.

Concepts

Math

  • Floating Point: The float implementation and limitations in computer science and Resonite.
  • Set Theory: The study of sets, which is basically a collection of "something" inside that set.

Problem Solving (& Design)

  • Cursed Knowledge: Helpful yet cursed information that may come in handy within the development of Resonite.
  • Unsolvable Problem: The concept of solving something, but discovering that the problem cannot be solved due to logical/mathematical limitations.
  • XY Problem: The concept of asking for X, but also asking follow up questions to know and figure out Y (Why).

Programming

  • Concurrency: The idea of code running after starting a task (in an attempt to prevent lockups from said task).
  • Defensive Programming: The idea and implementation of code that prevents bugs, both from a security standpoint and user input checking.
  • Asynchronous Safeness: The idea of using async in ProtoFlux in a safe context. Along with examples on what makes it safe.
  • Stateful vs Stateless: Stateful systems remember past interactions, while stateless systems do not, treating each request as a new, independent event.

Social

  • Accessibility: Users that have different impairments and how to design a way to make it easier for these users in Resonite.
  • Nerd Sniping: The idea of asking a silly or seemingly stupid question in hopes to get the answer a user is looking for.