haveblue posted:

that’s a kiloservice not a milliservice

big scary monsters posted:

kibiservices

graph posted:

https://twitter.com/RMac18/status/1719055397200564603

dpkg chopra posted:

the reigning theory, as I understand it, is that Elon wants to drive down the value so that he can rebuy the debt for pennies on the dollar and own the company free and clear (to do what with it? drive it further into the ground?).

Kenny Logins posted:

PokeJoe posted:

I have a CAT tractor key and it works in komatsu too. A shitload of the keys are identical because of supplier overlap and because no one gives a poo poo. I also have the 2nd key for the Big Boy tractors

The_Franz posted:

grand theft excavator

"drat, he's very slowly getting away!"

PokeJoe posted:

If you wanna file you own here you go. The weird one is the big boy key:

lament.cfg posted:

amillion buggs is an outlier and should nto have been counted

the gayest hobbit posted:

especially since he changed his name from "Inurmoms Pubichair"

lament.cfg posted:

amillion buggs is an outlier and should nto have been counted

Powerful Two-Hander posted:

https://twitter.com/BunkiePerkins/status/1719377676429819914

quote:

𝗪𝗵𝗮𝘁 𝗶𝘀 𝘁𝗵𝗲 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝗠𝗩𝗖, 𝗠𝗩𝗣, 𝗠𝗩𝗜, 𝗠𝗩𝗩𝗠, 𝗠𝗩𝗩𝗠-𝗖, 𝗮𝗻𝗱 𝗩𝗜𝗣𝗘𝗥 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀?

Here is the list of the most critical architectural patterns:

𝟭. 𝗠𝗩𝗖 (𝗠𝗼𝗱𝗲𝗹-𝗩𝗶𝗲𝘄-𝗖𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗲𝗿):

It is one of the earliest and most adopted design patterns. Its primary goal is to separate the application's data, user interface, and control logic into three interconnected components.

Here, the Model manages data and logic, the View displays the information, and the controller connects the Model and View, handling user input.

𝗨𝘀𝗮𝗴𝗲: For Web applications with a clear separation between data handling and UI.

𝟮. 𝗠𝗩𝗣 (𝗠𝗼𝗱𝗲𝗹-𝗩𝗶𝗲𝘄-𝗣𝗿𝗲𝘀𝗲𝗻𝘁𝗲𝗿):

The pattern evolved from MVC, aiming to address its shortcomings in event-driven environments by decoupling the View from the Model, with the Presenter acting as a middleman.

Here, the Model manages data, views display data, and sends user commands to the Presenter, while the Presenter retrieves data from the Model and presents it to the View.

𝗨𝘀𝗮𝗴𝗲: Applications emphasizing testing and UI logic, such as Android apps.

𝟯. 𝗠𝗩𝗜 (𝗠𝗼𝗱𝗲𝗹-𝗩𝗶𝗲𝘄-𝗜𝗻𝘁𝗲𝗻𝘁):

MVI is a reactive architecture embracing unidirectional data flow, ensuring that, given a state, the UI remains consistent.

Here, the Model represents the state, View reflects the state, while intent represents user actions that change the state.

𝗨𝘀𝗮𝗴𝗲: Reactive applications or frameworks like RxJava with a focus on state consistency.

𝟰. 𝗠𝗩𝗩𝗠 (𝗠𝗼𝗱𝗲𝗹-𝗩𝗶𝗲𝘄-𝗩𝗶𝗲𝘄𝗠𝗼𝗱𝗲𝗹):

MVVM arose to address complexities in UI development, promoting a decoupled approach with the ViewModel handling view logic without knowing the UI components.

Here, the Model manages and displays data, while ViewModel holds and contains UI-related data.

𝗨𝘀𝗮𝗴𝗲: UI-rich applications or platforms with data-binding, such as WPF or Android with LiveData.

𝟱. 𝗠𝗩𝗩𝗠-𝗖 (𝗠𝗩𝗩𝗠 𝘄𝗶𝘁𝗵 𝗖𝗼𝗼𝗿𝗱𝗶𝗻𝗮𝘁𝗼𝗿):

MVVM-C builds upon MVVM, introducing the Coordinator to handle navigation, decoupling it from View and ViewModel.

𝗨𝘀𝗮𝗴𝗲: larger applications, especially iOS, where complex navigation needs separation from view logic.

𝟲. 𝗩𝗜𝗣𝗘𝗥 (𝗩𝗶𝗲𝘄-𝗜𝗻𝘁𝗲𝗿𝗮𝗰𝘁𝗼𝗿-𝗣𝗿𝗲𝘀𝗲𝗻𝘁𝗲𝗿-𝗘𝗻𝘁𝗶𝘁𝘆-𝗥𝗼𝘂𝘁𝗲𝗿):

VIPER is a modular architecture akin to Clean Architecture. It emphasizes testability and the Single Responsibility Principle by breaking down application logic into distinct components.

Here, the View displays what the Presenter sends, the interactor contains business logic per use case, the Presenter contains view logic for preparing content, the entity includes a primary model object, and the router contains navigation logic.

𝗨𝘀𝗮𝗴𝗲: Complex applications, especially iOS, need modularity, testability, and clarity.

Cat Face Joe posted:

https://twitter.com/sportsguy839303/status/1720226722971628030