What do you feel are the biggest problems with the programming community at large?
Name:
Steve2017-03-01 23:58
python
Name:
Anonymous2017-03-02 0:08
Too much computer power. Everyone in the world should be given 700 MHz processor to work with (the exception being NASA, the LHC and other people who *really* need more power). That would make programmers learn to optimize their crap. There would be no JavaShit and such.
You think you need all that shit to make phone calls and use shitty apps? If they were restricted to a 700 MHz processor and 256 KB of RAM they would get the same functionality (but with better programming languages, more optimizations, less wasteful crap, etc...)
Name:
Anonymous2017-03-02 1:59
Ha, my shit phone has half a gig of ram and can barely open a single web page without OOMing.
Name:
Anonymous2017-03-02 7:57
>>7 That's still weaker than top-notch PC boxes, and not affordable to millions of African negroes who consider 700 MHz a blessing. Plus remember, on mobile devices there's the concern over battery life. And despite all that, approx. zero fucks are given by developers about performance, as >>8 confirms.
Name:
Anonymous2017-03-02 8:50
mobile performance is important
Each mobile site: Pls download 100MB app for optimal viewing OR ELSE
Name:
Anonymous2017-03-02 8:54
>>3 just ban automatic computation altogether. if we execute algorithms in our minds, we'll never use bloated software and we'll all care about memory usage and performance
Name:
Anonymous2017-03-02 9:32
>>11 Then, computer science will be renamed "Mental mathemathics"
Name:
Anonymous2017-03-02 10:04
SJWs
Name:
Anonymous2017-03-02 12:20
Too many idiots and failures are involved. Imagine if bridges were designed by ``architects'' whose only real knowledge about the topic comes from Structural Analysis for Dummies and blog posts. Imagine furthermore that the only reason they became architects is that they failed at everything else and architecture was already so overrun with vermin of their ilk that for once they weren't thrown out of a field. This is the state of programming today. The entire field is populated by mental midget teenagers, teenaged or otherwise, with unwarranted self-importance who first horribly break everything and then attempt to sell you their ``replacement'', which does approximately what the old thing did, except not really and kinda worse, while being three times as big.
This is, to me, the biggest problem of all. There are certainly other problems, such as a complete disregard for elegance and simplicity or the increasing subversion of open source projects by faggots who want to abuse them for political and financial gains, but there is no hope of solving these without addressing the bigger problem which provides fertile soil for them.
Name:
Anonymous2017-03-02 12:36
>>14 Code is not valued. Code monkeys from third-world countries are treated the same as talented programmers. There isn't a point writing "good code" for a company which views you as temp code monkey, easily outsourced/replaced. Its fundamental problem since managers believe Programming to be a commodity profession, like some Code Plumber.
Name:
Anonymous2017-03-02 18:53
SJWs, copying and pasting code from Stack overflow, macfags, teenagers, plebblitors
Name:
Anonymous2017-03-02 20:00
copying and pasting code from Stack overflow
One of these things isn't like the others. SO content is vital to answering hard questions fast. Are you pretending you never visit it?
Name:
Anonymous2017-03-02 20:49
>>17 I see this so often and I always think "well here is a guy who never actually does programming" beyond /g/ programming thread.
Typing out a stanza of fstat/fopen/fclose 50x doesn't make you a good programmer who "understands" files better than sombody smart that looked it up online, understood it and put it in their code.
It's a kind of "elitism" from below. Insecure non-programmers are trying to look intelligent so they advocate hard work and manual effort but this one of the things that really comes off as absurd - it exposes the fact they're just armchairing.
Name:
Anonymous2017-03-02 21:44
Why do garbage collected languages need to manually close the files?
Name:
Anonymous2017-03-02 22:06
if you're implying that you'd rather closing files was hooked into GC: just no. this is a terrible idea.
Name:
Anonymous2017-03-02 22:13
>>19 Because the kernel has a limit on how many file descriptors you can have open at any time, and you usually can't predict when or even if the garbage collector will run.
Name:
Anonymous2017-03-02 22:18
I think any language with GC has closing files hooked into GC, since you won't be able to reach them anymore anyway. It's still a bad idea to leave closing the files to the garbage collector.
>>21 You can if it is RC. Also you have a limit on memory too.
Name:
Anonymous2017-03-03 0:49
>>19 Kernel resources are subject to stricter limits than program memory. Misbehaving programs have far more leeway to leak memory without impacting the rest of the system than they do for network sockets, file handles, fonts, etc.
For example, older versions of Windows had a limit of 1200 GDI objects. When those were exhausted, programs would start to fail and the window manager itself could crash, often bringing the whole system down with it. You can't afford to release critical resources only when the GC kicks in.
Now, if your language runtime provides a deterministic guarantee about when the GC will run, and how long it will take, then GC-driven resource management would be feasible. But most languages with automatic memory management don't give you any such guarantees.
>>23 Any community that gets its laughs by pretending to be idiots will eventually be flooded by actual idiots who mistakenly believe they are in good company.