Please don't project your own opinions onto the rest of the UK.
456 karma · joined May 6, 2011
Please don't project your own opinions onto the rest of the UK.
Ok so that makes a lot more sense. Thanks for the explanation.
> Barbells also allow you to start with smaller weights at the beginning of the workout, and then move on to heavier sets when you're warm. AFAIK there's no way to do this with climbing.
So with climbing in general climbing harder problems (smaller holds, further apart, more overhang, etc etc) works muscles more, and the harder you climb, the fitter and stronger you will be.
To take two examples (these two because I am intimately familiar with them): Why should someone stop climbing or doing martial arts and start lifting barbells (by stop I mean assume said person doesn't have enough time to do both and must choose one or the other)? Both of the former seem (to me at least) really good for developing strength and, AFAICT do so in a much more realistic and natural way than lifting barbells.
It seems (to me at least) that some exercise is better than no exercise, and that more exercise (at least to an extent) is better than less exercise. It seems to me therefore, that people should find an exercise that they really enjoy (whether running, cycling, strength training, climbing, martial arts, etc) and do it. That way, they'll be doing something they enjoy and they'll do more of it.
It seems slightly disingenuous for "experts" to recommend that everyone drop everything else and just do one type of exercise as if everyone they're speaking to is exactly the same, has exactly the same goals and enjoys exactly the same stuff.
Are they targeting geeks/the HN crowd because geeks tend to favour the idea that there is one "right way" of doing something and are more likely to latch on to it?
You're right: a watch != a HUD. However, in the current iteration, people would be using a watch for pretty much the same purpose as Glass (which can't really do full on augmented reality either) so, despite their differences, they would definitely be in direct competition with each other.
Because, while it's a perfectly valid argument to make, technically winning an argument is different to actually winning an argument.
If most people don't know what a logical fallacy is, then you may as well be referring to the argument from magic pixies and fairy dust fallacy: they won't care or understand what you're saying. At worst, they'll assume you have an unwelcome air superiority about you and they'll start to ignore everything else you say as well.
The sad fact is that people listen to emotions because they can relate to them and, however invalid such an argument is, it's often the argument that wins.
For many people, having something that's pretty easy to use and lets them communicate with people that they already know is a really great thing.
Email really isn't designed as a social discovery tool. There are many other technologies (some of them built on top of email like mailing lists) that _are_ designed for those purposes, and several of them work perfectly well.
If what you're expecting is one tool that both fits and performs well at all possible use cases, then you're going to be severely disappointed.
The original comment you're replying to aside, it was likely because stating that you dismissed the entire comment without giving an actual objection to it added nothing at all to the discussion.
At the moment, Photoshop is difficult to use, but has thousands of features (I have no idea exactly how many) that presumably professionals make use of, at least to some degree or another.
Try making a modeless version of Photoshop like you describe and most people would have to look up the key combination before doing anything, at least until they've learned all the modifier keys (which sounds remarkably like emacs). Not exactly the paragon of usability.
As with almost everything, UI is a tradeoff between several different factors. In the case of modes, the applications that people like them in tend to be used by professionals or experts for a very specific purpose. In such a case, the utility, power and expressiveness is much more important than the initial ease of use.
If your aim is to create something that doesn't have thousands of features and should be usability immediately (or relatively so) by new users, then modes are likely a bad idea; if your aim is to create something powerful for experts who will be using it 8 hours a day for the next 5 years, modes may be worth considering.
The biggest issue that I found by far was communication. Especially in the Silicon Valley based companies that were looking to hire in London at the time. Communication times of a few weeks seemed fairly commonplace (with contact still extremely positive after such a long wait). One company (I suspect the same as the non-profit mentioned in TFA) took more than a month to get to my second interview, during which time one interview was cancelled about an hour before it was due, and one interviewer simply failed to turn up with no explanation.
My limited experience is obviously no indicator of any wider issue, but if that's generally how companies interview, then I'm really not surprised at all that they find it difficult to hire talent.
For a HN crowd interested in learning more about the domain, a blog post or something actually talking about it would be more appropriate and something that people can actually learn from.
A demo isn't something that people generally learn from. It's something that people look at, notice how pretty it is, and then move on, learning nothing.
You asked for an opinion. I gave you one (I'm in the middle of a large Ember project at the moment). I didn't expand on it as you appeared to have already made up your mind and written the whole thing off on the basis that the Java world keeps you pretty happy already.
> It adds no value over anything that we already use or what I see being used elsewhere. It's just another library that doesn't add any significant.
It sounds like you know a lot about it already. Why bother asking if it's worth learning then?
It's not a radical approach sure (that's the main point in fact). The main difference with Java is that Ember all happens inside the browser, and you write it in JavaScript. I have no idea how much experience you have with those things, so have no idea how much you'd learn if you picked it up.
In no way did I imply that you were stuck in Java rut. I said that if you were, you might learn something; if not, you might not. The things you'd learn about (unless you already know a lot about them already of course) involve things that you'd learn doing any front end development.
In no way should you feel bad for wanting to make a lot of money.
> Is Ember.js actually worth learning?
Yes.
> Will it make me a better programmer (like learning Haskell will)?
That depends on whether you've learnt the concepts that Ember introduces before or not. If you're stuck in a Java shaped rut, then yes. It will make you a better programmer.
> Will it enable me to get a pay rise from my current £480 per day contracting fees?
That depends whether you find someone who wants an Ember app that is willing to pay more than £480 per day. If you don't bother looking, then you're unlikely to find it. That said, if money is what you're after, there are many better avenues to go down than learning Ember or doing Java contracting.
> Is there a more diverse and active job market than there is around my current main language (Java)?
JavaScript is growing in popularity very quickly. If you wanted to switch to it from Java you wouldn't have any problems finding an interesting job.
> So the idea is that Ember may serve to fix one particular problem in my company... I don't see how it's any better than anything else. Just because I can knock out a basic web app in less time doesn't mean it's worth learning, especially when you add learning time into the development time and compare it to the Java equivalent.
You don't see how it's better because you haven't bothered learning it. By comparing it to the Java equivalent, I assume you mean GWT. In that case, yes. It's much better.
Ember isn't really designed for basic web apps. It's designed for big complicated web apps. I wouldn't recommend Ember for really basic web apps at all - it imposes a lot of structure that you only really see the benefit of when your app becomes larger.
> I wish I was still 22 years old and didn't need to care about earning decent money...
Never wish for something out of the past. It's gone. Look to the future instead.
Especially given Google's own statements saying that pictures/video are the (current) main use case (that they've discovered so far).
If the aim is to bake in syntactic sugar for different constructs within Ember that are awkward in plain CoffeeScript (and there are a few), wouldn't creating a CoffeeScript version of sweet.js[1] not be a better idea (I have no idea if such a thing exists already)?
document.querySelectorAll doesn't even support event listeners or forEach loops. I wouldn't call that extra functionality, I'd call that a basic requirement.
It lets you select elements using CSS selectors. That's good and all but if you want to actually do anything with that you're better off using some sort of library that abstracts the awkwardness away (i.e. jQuery).
That said, the following things irked me:
> Abstraction is more likely to increase speed, because someone smarter than you has written the bit that needs to be fast.
That's a very sweeping statement that doesn't really describe the situation. It obviously depends on what you're doing, who wrote the abstraction and how much is being abstracted.
> First: ignore pretty much anything Facebook has to say about DOM performance. They really have no idea what they are talking about. Sencha was able to make a version of the Facebook mobile app with their framework, and it was FASTER than the official, native app, and Sencha isn’t even particularly fast.
If you create an app that has half the feature set of another app it will likely be easier to make it go fast.
> Second: Stop using DOM libraries out of habit! If your target browser is IE8 or above, jQuery hardly provides any features that aren’t shipped on the host object anyway. document.querySelectorAll will pretty much do everything you need. jQuery is a tool, not a framework. Use it as such.
jQuery provides a clean sensible API. Something that is currently still lacking from the DOM (despite all the improvements). document.querySelectorAll will definitely not do "pretty much everything" you need out of the box.
With Reader, (apart from historical read/unread/starred/etc) this is as simple as downloading an OPML file and uploading it somewhere else.
With Gmail, it's more tricky. Migrating emails is fairly trivial, migrating the address itself though (unless you own the domain) involves updating all your contacts and changing your settings for every site you use on the internet (auto mail forwarding of course makes this easier).
With Notes, I'm not sure there's a standardised format for exporting/importing from one service to another. Certainly, with different features between each product a lot of information would be lost when doing so.
If you're fine with that and/or don't keep really important notes in the service then it's not really an issue. If you want to ensure they stick around as long as possible, then you need to pick a service that is committed, or one that you control yourself.
1) Google kills of Groups in favour of Google+ 2) If not (1), Google limits Groups postings to only those coming from a Google account. 3) Google kills off one or all of Sites, Offers, Finance, Blogger
Of those, I reckon (1) or (2) is the most likely. Groups (despite being really useful) was already out of date when it was launched.
Of course, that's all meaningless speculation like much of the linked article.
The conclusion at the end though (switching to an email account on your own domain), is relatively sensible (even if Google isn't about to close Gmail (hint: they aren't)). Controlling your own email address, if not the provider, reduces lock in and makes it generally a lot easier to switch to someone else in the future if/when something better turns up.
This seems like reasonable advice but I'm not sure it really follows from the heading. DRM in Spotify is reasonable because if they shut down you lose nothing and can move easily to another service (rdio or whatever).
Paying for something that you have no control over is reasonable only if you don't care whether you get to keep it long term (I'd personally put books on Kindle in this category as I'm only ever going to read them once). If you care about access to something long term, then either subscribe to a service that provides it (i.e. you explicitly own nothing (like Netflix and Spotify)), or get it DRM free.
In a roundabout way such concepts also apply to things like Google Reader, which is fairly trivial to migrate to another service vs Email, which (unless you own the domain) isn't.