subreddit stringclasses 7
values | author stringlengths 3 20 | id stringlengths 5 7 | content stringlengths 67 30.4k | score int64 0 140k |
|---|---|---|---|---|
programmingcirclejerk | james_pic | h7tzkpo | <|sols|><|sot|>[What's wrong with WebAssembly?] Sorry, but the response to that question is in the question!! Assembly!! Coding with assembly is multiplying time and bugs by 10!<|eot|><|sol|>https://medium.com/@abderhind/sorry-but-the-response-to-that-question-is-in-the-question-f164e8869212<|eol|><|sor|>What's the point of an assembly language that doesn't even let me indulge my fetish for GOTO?<|eor|><|eols|><|endoftext|> | 16 |
programmingcirclejerk | republitard_2 | h7u7wpl | <|sols|><|sot|>[What's wrong with WebAssembly?] Sorry, but the response to that question is in the question!! Assembly!! Coding with assembly is multiplying time and bugs by 10!<|eot|><|sol|>https://medium.com/@abderhind/sorry-but-the-response-to-that-question-is-in-the-question-f164e8869212<|eol|><|sor|>Yeah, sorry. Never believe words from someone that cannot buy domain. Especially, if they talks about software or programming.
There is an exception, thought, but only two or threes.<|eor|><|sor|>Even if they can buy a domain, it doesn't count unless they have enough traffic to justify putting it behind Cloudfare. Before I read anyone's blog, I try loading it through Tor. If it doesn't bring me to Cloudfare's CAPTCHA, it's not worth reading.<|eor|><|eols|><|endoftext|> | 16 |
programmingcirclejerk | themagicalcake | h7utcui | <|sols|><|sot|>[What's wrong with WebAssembly?] Sorry, but the response to that question is in the question!! Assembly!! Coding with assembly is multiplying time and bugs by 10!<|eot|><|sol|>https://medium.com/@abderhind/sorry-but-the-response-to-that-question-is-in-the-question-f164e8869212<|eol|><|sor|>/uj it's great how the original author actually went out their way to explain how people don't actually write webassembly and this person still doesn't get it<|eor|><|eols|><|endoftext|> | 15 |
programmingcirclejerk | republitard_2 | h7u7fq1 | <|sols|><|sot|>[What's wrong with WebAssembly?] Sorry, but the response to that question is in the question!! Assembly!! Coding with assembly is multiplying time and bugs by 10!<|eot|><|sol|>https://medium.com/@abderhind/sorry-but-the-response-to-that-question-is-in-the-question-f164e8869212<|eol|><|sor|>10x programmer = 1/10 the bugs
Rust compiles to WebAssembly; Rust = 1/10 the bugs
WebAssembly = 10x the bugs
1/10 * 1/10 * 10 = 1/10 the bugs
10x crabs always come out on top.<|eor|><|sor|>You have Rust code? Better rewrite it in Common Lisp for 10x the performance.<|eor|><|eols|><|endoftext|> | 14 |
programmingcirclejerk | camelCaseIsWebScale | h7tvk2g | <|sols|><|sot|>[What's wrong with WebAssembly?] Sorry, but the response to that question is in the question!! Assembly!! Coding with assembly is multiplying time and bugs by 10!<|eot|><|sol|>https://medium.com/@abderhind/sorry-but-the-response-to-that-question-is-in-the-question-f164e8869212<|eol|><|sor|>Hey smart guy, ever heard of a compiler?<|eor|><|sor|>What's a compiler? Is it like a transpiler?<|eor|><|sor|>Yes but less modern (legacy tech).<|eor|><|sor|>Hey guys what's the best ~~babel~~ ~~esbuild~~ swc for C?<|eor|><|eols|><|endoftext|> | 14 |
programmingcirclejerk | snorc_snorc | h7trrhw | <|sols|><|sot|>[What's wrong with WebAssembly?] Sorry, but the response to that question is in the question!! Assembly!! Coding with assembly is multiplying time and bugs by 10!<|eot|><|sol|>https://medium.com/@abderhind/sorry-but-the-response-to-that-question-is-in-the-question-f164e8869212<|eol|><|sor|>Ever heard of roller coaster tycoon? Check mate assembly deniers.<|eor|><|sor|>uj: thats a cool factoid
rj: lol not even as fast as DOOM<|eor|><|sor|>uj: it's a factoid that a factoid is a short fact.<|eor|><|eols|><|endoftext|> | 12 |
programmingcirclejerk | ProfessorSexyTime | h7ujge3 | <|sols|><|sot|>[What's wrong with WebAssembly?] Sorry, but the response to that question is in the question!! Assembly!! Coding with assembly is multiplying time and bugs by 10!<|eot|><|sol|>https://medium.com/@abderhind/sorry-but-the-response-to-that-question-is-in-the-question-f164e8869212<|eol|><|sor|>10x programmer = 1/10 the bugs
Rust compiles to WebAssembly; Rust = 1/10 the bugs
WebAssembly = 10x the bugs
1/10 * 1/10 * 10 = 1/10 the bugs
10x crabs always come out on top.<|eor|><|sor|>How do we get to only like 3 or 5Xs the bugs, though? I still want have a job after the release of a product.<|eor|><|eols|><|endoftext|> | 11 |
programmingcirclejerk | __JDQ__ | h7vakz3 | <|sols|><|sot|>[What's wrong with WebAssembly?] Sorry, but the response to that question is in the question!! Assembly!! Coding with assembly is multiplying time and bugs by 10!<|eot|><|sol|>https://medium.com/@abderhind/sorry-but-the-response-to-that-question-is-in-the-question-f164e8869212<|eol|><|sor|>Hey smart guy, ever heard of a compiler?<|eor|><|sor|>If you're having the compiler do the work and optimizations for you, you're clearly not 10X.<|eor|><|sor|>If youre not using punch cards anymore, youre clearly not 10X. I got an external punch card reader for my MBP so I can keep it real.<|eor|><|eols|><|endoftext|> | 6 |
programmingcirclejerk | lambda-male | ore5a9 | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|eols|><|endoftext|> | 151 |
programmingcirclejerk | exodusTay | h6hpu8e | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>My programming has been commended as being strongly functional which bothers some programmers. The word itself makes some programmers uncomfortable. Haskell.<|eor|><|eols|><|endoftext|> | 82 |
programmingcirclejerk | UnicornPrince4U | h6hy59w | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>My manager seems threatened by efforts to build business critical systems around my own unique and eccentric skillset.
He just doesn't seem to understand that I'm terribly insecure and need to keep my fellow developers at a disadvantage in order to mask my squarely average intelligence.<|eor|><|eols|><|endoftext|> | 50 |
programmingcirclejerk | ProfessorSexyTime | h6hrmk1 | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>Some jerk from the previous comment.
> General gratuitous toxicity. I've seen a presentation where the presenter mentioned a project was in Haskell and was (of course) rewritten in C++. Everyone laughed "oh yeah of course". This strangely never happens over shit python code, and god knows if the average quality of what comes out of pure breed C programmers is low. It just seems socially acceptable to bash Haskell.
\> talks about "gratuitous toxicity"
\> continues to talk poorly people programming in other languages
\> doesn't address shit Haskal out there, or rather pretends Haskal can't be shit
\> "Why is it socially acceptable to bash Haskal?"<|eor|><|eols|><|endoftext|> | 46 |
programmingcirclejerk | duckbill_principate | h6i04aa | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>My programming has been commended as being strongly functional which bothers some programmers. The word itself makes some programmers uncomfortable. Haskell.<|eor|><|sor|>Java Treehorn treats objects like women.<|eor|><|eols|><|endoftext|> | 31 |
programmingcirclejerk | stingraycharles | h6hzc8m | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>Some jerk from the previous comment.
> General gratuitous toxicity. I've seen a presentation where the presenter mentioned a project was in Haskell and was (of course) rewritten in C++. Everyone laughed "oh yeah of course". This strangely never happens over shit python code, and god knows if the average quality of what comes out of pure breed C programmers is low. It just seems socially acceptable to bash Haskell.
\> talks about "gratuitous toxicity"
\> continues to talk poorly people programming in other languages
\> doesn't address shit Haskal out there, or rather pretends Haskal can't be shit
\> "Why is it socially acceptable to bash Haskal?"<|eor|><|sor|>Haskal the incels of the programming community.
Everybody is always against us, they are so toxic! Why are they never toxic against each other but only us?!<|eor|><|eols|><|endoftext|> | 29 |
programmingcirclejerk | ackfoobar | h6i41kn | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>As a poor person, I do constantly feel threatened by joblessness.<|eor|><|eols|><|endoftext|> | 19 |
programmingcirclejerk | lambda-male | h6ik5hi | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>[deleted]<|eor|><|soopr|>>haskcel
In current year the proper pejorative term is *monoid*.<|eoopr|><|eols|><|endoftext|> | 19 |
programmingcirclejerk | AlexdDark | h6io5aj | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>Personally, after getting introduced to Haskell in uni I've gotten so anxious and frankly terrified of the transcendent purity of the functional approach that I had to immediately abandon my CS degree and turn into a corpo webshit. My life had never been the same after.
Thank you for scaring me onto the straight and narrow, Haskell.<|eor|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | lambda-male | h6htxqp | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>All kidding aside, I think haskell is great to learn to teach you how to think about programming in a broader way. ...it's just not always practical for real world problems. ...a lot of basic I/O is just impractical in it. And functional languages really need efficient in place updates like X = X + 2 to be more performant.
​
EDIT: I'll leave this here for what I mean about in place updates: [https://arxiv.org/abs/1801.04618](https://arxiv.org/abs/1801.04618) And I'm not saying you can't do I/O in it, just that it's more trouble.<|eor|><|soopr|>> a lot of basic I/O is just impractical in it. And functional languages really need efficient in place updates like X = X + 2 to be more performant.
I agree "haskell is great to learn", you should do it!<|eoopr|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | NynaevetialMeara | h6i40j9 | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>All kidding aside, I think haskell is great to learn to teach you how to think about programming in a broader way. ...it's just not always practical for real world problems. ...a lot of basic I/O is just impractical in it. And functional languages really need efficient in place updates like X = X + 2 to be more performant.
​
EDIT: I'll leave this here for what I mean about in place updates: [https://arxiv.org/abs/1801.04618](https://arxiv.org/abs/1801.04618) And I'm not saying you can't do I/O in it, just that it's more trouble.<|eor|><|sor|>So you be saying that a functional language is great at teaching a functional approach to programming, which is not generally applicable for all tasks?
Like, why would I use Has kell when I could use a perfect language like Rust writing pure functions and lambdas and getting to use the excuse of code taking long to compile for idleing?<|eor|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | PL_Design | h6ih6f5 | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>Of course I feel threatened by Haskell. I also feel threatened by ticks and leeches.<|eor|><|eols|><|endoftext|> | 11 |
programmingcirclejerk | Specific-Ad5738 | h6iw13j | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>All kidding aside, I think haskell is great to learn to teach you how to think about programming in a broader way. ...it's just not always practical for real world problems. ...a lot of basic I/O is just impractical in it. And functional languages really need efficient in place updates like X = X + 2 to be more performant.
​
EDIT: I'll leave this here for what I mean about in place updates: [https://arxiv.org/abs/1801.04618](https://arxiv.org/abs/1801.04618) And I'm not saying you can't do I/O in it, just that it's more trouble.<|eor|><|sor|>if your chief complaint about Haskal is I/O, then you havent written enough of the language. the ecosystem is a much, much bigger issue than burritos, which arent even that big of a deal. Monad stacks are slow and get slower (theres a few compiler optimizations for this), every single person has their own set of language extensions they like (and a lot of the extensions overlap in weird ways), 90% of the libraries on stackage are abandoned MS theses, and also I dont have a house and I live in a cardboard box please give me a job<|eor|><|eols|><|endoftext|> | 10 |
programmingcirclejerk | alibix | h6hmv4l | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>They are.<|eor|><|eols|><|endoftext|> | 8 |
programmingcirclejerk | republitard_2 | h6ka513 | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>Some jerk from the previous comment.
> General gratuitous toxicity. I've seen a presentation where the presenter mentioned a project was in Haskell and was (of course) rewritten in C++. Everyone laughed "oh yeah of course". This strangely never happens over shit python code, and god knows if the average quality of what comes out of pure breed C programmers is low. It just seems socially acceptable to bash Haskell.
\> talks about "gratuitous toxicity"
\> continues to talk poorly people programming in other languages
\> doesn't address shit Haskal out there, or rather pretends Haskal can't be shit
\> "Why is it socially acceptable to bash Haskal?"<|eor|><|sor|>> This strangely never happens over shit python code
Pythonistas are skilled at keeping non-webshits out of their organizations.<|eor|><|eols|><|endoftext|> | 8 |
programmingcirclejerk | republitard_2 | h6kaimh | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>My manager seems threatened by efforts to build business critical systems around my own unique and eccentric skillset.
He just doesn't seem to understand that I'm terribly insecure and need to keep my fellow developers at a disadvantage in order to mask my squarely average intelligence.<|eor|><|sor|>That's funny, my manager has no problem with me keeping my fellow developers at a disadvantage by constantly making changes to our `docker-compose.yml` that will force them to spend time debugging Docker problems. If they ask me about it I just say "fix your shit." Then at the stand-up meeting I make sure to draw attention to how little they got done.<|eor|><|eols|><|endoftext|> | 8 |
programmingcirclejerk | ProfessorSexyTime | h6mhsqt | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>Some jerk from the previous comment.
> General gratuitous toxicity. I've seen a presentation where the presenter mentioned a project was in Haskell and was (of course) rewritten in C++. Everyone laughed "oh yeah of course". This strangely never happens over shit python code, and god knows if the average quality of what comes out of pure breed C programmers is low. It just seems socially acceptable to bash Haskell.
\> talks about "gratuitous toxicity"
\> continues to talk poorly people programming in other languages
\> doesn't address shit Haskal out there, or rather pretends Haskal can't be shit
\> "Why is it socially acceptable to bash Haskal?"<|eor|><|sor|>"Why does `cabal install` never work?"
"It's a very sophisticated piece of tooling. You just need to get smarter. Now get down to doing binary search on your project dependencies, eliminating them one by one. The tool is good. Don't question the tool. You are the problem".
"But I'm just trying to install a single external library!"
"How dare you challenge the ways of the cabal, you fool?"<|eor|><|sor|>/uj
Can't tell how fucking annoying `cabal` and `stack` are. Maybe they've gotten better, but I remember for the longest time they wouldn't work because of some stupid shit, like not having the exact version of `libncurses` or something. And if you already had `ncurses` installed, going back a version would break other things.
To be fair, with much shit `ghc` and `ghc-libs` will make you install, and how large they are, spinning up a Docker container and using that is probably the sanest option.<|eor|><|eols|><|endoftext|> | 8 |
programmingcirclejerk | 32gbsd | h6i8wqn | <|sols|><|sot|>I think a lot of senior engineers and managers feel threatened by Haskell.<|eot|><|sol|>https://www.reddit.com/r/haskell/comments/or93z3/what_is_your_opinion_on_haskell_remaining_as/h6hbxj2/?context=999<|eol|><|sor|>I hear the word and segfault every time<|eor|><|eols|><|endoftext|> | 7 |
programmingcirclejerk | FinJoTheGreat | oikww1 | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|eols|><|endoftext|> | 153 |
programmingcirclejerk | pareidolist | h4w8tul | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>> Given this information, I think I would be able to make sure [Reddit] never comes up again after an outage. I am not going to do so
Thank goodness! That was a close one.<|eor|><|eols|><|endoftext|> | 128 |
programmingcirclejerk | UnicornPrince4U | h4wnz4q | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>"Stanford/MIT", clearly written by someone from Stanford as no one else would make that equivalency.<|eor|><|eols|><|endoftext|> | 103 |
programmingcirclejerk | 10xelectronguru | h4wuyjl | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>"Stanford/MIT", clearly written by someone from Stanford as no one else would make that equivalency.<|eor|><|sor|>> "Stanford/MIT", clearly written by someone from Stanford as no one else would make that equivalency.
Clearly written by someone from MIT.<|eor|><|eols|><|endoftext|> | 83 |
programmingcirclejerk | cmason37 | h4wy5ju | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>
lol @ Reddit engineering giving advice after the whole slow as shit designed by herds of new hires reactjs monstrosity redesign.<|eor|><|sor|>the fact that like half this site (including me) still uses old reddit & 3rd party apps *~~6~~ 3 fucking years* after the design was introduced even after everyone gave them feedback about what was wrong says it all<|eor|><|eols|><|endoftext|> | 81 |
programmingcirclejerk | cmason37 | h4wyj6k | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>> my post, on behalf of reddit engineering, about **how to improve your websites uptime**
the title is almost more jerkworthy than the comment, reddit giving lessons on uptime but being down 12 hours at a time like every fucking week lmao my sides<|eor|><|eols|><|endoftext|> | 60 |
programmingcirclejerk | UsingYourWifi | h4x2kkd | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>> my post, on behalf of reddit engineering, about **how to improve your websites uptime**
the title is almost more jerkworthy than the comment, reddit giving lessons on uptime but being down 12 hours at a time like every fucking week lmao my sides<|eor|><|sor|>***how to improve your websites uptime***
Step 1: Have legandarily shit uptime.
Step 2: Do literally anything, the bar really is that low<|eor|><|eols|><|endoftext|> | 53 |
programmingcirclejerk | jess-sch | h4wrfmy | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>> Reddit Engineering post
> claiming they have 5 9s
lol<|eor|><|eols|><|endoftext|> | 43 |
programmingcirclejerk | m0emura | h4wq82i | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>I think Reddit already reduced their operating costs by at least half when they offloaded page rendering to clients using the dogshit new JS site<|eor|><|eols|><|endoftext|> | 41 |
programmingcirclejerk | LeeHide | h4wqfzw | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>*advanced* degrees<|eor|><|sor|>Dont talk to me unless you have advanced (stage 4) compsci.<|eor|><|eols|><|endoftext|> | 41 |
programmingcirclejerk | exploooooosions | h4wpkpd | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>*advanced* degrees<|eor|><|eols|><|endoftext|> | 38 |
programmingcirclejerk | TempestasTenebrosus | h4z62xw | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>"Stanford/MIT", clearly written by someone from Stanford as no one else would make that equivalency.<|eor|><|sor|>Or as Ive recently taken to calling it, Stanford + MIT<|eor|><|eols|><|endoftext|> | 35 |
programmingcirclejerk | jess-sch | h4x0gue | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>> Reddit Engineering post
> claiming they have 5 9s
lol<|eor|><|sor|>Right after I browse this post I find out that saving your preferences is broken.<|eor|><|sor|>Oh, the wonders of microservices. Instead of everything breaking, only one thing breaks at a time.<|eor|><|eols|><|endoftext|> | 31 |
programmingcirclejerk | NakeyDooCrew | h4wgaom | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>> Given this information, I think I would be able to make sure [Reddit] never comes up again after an outage. I am not going to do so
Thank goodness! That was a close one.<|eor|><|sor|>HTML injection? Gasp!<|eor|><|eols|><|endoftext|> | 23 |
programmingcirclejerk | RedPandaDan | h4ypv9b | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>> Given this information, I think I would be able to make sure [Reddit] never comes up again after an outage. I am not going to do so
Thank goodness! That was a close one.<|eor|><|sor|>Raising my hopes just to knock them down.<|eor|><|sor|>> If it would cost more than $500 to crush your website with nothing you can do about it in the short term, I would be surprised.
Got $500?<|eor|><|sor|>Apologies, but I'm a firm believer in the principals of free software, specifically the bit where I don't need to pay for anything.<|eor|><|eols|><|endoftext|> | 20 |
programmingcirclejerk | 32gbsd | h4wqvpi | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>This constant mention of MIT is also done in movies. It must be ad placement or something.<|eor|><|eols|><|endoftext|> | 18 |
programmingcirclejerk | fp_weenie | h4xbbxz | <|sols|><|sot|>You don't mention cost for running Reddit. I'd expect that it can be reduced by at least half. Do you have any real engineers on staff? E.g. people from Stanford/MIT with advanced degrees in Computer Science?<|eot|><|sol|>https://www.reddit.com/r/programming/comments/oi57cj/-/h4vvtns<|eol|><|sor|>*advanced* degrees<|eor|><|sor|>Master's at least. Wouldn't want a lowly BA typing those `err != nil`s.<|eor|><|eols|><|endoftext|> | 17 |
programmingcirclejerk | First_Cardinal | l7rjdp | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|eols|><|endoftext|> | 152 |
programmingcirclejerk | the-computer-guy | gl8qjll | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>What part of "a branch is just a pointer to a node in an acyclic graph" do you not understand?<|eor|><|eols|><|endoftext|> | 91 |
programmingcirclejerk | yyogo | gl8eodv | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>Git is so useless. Real 10xers only write their code once and without bugs, then rewrite it from scratch when a new feature is needed.<|eor|><|eols|><|endoftext|> | 80 |
programmingcirclejerk | nehalem2049 | gl8w61e | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>My advice: git gud xD
not a single relevant criticism just useless tantrum of some idiot who suffers from mental breakdown everytime he sees a git pull terminal output. I'd hate to work with this kind of person.<|eor|><|eols|><|endoftext|> | 41 |
programmingcirclejerk | FascinatedBox | gl9d5aw | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>> You might be asking.. Why not just undo that commit? (good luck with that one, undoing commits cleanly requires a PHD-or-equivalent in Gitsciencetology)
git reset --soft HEAD~1<|eor|><|eols|><|endoftext|> | 31 |
programmingcirclejerk | the-computer-guy | gl9in0h | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>[removed]<|eor|><|sor|>"The key point here is our programmers are Googlers, theyre not researchers. Theyre typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. Theyre not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt."<|eor|><|eols|><|endoftext|> | 31 |
programmingcirclejerk | sfhtsxgtsvg | glc0upa | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>pardon my SJWness but
> The idea of being able to work offline, and later commit to a remote depo is frankly stupid.
> Wifi and 3G is everywhere. Even on airplanes.
really reads to me like
> if you arn't rich or live outside of the western world, just don't even try coding.
Like, that some fucked up classist bullshit, fuck this guy<|eor|><|eols|><|endoftext|> | 30 |
programmingcirclejerk | mizzu704 | gl9nnly | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>[removed]<|eor|><|sor|>Your dislike of Linux Torvalds's random graph generator is a minor offense compared to implicit unjerk<|eor|><|eols|><|endoftext|> | 29 |
programmingcirclejerk | tuckmuck203 | gla3sku | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>> You might be asking.. Why not just undo that commit? (good luck with that one, undoing commits cleanly requires a PHD-or-equivalent in Gitsciencetology)
git reset --soft HEAD~1<|eor|><|sor|>Omg I didn't think Linus Torvalds had reddit<|eor|><|eols|><|endoftext|> | 22 |
programmingcirclejerk | Jumpy-Locksmith6812 | gl8uxca | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>Git is so useless. Real 10xers only write their code once and without bugs, then rewrite it from scratch when a new feature is needed.<|eor|><|sor|>I thought git was there to scare off 1x ers.<|eor|><|eols|><|endoftext|> | 21 |
programmingcirclejerk | Noughmad | glb9ba6 | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>Git is so useless. Real 10xers only write their code once and without bugs, then rewrite it from scratch when a new feature is needed.<|eor|><|sor|>> rewrite it from scratch when a new feature is needed.
I just unpack the last tarball and add features.<|eor|><|sor|>That introduces unnecessary delays, I just edit the tarball without unpacking it first.<|eor|><|eols|><|endoftext|> | 21 |
programmingcirclejerk | NormalSquirrel0 | glb6viy | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>Git is so useless. Real 10xers only write their code once and without bugs, then rewrite it from scratch when a new feature is needed.<|eor|><|sor|>>then rewrite it ~~from~~ *in* Scratch
FTFY<|eor|><|eols|><|endoftext|> | 20 |
programmingcirclejerk | camelCaseIsWebScale | gl8wc1k | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>Quantum leap means very small change right?
Should have some shame for using perl.<|eor|><|eols|><|endoftext|> | 16 |
programmingcirclejerk | fp_weenie | gl9r9bf | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>> You might be asking.. Why not just undo that commit? (good luck with that one, undoing commits cleanly requires a PHD-or-equivalent in Gitsciencetology)
git reset --soft HEAD~1<|eor|><|sor|>> undoing commits cleanly requires a PHD-
So a Haskalar, basically.<|eor|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | 10xelectronguru | glcov7z | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>pardon my SJWness but
> The idea of being able to work offline, and later commit to a remote depo is frankly stupid.
> Wifi and 3G is everywhere. Even on airplanes.
really reads to me like
> if you arn't rich or live outside of the western world, just don't even try coding.
Like, that some fucked up classist bullshit, fuck this guy<|eor|><|sor|>/uj plus sometimes I like to work offline for a while just to avoid distractions. That guy sounds like a piece of shit.<|eor|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | lucasreta | gl95ji8 | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>My advice: git gud xD
not a single relevant criticism just useless tantrum of some idiot who suffers from mental breakdown everytime he sees a git pull terminal output. I'd hate to work with this kind of person.<|eor|><|sor|>more respect when talking about DeepFraud founder, sir<|eor|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | fp_weenie | gl9r61d | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>Git is so useless. Real 10xers only write their code once and without bugs, then rewrite it from scratch when a new feature is needed.<|eor|><|sor|>> rewrite it from scratch when a new feature is needed.
I just unpack the last tarball and add features.<|eor|><|eols|><|endoftext|> | 11 |
programmingcirclejerk | hekkonaay | glaz6nx | <|sols|><|sot|>Git/Github developers are living in a constant state of uncertainty, never quite sure when their next quantum leap (a Pull Request) will cause a catastrophic collapse of the universe. What we need is Back to the Future, what we get is Inception.<|eot|><|sol|>https://tom-vykes.medium.com/the-worst-things-about-github-8e8efc60fae3<|eol|><|sor|>This is what happens when people not well versed in graph theory, lambda calculus and gitology try to use the tools intended for the true gods. They start having mental breakdowns.
Why is it so difficult for these simpletons to understand that "I need internet to work" is a non-starter for git to manifest its might? You don't "need to be" online, you actively avoid it to showcase the power of decentralized workflow. And "I can't work without googling"? Spoken like a true .5xer.<|eor|><|sor|>> gitology
This is my religion. Every day I pray to our savior Linus Torvalds.<|eor|><|eols|><|endoftext|> | 10 |
programmingcirclejerk | Karma_Policer | hqbph8 | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|eols|><|endoftext|> | 155 |
programmingcirclejerk | BB_C | fxwyef1 | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>>> The problem with large C/C++ codebases is that they are invariably full of unintentional UB (e.g. crashes, use-after-free, etc) because it's very hard to write a C program that doesn't have some sort of possible UB in it. As you just brought up, every time you dereference any pointer you might be causing UB, either via a null pointer (which usually helpfully crashes), or more scarily via use-after free (which generally doesn't and instead causes very strange and unpredictable behavior)
> That's not really my experience with well-written code bases. This does happen if you work with amateurs, but it's very rare in professionally maintained code bases. Generally, you use design-patterns and documentation to make sure that behaviour is well-defined everywhere. I admit there are a lot of second-rate programmers who write shitty code out there. They are better served not writing in C though.
>
> Note that for most business logic written in C, the more natural migration path is to something like Go which solves all these resource allocation problems dynamically and allows you to write in mostly the same style as in C, whereas Rust really demands quite a different programming style.
>
> Also, don't mix C and C++ please. The idiomatic programming style and issues plaguing these two languages are entirely different.
>> The whole reason Rust exists is because this is a hard problem that humans have been repeatedly shown to be incapable of solving, so moving some of that work onto the compiler will help us write better programs.
> Humans are capable of solving these problems if trained correctly. The main problem with Rust is that it introduces an enormous amount of complexity and both syntactic and logic boilerplate that writing programs in it is an annoyingly tedious exercise. Every time I need to think about how to make the program logic I am thinking about agreeable to the language I am programming in instead of simply writing it down I am being affirmed that my choice of language is wrong. I used to think of this as an interesting challenge (back when I wrote a lot of Haskell) but now I'm just sick of it.
>
> If I want a safe language (i.e. one that reasons about memory usage for me), I use something like Go or an interpreted language. If I want a language without a runtime environment, I use C or write in assembly. I am never going to trade safety for complexity and my sanity. There might be some place for Rust when I need complex typing, but that can usually be avoided by not trying to overly generalise your program.
You can copy-paste any sentence and post it. You don't have to read it first.<|eor|><|eols|><|endoftext|> | 73 |
programmingcirclejerk | irqlnotdispatchlevel | fxwz6z0 | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>>> The problem with large C/C++ codebases is that they are invariably full of unintentional UB (e.g. crashes, use-after-free, etc) because it's very hard to write a C program that doesn't have some sort of possible UB in it. As you just brought up, every time you dereference any pointer you might be causing UB, either via a null pointer (which usually helpfully crashes), or more scarily via use-after free (which generally doesn't and instead causes very strange and unpredictable behavior)
> That's not really my experience with well-written code bases. This does happen if you work with amateurs, but it's very rare in professionally maintained code bases. Generally, you use design-patterns and documentation to make sure that behaviour is well-defined everywhere. I admit there are a lot of second-rate programmers who write shitty code out there. They are better served not writing in C though.
>
> Note that for most business logic written in C, the more natural migration path is to something like Go which solves all these resource allocation problems dynamically and allows you to write in mostly the same style as in C, whereas Rust really demands quite a different programming style.
>
> Also, don't mix C and C++ please. The idiomatic programming style and issues plaguing these two languages are entirely different.
>> The whole reason Rust exists is because this is a hard problem that humans have been repeatedly shown to be incapable of solving, so moving some of that work onto the compiler will help us write better programs.
> Humans are capable of solving these problems if trained correctly. The main problem with Rust is that it introduces an enormous amount of complexity and both syntactic and logic boilerplate that writing programs in it is an annoyingly tedious exercise. Every time I need to think about how to make the program logic I am thinking about agreeable to the language I am programming in instead of simply writing it down I am being affirmed that my choice of language is wrong. I used to think of this as an interesting challenge (back when I wrote a lot of Haskell) but now I'm just sick of it.
>
> If I want a safe language (i.e. one that reasons about memory usage for me), I use something like Go or an interpreted language. If I want a language without a runtime environment, I use C or write in assembly. I am never going to trade safety for complexity and my sanity. There might be some place for Rust when I need complex typing, but that can usually be avoided by not trying to overly generalise your program.
You can copy-paste any sentence and post it. You don't have to read it first.<|eor|><|sor|>>Generally, you use design-patterns and documentation to make sure that behaviour is well-defined everywhere.
I just removed all the bugs from our code base by doing `doxygen -g morality` in the root of the repository.<|eor|><|eols|><|endoftext|> | 54 |
programmingcirclejerk | w2qw | fxx58ex | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>>> The problem with large C/C++ codebases is that they are invariably full of unintentional UB (e.g. crashes, use-after-free, etc) because it's very hard to write a C program that doesn't have some sort of possible UB in it. As you just brought up, every time you dereference any pointer you might be causing UB, either via a null pointer (which usually helpfully crashes), or more scarily via use-after free (which generally doesn't and instead causes very strange and unpredictable behavior)
> That's not really my experience with well-written code bases. This does happen if you work with amateurs, but it's very rare in professionally maintained code bases. Generally, you use design-patterns and documentation to make sure that behaviour is well-defined everywhere. I admit there are a lot of second-rate programmers who write shitty code out there. They are better served not writing in C though.
>
> Note that for most business logic written in C, the more natural migration path is to something like Go which solves all these resource allocation problems dynamically and allows you to write in mostly the same style as in C, whereas Rust really demands quite a different programming style.
>
> Also, don't mix C and C++ please. The idiomatic programming style and issues plaguing these two languages are entirely different.
>> The whole reason Rust exists is because this is a hard problem that humans have been repeatedly shown to be incapable of solving, so moving some of that work onto the compiler will help us write better programs.
> Humans are capable of solving these problems if trained correctly. The main problem with Rust is that it introduces an enormous amount of complexity and both syntactic and logic boilerplate that writing programs in it is an annoyingly tedious exercise. Every time I need to think about how to make the program logic I am thinking about agreeable to the language I am programming in instead of simply writing it down I am being affirmed that my choice of language is wrong. I used to think of this as an interesting challenge (back when I wrote a lot of Haskell) but now I'm just sick of it.
>
> If I want a safe language (i.e. one that reasons about memory usage for me), I use something like Go or an interpreted language. If I want a language without a runtime environment, I use C or write in assembly. I am never going to trade safety for complexity and my sanity. There might be some place for Rust when I need complex typing, but that can usually be avoided by not trying to overly generalise your program.
You can copy-paste any sentence and post it. You don't have to read it first.<|eor|><|sor|>>Generally, you use design-patterns and documentation to make sure that behaviour is well-defined everywhere.
I just removed all the bugs from our code base by doing `doxygen -g morality` in the root of the repository.<|eor|><|sor|>I have a script to just cleanup existing code bases
#!/bin/bash
find . -not -name '*.rs' -delete<|eor|><|eols|><|endoftext|> | 48 |
programmingcirclejerk | dnkndnts | fxx9zhp | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>>> The problem with large C/C++ codebases is that they are invariably full of unintentional UB (e.g. crashes, use-after-free, etc) because it's very hard to write a C program that doesn't have some sort of possible UB in it. As you just brought up, every time you dereference any pointer you might be causing UB, either via a null pointer (which usually helpfully crashes), or more scarily via use-after free (which generally doesn't and instead causes very strange and unpredictable behavior)
> That's not really my experience with well-written code bases. This does happen if you work with amateurs, but it's very rare in professionally maintained code bases. Generally, you use design-patterns and documentation to make sure that behaviour is well-defined everywhere. I admit there are a lot of second-rate programmers who write shitty code out there. They are better served not writing in C though.
>
> Note that for most business logic written in C, the more natural migration path is to something like Go which solves all these resource allocation problems dynamically and allows you to write in mostly the same style as in C, whereas Rust really demands quite a different programming style.
>
> Also, don't mix C and C++ please. The idiomatic programming style and issues plaguing these two languages are entirely different.
>> The whole reason Rust exists is because this is a hard problem that humans have been repeatedly shown to be incapable of solving, so moving some of that work onto the compiler will help us write better programs.
> Humans are capable of solving these problems if trained correctly. The main problem with Rust is that it introduces an enormous amount of complexity and both syntactic and logic boilerplate that writing programs in it is an annoyingly tedious exercise. Every time I need to think about how to make the program logic I am thinking about agreeable to the language I am programming in instead of simply writing it down I am being affirmed that my choice of language is wrong. I used to think of this as an interesting challenge (back when I wrote a lot of Haskell) but now I'm just sick of it.
>
> If I want a safe language (i.e. one that reasons about memory usage for me), I use something like Go or an interpreted language. If I want a language without a runtime environment, I use C or write in assembly. I am never going to trade safety for complexity and my sanity. There might be some place for Rust when I need complex typing, but that can usually be avoided by not trying to overly generalise your program.
You can copy-paste any sentence and post it. You don't have to read it first.<|eor|><|sor|>Any time I hear someone say the solution to a problem is "more training" I just assume they're an idiot. Which is great, since that's Reddit's solution to like every problem ever.<|eor|><|eols|><|endoftext|> | 41 |
programmingcirclejerk | TheLastMeritocrat | fxx0vac | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>On behalf of myself and other C programmers working on multiple serious fields, I want it said on the record, and I want the world to know, that this person does not represent us.
We never worshiped C. We never thought we could write *correct C*. How could we when generation after generation of static analyzers and runtime sanitizers managed to continually ~~humiliate~~ humble us?
In fact, one of the few things that seems to unite us all is our continued fascination at how our code manages to actually work most of the time, or appears to be doing so at least.
Some of us never imagined that we will still be writing C in 2020, but here we are. C++ was a major contributor to C's extended relevance (we sometimes use this sentence as a test because C++ developers don't realize what we mean by it).
Thank you Bjarne, I think..
When Rust came out, we were mostly skeptical (did I mention C++ already?),
but some of us grew to like it, and most of us definitely respect it and understand the premises behind its existence.
I'm going to stop here so this doesn't become a TL;DR.
Again, **this person does not represent us C programmers**. I'm not saying he/she is definitely not a C programmer. No need to throw a *no true Scotsman* at me. I'm just making it clear that he/she is not representative of us.<|eor|><|eols|><|endoftext|> | 38 |
programmingcirclejerk | irqlnotdispatchlevel | fxxcf18 | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>>> The problem with large C/C++ codebases is that they are invariably full of unintentional UB (e.g. crashes, use-after-free, etc) because it's very hard to write a C program that doesn't have some sort of possible UB in it. As you just brought up, every time you dereference any pointer you might be causing UB, either via a null pointer (which usually helpfully crashes), or more scarily via use-after free (which generally doesn't and instead causes very strange and unpredictable behavior)
> That's not really my experience with well-written code bases. This does happen if you work with amateurs, but it's very rare in professionally maintained code bases. Generally, you use design-patterns and documentation to make sure that behaviour is well-defined everywhere. I admit there are a lot of second-rate programmers who write shitty code out there. They are better served not writing in C though.
>
> Note that for most business logic written in C, the more natural migration path is to something like Go which solves all these resource allocation problems dynamically and allows you to write in mostly the same style as in C, whereas Rust really demands quite a different programming style.
>
> Also, don't mix C and C++ please. The idiomatic programming style and issues plaguing these two languages are entirely different.
>> The whole reason Rust exists is because this is a hard problem that humans have been repeatedly shown to be incapable of solving, so moving some of that work onto the compiler will help us write better programs.
> Humans are capable of solving these problems if trained correctly. The main problem with Rust is that it introduces an enormous amount of complexity and both syntactic and logic boilerplate that writing programs in it is an annoyingly tedious exercise. Every time I need to think about how to make the program logic I am thinking about agreeable to the language I am programming in instead of simply writing it down I am being affirmed that my choice of language is wrong. I used to think of this as an interesting challenge (back when I wrote a lot of Haskell) but now I'm just sick of it.
>
> If I want a safe language (i.e. one that reasons about memory usage for me), I use something like Go or an interpreted language. If I want a language without a runtime environment, I use C or write in assembly. I am never going to trade safety for complexity and my sanity. There might be some place for Rust when I need complex typing, but that can usually be avoided by not trying to overly generalise your program.
You can copy-paste any sentence and post it. You don't have to read it first.<|eor|><|sor|>>Generally, you use design-patterns and documentation to make sure that behaviour is well-defined everywhere.
I just removed all the bugs from our code base by doing `doxygen -g morality` in the root of the repository.<|eor|><|sor|>I have a script to just cleanup existing code bases
#!/bin/bash
find . -not -name '*.rs' -delete<|eor|><|sor|>Ah yes, remove the README files: no users, no problems.<|eor|><|sor|>My readme file is a rust program.<|eor|><|eols|><|endoftext|> | 37 |
programmingcirclejerk | VeganVagiVore | fxx7med | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>Yeah, if your medical equipment can't handle something so simple as a null dereference without data (life) loss, then there are other things to fix than that null pointer dereference. Just don't get sick, what's the problem?<|eor|><|sor|>Just use a watchdog that detects if the process hangs and restarts the patient<|eor|><|eols|><|endoftext|> | 32 |
programmingcirclejerk | notjfd | fxwyqz2 | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>I'm not sure which sub pisses me off more, this one or /r/WeWantPlates.<|eor|><|eols|><|endoftext|> | 29 |
programmingcirclejerk | Karyo_Ten | fxxbo8u | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>>> The problem with large C/C++ codebases is that they are invariably full of unintentional UB (e.g. crashes, use-after-free, etc) because it's very hard to write a C program that doesn't have some sort of possible UB in it. As you just brought up, every time you dereference any pointer you might be causing UB, either via a null pointer (which usually helpfully crashes), or more scarily via use-after free (which generally doesn't and instead causes very strange and unpredictable behavior)
> That's not really my experience with well-written code bases. This does happen if you work with amateurs, but it's very rare in professionally maintained code bases. Generally, you use design-patterns and documentation to make sure that behaviour is well-defined everywhere. I admit there are a lot of second-rate programmers who write shitty code out there. They are better served not writing in C though.
>
> Note that for most business logic written in C, the more natural migration path is to something like Go which solves all these resource allocation problems dynamically and allows you to write in mostly the same style as in C, whereas Rust really demands quite a different programming style.
>
> Also, don't mix C and C++ please. The idiomatic programming style and issues plaguing these two languages are entirely different.
>> The whole reason Rust exists is because this is a hard problem that humans have been repeatedly shown to be incapable of solving, so moving some of that work onto the compiler will help us write better programs.
> Humans are capable of solving these problems if trained correctly. The main problem with Rust is that it introduces an enormous amount of complexity and both syntactic and logic boilerplate that writing programs in it is an annoyingly tedious exercise. Every time I need to think about how to make the program logic I am thinking about agreeable to the language I am programming in instead of simply writing it down I am being affirmed that my choice of language is wrong. I used to think of this as an interesting challenge (back when I wrote a lot of Haskell) but now I'm just sick of it.
>
> If I want a safe language (i.e. one that reasons about memory usage for me), I use something like Go or an interpreted language. If I want a language without a runtime environment, I use C or write in assembly. I am never going to trade safety for complexity and my sanity. There might be some place for Rust when I need complex typing, but that can usually be avoided by not trying to overly generalise your program.
You can copy-paste any sentence and post it. You don't have to read it first.<|eor|><|sor|>>Generally, you use design-patterns and documentation to make sure that behaviour is well-defined everywhere.
I just removed all the bugs from our code base by doing `doxygen -g morality` in the root of the repository.<|eor|><|sor|>I have a script to just cleanup existing code bases
#!/bin/bash
find . -not -name '*.rs' -delete<|eor|><|sor|>Ah yes, remove the README files: no users, no problems.<|eor|><|eols|><|endoftext|> | 29 |
programmingcirclejerk | Karyo_Ten | fxwyfzu | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>_ZFS has entered the chat_
Someone forgot to ECC their RAM to shield themselves against random flips due to pesky neutrinos.<|eor|><|eols|><|endoftext|> | 27 |
programmingcirclejerk | Poddster | fxx3gti | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>On behalf of myself and other C programmers working on multiple serious fields, I want it said on the record, and I want the world to know, that this person does not represent us.
We never worshiped C. We never thought we could write *correct C*. How could we when generation after generation of static analyzers and runtime sanitizers managed to continually ~~humiliate~~ humble us?
In fact, one of the few things that seems to unite us all is our continued fascination at how our code manages to actually work most of the time, or appears to be doing so at least.
Some of us never imagined that we will still be writing C in 2020, but here we are. C++ was a major contributor to C's extended relevance (we sometimes use this sentence as a test because C++ developers don't realize what we mean by it).
Thank you Bjarne, I think..
When Rust came out, we were mostly skeptical (did I mention C++ already?),
but some of us grew to like it, and most of us definitely respect it and understand the premises behind its existence.
I'm going to stop here so this doesn't become a TL;DR.
Again, **this person does not represent us C programmers**. I'm not saying he/she is definitely not a C programmer. No need to throw a *no true Scotsman* at me. I'm just making it clear that he/she is not representative of us.<|eor|><|sor|>> gain, this person does not represent us C programmers.
Fuxxy is the ideal C programmer. You may not like it, but this is what peak performance looks like.
Also he's the mod of the C subreddits so do what he says or get BANNED.<|eor|><|eols|><|endoftext|> | 24 |
programmingcirclejerk | UnheardIdentity | fxx4s56 | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>_ZFS has entered the chat_
Someone forgot to ECC their RAM to shield themselves against random flips due to pesky neutrinos.<|eor|><|sor|>Imagine not having triplicated ram, storage, and CPUs to avoid cosmic rays from messing up your beautiful program.<|eor|><|eols|><|endoftext|> | 23 |
programmingcirclejerk | dnkndnts | fxxcnzp | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>>> The problem with large C/C++ codebases is that they are invariably full of unintentional UB (e.g. crashes, use-after-free, etc) because it's very hard to write a C program that doesn't have some sort of possible UB in it. As you just brought up, every time you dereference any pointer you might be causing UB, either via a null pointer (which usually helpfully crashes), or more scarily via use-after free (which generally doesn't and instead causes very strange and unpredictable behavior)
> That's not really my experience with well-written code bases. This does happen if you work with amateurs, but it's very rare in professionally maintained code bases. Generally, you use design-patterns and documentation to make sure that behaviour is well-defined everywhere. I admit there are a lot of second-rate programmers who write shitty code out there. They are better served not writing in C though.
>
> Note that for most business logic written in C, the more natural migration path is to something like Go which solves all these resource allocation problems dynamically and allows you to write in mostly the same style as in C, whereas Rust really demands quite a different programming style.
>
> Also, don't mix C and C++ please. The idiomatic programming style and issues plaguing these two languages are entirely different.
>> The whole reason Rust exists is because this is a hard problem that humans have been repeatedly shown to be incapable of solving, so moving some of that work onto the compiler will help us write better programs.
> Humans are capable of solving these problems if trained correctly. The main problem with Rust is that it introduces an enormous amount of complexity and both syntactic and logic boilerplate that writing programs in it is an annoyingly tedious exercise. Every time I need to think about how to make the program logic I am thinking about agreeable to the language I am programming in instead of simply writing it down I am being affirmed that my choice of language is wrong. I used to think of this as an interesting challenge (back when I wrote a lot of Haskell) but now I'm just sick of it.
>
> If I want a safe language (i.e. one that reasons about memory usage for me), I use something like Go or an interpreted language. If I want a language without a runtime environment, I use C or write in assembly. I am never going to trade safety for complexity and my sanity. There might be some place for Rust when I need complex typing, but that can usually be avoided by not trying to overly generalise your program.
You can copy-paste any sentence and post it. You don't have to read it first.<|eor|><|sor|>Any time I hear someone say the solution to a problem is "more training" I just assume they're an idiot. Which is great, since that's Reddit's solution to like every problem ever.<|eor|><|sor|>Following your statements, representatives of discriminated populations look at you with resentment and hostility:
- teachers
- astronauts
- olympic athletes
- HR
- neural networks<|eor|><|sor|>Well it's a stretch to say athletes are solving a problem, so my statement doesn't really apply to them, but I get where you're coming from - it's important to smugly condescend to them nonetheless.<|eor|><|eols|><|endoftext|> | 22 |
programmingcirclejerk | crochet_du_gauche | fxx8snj | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>Crashing sounds awesome, I dont think our users will mind restarting their hours long data ingest process. Time to rewrite our code in C++, Rust was a mistake.<|eor|><|eols|><|endoftext|> | 21 |
programmingcirclejerk | camelCaseIsWebScale | fxwzbjh | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>*YOU* ARE FULL OF BULLSHIT
The point of null safety is not safety. It is being able to save a branch doing null checks in every function. Open some C man page and you can see every function does an unnecessary branch to handle NULL which means our icache footprint is scary due to C A R Hoare being drunk one day and introducing NULL to the world.
Because of icache footprint and branch overhead due to all the excessive null pointer checks, about a billion of computers have wasted about a dollar each in power consumption and you know longer the task takes display and wifi needs to be turned on for longer and display & wifi are a big part of power consumption. Therefore C A R Von Paul Neumann has concluded Null is billion dollar mistake. You don't get it because you are full of bullshit.<|eor|><|eols|><|endoftext|> | 19 |
programmingcirclejerk | BB_C | fxxacc3 | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>>> The problem with large C/C++ codebases is that they are invariably full of unintentional UB (e.g. crashes, use-after-free, etc) because it's very hard to write a C program that doesn't have some sort of possible UB in it. As you just brought up, every time you dereference any pointer you might be causing UB, either via a null pointer (which usually helpfully crashes), or more scarily via use-after free (which generally doesn't and instead causes very strange and unpredictable behavior)
> That's not really my experience with well-written code bases. This does happen if you work with amateurs, but it's very rare in professionally maintained code bases. Generally, you use design-patterns and documentation to make sure that behaviour is well-defined everywhere. I admit there are a lot of second-rate programmers who write shitty code out there. They are better served not writing in C though.
>
> Note that for most business logic written in C, the more natural migration path is to something like Go which solves all these resource allocation problems dynamically and allows you to write in mostly the same style as in C, whereas Rust really demands quite a different programming style.
>
> Also, don't mix C and C++ please. The idiomatic programming style and issues plaguing these two languages are entirely different.
>> The whole reason Rust exists is because this is a hard problem that humans have been repeatedly shown to be incapable of solving, so moving some of that work onto the compiler will help us write better programs.
> Humans are capable of solving these problems if trained correctly. The main problem with Rust is that it introduces an enormous amount of complexity and both syntactic and logic boilerplate that writing programs in it is an annoyingly tedious exercise. Every time I need to think about how to make the program logic I am thinking about agreeable to the language I am programming in instead of simply writing it down I am being affirmed that my choice of language is wrong. I used to think of this as an interesting challenge (back when I wrote a lot of Haskell) but now I'm just sick of it.
>
> If I want a safe language (i.e. one that reasons about memory usage for me), I use something like Go or an interpreted language. If I want a language without a runtime environment, I use C or write in assembly. I am never going to trade safety for complexity and my sanity. There might be some place for Rust when I need complex typing, but that can usually be avoided by not trying to overly generalise your program.
You can copy-paste any sentence and post it. You don't have to read it first.<|eor|><|sor|>Any time I hear someone say the solution to a problem is "more training" I just assume they're an idiot. Which is great, since that's Reddit's solution to like every problem ever.<|eor|><|sor|>*if we could just educate ourselves*<|eor|><|eols|><|endoftext|> | 19 |
programmingcirclejerk | TheLastMeritocrat | fxx4pme | <|sols|><|sot|>Rust is treating null pointer dereferences like a sacrilege when they are actually a fairly well-defined failure mode these days: they make your program crash. [...] If your program can't handle crashing without data loss, then there are other things to fix than that null pointer dereference.<|eot|><|sol|>https://www.reddit.com/r/programming/comments/hpzqvt/rust_is_surprisingly_good_as_a_server_language/fxvldlw<|eol|><|sor|>On behalf of myself and other C programmers working on multiple serious fields, I want it said on the record, and I want the world to know, that this person does not represent us.
We never worshiped C. We never thought we could write *correct C*. How could we when generation after generation of static analyzers and runtime sanitizers managed to continually ~~humiliate~~ humble us?
In fact, one of the few things that seems to unite us all is our continued fascination at how our code manages to actually work most of the time, or appears to be doing so at least.
Some of us never imagined that we will still be writing C in 2020, but here we are. C++ was a major contributor to C's extended relevance (we sometimes use this sentence as a test because C++ developers don't realize what we mean by it).
Thank you Bjarne, I think..
When Rust came out, we were mostly skeptical (did I mention C++ already?),
but some of us grew to like it, and most of us definitely respect it and understand the premises behind its existence.
I'm going to stop here so this doesn't become a TL;DR.
Again, **this person does not represent us C programmers**. I'm not saying he/she is definitely not a C programmer. No need to throw a *no true Scotsman* at me. I'm just making it clear that he/she is not representative of us.<|eor|><|sor|>> gain, this person does not represent us C programmers.
Fuxxy is the ideal C programmer. You may not like it, but this is what peak performance looks like.
Also he's the mod of the C subreddits so do what he says or get BANNED.<|eor|><|sor|>lol C subreddits<|eor|><|eols|><|endoftext|> | 17 |
programmingcirclejerk | coolreader18 | c3t3wz | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|eols|><|endoftext|> | 154 |
programmingcirclejerk | coolreader18 | ert3aga | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|soopr|> >>> with open('test.v','w') as f:
... f.writelines(["fn main() {\n"])
... f.writelines(["println('Hello World')\n"] * 1200000)
... f.writelines(["}\n"])
...
$ ./v test.v
pass=2 fn=`main`
panic: test.v:50003
more than 50 000 statements in function `main`
exit():
It puts a hard limit on how many statements you can have in a function, TRULY an opinionated lanuage.<|eoopr|><|eols|><|endoftext|> | 108 |
programmingcirclejerk | defunkydrummer | ert3st8 | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>>Maps
>mut m := map[string]int{} // Only maps with string keys are allowed for now
>//TODO: implement a way to check if the key exists
Not even released and it's already better than Go.<|eor|><|eols|><|endoftext|> | 102 |
programmingcirclejerk | SethDusek5 | ert7t9y | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|soopr|> >>> with open('test.v','w') as f:
... f.writelines(["fn main() {\n"])
... f.writelines(["println('Hello World')\n"] * 1200000)
... f.writelines(["}\n"])
...
$ ./v test.v
pass=2 fn=`main`
panic: test.v:50003
more than 50 000 statements in function `main`
exit():
It puts a hard limit on how many statements you can have in a function, TRULY an opinionated lanuage.<|eoopr|><|sor|>From the website (vlang.io)
- V compiles 1.2 million lines of code per second per CPU core.
- Such speed is achieved by direct machine code generation wip and a strong modularity.
- V can also emit C, then the compilation speed drops to 100k lines/second/CPU.
- As fast as C
But can it compare with Rust? With it's zero cost abstractions, move semantics, guaranteed memory safety, fearless concurrency, trait-based generics, pattern-matching, type inference, minimal runtime and efficient C bindings?<|eor|><|eols|><|endoftext|> | 70 |
programmingcirclejerk | git_commit_-m_sudoku | ert8p1f | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>https://github.com/vlang/v/blob/889d564f43927dc4fbe15ee8f67cb720776aaf63/compiler/main.v#L803-L806
> `if line.starts_with('print') {`
Parsing like a true 10er<|eor|><|eols|><|endoftext|> | 64 |
programmingcirclejerk | defunkydrummer | ert48uk | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>>Maps
>mut m := map[string]int{} // Only maps with string keys are allowed for now
>//TODO: implement a way to check if the key exists
Not even released and it's already better than Go.<|eor|><|soopr|>/uj what do you mean?<|eoopr|><|sor|>- Simpler to understand
- I never used anything other than strings as map keys and I don't need it.<|eor|><|eols|><|endoftext|> | 64 |
programmingcirclejerk | Joniator | ert5hqi | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>Is this some giant troll or something? So many things with this project that need to burn (Amount of stars, github sponsor link, discord, BDFL that replies to comments in a trollish manor "works for me", obviously broken features, features that are calling existing programs like curl, ect)
Sounds like you took the bait.
​
EDIT: It gets better - there's a [patreon page](https://www.patreon.com/vlang)<|eor|><|sor|>>there's a patreon page
[Ah yes, hiding your change logs behind a $5 paywall. Awesome](https://imgur.com/JfnCvUo)<|eor|><|eols|><|endoftext|> | 56 |
programmingcirclejerk | ineedmorealts | ert5wx8 | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>Is this some giant troll or something? So many things with this project that need to burn (Amount of stars, github sponsor link, discord, BDFL that replies to comments in a trollish manor "works for me", obviously broken features, features that are calling existing programs like curl, ect)
Sounds like you took the bait.
​
EDIT: It gets better - there's a [patreon page](https://www.patreon.com/vlang)<|eor|><|sor|>>there's a patreon page
[Ah yes, hiding your change logs behind a $5 paywall. Awesome](https://imgur.com/JfnCvUo)<|eor|><|sor|>Not even porn game devs put the change log behind a paywall<|eor|><|eols|><|endoftext|> | 54 |
programmingcirclejerk | Sleepi_ | ert3xl1 | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>> look at these Rust bots, they are all mad, daddy Mozilla aka Crapzilla didn't feed u enough of cum ?
Amazing
Apparently V uses the shell for its mkdir and http functions. What a disaster.<|eor|><|eols|><|endoftext|> | 47 |
programmingcirclejerk | hexane360 | ert9gm9 | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>> V functions are pure by default, meaning that their return values are only determined by their arguments, and their evaluation has no side effects.
If its true and there are no monads is it even possible to get the current date?
> There's no garbage collection or reference counting. V cleans up what it can during compilation.
This exceeds my cognitive skills. ELI5 pls.<|eor|><|sor|>He said somewhere it inserts free() 'where it can'. Where it cannot was not addressed.<|eor|><|sor|>Seriously, he just goes around in circles on this. First, he says something along the line of "I don't have to worry about memory in Go, so V will be the same". Then he says "it will be like Rust but simpler". Then he says "it'll be automatic except where it isn't, then it has to be manual". Then he says "if you can allocate memory I must have included some way to deallocate it", without actually telling you what that way is.<|eor|><|eols|><|endoftext|> | 44 |
programmingcirclejerk | WhyWasIShadowBanned_ | ert5v07 | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>> V functions are pure by default, meaning that their return values are only determined by their arguments, and their evaluation has no side effects.
If its true and there are no monads is it even possible to get the current date?
> There's no garbage collection or reference counting. V cleans up what it can during compilation.
This exceeds my cognitive skills. ELI5 pls.<|eor|><|eols|><|endoftext|> | 42 |
programmingcirclejerk | terserterseness | ert70ye | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>> V functions are pure by default, meaning that their return values are only determined by their arguments, and their evaluation has no side effects.
If its true and there are no monads is it even possible to get the current date?
> There's no garbage collection or reference counting. V cleans up what it can during compilation.
This exceeds my cognitive skills. ELI5 pls.<|eor|><|sor|>He said somewhere it inserts free() 'where it can'. Where it cannot was not addressed.<|eor|><|eols|><|endoftext|> | 42 |
programmingcirclejerk | ryeguy | ert7px4 | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>Is this some giant troll or something? So many things with this project that need to burn (Amount of stars, github sponsor link, discord, BDFL that replies to comments in a trollish manor "works for me", obviously broken features, features that are calling existing programs like curl, ect)
Sounds like you took the bait.
​
EDIT: It gets better - there's a [patreon page](https://www.patreon.com/vlang)<|eor|><|sor|>And the patreon is making over $800/month<|eor|><|sor|>This poor company decided to sponsor it for $200/month: https://offscale.io/<|eor|><|sor|>what the fuck is this website<|eor|><|eols|><|endoftext|> | 36 |
programmingcirclejerk | coolreader18 | ert0zoc | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>Is this some giant troll or something? So many things with this project that need to burn (Amount of stars, github sponsor link, discord, BDFL that replies to comments in a trollish manor "works for me", obviously broken features, features that are calling existing programs like curl, ect)
Sounds like you took the bait.
​
EDIT: It gets better - there's a [patreon page](https://www.patreon.com/vlang)<|eor|><|soopr|>I wasn't really all into it, it seemed like a pretty good language if it actually was all that it says it is, but this release that's a) late and b) not even working (I get a segfault when I try to compile the compiler from C sources) makes me think that this was some pet project that he posted about and got surprisingly popular. This is all hilarious though, so I'd say it's worth it, and I'd think that an actual working release will happen at some point soon.<|eoopr|><|eols|><|endoftext|> | 34 |
programmingcirclejerk | zacgarby | ert32iy | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>Is this some giant troll or something? So many things with this project that need to burn (Amount of stars, github sponsor link, discord, BDFL that replies to comments in a trollish manor "works for me", obviously broken features, features that are calling existing programs like curl, ect)
Sounds like you took the bait.
​
EDIT: It gets better - there's a [patreon page](https://www.patreon.com/vlang)<|eor|><|sor|>And the patreon is making over $800/month<|eor|><|sor|>This poor company decided to sponsor it for $200/month: https://offscale.io/<|eor|><|eols|><|endoftext|> | 34 |
programmingcirclejerk | JohnMcPineapple | ert824a | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>It's great that someone is creating a new alternative programming language! 4000 Stars aren't simply enough for the 2 hours that it's been online! It should have more!
--
`uj {`
Why does a programming language that released a mere 2 hours ago already have almost 4000 stars (and so much apparent hype)?<|eor|><|eols|><|endoftext|> | 32 |
programmingcirclejerk | Nickitolas | ert1izl | <|sols|><|sot|>V language was just released, there's a issue in its repo that's being used as a chat thread.<|eot|><|sol|>https://github.com/vlang/v/issues/319<|eol|><|sor|>Is this some giant troll or something? So many things with this project that need to burn (Amount of stars, github sponsor link, discord, BDFL that replies to comments in a trollish manor "works for me", obviously broken features, features that are calling existing programs like curl, ect)
Sounds like you took the bait.
​
EDIT: It gets better - there's a [patreon page](https://www.patreon.com/vlang)<|eor|><|sor|>And the patreon is making over $800/month<|eor|><|eols|><|endoftext|> | 31 |
programmingcirclejerk | cmov | au95yx | <|sols|><|sot|>I don't know how to fly a commercial airliner, but I could probably figure my way around a small single prop airplane. That's basically the difference between Go and a language like Rust or C++ or any language that requires a lot of up front investment, but then let's you work at power level 9000.<|eot|><|sol|>https://news.ycombinator.com/item?id=19222417<|eol|><|eols|><|endoftext|> | 151 |
programmingcirclejerk | ProfessorSexyTime | eh6io43 | <|sols|><|sot|>I don't know how to fly a commercial airliner, but I could probably figure my way around a small single prop airplane. That's basically the difference between Go and a language like Rust or C++ or any language that requires a lot of up front investment, but then let's you work at power level 9000.<|eot|><|sol|>https://news.ycombinator.com/item?id=19222417<|eol|><|sor|>If you unironically use analogies to describe programming languages, you're probably retarded.
/uj
If you unironically use analogies to describe programming languages, you're probably retarded.<|eor|><|eols|><|endoftext|> | 99 |
programmingcirclejerk | TheFearsomeEsquilax | eh6kr2r | <|sols|><|sot|>I don't know how to fly a commercial airliner, but I could probably figure my way around a small single prop airplane. That's basically the difference between Go and a language like Rust or C++ or any language that requires a lot of up front investment, but then let's you work at power level 9000.<|eot|><|sol|>https://news.ycombinator.com/item?id=19222417<|eol|><|sor|>Programming is the most rigorous and intense mental training in the world. Everybody in this country should learn to program a computer, because it teaches you how to think.<|eor|><|eols|><|endoftext|> | 65 |
programmingcirclejerk | Hyperman360 | eh6leo4 | <|sols|><|sot|>I don't know how to fly a commercial airliner, but I could probably figure my way around a small single prop airplane. That's basically the difference between Go and a language like Rust or C++ or any language that requires a lot of up front investment, but then let's you work at power level 9000.<|eot|><|sol|>https://news.ycombinator.com/item?id=19222417<|eol|><|soopr|>> work at power level 9000.
Ask PCJ: Which language lets you work at power level _over_ 9000?<|eoopr|><|sor|>anime.js<|eor|><|eols|><|endoftext|> | 41 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.