612 karma · joined December 10, 2010
I just wanted to check something on the internet and now is when you decide to stop and delay the user?
Edit: I'll explain. Cutting the middleman is the big idea though band camp isn't enough for that. The big labels have very strong marketing capabilities that individual acts can't compete with. Even YouTube, the land of indie, is dominated by the large labels. So maybe bandcamp needs a breakthrough marketing/distribution/discovery platform that can somehow be more meritocratic.
The problem is you get bad first-page load times (double-latency), but you get better second-page load times (no waiting for templates, just data requests).
This list was purely an opinion piece. It was the result of a subjective appraisal of both books, and the public opinion of them.
I'm quite disappointed.
I guess my eye has been trained to skip those.
Errors should never pass silently
Unless explicitly silenced
The problem with go is that you have 3 error modes:1. Explicitly handle everything
2. Implicitly silence sometimes
3. Panic/recover explodes sometimes (who knows where/when?)
Mode #2 is dangerous.
Java/Python give you 2 only modes:
1. Implicitly explode on error.
2. Explicitly silence sometimes.
Where both modes aren't inherently dangerous, i.e. they won't directly cause undefined states to execute.
--------------------
Concerning the nesting in my examples - I'm used to the style of C programming where failing is mostly handled by a return as to keep the program as readable (and thus flat) as possible. So pardon my french but I assumed "// do something" would somehow prevent further usage of 'f'.
Note that the Go example, although tedious, isn't bad in cases where you really do need to check every single possible error.
But in order to live in peace you have to either:
* Force every programmer to always check all the error values.
or
* Allow errors to pass silently.
So either you accept Go as a heavy-duty, heavy boilerplate error handling laden language. Or you accept it as a flaky, risky language.
Exceptions are the better compromise in my opinion. You get much cleaner code.
If this is the more common pattern for your programming life:
try:
f = float(someText)
use_it_here(f)
use_it_there(f)
catch Exception:
# I wanted to do things, but something went wrong.
# Here's what to do now, this is easy
Then you're better off using exceptions. If you need to check every single call (e.g. NASA or Kernel programming) then you might prefer this: if f, err := strconv.ParseFloat(text); err != nil {
// do something
}
if f, err := use_it_here(text); err != nil {
// do something
}
if f, err := use_it_there(text); err != nil {
// do something
}I believe I'm correct as no one has yet refuted the central problem discussed. The replies have mainly been justifying it.
Why on earth would they go 144x80 pixels shy of 720p, 1280x720?
Hasn't the world suffered enough from transcoding? So the eye sees your perfect DPI, but the pixels are going to be imperfect because it's a random down-sample size that doesn't divide anything standard.
I don't get it.
Might be related to the topic at hand.
Pretty damn revolutionary.
E.g. http://sourceforge.net/projects/malclassifier.adobe/files/Ad...
I daydream of a programming language to which I can fuzzily explain my needs and it automagically solves problem. Natural language processing might be hard to debug as part of a programming language though.
I'd love to further express my opinion on the subject, this just isn't the place for it. No matter how hard you spin it.
javascript:$('#mw-page-base, #mw-head-base, #content, #mw-head, #mw-panel, #footer').show();$('#mw-sopaOverlay').hide()
javascript:$('#mw-page-base, #mw-head-base, #content, #mw-head, #mw-panel, #footer').show();$('#mw-sopaOverlay').hide()
Built thanks to this wonderful analysis by tantalor.
Rank, Country, EF EPI Score, Level
1 Norway 69.09 Very High Proficiency
2 Netherlands 67.93 Very High Proficiency
3 Denmark 66.58 Very High Proficiency
4 Sweden 66.26 Very High Proficiency
5 Finland 61.25 Very High Proficiency
6 Austria 58.58 High Proficiency
7 Belgium 57.23 High Proficiency
8 Germany 56.64 High Proficiency
9 Malaysia 55.54 High Proficiency
10 Poland 54.62 Moderate Proficiency
11 Switzerland 54.60 Moderate Proficiency
12 Hong Kong 54.44 Moderate Proficiency
13 South Korea 54.19 Moderate Proficiency
14 Japan 54.17 Moderate Proficiency
15 Portugal 53.62 Moderate Proficiency
16 Argentina 53.49 Moderate Proficiency
17 France 53.16 Moderate Proficiency
18 Mexico 51.48 Moderate Proficiency
19 Czech Republic 51.31 Moderate Proficiency
20 Hungary 50.80 Moderate Proficiency
21 Slovakia 50.64 Moderate Proficiency
22 Costa Rica 49.15 Low Proficiency
23 Italy 49.05 Low Proficiency
24 Spain 49.01 Low Proficiency
25 Taiwan 48.93 Low Proficiency
26 Saudi Arabia 48.05 Low Proficiency
27 Guatemala 47.80 Low Proficiency
28 El Salvador 47.65 Low Proficiency
29 China 47.62 Low Proficiency
30 India 47.35 Low Proficiency
31 Brazil 47.27 Low Proficiency
32 Russia 45.79 Low Proficiency
33 Dominican Republic 44.91 Very Low Proficiency
34 Indonesia 44.78 Very Low Proficiency
35 Peru 44.71 Very Low Proficiency
36 Chile 44.63 Very Low Proficiency
37 Ecuador 44.54 Very Low Proficiency
38 Venezuela 44.43 Very Low Proficiency
39 Vietnam 44.32 Very Low Proficiency
40 Panama 43.62 Very Low Proficiency
41 Colombia 42.77 Very Low Proficiency
42 Thailand 39.41 Very Low Proficiency
43 Turkey 37.66 Very Low Proficiency
44 Kazakhstan 31.74 Very Low Proficiency