delsalk

I find it amusing that a application only runnable on OSX needs to drag along node + quite a few deps.

Surely doing that would require them to rewrite the Apache license (thus making it no longer the apache license) otherwise there's no legal way of enforcing the non-commercial use?

Unfortunately scaling becomes useless if you need todo any graphical related work, where you really do need 1:1 (retina) resolution.

This also goes for all of the retina models. Even the 15" has a smaller retina resolution than the non-retina higher-dpi older 15" MacBook Pro.

Apple really needs to get to the "next-generation" retina displays with 25% or more density.

It doesn't look like fantastic Ruby code, you're right. I just wouldn't agree that JS "works well" when it comes to their somewhat afterthought functional iterators.

You would probably get a better deal selling the watch as a watch itself than melting it down for its raw gold.

Apple has let you bring you old devices in to be recycled in the past however; Maybe they could extend this to buy back old watches? People have envisioned some upgrade program, though I'm doubtful Apple would be too concerned with melting down old watches for their gold.

They still have to sell the watch itself with their margins however. There's nothing stopping you from buying an aftermarket strap, and if they require you to purchase a strap with the watch -- well then it doesn't matter how they split the price up.

There seemed to be plenty of people from lots of different parts of the world. If you were actually concerned about diversity maybe you should be looking more than skin deep yourself.

Do you still require the JVM installed in the same way you would the Ruby's VM?

Works well meaning don't use functional calls at all if you want to escape from them.

RE binaries, compilability seems difficult due to how dynamic method calls are, but Rubymotion seems to have solved that to some extent, though it's a shame it requires a subscription to even develop on which doesnt appeal.

What are the "hacky" methods currently used for packaging you mentioned? The only methods I'm aware of no longer work or still require a separate runtime.

Not by itself no, but you can't block tracking beacons and then leave gaping holes in the form of AdSense, so if your motive is tracking then you're not going to see most ads regardless.

I don't think any normal internet user would consider ads in that way, only the lesser of two evils. People "voting with their mice" and choosing to install ad blockers isn't really a ringing endorsement.

While a good step, personally my reasons for blocking ads rests more from a tracking standpoint than visually.

Google being a middleman makes it logistically easy but removes the main reason why I would pay some amount directly to sites themselves.

Based on recent developments with both Google and MS in the past few years, I treat them with the same amount of trepidation.

Probably because HN doesnt want people accidentally linking to Google's tracking search results by accident, although HN should really wrap paywalled articles by default, or at least have a policy on what is allowed. Im sure more than 90% cant actually see anything without messing around with referral links.

>I occasionally wanted to watch Youtube videos that were Flash only

Are there any examples of flash only video? I used to use a 3rd party extension that would show videos in html5 and i never came accross any video that required me to load it in flash. I'm curious how Youtube tries to deliver those videos now.

Its quite embarrassing how badly Atom performs, how many subprocesses it opens and how much memory it will happily leak during the X hours its in use. I really wouldn't consider using anything NW/node-webkit or the like for all but the most trivial of applications.

There are definitely ways to incorporate Javascript into "native" programming. In Yosemite you can write Javascript that directly loads and calls native frameworks (like you can with Python/ Ruby). If you wanted you could write an entire application in Javascript, but taking shortcuts and trying to use HTML and the DOM for your interface only leads to these sorts of severe issues when doing anything nontrivial.

Agree, I am impressed with how Textmate development has been going since it was opensourced, but my point really was that OS issues, bugs and incompatibilities can quickly add up over the course of a year or two, without any active development. The advantage of something like VIM or emacs is that they're first and foremost terminal based, and are shielded from a lot of these issues.

Lets also not forget that Sublime text isnt free, and i am sure paying users dont really want to be left in the dark for 6 months to a year.

Especially since it seems to have been abandoned for a while now according to their website. The last beta build was 5 months ago, and the one before that over a year. (Obviously your editor doesn't need to be updated regularly, but it seems to be history repeating itself a la Textmate.)

Reading your first two links makes it seem like you get both, given that your statutory rights aren't affected by Apple's own warranty, so for the coverage for the first or 3 years you can get anything solved via AppleCare, and for the remaining 2 or 3 you'd be making the claim to Apple (if you bought it via their stores or their website) as part of your statutory rights.

I wonder how that applies when you purchase something from an Apple Store, since that means they're both.

I remember seeing a page on the Apple website listing info for extended warranties in EU member countries, which I assume this specific defect in the 2011 Macbooks is covered by.

Is that part of the EU wide protection places like the UK, Germany, etc also get or something specific to your country?