jonpacker

Joined 15 years ago

Karma

78

Submissions

28

Member since

Dec 14

View on Hacker News

Recent submissions

Comment · 6 months ago

For a start, you can't edit docs on mobile. But if you just use it for a while you notice there's a fairly large amount of bugs which need working on. Try entering a couple of dates and using their autofill to extend the sequence... it's pretty comical.

Comment · 3 years ago

Try the "Recursive Mono" or "PT Mono" variants of Iosevka.

Comment · 3 years ago

You can actually use the bottom of a ceramic mug as a whetstone to sharpen knives if you're dedicated enough!

Comment · 12 years ago

Minke whales are not in any way endangered (or close to it). Check your facts. https://en.wikipedia.org/wiki/Minke_whale

Comment · 12 years ago

So you would suggest using external text files to store every SQL/Cypher query that is used in a model-based node app?

Comment · 12 years ago

I use Browserify with Coffeescript modules, and the source maps work great. I'm using Coffeeify to do it: https://github.com/jnordberg/coffeeify

Comment · 12 years ago

Chrome on iOS is Safari in a box.

Comment · 12 years ago

I respect where you're coming from, but I disagree. One of the huge advantages of npm for me is that it's so transparent and I can see exactly how it's mapping to the file system. I know exactly which code is being run, from where—because it's incredibly easy to traverse the dependency tree. If you abstract away the fs level and flatten the dependencies into a single folder, you take this away, and you make the dependency tree essentially a big intimidating blob of code that requires slogging through package lists to determine what is actually being used.

Comment · 12 years ago

I disagree. I think node's approach is easily understandable, and quite robust. It's incredibly easy to dive down the dependency chain and see every package, and know exactly which one is being used where. Not something that can be said about package managers that use the flattened approach.

Comment · 12 years ago

I'm slightly confused by your wording but I think the functionality you're referring to is already available via Object.defineProperty's "get" and "set" options: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

Comment · 12 years ago

You can set a custom getters and setters, but I wouldn't call it operator overloading. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

So...

    > var x = {}
    > Object.defineProperty(x, 'value', { get: function() { return 1 }, set: function() { console.log('set') } })
    > x.value
    1
    > x.value = 2
    set
    > x.value
    1

Comment · 12 years ago

Well, to be fair, make and browserify do completely different jobs. You can't substitute browserify for make, nor vice versa.

But to be honest, if you see learning new things as wasting your attention on new fads, I don't think this stuff is for you. I really like trying new things that people have made and seeing what they can do. If that feels like a chore/hardship to you, you absolutely should just keep using make.

Comment · 12 years ago

Well, source maps are usually the solution for me. And yes, browserify supports source-mapping all the way back to coffeescript files using browserify-middleware. In the off case that I need to debug something in a browser that doesn't support source maps, you can turn minifying off and usually it is pretty easy to recognise the code you're inspecting, even if it comes from coffeescript. I've never had a case where I've been completely out of luck (usually this case only happens in IE).

Comment · 13 years ago

"The Other Half" on Jolla has a serial port which makes it possible for it to be a keyboard or a battery or an external device.

Comment · 14 years ago

They did not say anywhere that the 25% speed gain was the reason they did it...