As a sidenote, does anyone else find the language identification terms cringey? Rustacean, gopher, pythonista... just atrocious.
Nope, it's fun
Rust from a Gopher – Lessons 7, 8 and 9
31–40 of 58 posts
Re: Rust from a Gopher – Lessons 7, 8 and 9
#32“Prelude” is borrowed from Haskell, right?
ALGOL-68 already had a prelude.
Re: Rust from a Gopher – Lessons 7, 8 and 9
#33As a sidenote, does anyone else find the language identification terms cringey? Rustacean, gopher, pythonista... just atrocious.
I’m noticing a trend of mostly younger people misusing “cringe” and I wonder if it may have to do with dumb videos on YouTube misusing it, or maybe the word is changing. To cringe is to feel disgust or embarrassment that results in a physical reaction such as a grimace. Generally, this can be felt watching very socially awkward situations. Is this what you mean? Or is there a better word, like immature, silly, strange, or something? I think most people are not feeling socially awkward or whatnot referring to a community by a mascot or other title. It is just a silly word for “practitioners of a given language.” We do that with all kinds of term, roles, titles, professions, hobbies, etc.
Why does it make you cringe?
Re: Rust from a Gopher – Lessons 7, 8 and 9
#34Earlier quoted context omitted.
Interesting. This made me realize that a possible reason why some find the modules concept confusing is that it conflates the concepts of inclusion and namespacing. edit: corrected typo
Has the joke flown over my head, or have you conflated the words "conflate" (confuse) and "conflagrate" (burn)? Edit: I honestly think I might have just misunderstood some play on words you're trying to make. It would be something around setting namespaces and inclusion on fire, but none of the combinations I've tried in my head work out quite right.
D'oh! Thanks for the correction; there was no pun - I just intended that it combined the two concepts :-)
Re: Rust from a Gopher – Lessons 7, 8 and 9
#35As a sidenote, does anyone else find the language identification terms cringey? Rustacean, gopher, pythonista... just atrocious.
Yes. Fanboyism in general is cringe, but these "quirky" names are pure 100% dev.to-level cringe.
But to be honest, computer people were always more prone to cringey stuff than regular folk... (an extreme example would be the classic clip of Stallman eating dead skin from his feet) It's something with our upbringing I guess.
Re: Rust from a Gopher – Lessons 7, 8 and 9
#36Earlier quoted context omitted.
One important technical reason is that you need to be able to add attributes to modules, like these examples: // Only compile this code if the “foo” Cargo feature is enabled. #[cfg(feature = "foo")] pub mod foo; // Platform-specific stuff, as with std::os. pub mod os { #[cfg(windows)] pub mod windows; #[cfg(unix)] pub mod unix; } // You can even choose which file to load the module from. #[cfg_attr(windows, path = "w…
Interesting. This made me realize that a possible reason why some find the modules concept confusing is that it conflates the concepts of inclusion and namespacing. edit: corrected typo
Rust modules are primarily about namespacing, which is why the book only mentions the inclusion behavior in one short section at the end of the relevant chapter. For a non-namespacing include, there’s the `include!` macro.
Re: Rust from a Gopher – Lessons 7, 8 and 9
#37As a sidenote, does anyone else find the language identification terms cringey? Rustacean, gopher, pythonista... just atrocious.
I’m noticing a trend of mostly younger people misusing “cringe” and I wonder if it may have to do with dumb videos on YouTube misusing it, or maybe the word is changing. To cringe is to feel disgust or embarrassment that results in a physical reaction such as a grimace. Generally, this can be felt watching very socially awkward situations. Is this what you mean? Or is there a better word, like immature, silly, strang…
I think cringe fits here.
If I met a developer who said they were a gopher or rustacean or whatever. I'd feel physically embarrased for them.
Re: Rust from a Gopher – Lessons 7, 8 and 9
#38What's the rationale for making files modules? Modules being namespaces, and namespaces being collections, it's not desirable to have a file being a (large) collection of code. The feature that gives mixed feelings to the author (Re-exporting Imports) is indeed a workaround to this; since each file would externally generate one extra namespacing level, one reexports data structures in order to remove that level. This…
As someone who mostly writes Rust these days, I find it really nice that I can always (as long as I don't use wildcard imports) use intra-file search to find either the definition or the file that contains the definition. Whenever I have to touch Go code (for reading and debugging) it's really annoying to just end up going "okay, I've got the folder, now what". Or, even more annoyingly, I've just got an interface and…
> Or, even more annoyingly, I've just got an interface and no clue about where to find the implementation.
That bites me often times. Does gopls help in this regard? Can any tool besides the compiler help me to answer, what methods in a particular piece of code implement what interface?
Re: Rust from a Gopher – Lessons 7, 8 and 9
#39Earlier quoted context omitted.
I wouldn't say that it is cringey, but I agree with the sentiment. It always seemed kind of weird that programmers would attach themselves and identify with a programming language tribe, even though they are very well capable of learning other languages and frequently do.
The terms also emerge for certain languages with a specific type of community around them. For example, I don't know if C++ developers really care enough to give themselves these kinds of labels.
Most don't love the language that much.
I'm not implying that it's a bad language though. Like Java, it's a very widely used language in enterprise and industry, and I think that most of the programmers in those languages view programming as just a 9-to-5, white collar job that puts food on the table. Nothing wrong with this view either, but it's not the kind of environment that would create memes or inside jokes.
Rust, Haskell or Ocaml, on the other hand, are exactly the kind of languages that passionate programmers, that spend a lot of time in chatrooms and on forums like HN, would spend their time on.
Re: Rust from a Gopher – Lessons 7, 8 and 9
#40As a sidenote, does anyone else find the language identification terms cringey? Rustacean, gopher, pythonista... just atrocious.
Well then hold on to your hat then and take a look at this:
I mean it's an adorable crab! Who wouldn't want to join the rustacean legion behind Ferris. (Who is presumably named after Ferrous[Iron] which 'Rust's)