jkrems

11 ms·

61.
by jkrems 7y ago
Well, all of Google's shareholders are banding together against thousands of individual workers. We don't penalize them banding together. We just call it "a company". Why is it any different when some of the workers band
62.
by jkrems 7y ago
Entertainment unions handle such things like health insurance and retirement funds. Most actors aren't millionaires. Having the few millionaires in the same union is good for the non-millionaires. Because it means that studios only get
63.
by jkrems 7y ago
From somebody who used CoffeeScript extensively: I don't think it's a great choice for bigger production projects. The less "noisy" syntax has some very unfortunate consequences. For one, it has zero error correction. Al
64.
by jkrems 7y ago
Argument in the past: Because the best alternative is a complete audit of all past commits for IP issues, trade secrets, keys, network internals, ... It's just much easier to remove that hurdle from the process and only look at the cur
65.
by jkrems 7y ago
It isn't discrimination to treat people differently. By this logic you shouldn't have handicap parking spaces because that discriminates against people that can't use them. Making people pay the same amount of money for the s
66.
by jkrems 8y ago
Because you will be talking to other people, including the ones you have worked with and built a relationship with inside of the company. And the company has an interest in being seen as a viable place to work for others. So making sure tha
67.
by jkrems 8y ago
First: none of the exact rules are written yet. But current discussions seem to suggest "Yes, this will go away" for "./services" being resolved to anything but an absolute location ending in "/services&qu
68.
by jkrems 8y ago
But that would mean that every single webserver would have to implement that logic. Consistently.
69.
by jkrems 8y ago
> This is exactly how browsers do it, by the way. If you `import` something, is a module, period. The `<script>` tag is the only place that supports both, so they use a `module="true"` flag to indicate which is which. Thi
70.
by jkrems 8y ago
The discussion seems to be mostly driven by people who are used to a very specific syntax and can't understand why it wouldn't work for a real implementation for private. Nothing will stop these people from keeping their use of &q
71.
by jkrems 8y ago
Yes, and the result is people using old software on those old OS versions which... well, have blatant security issues. Apple shipping minimal security fixes to old OS versions has ripple effects that are really unfortunate and expecting eve
72.
by jkrems 8y ago
Yeah, but that's a really dangerous position to take and if they'd work with me I'd be quick to set them straight. Because that path leads to legal adventure. What you are describing is "source available", not &quot
73.
by jkrems 8y ago
Downvoted because this comment seems fairly OT. The post this responds to was clearly not actually making a literal statement about how all parents in the history of humanity bonded with their children. It was a criticism of the methodology
74.
by jkrems 8y ago
While those are true in some cases, in others layers slow down the build process and increase the total download size. It really depends on what is being built and how it is distributed if layers have an advantage, make no difference, or ar
75.
by jkrems 9y ago
Last I've heard no JS engine ships or wants to ship PTC. So I'd be surprised if V8 breaks away from the pack there, given that nothing changed.
76.
by jkrems 9y ago
But that question doesn't make sense. It contains the assumption that the alternative would be to never ship broken features to users. While the actual alternative would be that they'd ship the same broken feature to all users
77.
by jkrems 9y ago
I'd rather say: It's like the default set if knife/fork/spoon set out at the table. They might be taken away or replaced based on what you actually end up ordering. But for the most part they will work out.
78.
by jkrems 9y ago
Not sure which spec the article is referring to but it's not the one implemented by V8 natively. > The problem is that Promises have to be resolved in the next turn of the event loop. This is part of the spec. That statement is fals
79.
by jkrems 9y ago
> The fact that promises must be resolved in the next tick is baked into the spec From all I know, that statement is false. Promises aren't resolved in the next tick. They should be resolved as part of the microtask queue which ca
80.
by jkrems 9y ago
The article is about how C & Fortran ("traditional languages" by 1997 standards) compare to C++. This is not about functional- but procedural languages vs. OO. (!)
81.
by jkrems 9y ago
Downvoting this comment because: 1. Afaik every single OO language allows this. I wouldn't know of prior art for the opposite behavior (only allowing access to the same object). 2. TypeScript works under different constraints and - for
82.
by jkrems 9y ago
The value linters should (hopefully) provide is to keep code reviews focussed on actually important things instead of having to renegotiate naming, spacing, and other "arbitrary" things. Also, a decent linter for JavaScript will d
83.
by jkrems 9y ago
Yep, the same commands should still work. There's some additional commands now for CPU/memory profiles. But that's the biggest difference - hopefully.
84.
by jkrems 9y ago
Disclaimer: Author of `node-inspect` No, `node inspect` is the new command line debugger for `node --inspect` which replaces `node debug` for `node --debug`. The name is derived from `node --inspect` and has no relation to `node-inspector
85.
by jkrems 10y ago
Did you know about Moom? https://itunes.apple.com/us/app/moom/id419330170?mt=12
86.
by jkrems 10y ago
Read access to public repos just doesn't have to be granted - period. That's why there's no scope for it. The tool could just have excluded private repos.
87.
by jkrems 10y ago
You could just imperatively instrument the component, e.g.: class MyComponent extends React.Component { /* ... */ } debugReasonForRendering(MyComponent); Where `debugReasonForRendering` patches `arguments[0].prototype
88.
by jkrems 10y ago
There's was very vocal backlash from some developers. Most professional developers I talked to are perfectly fine with the changes. They just weren't interested in taking part in the online drama. Maybe they were slightly anno
89.
by jkrems 10y ago
Wonder why they didn't go with Cmd+C/Cmd+V for copy&paste. As a developer, that's one of the reasons I really enjoy working on macOS. There's no chance to confuse Ctrl+C and Cmd+C - both of which are shortcuts I use
90.
by jkrems 10y ago
Since the article doesn't even mention that the escape functionality is still there (although it's no longer a physical key but a touch button), I'm going to assume that its only source is jokes on twitter.

More ›