jhrobert

Great.

Based on that, what would be even more useful still is a way to browse my code from a within the editor itself. Something with say line numbers on some left pane synchronized with the corresponding file section on the right pane.

Some editors already provide a similar feature using line numbers from compilers ; that's usefull to fix syntax errors typically.

I just spent a couple of hours reading the Dart site.

Dart is a web friendly optimized SmallTalk with a Javascript like syntax.

It looks like Javascript but feels like SmallTalk.

If that marketing trick works, it will be ironic because Scheme inspired Javascript looked like Java for the same marketing reason...

CoffeeScript might be Javascript's swan song.

I'm getting bored with Javascript.

I had a look at Julia and as a result I think that there is some solid value in designing a language whose performance can match C if needed yet use dynamic typing when convenient.

I just don't know what to do next: CoffeeScript or Dart?

Both improve on Javascript. CoffeeScript with a cool syntax. Dart with performance.

How can I have both?

"All indexing in Julia is 1-based"

I once designed/implemented a language where the biggest mistake I made was using 1-based indexing. At first it looked like it was going to be easier to understand/use but 0-based indexing is actually much more convenient when dealing with indexes arithmetic.

PS: the "metaprogramming" stuff is fabulous.

This is just another brick in the wall to make Internet look like it is a source of danger for all of us.

But we know who it is an actual danger for.

Nice point. Yet...

What about "references"? int& a, b; or int &a, &b; ?

So, I think that I'll stick to int* pa; int* pb;

i.e. one variable per line.

Additionnaly it makes it easier too lookup for a variable's type when reading the source code because one does not need to walk thru a list to find the variable, it is always after the type. I actually use "auto" to make it even easier to find variable declarations, going as far as grouping such declarations to some extend to make them easier to find.

Styles vary.

It's a bold statement, sure, but I have to admit that I am not able to refute it.

So, is there, according to you, at least one paper that EVERY programmer should read? Please avoid papers about the difference between "every" and "most" ;)

If no such paper exists, what does it tell about programming? That it is a poorly understood discipline? That would be my guess.

It is either pure mad defamation or something is beyond rotten in the state of Wall Street. It will be interesting to observe the reactions of the involved individuals.

I'm french and I cannot imagine such a post beeing possible here, either because such scandals never occur here or because they are never disclosed, I don't know.

This leaves me puzzled, should I think of this post as a sign of hope in the american democracy or a sign of its total decline?

On a different perspective, if you may, ...

We don't walk enough, that's a known fact.

Elevators are bad for your health. Take a walk.

However Delevators are good because most accidents happen when you go downward.

Hence, Elevators going up should be for really older people only (unless you're in a hurry or carrying something heavy or already in good shape...).

Fight for Delevators!

name: value instead of :name => value makes as much sense as p->q instead of (*p).x in C

As an historical note, here are the message (and matz’s response) where I made a proposal for the new syntax, back in 2002. It includes rationals.

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/...

Matz’s response : http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/...

  out = [
    ["FizzBuzz", "Fizz", "Fizz", "Fizz", "Fizz"],
    ["Buzz"],
    ["Buzz"]
  ]
  (1..100).each do | ii |
    puts out[ii % 3][ii % 5] || ii
  end

Thanks!

PS: i am assuming this is the fastest you can do in ruby (but I suspect that blocks are expensive alas)

PS2: passing the test is interesting, having a look at the good and/or best answers would be a decent award for having tried in the first time.

The problem with both waterfall and agile is that we are missing the definition of "the Humble process" to develop software.

Unfortunately humility does not sell so well.

Javascript's closest equivalent is XXXX_de&&bug( xxxx)

where XXXX is the "tracepoint" and XXXX_de is a global variable set to "true" when trace is required.

When trace is not required, thanks to the && "progressive and" operator, bug() is not called (such avoiding bug()'s parameters evaluation).

de&&bug( faster) :)

With their infrastucture, Amazon could as well run browsers in the cloud and then update remote screens, VNC style. Other guys do that for games, latency is not an issue for them apparently.

I've read studies that say that talking to a passenger is distracting, hence dangerous.

Well... I haven't read such studies actually, yet. But I feel like it's safer to stay at home, and shut up, and let the villains rule the world. Kidding.

I believe that trading liberty for safety is the true danger. That's because there is no point in expecting a sense of responsibility in the mind of people without freedom. Freedom and responsibility go together, remove the former, you remove the latter.

if( test ){

Note: as a progressive optimization, the very same solution can also be extended to full pages, ie not just "body" parts.

In that case, the main benefit over a "regular" load is that javascript files that you use don't get to be evaluated over and over, ie you load them once for all.

On my machine, this alone saves 300ms per page.

I'm experiencing "node anxiety", let me explain:

There really are two kinds of functions in a node program.

Synchronous functions and asynchronous functions.

This has major consequences during refactoring when what used to be a synchronous function now needs to become an asynchronous function => all synchronous functions that used to call the synchronous function needs to be turned into asynchronous functions themselves.

Sometimes the ramifications go way beyond first expected.

Sometimes the ramifications turned to be massive.

This becomes worse when one realizes that synchronous function are much more readable, half the code and about 5 times faster than asynchronous ones (see http://jsperf.com/asynch-cost)

Eventually the idea of refactoring a synchronous function into an asynchronous function becomes a source of worries.

And that, my friends, is not something easy to figure out and is what I call "node anxiety"

They should make the "order" irrelevant. ie silently retest using password/username reversed.

What are the chances that both (password,username) and (username,password) succeed? Very low I guess.

If it ever happens, reset password and send a mail about that (on both accounts).

"Timing is everything"

It's related to "critical mass" People do things differently now then they did 3 years ago. What didn't work then may work now. You felt you had a great idea? It didn't work?

Try again, things have changed.

I could not agree more. I started a company when I was 21, sold it 10 years later. Worked in a startup, got bought 18 months later ($13m), restored my family house, raised two kids and now... I start a new venture, solo. Why? I'm not sure, let's say it's my "personality". Be yourself!

1/ How are wikis doing today?

2/ What is the future of wikis?

3/ How are you involved?

Addition, subtraction and order relationships (ie > & <) are the only math that really matters.

Not convinced? Count the number of * and / in any source file and compare that to the number of + and -

Not to say that math is not useful, it's useful if math related stuff is what you do, which is a very small subset of what CS is about.

"Takedown Policy Please include the full URLs to the infringing material; no categories or search queries. We follow the same takedown policy that Google uses." etc, etc

OK. So basically: want to take down something? try go faster than ligth's speed...

Funny

OK. Is that Iran? (kidding)

It claims to be 10 x faster than Squeak, wow. OTOH, comparing speed with native Javascript would help too.

Very nice indeed.

In the Resource Timeline, when hovering, it would be nice to have the exact millisecs in addition to the existing proportional colored rectangles. The absolute total time could be added on the black hovering div on the left.

Thanks to the tool I discovered that the DNS time of my domains was far from perfect, thanks! (my host in on amazon EC2 west, but my DNS is french Gandi.net...)

Also nice would be the performance on reload (ie with a hot cache instead of a cold one).

That's a difficult question. To solve it I "crowd sourced it", i.e. I have a UserVoice feedback buttons with 2 ideas: 1/Stay in Alpha 2/Go Beta. So far... I need to stay in Alpha... :(

Perseverance. I you hold to your vision long enough you may have some nice surprises along the way, like competitors giving up or pivoting.

It happened to me recently when wetpaint decided to pivot out of the market for simple wikis (under the "pressure" of impatient VCs maybe...).

Why limit that to "support"? I often would be happy to share a window with a friend.