allover

9 ms·

31.
by allover 7y ago
Tbf Microsoft have won back a lot of good faith with developers due to projects like VS Code and TypeScript, even for those of us who remember their past. And we're yet to hear of any negative impact of their Github acquisition (afaik
32.
by allover 7y ago
> "matchers" [...] let you test values in different ways Example docs for Jest's matchers: https://jestjs.io/docs/en/using-matchers Generally speaking, if you use a specific matcher, you get a be
33.
by allover 7y ago
Because in the grand-scheme of things, the countries that have banned guns don't have the problems you have. Crazy, I know.
34.
by allover 7y ago
I think you're missing that Europeans also recognise that giving every dumbass, desperate person or dormant psychopath a gun, is far more likely to get people killed NOW, than the chances that when the 'end-times' you imply c
35.
by allover 7y ago
More reasonable than the anti gun control people, but it's still an insane solution to the problem, in the grand scheme of things.
36.
by allover 7y ago
Um, why not both. The rest of the world doesn't have the school shooter problem. It's fixable, and the fix is bleedingly obvious. There's no excuse.
37.
by allover 7y ago
He said the drills are misguided though right? Not that the US obsession with guns and lax gun control that enables school shootings is defensible.
38.
by allover 7y ago
Deaths of children. At school. For literally nothing. They are _avoidable_, that's why they are not overstated.
39.
by allover 7y ago
You're _honestly_ saying that fears over school shootings in the US are overblown because it makes for good news?
40.
by allover 7y ago
I don't think there's any need to sealion the author on this. To your first question: JS's warts are well understood. You must already acknowledge this if you're a TS fan. To your second: TS isn't 'actually&#x2
41.
by allover 7y ago
Not sure if the HN thread or my comment has thrown you, but I'm replying to 'kazinator'. I know he's not defending it. What I said is that he (kazinator) is inadvertently attacking somebody that's also not defen
42.
by allover 7y ago
I agree, things shouldn't be this bad. But unless you're going to take this up with Linus, you're just yelling at your fellow disappointed spectators.
43.
by allover 7y ago
You are now ignoring the fact that in the initial quote you objected to was the intentionally tongue-in-cheek: > 'For a Git user interface this is relatively straightforward and concise'. It kinda looks like you missed the jo
44.
by allover 7y ago
> when they migrate from monolith to microservice: development is easier [...] Not even that -- that idea is still highly debatable. I would argue that it absolutely isn't easier, and the stepping-back-in-time of developer experienc
45.
by allover 7y ago
> Such an implementation would be GDPR compliant in not tracking any personal data, although your counsel might still say you need to list them as “analytics” cookies in a cookie banner (mine did). Your council should also have advised
46.
by allover 7y ago
As someone going through this right now, the main difficulty in being GDPR compliant with GA is the cookie problem. You can either disable cookies to run GA in cookieless mode [1], which presumably will affect how GA performs, since they ca
47.
by allover 7y ago
I never cease to wonder if articles like this are incredibly cleverly put together, or incredibly stupid. I feel like it would take me so much effort to string together these unrelated things and try to present them in a faux-scientific man
48.
by allover 7y ago
You will see it defended a lot on Hacker News, due to the disproportionate level of PL enthusiasts, and the Paul Graham thing. But yes, you're right that in reality, lisps have incredibly limited popularity. (You've met one more f
49.
by allover 7y ago
What is your bar for 'average users'? If we're talking project-wide repos rather than entire-org repos, I'd wager the vast majority of projects can use monorepos without special git tooling, and will retain huge producti
50.
by allover 7y ago
> Sure, if a package absolutely needs exact dependencies for its entire tree Not sure you're talking about the same thing as everyone else. There's a big difference if you're maintaining a package vs maintaining an app.
51.
by allover 7y ago
> But package lock is ignored for all users of your npm. Only root package’s lock file has effect. This makes it useless in most cases. But package-lock is intended to be used at the project level. i.e. lock all package versions in the
52.
by allover 7y ago
> Code smells if a change works with one lockfile but not another generated around the same time. This isn't true at all. You can't predict when a new, potentially breaking, version of a dependency might get published. It could
53.
by allover 7y ago
> I don't really. If you only wanted to control your first-level dependencies They didn't say "only", they said "things like".
54.
by allover 7y ago
But a lockfile is not like "any generated file", because for typical generated artifacts they should always be generated the same, for the same commit. This is not true for a lockfile, where the whole point is to capture the speci
55.
by allover 7y ago
> No, I think you mean "Yes, but also ..."
56.
by allover 7y ago
I never said people would "choose" TS because it's in its heyday, I said it'd be an unlikely time for most to wish to justify a switch back.
57.
by allover 7y ago
TypeScript is kind of in its heyday though, it's fairly unlikely many teams would be comfortable making a bold decision to "switch back to JS", even if they want to. Would need to be given more time for such a statistic to be
58.
by allover 7y ago
> Syntax, yeah, whatever. The vast majority of the programming world simply doesn't seem to agree.
59.
by allover 7y ago
> "you don't know what you're missing". I think I do. I've had the argument many times here, code-as-data, metaprogramming, structured-programming. Things I don't want, aren't worth the trade-off, and t
60.
by allover 7y ago
> were it not for my using an Open Source solution [...], it would be impossible for me to hook up [...] and other devices to Homekit without a bunch of different gateways (because some Zigbee endpoints simply refuse to talk to anything

More ›