C all the way
Anyone who uses Java should get hit by truck-kun
Have no fear, best /g/irl is here.
>went to school to be a cpa
>find out programming is becoming a ever attractive skill to have in the field
Annnd now I have a masters in cis. Never thought id be with the /g/ degenerates tho
What projects are you guys working on right now
>Spend years working hard at your major
>Only ever use the basics at work
>All the productivity gains and shit that management loves is a bunch of scripts, often done in VBA
>Be promoted for being a code-monkey with financial knowledge
You did the right thing.
learning gtk theming and keyboard firmware, for maximum rice
This is practically the rebellious teen of programming languages
Making stupid and arbitrary syntax changes ``just because'' only makes shit hard to read. It took me over an hour trying to learn Ant Colony just because the jackass who wrote it and SEO'd his website to the top of Google decided to do it in Ruby.
Python is really only suitable for scripts and other relatively short programs.
Attempting to do anything complicated in python (which means touching OOP) and you will feel like you have cancer.
Any language with syntax similar to C++ should be fine, but for simplicity's sake I think you should go for C#.
Modern C++ usage (14/17) involves the use of smart pointers, which are kind of complicated. That's not to say that you can't or shouldn't use raw pointers, but smart pointers are a hell of a lot more complicated for a developer to use than any other memory management system.
>/g/ is so bad that we have to have discussions in /a/ now
>Half-assing my CS major
>Third semester done, going to the fourth
>Still don't know what the fuck am I doing
Seriously, I need to install Java and Python on my PC but just procastinating
depends on what context.
I really like C++ in general though, and will point to MS's treatment of their other languages (e.g. VB, VBA, VBScript) as reasons not to go with C# as a bunch of others here are suggesting
Socket programming in C. It's great fun. Hoping to combine it with OpenGL to make something interesting.
/g/ is basically a combination of /wsr/, /v/, and /pol/.
I actually am currently using it for work and I do enjoy it. However I haven't used any feature that isn't present in other IDEs.
>Microsoft's treatment of their other languages
lel, you have no idea how hard they're pushing C#
They open sourced the compiler, they open sourced the core parts of .NET Framework
This language is going on for the long haul. If you pay attention to the language's design, it was literally designed to replace Java. If it weren't for it's shit Tuple implementation (even in C# 7), I'd say it's basically perfect.
I had this idea of an app that recognizes manga raw pictures on smartphone cameras and overlays translated lines over the word bubbles with appropriate 'subtitle' files loaded.
Actually making a working prototype would be a programmer's job
>with appropriate ``subtitle'' files loaded
good luck with getting people to roll with that shit. Never happening.
I'm personally a fan of booru style translating, but I know when to give up.
You'll also be shit out of luck trying to scan, warp, and correlate image matching across a massive database. Even Google wouldn't be able to do that. Their image matching algorithm shits itself if you change the base color of the page.
I was thinking the subtitle files themselves would contain the necessary image data for each 'chapter' of raw manga, but then again it would be a hassle to keep loading different files for each chapter.
>oh neat a programming thread this will be fun
>it's talk about C, C#, python, or ruby
every fucking time i swear to god does anybody on this website know anything beyond basic dynamic programming
how can you fucking fail a C# course what the fuck
Despite being in its elementary stages, it's surprisingly powerful. I'm interested to see where it goes as a language.
Depends. Was it a CS 101 course or something more complex?
It was supposed to be this kind of re-education type course because I can't find a job with my current degree (law). I like to excuse myself by saying that I'd never done anything related to programming before, but maybe I'm just dumb.
did my last summer of college at a C# shop and I have to admit the amount of built-in profiling is nice and has a good learning curve at first, but I had trouble getting as much out of it as gdb/valgrind/etc
I've been meaning to for years but haven't got around to it - it looks like it has solid functional options and that shit's like crack to me.
It's Tuple implementation is shit-tier compared to Python, where Tuples were baked into the language at design time.
C# 7.0's new tuples have unpacking now, but it stinks of a beta feature. It doesn't really mesh well with C#'s other fancy as hell features. I remember trying to use it and it didn't work in anything involving lambda expressions.
You misread the statement. You would fail at trying to figure out which subtitle file to load. Your idea is a gargantuan task that Google hasn't solved (more for lack of trying than anything else)
Probably because you don't actually understand computer logic and are forcing yourself into learning a language without understanding what the language is doing.
Pick up a book on computer systems and learn how the computer operates, how computers translate high level language to some form of machine code, basic data structures and how they expand in different ways, anything that isn't just straight language programming.
Knowing how a computer works, and thinking like a computer, helps understanding programming techniques and what stuff is like.
>I've been meaning to for years but haven't got around to it - it looks like it has solid functional options and that shit's like crack to me.
It does. Also DUB, the package manager, is pretty nice.
Im a /3/ artist i need more Chinese cartoons that pander to me.
It's less about Java as a language (it sucks by the way), and more about WHO uses Java. Namely, street-shitting Indians who know nothing and ruin codebases just by being around.
Would you want to be associated with street-shitters that ruin codebases? Would you want to work with them? Would you want to clean up their messes? I sure as fuck wouldn't.
Back in the day a lot of C/C++ progarmmers had to learn Java because it's applets were basically the only way to deliver non-shitty content via the internet. The resentment never went away.
>awful speed because everything has to be cycled through the JVM, the resources required for even simple operations grows at a ridiculous rate, slows down your entire machine at amplitudes greater than the next best language
>awful security issues, often bugs are generated not from programming oversight, but because the language's conversion is so crap
>infested with idiots learning their first language because retard CS professors thought Java was a good intro language (it isn't, at all)
the list goes on and on
>literally just 5-10% slower than C++
The only legitimate complaint about java is its strange inheritance system. Other than that it is pretty cool.
says the NEET who's never had to work with retards before.
I have literally never seen such a helpless culture that needs so much handholding before. If you've been programming long enough, you've visited blogs everywhere. When a dumbass who demands (yes DEMANDS) handholding posts in the comment section, they're invariably Indian.
(it's a surprisingly affective backend language)
>Despite being in its elementary stages, it's surprisingly powerful. I'm interested to see where it goes as a language.
Powerful my ass.
Even basic procedures need macros to work.
Yes I'm talking about print!, vec!, also that unwrap() bullshit.
Naming your class Ref, Vec, Cell, Box... doesn't help, either.
python or any form of functional programming language (haskell, scala, ML, lisp)
But for the sake of understanding at the most basic elements, Python is a very good beginner language.
This basically >>159608213. I learn C++ now and whenever I read about its fuckups like when to use auto and when decltype(auto) I imagine someone from /g/ standing over me with anime-smug face on.
>Powerful my ass.
>Even basic procedures need macros to work.
Rust macros are not C/C++ macros. They are safe and hygienic, and they need a proper grammar to be defined.
>that unwrap() bullshit
Unwrap is less common in production code, as it's just a way to ignore error handling in code samples.
>class Ref, Vec, Cell, Box
What is the problem with this? Also they are structs, not classes. There are no classes in Rust.
hey guys you are forgetting your anime pics please
seconding this, if only for interface default methods (used sparingly, but still useful)
* garbage collection
* it takes a fuckton of memory and basically never returns it to the OS for as long as the process lives
* VM'd language with JIT compilation runs slower
* the JVM has a pretty bad record on security
* Oracle suing people (Google) over use of the Java API
* Spring enabling some truly heinous bullshit
It's important that someone's first programming language should be imperative.
There's a balance you need to make between "how computers actually work", and "reasonable to use on a daily basis"
FPs are far and away not how computers work, and are better learned after programming language pragmatics (that's a book) are understood. You need to slowly and steadily unravel the magic into shit that makes sense. This is hard to do because FP is basically pure magic. "Why do things this way instead of that way?" Once language design choices are understood, FP starts to make true sense.
Start with C to properly understand memory management, then jump to modern C++ or C# for OOP. Learn a scripting language (Python) and a functional language (Scala) down the road, but you'd probably want to learn SQL before going there.
Nah, I'm just shitting around. Not touching that shit with a mile long stick.
Can't wait for wider wasm support already, to further deprecate it, instead of all these attempts to polish a turd.
So does anyone know if Elma actually ends up learning how to program?
>Start with C to properly understand memory management, then jump to modern C++ or C# for OOP
There's no need to go that route, you can learn proper memory management through any computer systems book, and python has OOP as well.
Trust me, just learn python as a beginner. The language will make way more sense with basic syntax and structure offered in python than it will in C.
C is quite frankly an awful language for a beginner.
despite not liking python in general (even smallish projects in dynamically typed languages are nightmares to inherit), I like it as a first language since it tends to be pretty straightforward and has a nice shell
If you go too low level the new programmers will not get a correct view of the power and theory of computation. FP is all about abstractions. Abstraction in imperative code are severely constrained, so a new programmer will have trouble wrapping their heads around it. Imperative programming is better left as a specialized field. FP is the true fields of academics.
its either going to be kotlin (for the backwards compability) or dart (cuz its an in house for google language). personally I think kotlin is a more appeling option because of the backwards compability however that means that we will still be cucked with the jdk meaning that you will be albe to write java till the end of the days of android.
I recommend you learn something you'll find fun/useful projects for
If you're still in HS, learn TI-BASIC, programs on your calculator tend to be fair game for standardized tests
If you play games, get involved in their modding community - writing RS bots was where I started. It's a good way to keep yourself interested
I took C# basics for luls in my uni and that shit was not for me. Well yeah I could make a program to save shit in table and get it from there but it took me quite a while.
I would say the chances we are both just idiots is pretty high since everybody else seemed to have no problems.
Why people say that C is a good language to start learning?
It's no like you will understand how to allocate memory or how to work with pointers when you barely know anything about programming. I have seen many students fail when trying to learn C as their first language.
If you go too high level, new programmers are going to assume that programming languages are magic, and are simply going to just ``try'' things all the time without even bothering to think about whether or not what they're ``trying'' will work or not.
Without a basis to understand how their programming language works, what they will ``try'' will explode in scope to an unmanageable extent.
Learning programming languages at a lower level and understanding language design choices will significantly constrain what they will ``try.''
You say abstraction, they hear ``magic'', and in any field of engineering, magic is something that must be severely and relentlessly contained.
How autistic do you have to be to enjoy reimplementing the same functions over and over, especially in a language that is sensitive to whitespace and so ends up punishing you for copy-pasting?
Well I mean, it was the original high level programming language.
And unless you hate yourself and are willing to write machine fucking specific Assembly, you can't get any closer to direct machine in hardware manipulation like you can in C.
C++ with bazel for builds. Anything else makes me puke these days. Haven't given Go or Rust honest tries yet, but the lack of open source third party libs will probably piss me off.
Also want to find time to play more with Julia.
If I remember right, I think they included Kotlin support directly in the SDK, yeah. But that's basically because Kotlin runs on the JVM.
Basically, it doesn't seem like Android will drop the JVM any time soon, and at best they might just make their own language to work with Android's implementation. I somehow doubt they'll try to fully migrate to something like Dart.
Not everyone that is learning how to program will inmediately try to hack into the compiler to understand every bit of the produced binary either. Understanding and being able to create good abstractions is a better skill to get at the first stages than the knowledge of how to optimize a software to run in the best way possible.
I remember taking a course in college and finding this textbook extremely useful in terms of understanding stuff
The downside is that it talks about all of the computer stuff with C as the language for example.
But you can slowly actually learn what the fuck C is doing in the process and it will make you a better programmer on a whole.
It's dense though, fair warning.
Also, there's free pdfs online I think, so you don't have to shill out hundreds for it.
And I mean, there are hundreds of computer systems books out there, don't be afraid to look around for one that might be a bit simpler and uses an easier language to understand like Python.
That's what I meant. It'd probably be easy-ish to get the text inside bubbles, but considering how much of a nightmare redrawing and editing text outside bubbles can be, even with a few hours spent on them, a program probably wouldn't be able to do much better.
All this talk about "best" prog.languages, when most of the time you need to choose one for the job, even if it is PHP in the end. Personally I find Java the most appealing, you can use it for mid to enterprise level microservices and apply any frontend you want. But again, C# is amazing if you need to work in windows environment and sometimes you can't escape c++.
>assembly is actually fun, i don't get why it is frowned upon - of course only use it for modular stuff it can speed up you c project considerably
Is this a serious fucking post?
PHP is the eva of web dev languages. Respect it.
i am being serious, yes - that being sad i am doing embedded stuff right now
i still find assembly to be fun and you should really learn assembly if you want to have any chance of reverse engineering something
>major in polsci
>had to learn python
I never asked for this
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>assembly is fun
Um, yeah no thanks I don't want to write architecture specific fucking assembly.
> learn assembly if you want to have any chance of reverse engineering something
Learning the absolute basics of assembly is all you need to know for RE, and even then you rarely have to do much assembly writing yourself unless you're writing a PWN exploit or something.
Like what the shit, never in my life have I ever encountered anyone autistic enough to enjoy writing in Assembly
When I say ``learning an imperative paradigm first'' is important, optimization is totally irrelevant.
In a perfect world, we would start with MIPS or another RISC assembly, because this will teach people the limits of computation. They will understand how a computer operates and not impose some unreasonable standard akin to magic, built up by decades of amazing language design. We then gradually pile on the abstractions. They would fully understand how these abstractions are designed by compiler developers.
You won't see where I'm going with this until we reach our end goals. See, when computer programmers actually understand how their languages are built and designed, when they write their programs, they will have less questions.
You often hear novice programmers talking about how a program fails if they ``remove a comment''--well, if those novice programmers understood how their language was designed, they would be able to think more deeply about the code they wrote than simply, ``I don't get it!"
consider me your first then
php really is a pain and if you want to do something outside of normal scripts and not break compatability or use php's shitty external-program gateway you have to extend the php engine and this one's a REAL mess
>preinstalled to any OS
maybe some dev-tier linux distro
>PHP is the cheapest
Getting a cheap VPS and setting up a webserver that doesn't use PHP is easy as fuck though.
Pretty much every Linux distro comes installed with it.
Welcome to the new age. Everything is technology now.
Knowing basics or at least how to do some spreadsheet or statistics operations in some programming language is vital now.
>i don't see any harm to admitting to enjoy assembly and it really does speed up your code
because you are LITERALLY WRITING MACHINE CODE
The amount of pure concentrated autism and ridiculous amount of time you would need to have to write assembly has to be soul crushing.
And doing it for fun???
i had to extend it for someone else, he wanted to only run signed scripts and allow third party retards (most likely indians (>>159608263)) to upload scripts to the main dir, which would only run in a test sandbox (not signed) and not production (signed)
for some reason splitting the testing from the production site was not an option
You'd be surprised how much of the stuff we use daily is Java and surprisingly not shit.
If I recall, the entirety of AWS is pretty much all Java and it is **the** benchmark we compare all cloud services too.
as i said don't write a whole project in assembly - i mean you can (and i did before) if it's not too big, but it really helps for speeding up your c code (especially cryptographic stuff)
just try writing a tiny os in x86 asembly it's actually intriguing
If people had to go from assembly to the actual abstractions that people use in common everyday programming to learn programming, maybe five of a thousand freshmen would actually make it to the end of their major courses.
Programming languages were made because people wanted to hide all those ugly limitations about computers and just focus on the logic. Besides, if we go with the problem of understanding a programming language, more than having to understand the produced machine code, it's better to understand the programming language theory to get a better idea of how code gets compiled to a lower level representation.
>I enjoy writing in assembly
I mean who the fuck enjoys writing something like this?
>hate for interest in esoteric peculiar shit
Reflect upon your self and leave.
>i mean you can (and i did before) if it's not too big
Jesus christ why would you torture yourself like that.
>but it really helps for speeding up your c code (especially cryptographic stuff)
Because it's fucking machine code you are literally changing the direct hardware instructions, of course optimizing them would make your programs run faster.
I've written in assembly before, it's an abysmal experience.
>not wanting to feel like an elite hacker
I'm sorry, I've met a lot of autists in programming, CE, and the math field, but never have I met anyone who enjoyed writing assembly, not even my professors.
Just blown away by the pure autism of this one anon. Admirable in a way.
and that's one reason why being able to program in assembly is a good thing and it IS used in the industry, have a look at openssl for example everything is optimised using assembly
Assembly with mnemonic instructions can be fun if your salary doesn't depend on it, it's simialr to solving CS problems. I had to write x64 assembly code in deprecated asm that didn't support x64 instructions in uni, now that was autism.
>dumbed down assembly is fun
Ok sure, something like RISC architecture with an easy overlay of instructions can be fun.
But pure x86? And having to track your own machines' memory? God that sounds nightmarish.
tracking your own memory is actually part of the fun - for me at least
the way i see it is that i have to simulate a x86 machine in my head, which will lead to an actual deep understanding of computers
well thank you for being nice, anon
That's why I said ``in a perfect world.'' The way you mentioned is the way I learned programming throughout college, and is the mainstream way of doing it. It works, I guess.
This is why I focused on imperative paradigms.
Higher level imperative languages have the advantage of assembly without the disadvantage of being encumbering--being completely honest, learning assembly is almost a waste of time, because you still learn all of the same concepts by learning C, while C is much more familiar to other languages.
You don't have to learn how an abstraction compiles to assembly. That's too much, and is frankly a waste of time. The way I learned more advanced abstractions--closures, lambdas, tail call optimization, functional programming's insistence on immutable structures and how that leads to optimizations--were all through the familiar language of C and whiteboard drawings. This method is perfectly sufficient for how I think people should learn programming languages.
>hating on CS problems
I found them fun in uni. I remember taking Computer Theory classes that were math heavy that had some neat discrete probability problems we had to solve.
If I go into Machine Intelligence track will I learn how to program my own virtual waifu?
I'm serious here, I told my classmates I'm interested in it because of Siri and all that but really I'm just lonely
>started my day literally typing static IP on every employee personal laptop on our company
>sysad is too tech illiterate to configure router and setup the IP on the firewall and just selected access point and called in the day
>duplicate fucking IP everywhere
Holy fuck, what a shitty day to start.
You can't be a retard and write assembly. It's not easy to write.
They may be turbo autists, but they aren't retards.
Machine Learning is the hottest thing out there right now. The market for it is fucking huge, and if you've gone to any hackathons or hacking competitions (building hacking, not DEFCON hacking) within the past 5 years or so, you'd know machine learning is literally THE buzz at all of them.
>Rust macros are not C/C++ macros. They are safe and hygienic, and they need a proper grammar to be defined.
Also slow. And rust is already slow to compile.
And compare to Elixir they are shit.
"Perfectly fine" isn't an adjective I'd use for Java. "Good enough" is more appropriate.
You use Java when neither productivity nor performance matter much. You use it when you want to get a working program while hiring the cheapest possible workforce where each individual programmer is easily replaceable. Even then, C# is as good as Java at that particular niche.
Doing a Siri-like system is not something you can build in your spare time. You can try to customize a readily available chatbot though, this is easy.
Now talking seriously, machine learning is very useful, but being a ML Engineer is VERY different from your typical programming job. Being a data scientist is different from being a programmer.
>You can't be a retard and write assembly.
There are varying fields of retardism.
Intelligence isn't linear. IE, someone who can solve complex equations instantaneously, but can not function at all like a normal person in every other field is definitely a retard of some extent.
In all honesty no, but I do setup routers on my relative's network now and then.
I just have the feeling that all this hard work could have been solve by just a couple of clicks.
Java is as productive as you can get while mantaining some very good performance.
That a ton of low tier fucks know it is related to it being seen as highly productive. That a lot of these low wage fucks will then go about writing the shitties worst code you have ever seen is a different problem and unrelated to the language.
And C# is pretty much a copy of Java, so what would you expect. Even then one of the main pushing things behind Java was "write once, deploy everywhere" which Microsoft sort of forgot about while doing their thing, and so failed to kill Java. They later wisened up a bit about it.
Nah, Ruby is still popular in Japan, in ways that it never was popular in the west.
Over there, it's a general purpose programming language, over here it's the language you use to program Rails apps. That's why Ruby is dying in the west, because Rails has many competitors.
It's also sponsored by the government so that helps.
>get involved in their modding community
>the "modding" community for the only game i play is just cheats
>against a literal rootkit of an anticheat
maybe not the best to start their for me
Are there any good resources on how Ruby's used in Japan? It's always interesting reading about how things develop in different countries.
Die and reincarnate as something not human, like a sunflower or a toaster or something.
Nah, writing Java, even if you're extremely skilled with Java, is a drag. You can get used to it, but humans are very good at getting used to uncomfortable shit. That's just how the language is designed, the priorities lie in a different place (namely, safety and verbosity).
>Even then one of the main pushing things behind Java was "write once, deploy everywhere"
Never once have I written (or seen) a non-trivial program in Java that I could run without any modification or special considerations on multiple OSes. Even if the JVM works on every OS out there, you still have to account for all the small differences between OSes.
In theory, it's "write once, deploy everywhere," but in practice it's about as portable as modern C++.
I am going through the end of my medicine Uni and the moment I will get my degree I will enter Tech Uni to get that sweet CS degree.
Being a programmer is like being a citizen of a modern civillisation. You know secrets of how things work around you that other people have no idea about.
If ou want to be an ultimate human being knowing programming is a must.
csgo & esea
but i am the desperate idiot
My school taught it as a first language. And I ended up programming significantly in it. If anything, in work it really showed me the importance of understanding what you're working with, especially with performance issues.
It's also made learning multiple languages much easier to understand. As a hobbyist with no actual teachers, its a poor choice. You will just end up making mistakes and endlessly repeating them.
Do tell then, what language do you think is more productive. I can't think of any OOP language that makes things even easier than Java while still being usable for non toy projects.
A friend and I are working on a game using libGDX.
Programmed on my own for 3 years during uni and another year at work. I'm a dumbass and I've realised it's not for me anymore.
That's cool anon, I hope the best for you.
> Essentially doing IT work at my job
> If I ever get to do any coding like I was hired to do it'll either be in COBOL or Access.
Series' name is SE (Systems Engineering).
who cares, i'm just put off by the knowledge i would need to stay undetectable from esea's anticheat and the manual inspections
well the promise sells I guess. That blossomsoft guy (yeah that one who delivered a quite decent game back in 2008, then wasted 9 years developing the second one; I always visit his site to promote self-confident: look that guy is one of us) got excited about it too.
My code is as good as they come
>comfy /g/ thread in /a/
Is this what paradise feels like?
>Finished Bachelors in CompSci
>Now about to do Masters
>No fucking idea what I'm doing with my life
At least I enjoy programming, but I have no real life experience with it, so most of the shit I've learnt are going to go out of the window I'm sure.
Did I get memed? I have a hunch that once I start working full time my enjoyment of programming is gonna cease.
I'm sure you're the kind of person who has a massive directory tree to hide his porn, with filepaths such as
>E:\documents\f\ff\fff\1\2\3\not porn\definitely porn\please don't judge\gay_sex_with_hats_on.jpg
I'd have probably stayed to get my Masters if I could afford to. I mean it'd be a chance to chill at school another few years. Probably gain fuck all from it though. Certainly won't help me finding a programming gig I want and it definitely won't give me any work to show to employers, if my BS is anything to go off of.
look into directory services, if you are not using a windows server and i pray to god you don't look intio freeipa for example, implement a proper system to manage the network and it's clients and get a raise
>paying for your masters
you guys are retards
You're supposed to get the company you work for to pay for your masters.
Software development as a career is in a bubble. You want as much work experience as you can get before it pops. The more specialized your work the better, so going to college is fine, but work experience takes priority.
That way you won't have such a hard time when you're fighting guys with 5 or 10 years experience over entry level positions in the next few years.
don't worry, I cleaned it up
>but I have no real life experience with it
You didn't get memed you got exactly what you paid for, Getting real life experience through other opportunities was something you should've done on your own.
fixed your code
mov ax, 0x03
mov ax, 0x0700
mov bh, 0x0f
xor cx, cx
mov dx, 0x184f
mov si, text_string
mov ah, 0x0E
cmp al, 0
text_string db 'Hello World!', 0
times 510-($-$$) db 0
Lol. Say that to US universities with their "safe spaces" and shit.
My university actually took effort to pass. From some 800 only 200 got bachelors and from those only 50 got master's.
>90% of all issues are misconfigurations due to BAs not communicating properly
>bet you at least 400 would get their bachelors and wouldn't fuck around.
This hasn't been the case in the US, instead what happened is that standards had to be continually lowered in order to not upset paying customers. Also universities succumb to industry demands and thus prepare students for whatever the industry requires at that particular moment, instead of providing a general education.
I wanna learn ASM, especially 6505 because that used to be popular to code old video games in. According to many anons it seems to be a lot less popular nowadays because even programmers with a degree barely use it and because it's tough to learn it. Nevertheless, I'd love to learn it if I had more time this upcoming summer.
Also, when will there be a good anime with programming?
>trying to learn programming to get a job
>don't have any projects I want to work on
Well I mean New Game is that.
Unless you mean like actual programming, where they go into detail about the programming, in which case never because that'd be boring as shit and no one would watch.
Setup a pastebin like this(not mines): https://github.com/Bonfire/Programming-Challenges
Or find something you like and make something for it for example I play plenty of POE and I was tired of faggots sniping good ass trade deals from me because they made their own trade bot so I ended up making my own small trade indexer that pulls directly from the POE item stream.
Honestly, working on game exploits or scripts starts to make the creativity side of programming projects way easier.
>want to write exploits for Overwatch but Blizzard when ridiculously overboard with their protections for the game, making it extremely difficult to exploit
Fucking mega-ASLR I swear to god.
And I've heard they'll sue the shit out of you too.
Some videogame related stuff would be fun but there aren't that many games out there that actually support modding anymore. Hell you're lucky to even have fucking public servers. Don't really care about trading.
A reverse-engineered client for Steam Link in Rust, though I've been prioritizing anime recently.
Audio/video/input works but not decoder stats feedback so the connection times out if there's no input for about a minute and there's no variable bitrate support (assuming the native encoder even does VBR, which I'm not sure of).
This is literally the first multiplayer PC game I have ever played where I have not had to worry about cheaters at all.
If anything I say they're doing a good job. They didn't even need to put in a fucking rootkit either.
>because I made a one letter error in my code
Do you not know what IDE's are?
It sounds like you gave up after 3 days.
I haven't had an issue with misspelling or dumb errors like that since the 1st day I started programming.
>Gosling: For me as a language designer, which I don't really count myself as these days, what "simple" really ended up meaning was could I expect J. Random Developer to hold the spec in his head. That definition says that, for instance, Java isn't -- and in fact a lot of these languages end up with a lot of corner cases, things that nobody really understands. Quiz any C developer about unsigned, and pretty soon you discover that almost no C developers actually understand what goes on with unsigned, what unsigned arithmetic is. Things like that made C complex. The language part of Java is, I think, pretty simple. The libraries you have to look up.
Gosling is even more of a hack than Miyazaki could ever dream of being.
Those old consoles were coded fpr in console specific assembler.
The commented code helps, but what you get from disassembling the rom is very similar to the real thing.
For example, not a nes game, here is the code for Prince of Persia on the apple 2 which was uploaded by the developer after he found it in a floppy some years ago:
Well they made it virtually un-decompilable (sp?) and it's completely randomized systems layout is impossible to trace.
There's no basic framework to go off of, they're not evident player frames/structure that's made evident (like in CS:GO it's basically a fucking 2-plane variable distribution of the character, you just need to change the "X and Y coordinates" to match a player).
Like the game is fucking unbreakable so far.
Good on them, clearly not overboard on their side of things.
>almost no C developers actually understand what goes on with unsigned
Are C devs really this shit or is Gosling just a fag?
I mean, I guess most devs without formal education won't know about 2s complement, but still.
It's a shame, overwatch is such a well polished game but it's crippled by deep fundamental problems with the gameplay and art design that will never be resolved.
not really as assembly is machine specific and the numbers refer to the instruction set and cpus are usually numerically encoded so numbers were a logical choice
stuff where it doesn't matter doesn't have numbers of course - the main thing being the syntax with the two most widely used ones being intel or at&t
Whenever I learned to program I couldn't help but think that i'm wasting my life away. There is just nothing intrinsic there for me, no problems i would like to show, all I can think of is autism bux. It also doesn't help that the more my programmer friend is working the more of a "programmer's mind" he acquires, to a point where he needs to break everything into simple tasks.
>numbers refer to the instruction set
Yes but these could have been named or given reduced code names, 65816 mode referring to one word, and 6502 referring to another.
Then again it was the 80/90's, so they probably didnt care about such things.
>tfw incredibly slow at programming and better at reading and understanding how code works than actually making it myself
I still can't write code of any kind properly and all I'm doing is copying code from other projects and explanations on the web and rigging it to work for my school projects.
On top of that I'm getting no real sense of fulfilment of the work I'm doing.
I think my question right now is; Is what I'm experiencing a skill/time issue? Cause I'll be honest in that the only times I program is for assignments
You need to sit down and think.
Writing programs as a beginner takes a lot of time. It's a very time consuming field, frankly.
You need to sit and think explicitly about what's happening inside of the computer. Not with your own logic, but how the computer does something.
The more you do this, the more you'll start to actually learn it.
I see you never learned how to learn.
Understanding code by reading it is easy. The people who wrote it often have a decent understanding of what it is they wrote, and the underlying logic behind which they wrote it is often highly pragmatic and easy to understand.
You lack the pragmatism and understanding they have, so it's no wonder that you're unable to produce the same result. This is a common phenomenon in standardized college assignment-tier work, and further a common symptom of sophomore anxiety. You'll get over it eventually.
The mainstream method of pedagogy used to teach programming and software engineering to college students often produces this result. Confusion, anxiety, then very late-stage enlightenment and understanding.
Obviously only programming for your assignments is going to hamper your ability to learn. If you don't dictate your own requirements and fulfill them, you will never get a feel for writing code outside of a sterile environment, and you will never be able to apply and test the rigorousness of the pragmatism and understanding acquired during class to more diverse project requirements.
Not the problems that have barely any complexity in them and should be solved by instinct. There is just this heaviness in him and he started to talk way less than before.
Still, he is quite good, eager to learn and his teaching method is metal as fuck. It's just that some programmer qualities seem to contradict with enjoying the life.
>really slow at programming
>copying and pasting code
Well duh anon how are you supposed to get better if you cut your learning in half. Programming is like learning a language you learn how to write/speak and then you learn how to read/listen.
While functionally identical, the first notation has the implication "this is a pointer to an array" while the second one has the implication "this is a pointer to a pointer, who knows what is there".
Making readable code is a big partof what makes a good programmer, think about the implications of what you're writing.
so the bottom line is I never knew how to program to begin with then. Time to go back to the beginning in my own time then.
What's a good place to actually begin with C# or C++
it's c we're talking about it is indeed a pointer to a pointer which is how it really works and anyone that has some kind of knowledge of how c works will understand this piece of code.
and i'm saying that if you have an understanding of c it is indeed readable, thus producing readable code.
maybe you should learn to stop being passive aggressive and actually read and understand?
``readable'' does not mean ``it can be parsed''
Just because the compiler understands does not mean that it's readable.
Syntax provides context. Context provides readability.
>complaining about readability, calling a function f instead of inferring what it does from the name
in this case it wants a pointer to an int not an array, see the previous posts
that's going a long way, just because you are unable to read it doesn't mean everybody else is unable to, you are not the standard of anything. and comparing c to js is a joke
If all you ever do is school assignments you probably skip buisness logic part and then do more problem solving than actual coding. Like, half-assedly coming up with architecture in your head and then trying to implement it step by step by googling and copy-pasting examples until it works somehow. Most people who work in teams know what needs to be done so they have nothing to be confused about. School assignments shouldn't be too hard on analytical part, just take a piece of paper and describe your domain and define class structure before coding. Think in interfaces, that's what OOP is for. Implementation should be easy and fast then, especially in something like C#.
I had fun reading Head first Java and Servlets/JSP with Spring and their long retarded class name only to use and apply what I learn in C#/ASP.NET MVC. It's fun backtracking Java code and finding how elegant C# deals with that area, blowing my mind everytime.
Java was my first language but I truly felt NTR'd.
You're missing the point.
Syntax provides context. Context provides readability.
If a static analyzer cannot read your code and determine the intent of a function or variable, YOU are the one who is going to have to figure out the intent of that function or variable.
A static analyzer can figure out that int is a 2D array. A static analyzer can't figure out that int** is a 2D array. But you can do some crawling and figure that out yourself.
Do you WANT to do that?
While you might not find it in the spec, the language design choices of C# and other new-ish .NET languages make it plainly obvious that they are languages optimized to be statically analyzed. The resulting product, Intellisense, is considered by and far the greatest achievement amongst IDEs.
>Like, half-assedly coming up with architecture in your head and then trying to implement it step by step by googling and copy-pasting examples until it works somehow.
It's like you're in my head right now cause that's exactly what I've been doing up till now.
>this is a solution
>jerry rig the solution
I think it might've given me a bad outlook on programming too, cause all its done is make me angry every time I do something cause it doesn't work and I spend hours looking for a solution.
Say I want to (re)learn C++ or C# based on my later post, are there any books or sites I can consult to actually LEARN the language instead of jerry rigging like I've been doing for all my school projects the past few years?
it all just comes down to personal preference, you know? i absolutely despise int and you should go through the code and understand what the fuck you are actually doing
the function will get a copy of a pointer are you sure you are able to read function signatures?
Arrays do not exist in C like they do in other programming languages.
int  is syntactic sugar for int *, and calling var is the same as *(var + (sizeof(var) * 2)). It's just memory, trying to abstract it just makes it more confusing.
>the function will get a copy of a pointer are you sure you are able to read function signatures?
I am, the one who seems unable to do it is you.
>you should go through the code and understand what the fuck you are actually doing
Ah, so you don't actually do any productive coding, nevermind then. Black box and encapsulation are the pillars of scalability.
/g/ has been taken over by /v/ and other boards for years now. Nothing has really changed.
The /v/-style immaturity of claiming that 'x' absolutely has to be the best and everything that is not 'x' is inherently shit because they are not the best, is prevalent across the board.
> someone hasn't read "the spineless tagless gmachine" or "making a fast a fast curry"
Instead of shitposting you should educate yourself on the implementation of functional languages.
>go through the code and understand what the fuck you are actually doing
At the level we're talking about, this is meaningless busywork that detracts from actually writing the business logic. Let the static analyzer handle that for you.
Things like this are the reason why C++ does not have good Intellisense. Elements of C++ are simply not compatible with static analyzers.
you do realise that if you declare your array like
it is creating a pointer
to an array it will allocate and free as soon as it's out of scope?
you can pass an array declared as int i or an int i using &i
Yup, but as I said, trying to abstract it just makes it harder to read. Writing C like it was java or python makes it pajeet tier but writing it like it was a superset of ASM makes it god tier and simple.  is unnecessary, but all hail goto.
Yes, I do. I know all this.
How can you be missing the point this hard.
>Yup, but as I said, trying to [make it explicit] just makes it harder to read.
In what bizarre ass backwards planet?
INTEL WAS KELLED IN ACTION BY AMADA!
>In what bizarre ass backwards planet?
>Treating memory like it is
>Creating abstractions like arrays that don't work in practice like they do on paper
It's a damn good thing the abstractions are optional in C.
It was a question of the pointer datatype and how the value is actually stored. In different applications the pointer could be an actual pointer, a slot in memory containing the address to something else. In smaller functions and especially when dealing with the stack arrays in scope the pointer doesn't really exist like K&R explains it, as it's optimized to be a value being passed around in registers without having a real physical memory location.
You're missing the point.
Any non retard C dev knows that arrays are pointers and such. If the "mix" confuses you, you're just some shit tier dev that shouldn't be employed.
On the other hand, nobody (not even future you) ever knows what the arbitrary function signature you made needs if it's not explicit. So you give them tools to understand your code as easily as possible. You don't make it pointlessly ambigous.
>int[N][M] for 2d array
contiguous in memory, NxM memory consumption
pointer to a list of pointers, Nx(M+1) memory consumption
one of these is *strictly worse* than the other
>Serverless aka aws lambdas functions are making backend devs redundant.
>React and Vue making web app experiences that are on-par with native mobile apps.
>Being in high-demand anywhere in the world, even for remote jobs
Web dev is in a golden age right now.