subreddit stringclasses 7
values | author stringlengths 3 20 | id stringlengths 5 7 | content stringlengths 67 30.4k | score int64 0 140k |
|---|---|---|---|---|
programmingcirclejerk | Audiblade | g85wxmw | <|sols|><|sot|>I consider debuggers to be a drug -- an addiction. Programmers can get into the horrible habbit of depending on the debugger instead of on their brain.<|eot|><|sol|>https://www.artima.com/weblogs/viewpost.jsp?thread=23476<|eol|><|sor|>> I teach a lot of classes in C++, Java, C#, TDD, XP, Patterns, etc. In those classes I often have the students write code. It is not unusual for me to find a student with his or her nose buried in a debugger, painstakingly stepping from line to line, examining variables, setting breakpoints, and generally wasting time. The bug they are tracking could be found through simple inspection of the code.
Damn millennials, not being able to instantly understand everything wrong with a piece of code that uses an idea they explicitly are being taught about for the first time in their careers. They should muddle through it by changing bits randomly until it works like I did, not killing the Stack Overflow industry by painstakingly seeking to actually have a thorough insight into what's going on.<|eor|><|eols|><|endoftext|> | 10 |
programmingcirclejerk | Pastoolio91 | g85fc7b | <|sols|><|sot|>I consider debuggers to be a drug -- an addiction. Programmers can get into the horrible habbit of depending on the debugger instead of on their brain.<|eot|><|sol|>https://www.artima.com/weblogs/viewpost.jsp?thread=23476<|eol|><|sor|>Who needs debuggers or a brain when I can code purely with my base instinct. I close my eyes and feel the rivers of code flow forth from my nimble fingers with the productivity of 1000 10x'ers. Recently, I've noticed programmers can get into the horrible habit of depending on looking at the computer screen, instead of being one with the essence of the code. To be a 10,000x'er like me, you must become the code. You do not make errors. The outside world is the error.<|eor|><|eols|><|endoftext|> | 10 |
programmingcirclejerk | nmarshall23 | g85ddyo | <|sols|><|sot|>I consider debuggers to be a drug -- an addiction. Programmers can get into the horrible habbit of depending on the debugger instead of on their brain.<|eot|><|sol|>https://www.artima.com/weblogs/viewpost.jsp?thread=23476<|eol|><|sor|>17 years later this still holds true. People have yet to realize that they just need to write correct code.<|eor|><|sor|>> Since I started using Test Driven Development in 1999, I have not found a serious use for a debugger.
Just imagine what this guy is capable of when he finds out he can use a debugger on his unit tests.<|eor|><|sor|>()
How does one learn this black art?<|eor|><|eols|><|endoftext|> | 10 |
programmingcirclejerk | Audiblade | g85wbyr | <|sols|><|sot|>I consider debuggers to be a drug -- an addiction. Programmers can get into the horrible habbit of depending on the debugger instead of on their brain.<|eot|><|sol|>https://www.artima.com/weblogs/viewpost.jsp?thread=23476<|eol|><|sor|>I use a text editor, I don't need that BLOAT of an IDE killing my computer, I see all the variables in my head or just use print.<|eor|><|sor|>Don't get me started about bookmarks, I know exactly at what line each function is.<|eor|><|sor|>You use functions? I just hardcode jumps to specific memory addresses. Sure, you have to remember what's in each byte of your compiled program, but it's not like it's hard to keep track of.<|eor|><|eols|><|endoftext|> | 9 |
programmingcirclejerk | norzn | g84m1vk | <|sols|><|sot|>I consider debuggers to be a drug -- an addiction. Programmers can get into the horrible habbit of depending on the debugger instead of on their brain.<|eot|><|sol|>https://www.artima.com/weblogs/viewpost.jsp?thread=23476<|eol|><|sor|>I laughed at this, then I debugged a bit.<|eor|><|eols|><|endoftext|> | 8 |
programmingcirclejerk | silentconfessor | g84nlbr | <|sols|><|sot|>I consider debuggers to be a drug -- an addiction. Programmers can get into the horrible habbit of depending on the debugger instead of on their brain.<|eot|><|sol|>https://www.artima.com/weblogs/viewpost.jsp?thread=23476<|eol|><|sor|>lol vintage jerk<|eor|><|eols|><|endoftext|> | 8 |
programmingcirclejerk | Dominus543 | g855siv | <|sols|><|sot|>I consider debuggers to be a drug -- an addiction. Programmers can get into the horrible habbit of depending on the debugger instead of on their brain.<|eot|><|sol|>https://www.artima.com/weblogs/viewpost.jsp?thread=23476<|eol|><|sor|>Rewrite it in Rust and debuggers will not be needed anymore.<|eor|><|eols|><|endoftext|> | 8 |
programmingcirclejerk | DoomFrog666 | gxevsm | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|eols|><|endoftext|> | 152 |
programmingcirclejerk | orgulodfan82 | ft1iih4 | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>This is brilliant on the part of the people rejecting this guys language-switch proposals. Its like when parents promise their kids that they can have something but only after they accomplish some impossible task.
Wed totally be on board to stop the world, retrain all of our devs in Go, and then switch over and rewrite everything, but, uhh, that one curly brace is really a deal breaker. Get that changed and well talk!<|eor|><|sor|>Your comment is a little misguided. You're implying that the whitespace between control flow statements and curly braces is irrelevant, but consider the following example:
if err != nil {
return err
}
I think anyone who is at least moderately bright will agree that this is terribly cluttered, ugly and tough to read. However with one simple change we can transform it into this:
if err != nil
{
return err
}
Immediately the code becomes so much clearer. You can tell just at a glance what the purpose of this code is.
We all need to realize that programming languages are not just about generics and abstractions and all that. They are about bridging the gap between man and machine, and if they are to accomplish that, they must be easily readable not just to experienced code artisans such as I, but also to Jimmy, who just finished a 3 week-long bootcamp and is looking to contribute value to the company, or Eric, the CTOs nephew with 2 years of BASIC experience. I sincerely hope that you don't just brush aside these facts that I brought up and really think about what something as simple as a line break can achieve in terms of inclusivity and shaping the IT industry as a whole.<|eor|><|eols|><|endoftext|> | 83 |
programmingcirclejerk | PragmaticFinance | ft1bxcr | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>This is brilliant on the part of the people rejecting this guys language-switch proposals. Its like when parents promise their kids that they can have something but only after they accomplish some impossible task.
Wed totally be on board to stop the world, retrain all of our devs in Go, and then switch over and rewrite everything, but, uhh, that one curly brace is really a deal breaker. Get that changed and well talk!<|eor|><|eols|><|endoftext|> | 68 |
programmingcirclejerk | AaronPaulie | ft1v3u1 | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>I'll take 'things that scream "I'm a bad programmer" for 800 Alex'<|eor|><|sor|>Is it:
A) evangelizing the new shinies when it doesnt matter
B) caring about syntactical trivialities
C) go
D) all of the above<|eor|><|eols|><|endoftext|> | 31 |
programmingcirclejerk | TimeWarden17 | ft1b8pm | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>I'll take 'things that scream "I'm a bad programmer" for 800 Alex'<|eor|><|eols|><|endoftext|> | 25 |
programmingcirclejerk | ninjaaron | ft33lp3 | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>/uj hold on for just a hot minute there. I didn't know the Go parser would take a dump if a bracket was on the next line. I've never never actually tried it because 1) Allman style, lol and 2) I've only tried Go a couple timesbut geez, talk about lazy. Having a canonical format for the community is fine, but creating a broken parser in the name of coding style is so gross.<|eor|><|eols|><|endoftext|> | 22 |
programmingcirclejerk | Puzomor | ft3nj7y | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>/uj hold on for just a hot minute there. I didn't know the Go parser would take a dump if a bracket was on the next line. I've never never actually tried it because 1) Allman style, lol and 2) I've only tried Go a couple timesbut geez, talk about lazy. Having a canonical format for the community is fine, but creating a broken parser in the name of coding style is so gross.<|eor|><|sor|>/uj the real jerk is the reason for that. Go inserts ; at the end of the line so the programmer "doesn't have to worry".
This produces situation where seemingly correct code like the brace example doesn't work, and makes the programmer think even harder about "how will the go compiler fuck me over this time".
Beautiful counter effect. Even worse, gophers still justify it in the most circlejerk matter, and here we are laughing at a guy who thought having a newline won't break the compiler.<|eor|><|eols|><|endoftext|> | 20 |
programmingcirclejerk | CodeReclaimers | ft3y46g | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>(Stop (using (brackets (you (filthy (casuals .))))))<|eor|><|eols|><|endoftext|> | 14 |
programmingcirclejerk | TimeWarden17 | ft1wi8j | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>I'll take 'things that scream "I'm a bad programmer" for 800 Alex'<|eor|><|sor|>Is it:
A) evangelizing the new shinies when it doesnt matter
B) caring about syntactical trivialities
C) go
D) all of the above<|eor|><|sor|>D, but mostly B<|eor|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | lordlicorice | ft3ivq7 | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>This is brilliant on the part of the people rejecting this guys language-switch proposals. Its like when parents promise their kids that they can have something but only after they accomplish some impossible task.
Wed totally be on board to stop the world, retrain all of our devs in Go, and then switch over and rewrite everything, but, uhh, that one curly brace is really a deal breaker. Get that changed and well talk!<|eor|><|sor|>Your comment is a little misguided. You're implying that the whitespace between control flow statements and curly braces is irrelevant, but consider the following example:
if err != nil {
return err
}
I think anyone who is at least moderately bright will agree that this is terribly cluttered, ugly and tough to read. However with one simple change we can transform it into this:
if err != nil
{
return err
}
Immediately the code becomes so much clearer. You can tell just at a glance what the purpose of this code is.
We all need to realize that programming languages are not just about generics and abstractions and all that. They are about bridging the gap between man and machine, and if they are to accomplish that, they must be easily readable not just to experienced code artisans such as I, but also to Jimmy, who just finished a 3 week-long bootcamp and is looking to contribute value to the company, or Eric, the CTOs nephew with 2 years of BASIC experience. I sincerely hope that you don't just brush aside these facts that I brought up and really think about what something as simple as a line break can achieve in terms of inclusivity and shaping the IT industry as a whole.<|eor|><|sor|>In the next meeting I will yell "this is all about brackets, and you know it!", slamming the table. We have to rise the awereness about this. Let's unveil the truth!<|eor|><|sor|>Smh, that kind of lazy, imprecise verbiage is exactly why you'll never be a true 10x developer. `{`s are braces and `[`s are brackets.<|eor|><|eols|><|endoftext|> | 12 |
programmingcirclejerk | randompecans | ft53f38 | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>(Stop (using (brackets (you (filthy (casuals .))))))<|eor|><|sor|>/r/ihavesex(pressions)<|eor|><|eols|><|endoftext|> | 11 |
programmingcirclejerk | bunnies4president | ft5v7k4 | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>I'll take 'things that scream "I'm a bad programmer" for 800 Alex'<|eor|><|sor|>Is it:
A) evangelizing the new shinies when it doesnt matter
B) caring about syntactical trivialities
C) go
D) all of the above<|eor|><|sor|>E) preferring Allman style over K&R<|eor|><|eols|><|endoftext|> | 11 |
programmingcirclejerk | AaronPaulie | ft1vp1p | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>[deleted]<|eor|><|sor|>Just tell them that if they stop using _ for that random extra throwaway return value they can copy and paste three extra lines everywhere.<|eor|><|eols|><|endoftext|> | 9 |
programmingcirclejerk | ignlg | ft3bqct | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>This is brilliant on the part of the people rejecting this guys language-switch proposals. Its like when parents promise their kids that they can have something but only after they accomplish some impossible task.
Wed totally be on board to stop the world, retrain all of our devs in Go, and then switch over and rewrite everything, but, uhh, that one curly brace is really a deal breaker. Get that changed and well talk!<|eor|><|sor|>Your comment is a little misguided. You're implying that the whitespace between control flow statements and curly braces is irrelevant, but consider the following example:
if err != nil {
return err
}
I think anyone who is at least moderately bright will agree that this is terribly cluttered, ugly and tough to read. However with one simple change we can transform it into this:
if err != nil
{
return err
}
Immediately the code becomes so much clearer. You can tell just at a glance what the purpose of this code is.
We all need to realize that programming languages are not just about generics and abstractions and all that. They are about bridging the gap between man and machine, and if they are to accomplish that, they must be easily readable not just to experienced code artisans such as I, but also to Jimmy, who just finished a 3 week-long bootcamp and is looking to contribute value to the company, or Eric, the CTOs nephew with 2 years of BASIC experience. I sincerely hope that you don't just brush aside these facts that I brought up and really think about what something as simple as a line break can achieve in terms of inclusivity and shaping the IT industry as a whole.<|eor|><|sor|>In the next meeting I will yell "this is all about brackets, and you know it!", slamming the table. We have to rise the awereness about this. Let's unveil the truth!<|eor|><|eols|><|endoftext|> | 8 |
programmingcirclejerk | UsingYourWifi | ft3k11x | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>[deleted]<|eor|><|sor|>The only choice if you have any interest in living a morally pure life.<|eor|><|eols|><|endoftext|> | 7 |
programmingcirclejerk | ninjaaron | ft3ou99 | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>/uj hold on for just a hot minute there. I didn't know the Go parser would take a dump if a bracket was on the next line. I've never never actually tried it because 1) Allman style, lol and 2) I've only tried Go a couple timesbut geez, talk about lazy. Having a canonical format for the community is fine, but creating a broken parser in the name of coding style is so gross.<|eor|><|sor|>/uj the real jerk is the reason for that. Go inserts ; at the end of the line so the programmer "doesn't have to worry".
This produces situation where seemingly correct code like the brace example doesn't work, and makes the programmer think even harder about "how will the go compiler fuck me over this time".
Beautiful counter effect. Even worse, gophers still justify it in the most circlejerk matter, and here we are laughing at a guy who thought having a newline won't break the compiler.<|eor|><|sor|>I guess looking ahead wouldn't be brutally practical.<|eor|><|eols|><|endoftext|> | 7 |
programmingcirclejerk | t0mRiddl3 | ft1jfhb | <|sols|><|sot|>I cannot get Go adopted for new projects because experienced developers are not prepared to write and look at ugly unreadable code all day long<|eot|><|sol|>https://github.com/golang/go/issues/39421<|eol|><|sor|>I'll take 'things that scream "I'm a bad programmer" for 800 Alex'<|eor|><|sor|>nil<|eor|><|eols|><|endoftext|> | 6 |
programmingcirclejerk | AmateurHero | gqxd15 | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|eols|><|endoftext|> | 152 |
programmingcirclejerk | ConcernedInScythe | frvdue2 | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>maybe we could even write tests to ensure that functions aren't called with arguments of the wrong type, and streamline the process by using some sort of abstract interpretation that only checks type-level behaviour rather than sampling a handful of concrete values<|eor|><|eols|><|endoftext|> | 195 |
programmingcirclejerk | AmateurHero | frvermr | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>maybe we could even write tests to ensure that functions aren't called with arguments of the wrong type, and streamline the process by using some sort of abstract interpretation that only checks type-level behaviour rather than sampling a handful of concrete values<|eor|><|soopr|>This is such an insult to the creator of JS. If he wanted a deep type system, he would have added one from the start. You dont get a language as big as JS without proper planning and years of agonizing research with user testing.
Go back to your dinosaur langs like C and Java.<|eoopr|><|eols|><|endoftext|> | 111 |
programmingcirclejerk | NedDeadStark | frvll84 | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>lol thinking one won't still write hundreds of unit tests even while using Typescript.<|eor|><|sor|>You guys are writing tests ?!?<|eor|><|eols|><|endoftext|> | 51 |
programmingcirclejerk | escaperoommaster | frvrabo | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>> You dont get a language as big as JS without proper planning and years of agonizing research with user testing.
(X) doubt<|eor|><|sor|>I think it means "get" as in "understand"
> [One cannot understand] a language as big as JS [because it does not have] proper planning and years of agonizing research with user testing.
It's an easy mistake to make<|eor|><|eols|><|endoftext|> | 48 |
programmingcirclejerk | shami1kemi1 | frvtaeb | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>maybe we could even write tests to ensure that functions aren't called with arguments of the wrong type, and streamline the process by using some sort of abstract interpretation that only checks type-level behaviour rather than sampling a handful of concrete values<|eor|><|soopr|>This is such an insult to the creator of JS. If he wanted a deep type system, he would have added one from the start. You dont get a language as big as JS without proper planning and years of agonizing research with user testing.
Go back to your dinosaur langs like C and Java.<|eoopr|><|sor|>> dinosaur langs
lol no deno<|eor|><|eols|><|endoftext|> | 40 |
programmingcirclejerk | ProfessorSexyTime | frvhn76 | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>lol thinking one won't still write hundreds of unit tests even while using Typescript.<|eor|><|eols|><|endoftext|> | 39 |
programmingcirclejerk | relok123 | frviqwc | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>This, but with
console.log(); console.log(); console.log(); console.log(); console.log(); console.log(); console.log(); console.log(); console.log(); console.log(); console.log(); console.log(); console.log(); console.log();<|eor|><|eols|><|endoftext|> | 38 |
programmingcirclejerk | SoInsightful | frvrwqf | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>> You dont get a language as big as JS without proper planning and years of agonizing research with user testing.
(X) doubt<|eor|><|sor|>To be fair, it's not like JavaScript was created by one dude in 10 days.
Wait, *it was?* Shit.<|eor|><|eols|><|endoftext|> | 36 |
programmingcirclejerk | NotSoButFarOtherwise | frvpf24 | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>maybe we could even write tests to ensure that functions aren't called with arguments of the wrong type, and streamline the process by using some sort of abstract interpretation that only checks type-level behaviour rather than sampling a handful of concrete values<|eor|><|sor|>/uj
I was using a JS library that occasionally threw a "string" instead of throwing an "Error". Testing in TS/JS is actually quite nice because its pretty easy to mock something stupid like that:
`mockCamera.getPicture.and.callFake(() => {`
`// tslint:disable-next-line: no-string-throw Cordova throws errors like this`
`throw 'Unable to retrieve path to picture!';`
`});`
On the other hand, TS/JS is quite horrible in that the library could throw whatever it liked in the first place.
/rj what kind of language wouldn't let you throw your entire codebase as an error?<|eor|><|sor|>>/rj what kind of language wouldn't let you throw your entire codebase as an error?
Holy shit! I never thought of that. Why bother throwing exceptions - imposing the runtime overheard of object creation and ultimately causing GC churn - when you can just having the offending function throw itself? No messy stack traces to deal with, either - just find the bug and fix it!<|eor|><|eols|><|endoftext|> | 29 |
programmingcirclejerk | wrkbt | frvemzp | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>maybe we could even write tests to ensure that functions aren't called with arguments of the wrong type, and streamline the process by using some sort of abstract interpretation that only checks type-level behaviour rather than sampling a handful of concrete values<|eor|><|sor|>That would reduce the amount of busywork that makes me feel I am doing something significant. The only thing left for me would be finding a Go gig :/<|eor|><|eols|><|endoftext|> | 28 |
programmingcirclejerk | BurkusCat | frvmbz7 | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>maybe we could even write tests to ensure that functions aren't called with arguments of the wrong type, and streamline the process by using some sort of abstract interpretation that only checks type-level behaviour rather than sampling a handful of concrete values<|eor|><|sor|>/uj
I was using a JS library that occasionally threw a "string" instead of throwing an "Error". Testing in TS/JS is actually quite nice because its pretty easy to mock something stupid like that:
`mockCamera.getPicture.and.callFake(() => {`
`// tslint:disable-next-line: no-string-throw Cordova throws errors like this`
`throw 'Unable to retrieve path to picture!';`
`});`
On the other hand, TS/JS is quite horrible in that the library could throw whatever it liked in the first place.
/rj what kind of language wouldn't let you throw your entire codebase as an error?<|eor|><|eols|><|endoftext|> | 22 |
programmingcirclejerk | stone_henge | frwdadu | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>maybe we could even write tests to ensure that functions aren't called with arguments of the wrong type, and streamline the process by using some sort of abstract interpretation that only checks type-level behaviour rather than sampling a handful of concrete values<|eor|><|sor|>/uj
I was using a JS library that occasionally threw a "string" instead of throwing an "Error". Testing in TS/JS is actually quite nice because its pretty easy to mock something stupid like that:
`mockCamera.getPicture.and.callFake(() => {`
`// tslint:disable-next-line: no-string-throw Cordova throws errors like this`
`throw 'Unable to retrieve path to picture!';`
`});`
On the other hand, TS/JS is quite horrible in that the library could throw whatever it liked in the first place.
/rj what kind of language wouldn't let you throw your entire codebase as an error?<|eor|><|sor|>>/rj what kind of language wouldn't let you throw your entire codebase as an error?
Holy shit! I never thought of that. Why bother throwing exceptions - imposing the runtime overheard of object creation and ultimately causing GC churn - when you can just having the offending function throw itself? No messy stack traces to deal with, either - just find the bug and fix it!<|eor|><|sor|>I always throw a Fetch promise that resolves to the xkcd comic that best describes the problem<|eor|><|eols|><|endoftext|> | 21 |
programmingcirclejerk | UsingYourWifi | frvvm0r | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>lol thinking one won't still write hundreds of unit tests even while using Typescript.<|eor|><|sor|>You guys are writing tests ?!?<|eor|><|sor|>I tell people that, it helps with getting jobs, but the last time I wrote a test was 4 years ago, and it was during an interview coding session.<|eor|><|sor|>As far as I can tell tests only exist in interviews.<|eor|><|eols|><|endoftext|> | 19 |
programmingcirclejerk | CptJero | frw020g | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>maybe we could even write tests to ensure that functions aren't called with arguments of the wrong type, and streamline the process by using some sort of abstract interpretation that only checks type-level behaviour rather than sampling a handful of concrete values<|eor|><|sor|>/uj
I was using a JS library that occasionally threw a "string" instead of throwing an "Error". Testing in TS/JS is actually quite nice because its pretty easy to mock something stupid like that:
`mockCamera.getPicture.and.callFake(() => {`
`// tslint:disable-next-line: no-string-throw Cordova throws errors like this`
`throw 'Unable to retrieve path to picture!';`
`});`
On the other hand, TS/JS is quite horrible in that the library could throw whatever it liked in the first place.
/rj what kind of language wouldn't let you throw your entire codebase as an error?<|eor|><|sor|> function window() {
throw Myself;
}<|eor|><|eols|><|endoftext|> | 17 |
programmingcirclejerk | icholy | frvxmux | <|sols|><|sot|>"Another thing I disliked about TS, which instead is praised by many, is the type system. In general I think that the best option, especially for highly dynamic languages, is to write a large number of tests, to cover as many cases as possible, and to ensure that the application state is coherent."<|eot|><|sol|>https://old.reddit.com/r/javascript/comments/gqkpob/askjs_i_prefer_vanillajs_to_typescript_change_my/<|eol|><|sor|>maybe we could even write tests to ensure that functions aren't called with arguments of the wrong type, and streamline the process by using some sort of abstract interpretation that only checks type-level behaviour rather than sampling a handful of concrete values<|eor|><|sor|>/uj
I was using a JS library that occasionally threw a "string" instead of throwing an "Error". Testing in TS/JS is actually quite nice because its pretty easy to mock something stupid like that:
`mockCamera.getPicture.and.callFake(() => {`
`// tslint:disable-next-line: no-string-throw Cordova throws errors like this`
`throw 'Unable to retrieve path to picture!';`
`});`
On the other hand, TS/JS is quite horrible in that the library could throw whatever it liked in the first place.
/rj what kind of language wouldn't let you throw your entire codebase as an error?<|eor|><|sor|> throw window<|eor|><|eols|><|endoftext|> | 17 |
programmingcirclejerk | yeetingAnyone | gg2o8h | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|eols|><|endoftext|> | 149 |
programmingcirclejerk | johnnyapol | fpxopwb | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>Luckily this guy was only emotionally invested - I put the deed to my house up as collateral for a bet that Rust will replace all the C in the Linux kernel by 2022.<|eor|><|eols|><|endoftext|> | 89 |
programmingcirclejerk | isthistechsupport | fpxggw3 | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>I, of course, find it unbearable whenever someone doesn't recognize that the only moral option, by necessity, can't fail at anything! To acknowledge such a ludicrous thing means granting victory to that evildoer that is Teh Script<|eor|><|eols|><|endoftext|> | 62 |
programmingcirclejerk | Vaglame | fpxxe33 | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>> Please be nice to the author as usual. I am not the author ;)
> hit me instead ;)
This community has a lot of issues to work through<|eor|><|eols|><|endoftext|> | 49 |
programmingcirclejerk | Stargateur | fpxpdhv | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>Luckily this guy was only emotionally invested - I put the deed to my house up as collateral for a bet that Rust will replace all the C in the Linux kernel by 2022.<|eor|><|sor|>sorry for your loss<|eor|><|eols|><|endoftext|> | 29 |
programmingcirclejerk | Vaglame | fpygvf9 | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>> Please be nice to the author as usual. I am not the author ;)
> hit me instead ;)
This community has a lot of issues to work through<|eor|><|sor|>;)<|eor|><|sor|>I feel like you're about to do `unsafe { something() }` to me<|eor|><|eols|><|endoftext|> | 27 |
programmingcirclejerk | cheeto_snorter | fpxpgg3 | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>I, of course, find it unbearable whenever someone doesn't recognize that the only moral option, by necessity, can't fail at anything! To acknowledge such a ludicrous thing means granting victory to that evildoer that is Teh Script<|eor|><|sor|>I thought you were describing Javascript until the last two words, I am literally shaking rn I can't take this bs anymore<|eor|><|eols|><|endoftext|> | 24 |
programmingcirclejerk | Shorttail0 | fpz92pi | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>Luckily this guy was only emotionally invested - I put the deed to my house up as collateral for a bet that Rust will replace all the C in the Linux kernel by 2022.<|eor|><|sor|>sorry for your loss<|eor|><|sor|>Loss? We got two more years.<|eor|><|eols|><|endoftext|> | 23 |
programmingcirclejerk | scroy | fpyx2n0 | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>Only someone blind in love in Rust will say Rust is good for math. But that apply to a lot of language. That why we invent python. They code in python, and we translate it to whatever better performing language we want. That why coding is a skill and that science people don't have it :p<|eor|><|sor|>Exactly I see all these scientists writing simulations and providing papers of their work, detailed with proofs, data, etc.
Yet there is no unit tests! How can this be? I don't understand...<|eor|><|sor|> import unjerk
Have you seen the code the average scientist produces? can't unit test when there are no units<|eor|><|eols|><|endoftext|> | 21 |
programmingcirclejerk | ahok_ | fpydmam | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>> Please be nice to the author as usual. I am not the author ;)
> hit me instead ;)
This community has a lot of issues to work through<|eor|><|sor|>[deleted]<|eor|><|sor|>> not using `rg` in 2020<|eor|><|eols|><|endoftext|> | 19 |
programmingcirclejerk | duckbill_principate | fpy4pso | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>> Please be nice to the author as usual. I am not the author ;)
> hit me instead ;)
This community has a lot of issues to work through<|eor|><|sor|>;)<|eor|><|eols|><|endoftext|> | 18 |
programmingcirclejerk | somewhataccurate | fpy4cpd | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>Only someone blind in love in Rust will say Rust is good for math. But that apply to a lot of language. That why we invent python. They code in python, and we translate it to whatever better performing language we want. That why coding is a skill and that science people don't have it :p<|eor|><|sor|>/uj
python should be renamed to cwrapscript
/rj
python should be renamed to cwrapscript<|eor|><|eols|><|endoftext|> | 17 |
programmingcirclejerk | Karyo_Ten | fpzjhqo | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>How did that even make it back to reddit, :P.
I'm the original author of the linked blog post (dead website, I prefer to update my github repo)<|eor|><|eols|><|endoftext|> | 16 |
programmingcirclejerk | pronuntiator | fpylpdo | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>Luckily this guy was only emotionally invested - I put the deed to my house up as collateral for a bet that Rust will replace all the C in the Linux kernel by 2022.<|eor|><|sor|>Luxury. I sacrificed my firstborn to understand borrowing semantics.<|eor|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | Stargateur | fpzeman | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>Luckily this guy was only emotionally invested - I put the deed to my house up as collateral for a bet that Rust will replace all the C in the Linux kernel by 2022.<|eor|><|sor|>sorry for your loss<|eor|><|sor|>Loss? We got two more years.<|eor|><|sor|>Serious mode: While Rust is a very good replacement of C contrary to C++ (no offence just as replacement), there is no point to rewrite linux in Rust, write another new OS in Rust is a good thing but there is no point to rewrite linux in any other language. Basically you will rewrite the OS entirely and worst you will need to keep compatibility (that you don't want).
[https://www.redox-os.org/](https://www.redox-os.org/) is here for that. I think we should not try to change linux language.<|eor|><|eols|><|endoftext|> | 12 |
programmingcirclejerk | three18ti | fpyb6ot | <|sols|><|sot|>For anybody else who is emotionally invested in Rust (like me!) and felt an irrational rage upon seeing somebody describing Rust as "fail[ing] hard": you aren't alone! Take a deep breath...let it all out.<|eot|><|sol|>https://np.reddit.com/r/rust/comments/76olo3/why_rust_fails_hard_at_scientific_computing/dog4q7v?utm_source=share&utm_medium=web2x<|eol|><|sor|>Luckily this guy was only emotionally invested - I put the deed to my house up as collateral for a bet that Rust will replace all the C in the Linux kernel by 2022.<|eor|><|sor|>Are you suggesting that rust won't?<|eor|><|eols|><|endoftext|> | 11 |
programmingcirclejerk | lvinci | dzha1t | <|sols|><|sot|>Kernel Bruh Moment<|eot|><|sol|>https://github.com/torvalds/linux/pull/753/files<|eol|><|eols|><|endoftext|> | 146 |
programmingcirclejerk | _babu_ | f87oavi | <|sols|><|sot|>Kernel Bruh Moment<|eot|><|sol|>https://github.com/torvalds/linux/pull/753/files<|eol|><|sor|>Yeah, now do it on the mailing lists you pussy<|eor|><|eols|><|endoftext|> | 130 |
programmingcirclejerk | CodeReclaimers | f8817fk | <|sols|><|sot|>Kernel Bruh Moment<|eot|><|sol|>https://github.com/torvalds/linux/pull/753/files<|eol|><|sor|>I like [this change](https://github.com/torvalds/linux/pull/684/commits/402f0fff292bd1f4376b4a9b260130494accfd0a#r328547492) better.<|eor|><|eols|><|endoftext|> | 46 |
programmingcirclejerk | lvinci | f88vuqe | <|sols|><|sot|>Kernel Bruh Moment<|eot|><|sol|>https://github.com/torvalds/linux/pull/753/files<|eol|><|sor|>Yeah, now do it on the mailing lists you pussy<|eor|><|soopr|>I want to see linus' response<|eoopr|><|eols|><|endoftext|> | 38 |
programmingcirclejerk | DocMcBrown | f88u0dg | <|sols|><|sot|>Kernel Bruh Moment<|eot|><|sol|>https://github.com/torvalds/linux/pull/753/files<|eol|><|sor|>Reminds me of that epic troll who made a pull request to the MsDOS 1.25 and 2.0 open-sourced GitHub repo where he deleted everything and titled his commit "Refactoring legacy code".
Truly a hilarious prank that will be remembered forever by GitHub connoisseurs.<|eor|><|eols|><|endoftext|> | 36 |
programmingcirclejerk | lvinci | f87yt5b | <|sols|><|sot|>Kernel Bruh Moment<|eot|><|sol|>https://github.com/torvalds/linux/pull/753/files<|eol|><|sor|>import Data.Unjerk
Did you mean to repost this (https://github.com/torvalds/linux/pull/684/commits/402f0fff292bd1f4376b4a9b260130494accfd0a) but couldn't find the original?
Why make a new joke commit that's nearly exactly identical?<|eor|><|soopr|>Ooooof. Idk. You have to ask the author of that commit<|eoopr|><|eols|><|endoftext|> | 22 |
programmingcirclejerk | ArmoredPancake | f87ixgv | <|sols|><|sot|>Kernel Bruh Moment<|eot|><|sol|>https://github.com/torvalds/linux/pull/753/files<|eol|><|sor|>making it more modern
:)<|eor|><|eols|><|endoftext|> | 21 |
programmingcirclejerk | VeganVagiVore | f87xgu5 | <|sols|><|sot|>Kernel Bruh Moment<|eot|><|sol|>https://github.com/torvalds/linux/pull/753/files<|eol|><|sor|>making it more modern
:)<|eor|><|sor|>Finally bringing Linux into the 21st-and-three-tenths century<|eor|><|eols|><|endoftext|> | 20 |
programmingcirclejerk | FreedomKomisarHowze | f89zotn | <|sols|><|sot|>Kernel Bruh Moment<|eot|><|sol|>https://github.com/torvalds/linux/pull/753/files<|eol|><|sor|>Yeah, now do it on the mailing lists you pussy<|eor|><|sor|>PRs for Linux on github is the best designated shitposting zone.<|eor|><|eols|><|endoftext|> | 16 |
programmingcirclejerk | Quartent | f89k8md | <|sols|><|sot|>Kernel Bruh Moment<|eot|><|sol|>https://github.com/torvalds/linux/pull/753/files<|eol|><|sor|>Yeah, now do it on the mailing lists you pussy<|eor|><|soopr|>I want to see linus' response<|eoopr|><|sor|>That git repo is read only. You have to submit a patch to the mailing list. Even then it'll almost certainly be shot down by a maintainer before it reaches Linus.<|eor|><|eols|><|endoftext|> | 14 |
programmingcirclejerk | lvinci | f8aywso | <|sols|><|sot|>Kernel Bruh Moment<|eot|><|sol|>https://github.com/torvalds/linux/pull/753/files<|eol|><|sor|>Yeah, now do it on the mailing lists you pussy<|eor|><|soopr|>I want to see linus' response<|eoopr|><|sor|>That git repo is read only. You have to submit a patch to the mailing list. Even then it'll almost certainly be shot down by a maintainer before it reaches Linus.<|eor|><|soopr|>I know that, that's why I responded that to the mailing lists comment.
And I am sure that you are right on it never reaching Linus.<|eoopr|><|eols|><|endoftext|> | 7 |
programmingcirclejerk | CanIComeToYourParty | f89i6zy | <|sols|><|sot|>Kernel Bruh Moment<|eot|><|sol|>https://github.com/torvalds/linux/pull/753/files<|eol|><|sor|>Makes me wonder if online communities will some day be age restricted.<|eor|><|eols|><|endoftext|> | 6 |
programmingcirclejerk | saulmessedupman | byjr0a | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|eols|><|endoftext|> | 150 |
programmingcirclejerk | ProfessorSexyTime | eqing31 | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|sor|>> I was mad that, while I spent my nights learning F#, my daughter started calling everyone around fathers. And this guy, instead of getting better at his job, went home to his children. And I wanted to punish him.
Tfw your feeling of self-righteousness at work because you think you're a strong developer and obsessive need to learn .NET's OCaml ends up causing you to willingly neglect your family is what will end up causing your daughter to have daddy issues, and will probably end up with your wife cucking you at every moment she can.<|eor|><|eols|><|endoftext|> | 109 |
programmingcirclejerk | syndbg | eqitzay | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|sor|>Title and text bait to read Javascript code<|eor|><|eols|><|endoftext|> | 68 |
programmingcirclejerk | notjfd | eqj4ne7 | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|sor|>> I was mad that, while I spent my nights learning F#, my daughter started calling everyone around fathers. And this guy, instead of getting better at his job, went home to his children. And I wanted to punish him.
Tfw your feeling of self-righteousness at work because you think you're a strong developer and obsessive need to learn .NET's OCaml ends up causing you to willingly neglect your family is what will end up causing your daughter to have daddy issues, and will probably end up with your wife cucking you at every moment she can.<|eor|><|sor|>if your wife isn't cucking you you'll never be a 10xer<|eor|><|sor|>Behind every 10x dev stands a 10x wife.<|eor|><|eols|><|endoftext|> | 62 |
programmingcirclejerk | grantras | eqit1yh | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|sor|>tl;dr I was bullied to the point of almost quitting when I was learning to code, turning me into a jaded asshole so now I'm going to be a dick to other junior devs to perpetuate the cycle of elitism and toxicity in the industry<|eor|><|eols|><|endoftext|> | 37 |
programmingcirclejerk | VeganVagiVore | eqjpwf0 | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|sor|>> I was mad that, while I spent my nights learning F#, my daughter started calling everyone around fathers. And this guy, instead of getting better at his job, went home to his children. And I wanted to punish him.
Tfw your feeling of self-righteousness at work because you think you're a strong developer and obsessive need to learn .NET's OCaml ends up causing you to willingly neglect your family is what will end up causing your daughter to have daddy issues, and will probably end up with your wife cucking you at every moment she can.<|eor|><|sor|>if your wife isn't cucking you you'll never be a 10xer<|eor|><|sor|>Behind every 10x dev stands a 10x wife.<|eor|><|sor|>10x as many partners?<|eor|><|eols|><|endoftext|> | 32 |
programmingcirclejerk | lol-no-monads | eqkstuy | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|sor|>Title and text bait to read Javascript code<|eor|><|sor|>As someone who's about to start a job going from full stack to probably purely front end, Gross. JavaScript is the devil.
Also on the notes that this guy has brought up, it sounds like he's making the place toxic to work at. If your code reviews are just telling people their code is bad, your opening the business up to masses of competent developers thinking that they're useless and looking for other opportunities. If you're bleeding developers and turnover is high, there's a problem. Code reviews are not to tear people's code to pieces, it's a place where people can give advice on how to do things better, a learning place to say why a different way of doing something is more preferable.
Code review is a place of learning, not unabashed criticism. Constant negative comments like "don't do this" or "do this better" aren't helpful and make developers defensive about their code. If you're always on the back heel having to defend your code and your decisions, you're going to burn time arguing semantics and other unnecessary shit until sometime gives up and the project suffers. Unless you're showing people that while their way works fine, a different way is more preferable because it's faster, sticks to standards or more future-proof, why would someone do it any differently? Code reviews are a learning place and to pick up minor things like missed debug statements in code, spelling mistakes and minor fixes. It's not a place to destructively criticize. If that needs to happen, it should be in a performance review, if at all.
The writer of that article is toxic and the product has undoubtedly suffered because of his narcissism. It's good that he's thinking of how to be better, but he's undoubtedly damaged his team and fixing that is an uphill battle.<|eor|><|sor|>Sir, this is programmingcirclejerk, not programminggivethoughtfulcritique.<|eor|><|eols|><|endoftext|> | 30 |
programmingcirclejerk | hiptobecubic | eqim1m7 | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|sor|>Jesus Christ. Company should have fired this guy instead.<|eor|><|eols|><|endoftext|> | 29 |
programmingcirclejerk | monotux | eqirrq7 | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|soopr|>**Warning**: written in an unreadable style<|eoopr|><|sor|>Not sure if you are an asshole picking at the fact that his English isn't perfect as it's not his first language, or if you hate his code formatting.<|eor|><|eols|><|endoftext|> | 28 |
programmingcirclejerk | saulmessedupman | eqibgm5 | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|soopr|>**Warning**: written in an unreadable style<|eoopr|><|eols|><|endoftext|> | 26 |
programmingcirclejerk | Blaz3 | eqkph6z | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|sor|>Title and text bait to read Javascript code<|eor|><|sor|>As someone who's about to start a job going from full stack to probably purely front end, Gross. JavaScript is the devil.
Also on the notes that this guy has brought up, it sounds like he's making the place toxic to work at. If your code reviews are just telling people their code is bad, your opening the business up to masses of competent developers thinking that they're useless and looking for other opportunities. If you're bleeding developers and turnover is high, there's a problem. Code reviews are not to tear people's code to pieces, it's a place where people can give advice on how to do things better, a learning place to say why a different way of doing something is more preferable.
Code review is a place of learning, not unabashed criticism. Constant negative comments like "don't do this" or "do this better" aren't helpful and make developers defensive about their code. If you're always on the back heel having to defend your code and your decisions, you're going to burn time arguing semantics and other unnecessary shit until sometime gives up and the project suffers. Unless you're showing people that while their way works fine, a different way is more preferable because it's faster, sticks to standards or more future-proof, why would someone do it any differently? Code reviews are a learning place and to pick up minor things like missed debug statements in code, spelling mistakes and minor fixes. It's not a place to destructively criticize. If that needs to happen, it should be in a performance review, if at all.
The writer of that article is toxic and the product has undoubtedly suffered because of his narcissism. It's good that he's thinking of how to be better, but he's undoubtedly damaged his team and fixing that is an uphill battle.<|eor|><|eols|><|endoftext|> | 24 |
programmingcirclejerk | Blaz3 | eqkur8c | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|sor|>Title and text bait to read Javascript code<|eor|><|sor|>As someone who's about to start a job going from full stack to probably purely front end, Gross. JavaScript is the devil.
Also on the notes that this guy has brought up, it sounds like he's making the place toxic to work at. If your code reviews are just telling people their code is bad, your opening the business up to masses of competent developers thinking that they're useless and looking for other opportunities. If you're bleeding developers and turnover is high, there's a problem. Code reviews are not to tear people's code to pieces, it's a place where people can give advice on how to do things better, a learning place to say why a different way of doing something is more preferable.
Code review is a place of learning, not unabashed criticism. Constant negative comments like "don't do this" or "do this better" aren't helpful and make developers defensive about their code. If you're always on the back heel having to defend your code and your decisions, you're going to burn time arguing semantics and other unnecessary shit until sometime gives up and the project suffers. Unless you're showing people that while their way works fine, a different way is more preferable because it's faster, sticks to standards or more future-proof, why would someone do it any differently? Code reviews are a learning place and to pick up minor things like missed debug statements in code, spelling mistakes and minor fixes. It's not a place to destructively criticize. If that needs to happen, it should be in a performance review, if at all.
The writer of that article is toxic and the product has undoubtedly suffered because of his narcissism. It's good that he's thinking of how to be better, but he's undoubtedly damaged his team and fixing that is an uphill battle.<|eor|><|sor|>Sir, this is programmingcirclejerk, not programminggivethoughtfulcritique.<|eor|><|sor|>Oh dear, I appear to be lost again, thank you good sir.
\*ahem\*
FUCK JAVASCRIPT AND FUCK ELECTRON APPS<|eor|><|eols|><|endoftext|> | 24 |
programmingcirclejerk | ws-ilazki | eqjciy1 | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|sor|>lol a real alpha wouldn't have ever backed down
​
/uj
​
We should be encouraging stronger quality standards in code. Sometimes they're hard to push though for the dumbest of reasons. For example, if a new function doesn't feel familiar enough, people will eschew it even if it's """technically superior""".
​
The best case of this is in Ruby:
str1.downcase == str2.downcase
# vs
str1.casecmp(str2).zero?
These functions both do a case-insensitive comparisons of two strings but the first one creates a new string for each \`.downcase\` call. \`.casecmp\` does no such thing.
​
While this is even a part of RuboCop, the second impl is rejected because the first one is "more clear". The real reason is, unfamiliar things are unfamiliar and we tend to shy away from those things.
​
There's no logical or technical reason to prefer the first version outside of emotion which is ultimately a detrimental mindset to have while coding. And it's frustrating when you interact with programmers that don't think about what's the best possible code they could write but rather, what code do they feel like writing and what makes them feel good and happy.
​
This is where the toxicity from the "elite" programmers comes from. It's an expression of frustration in people's inability to grow and adapt like them. In short, they become too smart for their own good and wind up self-destructing.<|eor|><|sor|>What is this Ruby you talk about?<|eor|><|sor|>Ruby is the platform that the Rails language is hosted on, much like the JVM for Kotlin, or the CLR for F#. Unlike them, however, it has no notability for hosting other, better languages.<|eor|><|eols|><|endoftext|> | 23 |
programmingcirclejerk | anoliss | eqkjmgj | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|sor|>> I was mad that, while I spent my nights learning F#, my daughter started calling everyone around fathers. And this guy, instead of getting better at his job, went home to his children. And I wanted to punish him.
Tfw your feeling of self-righteousness at work because you think you're a strong developer and obsessive need to learn .NET's OCaml ends up causing you to willingly neglect your family is what will end up causing your daughter to have daddy issues, and will probably end up with your wife cucking you at every moment she can.<|eor|><|sor|>if your wife isn't cucking you you'll never be a 10xer<|eor|><|sor|>Behind every 10x dev stands a 10x wife.<|eor|><|sor|>10x as many partners?<|eor|><|soopr|>At the same time?!<|eoopr|><|sor|>They have a multi-threaded relationship<|eor|><|eols|><|endoftext|> | 22 |
programmingcirclejerk | saulmessedupman | eqjsobl | <|sols|><|sot|>I ruin developers lives with my code reviews and I'm sorry<|eot|><|sol|>https://habr.com/en/post/440736/<|eol|><|sor|>> I was mad that, while I spent my nights learning F#, my daughter started calling everyone around fathers. And this guy, instead of getting better at his job, went home to his children. And I wanted to punish him.
Tfw your feeling of self-righteousness at work because you think you're a strong developer and obsessive need to learn .NET's OCaml ends up causing you to willingly neglect your family is what will end up causing your daughter to have daddy issues, and will probably end up with your wife cucking you at every moment she can.<|eor|><|sor|>if your wife isn't cucking you you'll never be a 10xer<|eor|><|sor|>Behind every 10x dev stands a 10x wife.<|eor|><|sor|>10x as many partners?<|eor|><|soopr|>At the same time?!<|eoopr|><|eols|><|endoftext|> | 20 |
programmingcirclejerk | StallmanTheWhite | 6xdzuc | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|eols|><|endoftext|> | 151 |
programmingcirclejerk | dnkndnts | dmfda9k | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>Should probably concat all the `.c` files into a single `index.c` as well.<|eor|><|eols|><|endoftext|> | 65 |
programmingcirclejerk | ArcTimes | dmfg1ia | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>Should probably concat all the `.c` files into a single `index.c` as well.<|eor|><|sor|>kernel-min.c<|eor|><|eols|><|endoftext|> | 46 |
programmingcirclejerk | CruxMostSimple | dmf5y9w | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>Can Linux kernel webscale? <|eor|><|eols|><|endoftext|> | 44 |
programmingcirclejerk | StallmanTheWhite | dmf70r2 | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>Can Linux kernel webscale? <|eor|><|soopr|>Maybe if you rewrote it with node.js and used mongodb for the kernel tables.<|eoopr|><|eols|><|endoftext|> | 44 |
programmingcirclejerk | Shorttail0 | dmfk6tv | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>This is why Linux development doesn't take place on Github.<|eor|><|eols|><|endoftext|> | 38 |
programmingcirclejerk | cheeseboythrowaway | dmg1sf0 | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>This is why Linux development doesn't take place on Github.<|eor|><|sor|>I wish it did (or GitLab, or just... anything other than emailing patch files)
Even though there are trolls, I think the inconvenience of email is a bit of a barrier.
Though, for being a large insanely popular public repo, I'd want at least minimum character amounts for top-level comments to get rid of the silly :+1: spam<|eor|><|sor|>The Linux kernel project is all about barriers to entry; if they had it their way they'd never talk to anyone.<|eor|><|eols|><|endoftext|> | 29 |
programmingcirclejerk | axisofdenial | dmf80gw | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>> Needs to be structured a bit better
gofmt?<|eor|><|eols|><|endoftext|> | 26 |
programmingcirclejerk | pftbest | dmfnfnn | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>Should probably concat all the `.c` files into a single `index.c` as well.<|eor|><|sor|> #ifdef UJ
It's called "poor man's LTO", and I've seen this in some real projects.
<|eor|><|eols|><|endoftext|> | 18 |
programmingcirclejerk | binaryblade | dmfjvi6 | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>Can Linux kernel webscale? <|eor|><|soopr|>Maybe if you rewrote it with node.js and used mongodb for the kernel tables.<|eoopr|><|sor|>electron using UEFI is obviously the only webscale solution.<|eor|><|eols|><|endoftext|> | 16 |
programmingcirclejerk | StallmanTheWhite | dmgozfb | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>This is why Linux development doesn't take place on Github.<|eor|><|sor|>I wish it did (or GitLab, or just... anything other than emailing patch files)
Even though there are trolls, I think the inconvenience of email is a bit of a barrier.
Though, for being a large insanely popular public repo, I'd want at least minimum character amounts for top-level comments to get rid of the silly :+1: spam<|eor|><|soopr|>> I think the inconvenience of email is a bit of a barrier.
But... this is the whole point. There is no need for more lazy and incompetent kernel developers. A dedicated kernel dev who has the skill will be able to adjust to the email based workflow.<|eoopr|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | yarauuta | dmg85w7 | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>This is why Linux development doesn't take place on Github.<|eor|><|sor|>"GitHub does not scale to larger projects. He pointed at theKubernetesproject, which has over 4,000 open issues and 511 open pull requests. The system, he said, does not work well for large numbers of reviewers. It hasa reasonable mechanism for discussion threads attached to pull requests GitHub has duplicated email for that feature, he said but only the people who are actually assigned to a pull request can see that thread. GitHub also requires online access, but there are a lot of kernel developers who, for whatever reason, do not have good access to the net while they are working. In general, it is getting better, but projects like Kubernetes are realizing that they need to find something better suited to their scale; it would never work for the kernel."
Source: https://lwn.net/Articles/702177/<|eor|><|eols|><|endoftext|> | 12 |
programmingcirclejerk | DerNalia | dmfsp0x | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>This is why Linux development doesn't take place on Github.<|eor|><|sor|>I wish it did (or GitLab, or just... anything other than emailing patch files)
Even though there are trolls, I think the inconvenience of email is a bit of a barrier.
Though, for being a large insanely popular public repo, I'd want at least minimum character amounts for top-level comments to get rid of the silly :+1: spam<|eor|><|eols|><|endoftext|> | 10 |
programmingcirclejerk | clearandpresent | dmfqz4b | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>Good trolling there <|eor|><|eols|><|endoftext|> | 9 |
programmingcirclejerk | SnowdensOfYesteryear | dmfgtof | <|sols|><|sot|>Web developer fixes the Linux kernel.<|eot|><|sol|>https://github.com/torvalds/linux/pull/437<|eol|><|sor|>Maybe the source code should be mini-fied?<|eor|><|eols|><|endoftext|> | 5 |
programmingcirclejerk | u70 | 6lznd2 | <|sols|><|sot|>"It came to them with a message.."<|eot|><|sol|>https://twitter.com/phollow/status/883232406538420224<|eol|><|eols|><|endoftext|> | 154 |
programmingcirclejerk | alexbarrett | djxurmb | <|sols|><|sot|>"It came to them with a message.."<|eot|><|sol|>https://twitter.com/phollow/status/883232406538420224<|eol|><|sor|>>who made this
I'd be so famous if I had a Twitter account.
edit: found you /u/seriouslulz
lol he's a gopher<|eor|><|eols|><|endoftext|> | 36 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.