Go is fast they said, Go is lightweight they said.

package main

import "fmt"

func main() {
var nums []int
for i := 10; i > 0; i++ {
nums = append(nums, i)
i--
}
fmt.Println(nums)
}

# htop
| PID | USER | VIRT | %CPU | %MEM
| 12048 | root | 16.9g | 101.3 | 94.2

WTF is eating my resources to hell and.... oh... oh im a dickhead!

So I do not get why people use ReactJS. I hate it. for 3 years passionately. And I have to work with it every day.

- one-way data binding
this makes you write twice as much code, which will have twice as much bugs, you need to read through twice as much code from other devs.
- mixing html and JS
after all I like to pour my coffee on my omlette so I can eat and drink at the same time in the morning. This kills productivity and ugly AF
- not unified
Every dev uses their own special snowflake framework with React there is no unified way of doing things and you cannot use your familiar tools. Every project you need to start over from zero.
- Bugs bugs bugs
infinite loops, max update depth reached, key not present on list element. Let me ask you something dear ReactJS. If you know that there should be a unique key on that element. Why cannot you just put it there and shut the f up?
- works reeaally slow when compiled with TS
ReactJS was never designed to work with TS and now the tools for it are really slow. And why TS? Explicit contract is always better than an implicit contract. TS helps you in coding time, but for some reason React devs decided to worth 3 seconds to wait for compile and then realize you mad an error. ReactJS is bad and inefficient so stop making projects with it please.

So I'm writing a function in Unity3D that walks a rectangular grid. At one place in the code, I got the x+y coordinates backwards, which caused the function to infinitely loop between two coordinates.

Not seeing a way to kill the loop, I looked it up on Google. The suggestions I get are. . .

1. You need to kill the Unity3D task and lose your edits because the environment and the player run on the same thread.
2. You can pay ten bucks for an extension that lets you break out of infinite loops.
3. You should really avoid writing infinite loops. That's just bad form.

SERIOUSLY?