Hello /g/. I'm a stupid techlet retard. I want to learn a programming language. Not really because I need it, I just want to do something engaging in my free time, and I've always been very self-conscious about being too retarded to understand technology. I don't really care about AI, making stuff isn't really my goal. Would Go be a good option to learn? I like this funny looking lil nigga, reminds me of my dog.
>>110038452it's fun.Just ignore the haters that will come in 1 second complaining about verbosity and muh bad if err nilHint: it's not bad. It's actually fucking good.
>>110038452If you aren't even aiming to be employable you might as well learn something fun like Smalltalk or CL or at least Odin or something. Go is a boring, soulless cubefarm codemonkey language.
>>110038452Go is a very good language. Lua is also good.
>>110038452go is not a beautiful language by any means and is quite unimaginative but it is very pragmatic
>>110038452Use ai>I don’t care about aiThen die, snailcat
python would be the smartest to learn, but you shouldn't be thinking about learning a programming language - learn to program
>>110038497>you shouldn't be thinking about learning a programming language - learn to programCan you elaborate what you mean, anon
>>110038518He means he's devoid of metacognition and never stopped to reflect how the programming languages he uses are shaping the way he thinks about problems.
>>110038518>be you, absolute luddite>probably reading this on a screen you think steals your soul>some tech bro tells you to "learn to code">you start sweating, thinking you have to memorize a 10,000-page dictionary of beep-boop matrix symbols called Python or C++>you think the secret is memorizing the exact spelling of the commandsngmi (not gonna make it)listen here anonlearning a specific programming language is literally just learning how to hold a hammerwho cares if you know how to hold a hammer, a wrench, or a nail gun if you don't know how to build a freaking house?the languages change every 5 years anyway. what's trendy today becomes legacy garbage tomorrowthe syntax (where the brackets and semicolons go) is just spelling. AI can do the spelling for us now anywaylearning to program, on the other hand, is learning how to thinkit's taking a massive, chaotic, real-world problem and violently smashing it down into tiny, autistic little steps that even a stupid rock filled with lightning (a computer) can understandit's pure logic. "if X happens, do Y. until Z is empty, repeat X."once you actually understand the logic of how to build the house, picking up a new hammer (learning a new language) takes like a weekthe language is just the translation layer between your brain and the microchipstop hyperventilating over which language to learnlearn how to solve the puzzle firstnow go back to churning butter or whatever it is you do
>>110038452Once you learn a language, you can more simply pick up another in a week, if the synthax isnt autismo or hyper-creative/stupid. It is more difficult to remember what is available to you in the standard library, and where to look if you want to make a map, or a binary search tree or something like that. What is really important when starting programming, is to be in an environment with a lot of visual feedback, simple debugging, and a lot of creative spark that can motivate you to try to do new things. I started programming in game engines, at that is what motivated me to continue programming. And eventually my projects got more and more independant, and more low level. Go has a cute mascot, but i think that it is mostly used for server backend stuff, and it probably reflects in its standard library. It also has a slow foreign function interface, but maybe that ain't a problem for you.
>>110038452>>110038555Also, words you need to know are: IDE, language server, intelli-sence, compilation, building a program, and the rest is breadcrumbs
>>110038452>I've always been very self-conscious about being too retarded to understand technologyIf your goal is to understand computers and you don't care about building useful things, try C. It will teach you how a computer works better than the other suggestions in this thread.
>>110038452>I've always been very self-conscious about being too retarded to understand technologyIf your goal is to understand computers and you don't care about building useful things, try Assembly. It will teach you how a computer works better than the other suggestions in this thread.
>>110038452Unironically, I think Go is a great choice. Low-level enough that concepts like pointers, types and thinking a little bit about memory and compiler are still there, but high-level enough to not want to kill yourself because it takes a day to write an http endpoint.
>>110041257ASSembly is too hard. I'm a tech wizard and even I don't understand it.
>>110041625Also, if you really want to learn avoid vibe coding at all costs, pick up a book (although that Joel Bodner one is fucking too convoluted at times, even for seasoned programmers) read it and write little programs. Only ask AI questions when you don't understand what's written in a book or what certain code means (prefer per line and maybe even per word why's rather than asking how this function works). Also, don't ask AI questions why something doesn't work, try to figure it out yourself, only ask why something works.
>>110041257This is a true statement.
>>110041631I feel like assembly isn't hard, but more like too much meaning detached from code. You literally have to assume that placing value in a special magic register means something.
>>110038452go has a retarded syntax despite supposedly being a simple languagefoo := []string{"foo", "bar", "bar"}when it could've just beenfoo := {"foo","bar","baz"}it makes the code unreadable as shit
foo := []string{"foo", "bar", "bar"}
foo := {"foo","bar","baz"}
>>110041932It's maybe a small syntax sugar and yes, it could've been better, but then I rarely write literal slices like that anyway. Not a deal breaker.
>>110038452Start with JavaScript so that you'll be better able to appreciate Go.
>>110041932But then how's the compiler support to infer the type of {}?
>>110041947syntax is like accenteven if your grammar is perfect, if you have a repulsive accent then your words are incomprehensiblego is next to perl when it comes to being unreadable
>>110041984string{} is fine, but not []string{}, when you can't even specify the length of the list like [10]string{}
string{}
[]string{}
[10]string{}
>>110038452>I don't understand technology >I want to make programs that require the use of technology to work Good morning SAAR!
>>110041988Rust is unredeable, maybe Bash. Go is fine. Syntax quirks are easy to get used to. Sure , I don't like everything about Go either, but normally you just ignore the little annoyances and just learn and write in the language anyway and then the little annoyances either become irrelevant or you maybe even grow to appreciate them. I can program in maybe 10 languages and I can also tell you what I used to think was pretty can start to look ugly or boring after a while.
>>110042019I am usually on board with shitting on Indians, but I don't get this one, if anything, Op's stance is the opposite of an average pajeet poster.
>>110038452I wouldn't start with Go. It doesn't have the features 90% of other languages do. It's strengths are asynchronous tasks, which can be confusing for a new programmer.Java would unironically be a good start.
>>110038452learn python, it was literally made for retarded nocoders, go is more for retarded google cooders
