No… I get it… 41 < 105… I totally agree haha funny joke. I’m just over this debate. Who gives a fuck what temperature scale you use? Just use the one you know. We have conversions for that reason.
No… I get it… 41 < 105… I totally agree haha funny joke. I’m just over this debate. Who gives a fuck what temperature scale you use? Just use the one you know. We have conversions for that reason.
Once again… the classic argument of: “Well, I grew up using this system, and I’m used to the system. I have built an internal intuition for how hot and cold the temperature is. I am used to >100 being hot! 40 is not hot!”
Well then. I grew up using celcius and… “IT’S FOURTY FUCKING ONE DEGREES OUTSIDE?” sounds just as hot.
Most of the stuff here can be avoided by using quotes for strings…
Yeah but Haskell is mostly used by mathematicians…
People hate hearing that they are bad coders 😂
You and the other guy are saying to focus on writing code with less indentation and using smaller methods, and you both got downvoted.
I fully agree, small methods all the way, and when that’s not possible it’s time to refactor into possibility!
But it’s not a markup language… It’s for data serialisation…
Nope, but I was in Australia. Not quite as swampy.
I LOVE the thought of a world-covering swamp with pseudo-trees and giant fucking bugs. Such a stimulating thought. I’d love to explore and see it.
Badass or stupid and incompetent? Take your pick lol
Probably not unless it’s stylistically like that. Grackles has black beaks anyway
For me it just depends on what I expect. They’re all relatively the same thing. As long as the status code is appropriate (403), it doesn’t matter whether it’s JSON or plaintext. Ideally the API would respect and handle the request header, and return plaintext if you request plaintext.
At work, was recently working on a script that alters the repo significantly. Every time I tested the script, I used the up arrow to get the git clean
and git checkout HEAD -- files
commands to reset the repo. I must’ve used those 100+ times.
I agree with your point, but our algorithms are not deterministic and I doubt they ever will be again. Perhaps they could use a set of tags to create a deterministic result for a certain “genre” of results.
I mean of course that would be nice, but that’s just not realistic. You can’t store that info in a link without it being monstrous.
Why do you say they couldn’t cache the results and instead of re-fetching everything just use the cache results?
They could cache the results you receive on your last visit of the home page which would fix this
Users can be like clients too though.
Trango
Base /+1 lol
Ah true.