Sure. But the author cites that as a disadvantage of emacs and links to an article about the person who invented ctrl-c
and ctrl-v
for copy and paste.
Sure. But the author cites that as a disadvantage of emacs and links to an article about the person who invented ctrl-c
and ctrl-v
for copy and paste.
The author also makes some incorrect or misleading claims, specifically about emacs. I acknowledge there’s a high bar for entry there and don’t personally like emacs, but it’s not modal, and it does have the ability to display images and markdown previews.
I know several world class programmers, and interestingly, the commonality among them is that they all seem to use Vim as their code editor. Many people I know who think of themselves as world class programmers use Emacs.
What a burn!
Wow, that was not at all clear. I was shocked that 50% of respondants identify as LGBTQ; 7% is a much less surprising figure.
How is that easier? It doesn’t look like it provides a list of which modules have a __name__ == "__main__"
block.
…yeah, that’s really unfortunate. Part of why I said “in principle”.
Minor point of clarification: it can’t have runtime reflection, but in principle it could have compile time reflection.
Yeah, Boats’ point there is definitely about semantic correctness rather than performance. Goroutines do indeed have good performance.
Ah. No, keep reading:
In a less than optimal world, you might decide to do something less inspired. You might take that break from the C runtime and then just implement threads again, with basically the same semantics, except that they are scheduled in userspace. Your users would be required to implement concurrency in terms of threads, locks and channels, just like they had always been in the past. You might also decide your language should have other classic features like null pointers, default constructors, data races and GOTO, for reasons known only to you. Maybe you would also drag your feet for years on adding generics, despite frequent user requests. You might go do that, in a less than optimal world.
(Emphasis on “go” is in the original.)
It doesn’t mention him by name, but he’s the “language designer of some renown” alluded to here:
If you were a language designer of some renown, you might convince a large and wealthy technology company to fund your work on a new language which isn’t so beholden to C runtime…
Critical hit! It worked on the first try and you fixed some tech debt!
I’m pretty sure that when programmers and other techies call themselves “hackers”, they don’t mean in the security-breaching sense. It means that you can “hack together” something.
The bit about Rob Pike at the end is killer.
It’s simply not true that there “aren’t really that many definitions of OOP”, much less that the guide you’ve linked is “comprehensive” when it is specifically about Java.
This is a good, brief post about the different conflicting definitions: https://paulgraham.com/reesoo.html
This is a much more comprehensive but also less focused overview, with many links, from a site that is effectively both a wiki and a forum: https://wiki.c2.com/?ReesOnObjectOrientedFeatures
Or Ruby, if you want to suffer less psychic damage…
Go if you want a real mental challenge
I don’t mean to be rude, but I find this baffling; what do you mean by it? One of the primary design goals of Go is to be simple to learn (this is fairly well documented), and it’s one of the few things I really have to give the language credit for. Rob Pike has specifically discussed wanting it to be accessible to recent CS graduates who have mostly used Java. I have never heard anyone before describe learning Go as a “challenge.”
That would be helpful! Thank you.
You’re misunderstanding the posts you’re explaining. Sanitizers, including ASan, HWASan, and bound sanitizer, are not “static analysis tools”. They are runtime tools, which is why they have a performance impact. They’re not intended to be deployed as part of a final executable.
I don’t know how you can read this sentence and interpret it to mean that they “haven’t onboarded AddressSanitizer”:
In previous years our memory bug detection efforts were focused on Address Sanitizer (ASan).
Sorry, what project is this? GCC?
Yeah, I commented elsewhere on the misinformation regarding emacs in the article.