How to LÖVE - Now with text-based tutorials

[Robin]

Basically thats what I do for every module, but why should I add an extra line "local Object=require("class")" to every single class, for every single required module I create. I don't see the mysterious big advantage when doing everything local. All my main.lua files look like this:

Sorry to bring the globals thing up again, but IMO that's like saying "The warning lights kept flashing. I thought that was annoying so I turned them off. I don't see the mysterious big advantage for using warning lights."

[s-ol]

Basically thats what I do for every module, but why should I add an extra line "local Object=require("class")" to every single class, for every single required module I create. I don't see the mysterious big advantage when doing everything local. All my main.lua files look like this:

Sorry to bring the globals thing up again, but IMO that's like saying "The warning lights kept flashing. I thought that was annoying so I turned them off. I don't see the mysterious big advantage for using warning lights."

He emphasized "everything", I totally agree with him. IMO blindly following the "no globals" rule is just as bad as not thinking about scope at all. If he literally uses that throughout all his files, it would be foolish not to have it global.

[Robin]

It's still treating the symptoms of high coupling. Organising your code in a way that leads to more separation of concerns leads to less moving parts, less bugs, less boilerplate and less temptation to use globals.

I never use globals any more and it makes my code healthier, because I can actually see when my code is becoming too highly coupled and needs to be refactored before the technical debt starts accruing.

[Sheepolution]

How to LÖVE is back, now with text-based tutorials!

Check it out!

I will keep writing tutorials till I can't think of anything to write about.

[D0NM]

How to LÖVE is back, now with text-based tutorials!

Check it out!

I will keep writing tutorials till I can't think of anything to write about.

To explain collisions I'd start with easier cases:
- 1 point and another point
- 1 point and a rectangle
- point & circle
- circle & circle

Anyway. Your tutorials are very cool. I've posted links to them here and there. Hope my friends & pupils would love them.

[Karai17]

If you're still looking for help writing some chapters, I could write a chapter on why classes suck, and why ECS is master race. I ditched OOP last year and couldn't be happier.

[Nixola]

If you're still looking for help writing some chapters, I could write a chapter on why classes suck, and why ECS is master race. I ditched OOP last year and couldn't be happier.

I would be interested in this.

[Sheepolution]

If you're still looking for help writing some chapters, I could write a chapter on why classes suck, and why ECS is master race. I ditched OOP last year and couldn't be happier.

Actually, yes. I think it should be chapter 20+, but once there I was already planning on asking you or one of the ECS master race people to write a chapter about it, since I have never really invested time in ECS myself.

I will probably keep using classes for future chapters, unless your chapter is able to convince me not to.

I could also use help with a chapter for love.physics.

Here's my current list of ideas for future chapters, in no particular order:

• Distribution
• Angles and distance
• Errors
• Camera
• Online
• ECS
• Audio
• Tweening
• Animation
• Tiles
• Platformer
• Terminology
• Clean code
• Physics
• Filesystem
• Text

[Karai17]

Alright, I'll stay writing something today and link you to a Google doc via pm when I have a draft ready.

[Sheepolution]

I put the whole thing on Github.