subreddit stringclasses 7
values | author stringlengths 3 20 | id stringlengths 5 7 | content stringlengths 67 30.4k | score int64 0 140k |
|---|---|---|---|---|
programmingcirclejerk | fijt | eh6l9wd | <|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|><|sor|>Let me reply with this quote:
>To me, Go is a better Python. It's easier to learn, faster, more scalable, and safer, and just as easy and quick to write. It's just not a language for big projects.
​<|eor|><|eols|><|endoftext|> | 38 |
programmingcirclejerk | sportif11 | eh7pkw3 | <|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|><|sor|>Let me reply with this quote:
>To me, Go is a better Python. It's easier to learn, faster, more scalable, and safer, and just as easy and quick to write. It's just not a language for big projects.
​<|eor|><|sor|>>more scalable
>not for big projects
ok<|eor|><|eols|><|endoftext|> | 36 |
programmingcirclejerk | cmov | eh6l8xl | <|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|><|eols|><|endoftext|> | 35 |
programmingcirclejerk | BufferUnderpants | eh702qf | <|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|><|sor|>[deleted]<|eor|><|sor|>Join the webshit army! For a mere $20000 crash course you too can earn less than an auto mechanic, and that's before the inevitable market correction!<|eor|><|eols|><|endoftext|> | 29 |
programmingcirclejerk | defunkydrummer | eh6qtg1 | <|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|>>Ask PCJ: Which language lets you work at power level over 9000?
There are at least three of them:
If you want to work at power level Over 9000 and be practical yet immoral, use Lisp.
If you want to work at power level Over 9000 and be morally right yet ridculous, use Rust.
If you want to work at power level Over 9000 and be scientific yet unemployed, use Haskal.
<|eor|><|eols|><|endoftext|> | 28 |
programmingcirclejerk | defunkydrummer | eh75mab | <|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|>As someone that knows flight physics and a generally aerospace autist, this guys metaphor is about as solid as the mud in the battle of ypres<|eor|><|sor|>> As someone that knows flight physics and a generally aerospace autist,
A long way to write "C# wageslave"
<|eor|><|eols|><|endoftext|> | 25 |
programmingcirclejerk | three18ti | eh6utdd | <|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|><|sor|>You mean it teaches you how to copy/paste code from stack overflow.<|eor|><|eols|><|endoftext|> | 23 |
programmingcirclejerk | cmov | eh6kyjt | <|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|>> It will take you a lot longer to get there when you aren't going 600MPH, and you can carry a lot less people, but at least you aren't driving a car like the people using Python. Sure it's probably not going to be as rigorously inspected as the Boeing borrow checker, but Go is at least getting an inspection, whereas your Python code is just going to break down on the side of the road when the problems surface itself because you didn't check the oil light.<|eoopr|><|eols|><|endoftext|> | 20 |
programmingcirclejerk | porjolovsky | eh7obyo | <|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|>Im new to this sub, I see a lot of Go mentions in every post it seems like.
I wasnt aware that people actually made fun of Go that much before. I feel enlightened.
Can someone give me a quick low down on wtf is really going on around here?<|eor|><|sor|>Hi and welcome, though you probably wont last long if you werent yet able to fogure out the following BASIC facts of life by yourself:
Go is bad. Haskell is bad. Rust is moral but bad. C# is for corporate wageslaves. Python is for webshits. NPM has lots of neat and usefull packages you should check out. C is old and probably bad, but I dont think its tragic to use it from a moral perspective. C++ is dead, but otherwise good.
Java & PHP (5.x) are safe, but SmallTalk is KING.<|eor|><|eols|><|endoftext|> | 18 |
programmingcirclejerk | jk_scowling | eh7ezf0 | <|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|><|sor|>You mean it teaches you how to copy/paste code from stack overflow.<|eor|><|sor|>Sssssh, don't go blurting out guild secrets in public!<|eor|><|eols|><|endoftext|> | 16 |
programmingcirclejerk | defunkydrummer | eh6qlj8 | <|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|>>>But one refreshing thing is how opinionated the language and the frameworks are refreshing as theres only one acceptable way to do many things.
Presented without further comment.<|eor|><|eols|><|endoftext|> | 15 |
programmingcirclejerk | hexane360 | eh72zbd | <|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|><|sor|>What about the other way around: https://news.ycombinator.com/item?id=17260199
>did you just use technical debt as a metaphor for regular old debt?<|eor|><|eols|><|endoftext|> | 15 |
programmingcirclejerk | haskell_leghumper | 9clung | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|eols|><|endoftext|> | 152 |
programmingcirclejerk | SelfDistinction | e5bkkal | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|sor|>> In 'filter.js':
> `export default (filter, arr) => arr.filter(filter);`
Damn. That's some extremely clever Javascript code. I never thought it possible to implement such complex behaviour in such a simple, straightforward yet elegant and powerful way. <|eor|><|eols|><|endoftext|> | 108 |
programmingcirclejerk | belst | e5bkuqu | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|sor|>> In 'filter.js':
> `export default (filter, arr) => arr.filter(filter);`
Damn. That's some extremely clever Javascript code. I never thought it possible to implement such complex behaviour in such a simple, straightforward yet elegant and powerful way. <|eor|><|sor|>You know you made it, when `import { filter } from '1-liners/module/index'` is longer than the actual implementation.<|eor|><|eols|><|endoftext|> | 60 |
programmingcirclejerk | haskell_leghumper | e5bjha2 | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|soopr|>[Bonus: "I strongly believe in writing one-line node modules: how to get to the top of npm"](https://dev.to/hemanth/authoring-node-modules-3k8a)<|eoopr|><|eols|><|endoftext|> | 40 |
programmingcirclejerk | fojam | e5bkgn6 | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|sor|>Jeaus most of these "tools" are things that take no time to just write in the way the language intended. Why do I need to write and(a, b) instead of (a && b)?? Wtf is the point of this library<|eor|><|eols|><|endoftext|> | 40 |
programmingcirclejerk | YqQbey | e5boq7e | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|sor|>And no isOdd and isEven. What use of this library then?<|eor|><|eols|><|endoftext|> | 39 |
programmingcirclejerk | hnerixh | e5bm0al | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|sor|>The world obviously need more attempts at implementing a simple `map` function. I'd like to write a long rant about 'Map considered harmful', but I'd rather go start up steam and play some games.<|eor|><|eols|><|endoftext|> | 34 |
programmingcirclejerk | limasxgoesto0 | e5bmrya | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|sor|>> made in Switzerland<|eor|><|eols|><|endoftext|> | 31 |
programmingcirclejerk | MrMetalfreak94 | e5c274m | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|sor|>The world obviously need more attempts at implementing a simple `map` function. I'd like to write a long rant about 'Map considered harmful', but I'd rather go start up steam and play some games.<|eor|><|sor|>They are not even implementing their own map function, their implementation is far more embarrassing:
export default (map, arr) => arr.map(map);
<|eor|><|eols|><|endoftext|> | 30 |
programmingcirclejerk | DecentSatisfaction | e5bokgs | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|sor|>Shit I'm like a month on this sub and wanted to learn what kind of mistakes not to do but this is just so bizarre. What's with making functions for binary and logic operators ([division is named by](https://github.com/1-liners/1-liners/tree/master/documentation#by)), adding function to remove implicit this like [charAt](https://github.com/1-liners/1-liners/tree/master/documentation#charat), renaming functions that [already](https://github.com/1-liners/1-liners/tree/master/documentation#concat) [exist](https://github.com/1-liners/1-liners/tree/master/documentation#endswith), [wtf](https://github.com/1-liners/1-liners/tree/master/documentation#dec), [identity function](https://github.com/1-liners/1-liners/tree/master/documentation#identity) or [noop](https://github.com/1-liners/1-liners/tree/master/documentation#noop), all this shit with classic javascript [NaN is a number](https://github.com/1-liners/1-liners/tree/master/documentation#isnumber).<|eor|><|eols|><|endoftext|> | 28 |
programmingcirclejerk | StallmanTheHot | e5c6u5w | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|soopr|>[Bonus: "I strongly believe in writing one-line node modules: how to get to the top of npm"](https://dev.to/hemanth/authoring-node-modules-3k8a)<|eoopr|><|sor|>>Dig into GitHub and find a few trending projects, read the source, find code that can be extracted into a module, make a module and send a PR with it, most of time it gets accepted as modularity always wins.<|eor|><|eols|><|endoftext|> | 26 |
programmingcirclejerk | 1024KiB | e5bvz59 | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|sor|>Shit I'm like a month on this sub and wanted to learn what kind of mistakes not to do but this is just so bizarre. What's with making functions for binary and logic operators ([division is named by](https://github.com/1-liners/1-liners/tree/master/documentation#by)), adding function to remove implicit this like [charAt](https://github.com/1-liners/1-liners/tree/master/documentation#charat), renaming functions that [already](https://github.com/1-liners/1-liners/tree/master/documentation#concat) [exist](https://github.com/1-liners/1-liners/tree/master/documentation#endswith), [wtf](https://github.com/1-liners/1-liners/tree/master/documentation#dec), [identity function](https://github.com/1-liners/1-liners/tree/master/documentation#identity) or [noop](https://github.com/1-liners/1-liners/tree/master/documentation#noop), all this shit with classic javascript [NaN is a number](https://github.com/1-liners/1-liners/tree/master/documentation#isnumber).<|eor|><|sor|> u(n(j(e(r(k())))))
i think the point is to make functions out of all the operators so they can be converted to curried form (e.g. `f(x, y) = x * y` turns to `f(x) = f(y) = x * y`). then you can do all kinds of write-only functional composition tricks really slowly in a language that wasn't designed for it.
for example, instead of writing `const inc = x => x + 1` you can now write `const inc = plus(1)`. there's already a much better library for that particular vice called "ramda" so this library is a pointless waste of time and energy even for needlessly complicating webshits<|eor|><|sor|>lmao you dont need all that ivory tower shit just write a for loop in go and compile to wasm<|eor|><|eols|><|endoftext|> | 25 |
programmingcirclejerk | stone_henge | e5btjqg | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|sor|>Shit I'm like a month on this sub and wanted to learn what kind of mistakes not to do but this is just so bizarre. What's with making functions for binary and logic operators ([division is named by](https://github.com/1-liners/1-liners/tree/master/documentation#by)), adding function to remove implicit this like [charAt](https://github.com/1-liners/1-liners/tree/master/documentation#charat), renaming functions that [already](https://github.com/1-liners/1-liners/tree/master/documentation#concat) [exist](https://github.com/1-liners/1-liners/tree/master/documentation#endswith), [wtf](https://github.com/1-liners/1-liners/tree/master/documentation#dec), [identity function](https://github.com/1-liners/1-liners/tree/master/documentation#identity) or [noop](https://github.com/1-liners/1-liners/tree/master/documentation#noop), all this shit with classic javascript [NaN is a number](https://github.com/1-liners/1-liners/tree/master/documentation#isnumber).<|eor|><|sor|> u(n(j(e(r(k())))))
i think the point is to make functions out of all the operators so they can be converted to curried form (e.g. `f(x, y) = x * y` turns to `f(x) = f(y) = x * y`). then you can do all kinds of write-only functional composition tricks really slowly in a language that wasn't designed for it.
for example, instead of writing `const inc = x => x + 1` you can now write `const inc = plus(1)`. there's already a much better library for that particular vice called "ramda" so this library is a pointless waste of time and energy even for needlessly complicating webshits<|eor|><|eols|><|endoftext|> | 20 |
programmingcirclejerk | i9srpeg | e5c4j1m | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|sor|>Shit I'm like a month on this sub and wanted to learn what kind of mistakes not to do but this is just so bizarre. What's with making functions for binary and logic operators ([division is named by](https://github.com/1-liners/1-liners/tree/master/documentation#by)), adding function to remove implicit this like [charAt](https://github.com/1-liners/1-liners/tree/master/documentation#charat), renaming functions that [already](https://github.com/1-liners/1-liners/tree/master/documentation#concat) [exist](https://github.com/1-liners/1-liners/tree/master/documentation#endswith), [wtf](https://github.com/1-liners/1-liners/tree/master/documentation#dec), [identity function](https://github.com/1-liners/1-liners/tree/master/documentation#identity) or [noop](https://github.com/1-liners/1-liners/tree/master/documentation#noop), all this shit with classic javascript [NaN is a number](https://github.com/1-liners/1-liners/tree/master/documentation#isnumber).<|eor|><|sor|> u(n(j(e(r(k())))))
i think the point is to make functions out of all the operators so they can be converted to curried form (e.g. `f(x, y) = x * y` turns to `f(x) = f(y) = x * y`). then you can do all kinds of write-only functional composition tricks really slowly in a language that wasn't designed for it.
for example, instead of writing `const inc = x => x + 1` you can now write `const inc = plus(1)`. there's already a much better library for that particular vice called "ramda" so this library is a pointless waste of time and energy even for needlessly complicating webshits<|eor|><|sor|>lmao you dont need all that ivory tower shit just write a for loop in go and compile to wasm<|eor|><|sor|>I feel like Go is too academic now, with all those generics and fancy error handling, which makes it really hard to follow the code. I'm going back to C.<|eor|><|eols|><|endoftext|> | 20 |
programmingcirclejerk | Resquid | e5cf1jz | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|soopr|>[Bonus: "I strongly believe in writing one-line node modules: how to get to the top of npm"](https://dev.to/hemanth/authoring-node-modules-3k8a)<|eoopr|><|sor|>>Dig into GitHub and find a few trending projects, read the source, find code that can be extracted into a module, make a module and send a PR with it, most of time it gets accepted as modularity always wins.<|eor|><|sor|>Hahaha holy shit I always assumed that's what people were doing but here it is in black and white.<|eor|><|eols|><|endoftext|> | 18 |
programmingcirclejerk | ryeguy | e5d26jg | <|sols|><|sot|>136 lines of code, 136 npm micro-modules, each hand-crafted with love and attention, products of top-quality functional programming craftmanship<|eot|><|sol|>https://github.com/1-liners/1-liners<|eol|><|soopr|>[Bonus: "I strongly believe in writing one-line node modules: how to get to the top of npm"](https://dev.to/hemanth/authoring-node-modules-3k8a)<|eoopr|><|sor|>>Dig into GitHub and find a few trending projects, read the source, find code that can be extracted into a module, make a module and send a PR with it, most of time it gets accepted as modularity always wins.<|eor|><|sor|>Why the fuck would a project maintainer accept a PR that replaces a line of code or two with a dependency? I guess I haven't ascended to this level yet.<|eor|><|eols|><|endoftext|> | 17 |
programmingcirclejerk | quasarj | 8d0t26 | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|eols|><|endoftext|> | 150 |
programmingcirclejerk | GOPHERS_GONE_WILD | dxjfign | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>BTFO by paintbucket tool<|eor|><|eols|><|endoftext|> | 42 |
programmingcirclejerk | haskell_leghumper | dxjgw5t | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>[deleted]<|eor|><|sor|>Just like that, you have rocked your coding interview.<|eor|><|eols|><|endoftext|> | 41 |
programmingcirclejerk | TwiSparklePony | dxjqaug | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>The most incredible part of the thread was watching them give an example that was supposed to be uncolorable, but then having multiple people respond with the 4-color solution and then just ignoring their replies.
<uj> Makes me think that this person is just trolling </uj><|eor|><|eols|><|endoftext|> | 40 |
programmingcirclejerk | pingpong | dxjni3g | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>I like all of the pretty MS Paint drawings we get from different users.
[jnky](https://i.imgur.com/m3Ruasq.png)
[bronson](https://i.imgur.com/88tEMcX.png)
[guskel](https://i.imgur.com/tLyGyc3.png)
[kr99x](https://i.imgur.com/jRMP9rJ.png)<|eor|><|eols|><|endoftext|> | 35 |
programmingcirclejerk | frkbmr | dxjq9m2 | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>[deleted]<|eor|><|sor|>This is a work of art<|eor|><|eols|><|endoftext|> | 25 |
programmingcirclejerk | Resquid | dxjt1jx | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>There are a discrete number of primes. Prove me wrong, pcj.<|eor|><|eols|><|endoftext|> | 23 |
programmingcirclejerk | stone_henge | dxjypun | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>last post from that same user offers an explanation
> I think for a large number of people, myself included, the "Eureka!" moment often occurs when you're least focused on the problem at hand. <|eor|><|eols|><|endoftext|> | 22 |
programmingcirclejerk | pilotInPyjamas | dxjtuya | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>I like all of the pretty MS Paint drawings we get from different users.
[jnky](https://i.imgur.com/m3Ruasq.png)
[bronson](https://i.imgur.com/88tEMcX.png)
[guskel](https://i.imgur.com/tLyGyc3.png)
[kr99x](https://i.imgur.com/jRMP9rJ.png)<|eor|><|sor|>+1 for anyone who coloured the background too.<|eor|><|eols|><|endoftext|> | 22 |
programmingcirclejerk | one_zer | dxjttfk | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>There are a discrete number of primes. Prove me wrong, pcj.<|eor|><|sor|>finite : discrete :: pcj : lolnogenerics<|eor|><|eols|><|endoftext|> | 17 |
programmingcirclejerk | InvisibleEar | dxjcrij | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>Wake up sheeple! <|eor|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | UsingYourWifi | dxk01zs | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>[deleted]<|eor|><|sor|>Have you met our lord and savior the bipartite graph? Are you familiar with his work the implied subgraph?<|eor|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | Code_Artisan | dxkqb6b | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>There are a discrete number of primes. Prove me wrong, pcj.<|eor|><|sor|>there is exactly 425 656 284 035 217 743 primes. Proof by code
unsigned long long countPrimesUpTo(unsigned long long n);
unsigned long long biggestNumber()
{
int p = 0;
int n = 0;
while(++n > p) ++p;
return p;
}
printf("%llu\n", countPrimesUpTo( biggestNumber() );
code never lie.<|eor|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | roxven | dxjcq6z | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>/u/guskel is my [hero](https://m.imgur.com/a/JE5Ov)<|eor|><|eols|><|endoftext|> | 10 |
programmingcirclejerk | 6nf | dxjidou | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>HAHAHAHAHAHA<|eor|><|eols|><|endoftext|> | 9 |
programmingcirclejerk | terserterseness | dxk3gqr | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>[deleted]<|eor|><|sor|>> onto a pile of unwashed clothes
That's the optimist in you there. <|eor|><|eols|><|endoftext|> | 9 |
programmingcirclejerk | DuBistKomisch | dxke5ts | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>There are a discrete number of primes. Prove me wrong, pcj.<|eor|><|sor|>>discrete
what did he mean by this?<|eor|><|eols|><|endoftext|> | 9 |
programmingcirclejerk | throwaway27464829 | dxjyozq | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>I like all of the pretty MS Paint drawings we get from different users.
[jnky](https://i.imgur.com/m3Ruasq.png)
[bronson](https://i.imgur.com/88tEMcX.png)
[guskel](https://i.imgur.com/tLyGyc3.png)
[kr99x](https://i.imgur.com/jRMP9rJ.png)<|eor|><|sor|>They kind of look like a janky OSI logo.<|eor|><|eols|><|endoftext|> | 8 |
programmingcirclejerk | elbitjusticiero | dxjvt33 | <|sols|><|sot|>HN poster disproves 4-color map theory<|eot|><|sol|>https://news.ycombinator.com/item?id=16862553<|eol|><|sor|>I like all of the pretty MS Paint drawings we get from different users.
[jnky](https://i.imgur.com/m3Ruasq.png)
[bronson](https://i.imgur.com/88tEMcX.png)
[guskel](https://i.imgur.com/tLyGyc3.png)
[kr99x](https://i.imgur.com/jRMP9rJ.png)<|eor|><|sor|>[deleted]<|eor|><|sor|>Indeed!<|eor|><|eols|><|endoftext|> | 8 |
programmingcirclejerk | anatolya | qnw7r5 | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|eols|><|endoftext|> | 150 |
programmingcirclejerk | NiceTerm | hjj2jpx | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>I use crashing instead of branching: you wont find ifs in my code<|eor|><|eols|><|endoftext|> | 82 |
programmingcirclejerk | RustEvangelist10xer | hjj92oz | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>I use crashing instead of branching: you wont find ifs in my code<|eor|><|sor|>This is how I detect 10xers. If I `grep` your repo and find more than 2 `if` or `else` statements, it's clear to me that you write junk, not clean code.<|eor|><|eols|><|endoftext|> | 50 |
programmingcirclejerk | herder | hjjmrzp | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>Working code: YAGNI<|eor|><|eols|><|endoftext|> | 33 |
programmingcirclejerk | ProfessorSexyTime | hjk13gc | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>Why refactor when you can keep pushing out features every sprint so your PM(s) wanna blow you and you can climb that corporate ladder?
EDIT: This got me thinking.
We should start showing these kinds of posts to university students to show them how it doesn't _really_ matter how knowledgeable you are or how correct your code is: if it satisfies as a feature and it passes all the test, who cares? Just type away at the keyboard and pump out the code, kid.<|eor|><|eols|><|endoftext|> | 23 |
programmingcirclejerk | RepresentativeNo6029 | hjj9b0n | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>I use crashing instead of branching: you wont find ifs in my code<|eor|><|sor|>I don't use loops. Just checkpoint to S3 and restart.<|eor|><|eols|><|endoftext|> | 20 |
programmingcirclejerk | Silly-Freak | hjkhqka | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>Why refactor when you can keep pushing out features every sprint so your PM(s) wanna blow you and you can climb that corporate ladder?
EDIT: This got me thinking.
We should start showing these kinds of posts to university students to show them how it doesn't _really_ matter how knowledgeable you are or how correct your code is: if it satisfies as a feature and it passes all the test, who cares? Just type away at the keyboard and pump out the code, kid.<|eor|><|sor|>Professors: don't bother with proper error handling.
Students: Wait, were we supposed to do that before?<|eor|><|eols|><|endoftext|> | 17 |
programmingcirclejerk | watcher202010 | hjkj4g9 | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>Writing poor code was always a breeze. It's the consequences that are usually the problem.<|eor|><|eols|><|endoftext|> | 14 |
programmingcirclejerk | watcher202010 | hjjn5fp | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>Great news! Switching to unsafe code in Rust!<|eor|><|eols|><|endoftext|> | 14 |
programmingcirclejerk | _wjp_ | hjkwa91 | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>I use crashing instead of branching: you wont find ifs in my code<|eor|><|sor|>This is how I detect 10xers. If I `grep` your repo and find more than 2 `if` or `else` statements, it's clear to me that you write junk, not clean code.<|eor|><|sor|>https://www.reddit.com/r/programmingcirclejerk/comments/qjp2hc/good_code_is_the_one_that_lacks_of_else_statement/<|eor|><|eols|><|endoftext|> | 13 |
programmingcirclejerk | grapesmoker | hjkwcku | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>why do a good job when you can do a bad job and expend way less effort?<|eor|><|eols|><|endoftext|> | 11 |
programmingcirclejerk | Teln0 | hjjnsuk | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>Great news! Switching to unsafe code in Rust!<|eor|><|sor|>Just unwrap a None duh<|eor|><|eols|><|endoftext|> | 11 |
programmingcirclejerk | fp_weenie | hjmatmk | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>Why shit in toilet when janitor will wash floor??<|eor|><|eols|><|endoftext|> | 10 |
programmingcirclejerk | fp_weenie | hjmav94 | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>why do a good job when you can do a bad job and expend way less effort?<|eor|><|sor|>> job when you can do a bad job and expend way less effort?
using Google-scale technologies, too!<|eor|><|eols|><|endoftext|> | 9 |
programmingcirclejerk | camelCaseIsWebScale | hjk1bzd | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>R.I.P
/uj
R.I.P<|eor|><|eols|><|endoftext|> | 7 |
programmingcirclejerk | Kyo91 | hjl6sqm | <|sols|><|sot|>Kubernetes made writing poor code a breeze. At work we have microservices crashing 20 times a week but SLOs are not affected since traffic is routed to surviving pods. So we can concentrate on churning features fast instead of writing good code.<|eot|><|sol|>https://news.ycombinator.com/item?id=29128119<|eol|><|sor|>Why refactor when you can keep pushing out features every sprint so your PM(s) wanna blow you and you can climb that corporate ladder?
EDIT: This got me thinking.
We should start showing these kinds of posts to university students to show them how it doesn't _really_ matter how knowledgeable you are or how correct your code is: if it satisfies as a feature and it passes all the test, who cares? Just type away at the keyboard and pump out the code, kid.<|eor|><|sor|>Professors: don't bother with proper error handling.
Students: Wait, were we supposed to do that before?<|eor|><|sor|>Next you'll tell them they can stop writing so many unit tests on their assignments!<|eor|><|eols|><|endoftext|> | 5 |
programmingcirclejerk | cmov | p9wqjd | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|eols|><|endoftext|> | 151 |
programmingcirclejerk | BIG_SNYK_ENERGY | ha0kjwa | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>> I've become highly suspicious of any code
Yeah me too<|eor|><|eols|><|endoftext|> | 152 |
programmingcirclejerk | MySlicedHat | ha0thwb | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>> Go's popularity _without_ generics should be a testament to how little they're actually needed.
The popularity of flagship phones _without_ headphone jacks should be a testament to how little they're actually needed.<|eor|><|eols|><|endoftext|> | 129 |
programmingcirclejerk | BIG_SNYK_ENERGY | ha0wpq4 | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>> Go's popularity _without_ generics should be a testament to how little they're actually needed.
The popularity of flagship phones _without_ headphone jacks should be a testament to how little they're actually needed.<|eor|><|sor|>The popularity of sex WITHOUT protection should be a testament of how little it is actually needed<|eor|><|eols|><|endoftext|> | 94 |
programmingcirclejerk | camelCaseIsWebScale | ha0z744 | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>There's an upper bound for your IQ if you want to work in our enterprise.<|eor|><|eols|><|endoftext|> | 59 |
programmingcirclejerk | glasshalf3mpty | ha10tud | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>> Go's popularity _without_ generics should be a testament to how little they're actually needed.
The popularity of flagship phones _without_ headphone jacks should be a testament to how little they're actually needed.<|eor|><|sor|>The popularity of sex WITHOUT protection should be a testament of how little it is actually needed<|eor|><|sor|>The popularity of sex without me having any is testament to how bad I smell<|eor|><|eols|><|endoftext|> | 59 |
programmingcirclejerk | xigoi | ha1ig4q | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>I feel (hope) functions are a thing that will exist only within the standard library and never make it into code me and my team writes. It'll be one of those things that junior devs will constantly try to reach for and an instant code smell for the reviewer.<|eor|><|eols|><|endoftext|> | 45 |
programmingcirclejerk | bog_deavil13 | ha16kp7 | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>> I've become highly suspicious of any code
Yeah me too<|eor|><|sor|>Specially my own code<|eor|><|eols|><|endoftext|> | 36 |
programmingcirclejerk | lorslara2000 | ha1xx21 | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>Generics, what are they good for?<|eor|><|sor|>Gatekeeping. Generics are scary and I don't like them. I feel stupid when I see code with generics so generics are stupid.<|eor|><|eols|><|endoftext|> | 35 |
programmingcirclejerk | LloydAtkinson | ha2bgiy | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>/uj
Yet most enterprise code Ive seen is Java and C# (my favourite language) which both make heavy use of generics
go shills only argument against generics is the same as saying we dont need computer printers because we have pen and pencil<|eor|><|eols|><|endoftext|> | 33 |
programmingcirclejerk | camelCaseIsWebScale | ha1akfi | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>> Go's popularity _without_ generics should be a testament to how little they're actually needed.
The popularity of flagship phones _without_ headphone jacks should be a testament to how little they're actually needed.<|eor|><|sor|>The popularity of sex WITHOUT protection should be a testament of how little it is actually needed<|eor|><|sor|>The popularity of sex without me having any is testament to how bad I smell<|eor|><|sor|>It's a testament to your flair actually<|eor|><|eols|><|endoftext|> | 26 |
programmingcirclejerk | silentconfessor | ha2o7iq | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>> Go's popularity _without_ generics should be a testament to how little they're actually needed.
The popularity of flagship phones _without_ headphone jacks should be a testament to how little they're actually needed.<|eor|><|sor|>The popularity of sex WITHOUT protection should be a testament of how little it is actually needed<|eor|><|sor|>The popularity of sex without me having any is testament to how bad I smell<|eor|><|sor|>It's a testament to your flair actually<|eor|><|sor|>Currying is sexy, fight me<|eor|><|soopr|> f g (f (x,y) = (g x) y)
Where's your God now?<|eoopr|><|sor|>all functions are equal, but some functions are more equal than others<|eor|><|eols|><|endoftext|> | 21 |
programmingcirclejerk | wildmonkeymind | ha2vh2o | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>Generics, what are they good for?<|eor|><|sor|>Seriously. The type Object and class-casting should be good enough for anyone. Plus, it adds *mystery*, which every codebase needs.<|eor|><|eols|><|endoftext|> | 18 |
programmingcirclejerk | cmov | ha2n1v8 | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>> Go's popularity _without_ generics should be a testament to how little they're actually needed.
The popularity of flagship phones _without_ headphone jacks should be a testament to how little they're actually needed.<|eor|><|sor|>The popularity of sex WITHOUT protection should be a testament of how little it is actually needed<|eor|><|sor|>The popularity of sex without me having any is testament to how bad I smell<|eor|><|sor|>It's a testament to your flair actually<|eor|><|sor|>Currying is sexy, fight me<|eor|><|soopr|> f g (f (x,y) = (g x) y)
Where's your God now?<|eoopr|><|eols|><|endoftext|> | 18 |
programmingcirclejerk | HorstKugel | ha0z2ht | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>> I noticed while writing this project that my literacy reading the generics code greatly increased (this only took a few days)<|eor|><|eols|><|endoftext|> | 17 |
programmingcirclejerk | nuggins | ha3c9x9 | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>> Go's popularity _without_ generics should be a testament to how little they're actually needed.
The popularity of flagship phones _without_ headphone jacks should be a testament to how little they're actually needed.<|eor|><|sor|>The popularity of programming _without_ golang should be a testament to how little it's actually needed.<|eor|><|eols|><|endoftext|> | 16 |
programmingcirclejerk | pareidolist | ha4aupj | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>/uj
Yet most enterprise code Ive seen is Java and C# (my favourite language) which both make heavy use of generics
go shills only argument against generics is the same as saying we dont need computer printers because we have pen and pencil<|eor|><|sor|>No, it's like saying "computer printers are *bad* because we have pen and pencil"<|eor|><|eols|><|endoftext|> | 15 |
programmingcirclejerk | senj | ha2sbdw | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>> I've become highly suspicious of any code that even uses a channel
Go's popularity _with_ channels should be a testament to how much they're actually needed. Devs can play without channels in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eor|><|eols|><|endoftext|> | 14 |
programmingcirclejerk | afdsadf | ha2uih1 | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>regular variables? good and not a code smell
type variables? who do you think I am, an *academic?*<|eor|><|eols|><|endoftext|> | 10 |
programmingcirclejerk | earthisunderattack | ha4r03r | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>> I've become highly suspicious of any code
Yeah me too<|eor|><|sor|>Specially my own code<|eor|><|sor|>wym just use coq and blindly
prove ur code. if it gives ok then run and go home<|eor|><|eols|><|endoftext|> | 10 |
programmingcirclejerk | 32gbsd | ha1uu08 | <|sols|><|sot|>Devs can play with generics in their own time all they want, but in an enterprise code base there are standards on what we do and don't allow.<|eot|><|sol|>https://old.reddit.com/r/golang/comments/p7iget/using_go_generics/h9obbfs/<|eol|><|sor|>Generics, what are they good for?<|eor|><|eols|><|endoftext|> | 9 |
programmingcirclejerk | rohitkg98 | n2ydtq | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|eols|><|endoftext|> | 150 |
programmingcirclejerk | elmosworld37 | gwmumdm | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>Is this /r/oldpeoplefacebook but for coding<|eor|><|eols|><|endoftext|> | 70 |
programmingcirclejerk | YM_Industries | gwn5d1b | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>/uj hes kinda right though, if you only ever use the core commands youll never have a problem. The only time people get themselves into a mess is when they try to be clever and use and advanced command they dont understand. This is why git GUIs are harmful.<|eor|><|sor|>Hey, not sure if you noticed, but it seems you accidentally wrote /uj at the start of your comment.<|eor|><|eols|><|endoftext|> | 59 |
programmingcirclejerk | DuBistKomisch | gwncrzd | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>based<|eor|><|sor|>rebased<|eor|><|eols|><|endoftext|> | 46 |
programmingcirclejerk | camelCaseIsWebScale | gwmquto | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>Bro u/rohitkg98 it's an xkcd knockoff meme.<|eor|><|eols|><|endoftext|> | 40 |
programmingcirclejerk | TwoCoresOneThread | gwms8cv | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>Noooo you can't just not understand git
Haha files go plop plop<|eor|><|eols|><|endoftext|> | 31 |
programmingcirclejerk | ranqus | gwmz6az | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>When a joke described your standard procedure.<|eor|><|eols|><|endoftext|> | 27 |
programmingcirclejerk | staybythebay | gwo0fa7 | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>You may not like it but this is what peak workflow looks like<|eor|><|eols|><|endoftext|> | 21 |
programmingcirclejerk | coolreader18 | gwoenrb | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|> <|eor|><|eols|><|endoftext|> | 21 |
programmingcirclejerk | CodyCigar96o | gwn6t2y | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>/uj hes kinda right though, if you only ever use the core commands youll never have a problem. The only time people get themselves into a mess is when they try to be clever and use and advanced command they dont understand. This is why git GUIs are harmful.<|eor|><|sor|>Hey, not sure if you noticed, but it seems you accidentally wrote /uj at the start of your comment.<|eor|><|sor|>I have to first unjerk in order to implicit rejerk.<|eor|><|eols|><|endoftext|> | 18 |
programmingcirclejerk | CodyCigar96o | gwn2koe | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>/uj hes kinda right though, if you only ever use the core commands youll never have a problem. The only time people get themselves into a mess is when they try to be clever and use and advanced command they dont understand. This is why git GUIs are harmful.<|eor|><|eols|><|endoftext|> | 16 |
programmingcirclejerk | JanewaDidNuthinWrong | gwnighj | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>/uj hes kinda right though, if you only ever use the core commands youll never have a problem. The only time people get themselves into a mess is when they try to be clever and use and advanced command they dont understand. This is why git GUIs are harmful.<|eor|><|sor|>Hey, not sure if you noticed, but it seems you accidentally wrote /uj at the start of your comment.<|eor|><|sor|>I have to first unjerk in order to implicit rejerk.<|eor|><|sor|>"Explicit is better than implicit"<|eor|><|eols|><|endoftext|> | 14 |
programmingcirclejerk | bruce3434 | gwmydl5 | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>based<|eor|><|eols|><|endoftext|> | 11 |
programmingcirclejerk | republitard_2 | gwq4nt8 | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>based<|eor|><|sor|>rebased<|eor|><|sor|>> `merge conflict`
Uh-oh. Time to buy a new computer.<|eor|><|eols|><|endoftext|> | 8 |
programmingcirclejerk | JanewaDidNuthinWrong | gwns38z | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>/uj hes kinda right though, if you only ever use the core commands youll never have a problem. The only time people get themselves into a mess is when they try to be clever and use and advanced command they dont understand. This is why git GUIs are harmful.<|eor|><|sor|>Hey, not sure if you noticed, but it seems you accidentally wrote /uj at the start of your comment.<|eor|><|sor|>I have to first unjerk in order to implicit rejerk.<|eor|><|sor|>"Explicit is better than implicit"<|eor|><|sor|>Code yes, irony no.<|eor|><|sor|>That's if you aren't coding ironically.<|eor|><|eols|><|endoftext|> | 8 |
programmingcirclejerk | BufferUnderpants | gwp8fxg | <|sols|><|sot|>I use Git from the App, it let's push, pull and commit. If git says anything else than OK, I rm -rf the directory and start again.<|eot|><|sol|>https://twitter.com/j_v_66/status/1387729342550130690?s=19<|eol|><|sor|>/uj hes kinda right though, if you only ever use the core commands youll never have a problem. The only time people get themselves into a mess is when they try to be clever and use and advanced command they dont understand. This is why git GUIs are harmful.<|eor|><|sor|>Ive never used cherry-pick and Ive never missed it
`@UnJerk`
Ive never used cherry-pick and Ive never missed it<|eor|><|eols|><|endoftext|> | 6 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.