- 0 Posts
- 26 Comments
Doesn’t seem like that to me.
1·2 months agoYes. I thought it was poorly written.
Why? This is isn’t about git. It’s about github. Two completely different tools.
No, you’ll fix it now if you want my approval. I’m not falling for that again.
Alright, enough making fun of languages that suck…let’s talk about JavaScript.
loop, innerloop, innerinnerloop, …
Usually people say “premature optimization is the root of all evil” to say “small optimizations are not worth it”
No, that’s not what people mean. They mean measure first, then optimize. Small optimizations may or may not be worth it. You don’t know until you measure using real data.
Git is p2p and distributed from day 1. Github is just a convenient website. If Microsoft takes down your repo, just upload to another system. Nothing but convenience will be lost.
I disagree that parsing is validating. For example, you could give me a valid ISO date time string, but I want a shipping date and you gave me something in the past. It parses, but is not valid.
I disagree that validating early is bad because some other part of the code might also validate later and possibly do it differently. Yes, that’s bad, but not a reason to not validate early.
I understand the concept. I just disagree that it’s a good idea.
I don’t see it. I would much prefer to validate early rather than late. The example of ‘other code might validate it differently or not at all’ seems specious. I don’t want invalid information “deep within the bowels of the system”.
Underrated by who? Who the hell is rating these things anyway?
Pretty sure you have to abort and start over.
Faster. Less memory. Maps to physical things well (e.g. a device with memory mapped registers). No garbage collection / object destruction needed. No need to initialize new objects all the time.
Kajagoogoo