Otherwise we're throwing away other people's posts, which I don't like to do.
throwing away other people's posts, which I don't like to do.
throwing away other people's posts, which I don't like
Otherwise we're throwing away other people's posts, which I don't like to do.
throwing away other people's posts, which I don't like to do.
throwing away other people's posts, which I don't like
I'm here too. Although sporadically. And I'm well aware of the other thread. And somewhat surprised to be alive and kicking on meta...
I'd have expected one of the tdcktd people to jump in an say something along the lines of them using Discourse for tracking all bugs and how awesome that was working out, to which I had a couple of polite but interesting replies, but no cigar.
It turns out that how you treat your community somehow affects what kind of contributions you can expect back from that community?
$COMPANY runs a lint rule that requires that exported identifiers are commented. Go standard for comments is that they begin with the identifier name. So we get stuff like
// AddWidget ...
func AddWidget(w Widget) {
...
}
// FrobbleBananas ...
func FrobbleBananas(n int) {
...
}
Yes, literal function-name dot dot dot as documentation for each function. To satisfy the rules.
This is so fucking sad. "Unprofessional" doesn't even scratch the surface. And even just lurking on meta.d is seriously frustrating. I mean just look at this. "Seems correct to me".
OK!
jb@syno:~/tmp $ npm install is-positive-integer
is-positive-integer@1.0.0 node_modules/is-positive-integer
├── is-positive@3.1.0
├── is-integer@1.0.6 (is-finite@1.0.1)
└── 101@1.5.0 (clone@1.0.2, keypather@1.10.2, deep-eql@0.1.3)
Right on. Lets see how tested this is.
jb@syno:~/tmp $ find node_modules -name test
node_modules/is-positive-integer/node_modules/101/node_modules/keypather/test
node_modules/is-positive-integer/test
jb@syno:~/tmp $ npm list
/Users/jb/tmp
└─┬ is-positive-integer@1.0.0
├─┬ 101@1.5.0
│ ├── clone@1.0.2
│ ├─┬ deep-eql@0.1.3
│ │ └── type-detect@0.1.1
│ └── keypather@1.10.2
├─┬ is-integer@1.0.6
│ └─┬ is-finite@1.0.1
│ └── number-is-nan@1.0.0
└── is-positive@3.1.0
Eh... Not so much? Huh. How much code is it, anyway?
jb@syno:~/tmp $ cloc node_modules --exclude-dir test
102 text files.
100 unique files.
30 files ignored.
http://cloc.sourceforge.net v 1.64 T=0.27 s (282.0 files/s, 13966.0 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Javascript 59 325 715 1750
JSON 10 0 0 731
HTML 2 15 0 155
YAML 4 2 0 21
-------------------------------------------------------------------------------
SUM: 75 342 715 2657
-------------------------------------------------------------------------------
Ah, 1750 lines, most of which without any tests? I think I'll go with @RaceProUK's approach here.
Funny stuff... I just "earned" the "tester" badge for apparently doing such awesome QA for the team. These are the current holders:
There seems to be a higher than average number of suspended (and anonymized...) users in this group... Very odd.
Serving static images is too complicated. I give up.
https://meta.discourse.org/t/optimizing-letter-avatar-rendering/33082/53
So this was just posted:
Why's that the headline feature? Nobody uses it, right?
That email thing is beautiful. There's three places where a moderator (not admin) can get a user's email address:
I mean I'm sort of used to some things not making total sense here, but this is something of a even for my quite Discourse-hardened mind...
$COMPANY runs a lint rule that requires that exported identifiers are commented. Go standard for comments is that they begin with the identifier name. So we get stuff like
// AddWidget ...
func AddWidget(w Widget) {
...
}
// FrobbleBananas ...
func FrobbleBananas(n int) {
...
}
Yes, literal function-name dot dot dot as documentation for each function. To satisfy the rules.
I'm here too. Although sporadically. And I'm well aware of the other thread. And somewhat surprised to be alive and kicking on meta...
I'd have expected one of the tdcktd people to jump in an say something along the lines of them using Discourse for tracking all bugs and how awesome that was working out, to which I had a couple of polite but interesting replies, but no cigar.
@kt_ said in More Windows 10 auto-update auto-reboot nonsense:
So is your sole argument for annoying auto updates "some people are too stupid?"
It's a fairly compelling argument.
Not to mention that anyone who thinks using a size_t for a boolean is perfectly fine because it can represent "the range of a bool value" is a fucking idiot. In code that's supposed to be security focused, no less.
@dkf Well... I'm on a high DPI display, but the images sent are 360x360 and rendered at 46x46 which is a tad higher multiplication factor than my display has.
Uh, on that note, wtf is it sending the full sized images as avatars? Would it not make sense to send scaled down versions more suited to how they're going to be displayed?
@Yamikuronue Yeah there are a few more tests than my find shows up. The whole thing is still a fucking farce though.
OK!
jb@syno:~/tmp $ npm install is-positive-integer
is-positive-integer@1.0.0 node_modules/is-positive-integer
├── is-positive@3.1.0
├── is-integer@1.0.6 (is-finite@1.0.1)
└── 101@1.5.0 (clone@1.0.2, keypather@1.10.2, deep-eql@0.1.3)
Right on. Lets see how tested this is.
jb@syno:~/tmp $ find node_modules -name test
node_modules/is-positive-integer/node_modules/101/node_modules/keypather/test
node_modules/is-positive-integer/test
jb@syno:~/tmp $ npm list
/Users/jb/tmp
└─┬ is-positive-integer@1.0.0
├─┬ 101@1.5.0
│ ├── clone@1.0.2
│ ├─┬ deep-eql@0.1.3
│ │ └── type-detect@0.1.1
│ └── keypather@1.10.2
├─┬ is-integer@1.0.6
│ └─┬ is-finite@1.0.1
│ └── number-is-nan@1.0.0
└── is-positive@3.1.0
Eh... Not so much? Huh. How much code is it, anyway?
jb@syno:~/tmp $ cloc node_modules --exclude-dir test
102 text files.
100 unique files.
30 files ignored.
http://cloc.sourceforge.net v 1.64 T=0.27 s (282.0 files/s, 13966.0 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Javascript 59 325 715 1750
JSON 10 0 0 731
HTML 2 15 0 155
YAML 4 2 0 21
-------------------------------------------------------------------------------
SUM: 75 342 715 2657
-------------------------------------------------------------------------------
Ah, 1750 lines, most of which without any tests? I think I'll go with @RaceProUK's approach here.