It also mentions that two years ago programming should be renamed googling stack overflow. If you're using stack overflow that often, you probably don't know how to program. Should you never use stack overflow? of course you should use it sometimes, but if you're using it for every single thing, you're not thinking enough and/or shouldn't be programming.
It's sometimes useful for programming projects in school. But once I figured out how to read the write-up on a function(it looks like pure gobbledygook to a newb), and see a small example of how it's used(by playing with it), I don't have to revert to stack overflow much. Besides, that place can be pure fucking cancer sometimes.
Java security plagued by crappy docs, complex APIs, bad advice • The Register
'They looked at common concerns related to secure Java coding, common development challenges, and common security vulnerabilities. '
'The researchers had nothing nice to say about Spring, which accounted for 55 per cent of the Java security implementation questions that were analyzed. '
'Stack Overflow answers also recommended trusting all SSL/TLS certificates to bypass cert verification errors, even though this disables SSL security checks. '
'And they found that many of the answers endorsed by the Stack Overflow community led to insecure code. '
'The paper recommends that developers spend more time testing security features, avoid disabling security checks, and exercise caution with community answers. '
Java was designed specifically to allow marginal and mediocre coders to write code that would be clunky tacky and ugly - and still run without crashing. It was designed for the Pajeet straight out of the mud hut. Asking anything more from the people who do Java? You gotta be kidding. Forget it.
5 comments
2 u/jcal22x 30 Sep 2017 17:21
Is this news?
1 u/Norm 30 Sep 2017 18:07
It also mentions that two years ago programming should be renamed googling stack overflow. If you're using stack overflow that often, you probably don't know how to program. Should you never use stack overflow? of course you should use it sometimes, but if you're using it for every single thing, you're not thinking enough and/or shouldn't be programming.
1 u/Plavonica 01 Oct 2017 05:06
It's sometimes useful for programming projects in school. But once I figured out how to read the write-up on a function(it looks like pure gobbledygook to a newb), and see a small example of how it's used(by playing with it), I don't have to revert to stack overflow much. Besides, that place can be pure fucking cancer sometimes.
0 u/derram 30 Sep 2017 16:19
https://archive.fo/lFRdD | :
'They looked at common concerns related to secure Java coding, common development challenges, and common security vulnerabilities. '
'The researchers had nothing nice to say about Spring, which accounted for 55 per cent of the Java security implementation questions that were analyzed. '
'Stack Overflow answers also recommended trusting all SSL/TLS certificates to bypass cert verification errors, even though this disables SSL security checks. '
'And they found that many of the answers endorsed by the Stack Overflow community led to insecure code. '
'The paper recommends that developers spend more time testing security features, avoid disabling security checks, and exercise caution with community answers. '
This has been an automated message.
0 u/10677862 03 Oct 2017 00:19
Java was designed specifically to allow marginal and mediocre coders to write code that would be clunky tacky and ugly - and still run without crashing. It was designed for the Pajeet straight out of the mud hut. Asking anything more from the people who do Java? You gotta be kidding. Forget it.