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.
Sekiro can jump, climb, grapple and swim. Those kinds of more agile behaviors add a lot requirements and considerations to the engine and content makers.
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.
Ahh, it is the same thing. Rust example surely has some cruft, but mostly for the better. I’m sure not all of it is needed.
Computer science is a branch of math. And while it has applications in software, most developers do not interact with it, only using existing implementations of CS results.
Show the alternative, I’ll have a good laugh.
It is black sea fleet
Move the wheel under the thumb. Until then it’s anything but ergonomic.
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.
On a side note, “jokes for 300” is a template response for joke, referencing to a lockal jeopardy! show equivalent. This response means that joke was mediocre at best.
Correspondence is quite a weak relation. Very far from one being another.
I don’t think you understand how percentage works.
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.
It has nothing to do with clang being command line. It consists of many binaries, all of them untrusted. Any time new dynamic lib is loaded Mac stops the process and complains. Then you need to do manual stuff, as you can’t automatically trust a binary, for obvious reasons. This happened almost two years ago, maybe clang got apple certificates or some shit to combat the issue. But my point was that every OS update on Mac brings annoying issues for developers.
Depends on what you are doing. My company was using clang for c++ compilation and it was a drag to make all this clicks for each .so every is update. And there is no way to automate the process. And those occasional compatibility breaks didn’t help either.
I agree. With “Lemmy is fantastic” part, too.
It surely does. Check pirates post for clean math formatting