Skip to content
This repository has been archived by the owner on Jun 8, 2020. It is now read-only.
/ ooop Public archive

OOP has never been sooo professionally over engineered before.

License

Notifications You must be signed in to change notification settings

OctoD/ooop

Repository files navigation

OOOP

Over-engineered object oriented programming

Install

npm i ooop

Yeah ok but why?

Because your code will look more professional®, everybody know that skilled developers tend to over-engineer their codebase.

An hello world example

import ooop from 'ooop';

new ooop.Types.Function(
  () => (
    new ooop.Types.ObjectString(`hello world`)
  )
).call();

Simple, over-engineered and so professional.

Best practices using ooop

Strings

Don't

const varname = 'hello'; // too simple

Do

import ooop from 'ooop';

new ooop.Types.ObjectString(`hello`);

Better.

Numbers

Don't

const varname = 100; // it could be an Int, a Float, a Decimal...
const varname2 = 100.22; // idem

Do

import ooop from 'ooop';

new ooop.Types.ObjectInt(100);
new ooop.Types.ObjectDecimal(100.22);

Lovely.

Releases

No releases published

Packages

No packages published