Apart from screaming case, which is for textual macros, i approve.
Apart from screaming case, which is for textual macros, i approve.
It is also a “refactoring”.
It is trivial arithmetic: 4.52403840*2160 ≈ 9 GB/ s. Not even close. Even worse, that cable will struggle to get ordinary 60hz 4k delivered.
In many modern environments the second I start scrolling my eyes start to bleed. Yes, I want 60 fps min. That was the first part. The second part is about stability. 20 fps may be enough for typing, but it needs to be 20 fps all the time. Not the average between 1 and 60, it is makes IDEs unusable.
If FPS is NOT an important metric in text editing, you are doing something wrong. Otherwise, good points.
Show the alternative, I’ll have a good laugh.
Exactly. If you are a coder and care about ergonomics of layouts, get split programmable keyboard, do not try to find good layout for normal keyboard, they do not exist. I personally do not like the particular keyboard at the picture, but there are many others to choose from and find a good fit for everyone.
Correspondence is quite a weak relation. Very far from one being another.
Proofs can be represented as programs, not the other way around. Also, USA allows for algorithm parents, and algorithms are maths. While I agree with you, your reasoning is not correct.
For those saying it’s like satisfactory. Actually, it draws much inspiration from fortress craft evolved. At least game mechanics wise. But foundry seems to be much more polished, plus they add their own twists to the formula. I wouldn’t dismiss it just based on the looks.
It surely does. Check pirates post for clean math formatting