News for hackers. Stuff that matters.
Re:C++: A language for next generation web apps by yummyfajitas on Tuesday January 26, 2010 @08:08PM (#1079455)
To be fair, after coming back to C++ after years in the world of Python and Haskell, it's not as bad as I remembered.

C++ is actually a moderately effective functional programming language. With reasonable knowledge of the standard data structures, and using BOOST, one can actually write fairly expressive and effective C++ code.

Most of the time, I feel like all I'm doing is writing a much more verbose version of Python. The rest of the time, I'm hunting nightmarish segfaults and segfault and template errors.

Re:C++: A language for next generation web apps by SamAtt on Tuesday January 26, 2010 @09:06PM (#1079563)
The question isn't "Can C++ work?" or "Will C++ be faster?" because we all know it can work and that it will be faster. The question is "At what point does the extra development time become more expensive than just adding another server to my Ruby/Python/C#/Whatever App"

For me, someone who learned C++ in school but has been in managed enviornments ever since, I'd be too scared to use C++. I'm not ashamed to admit I get a lot of help from the Internet when I'm stuck on a problem and that help is available because everyone else is using the same tools I am. Using C++ to code web apps puts you out in the wilderness as far as I'm concerned and I just don't think I could do it.

Re:C++: A language for next generation web apps by spamizbad on Wednesday January 27, 2010 @12:34AM (#1079856)
And it's not just the dev time: with C++ (and C, and any notorious unsafe language..) you've got to be extra diligent about security, which uses even more time, and requires expertise not just in C++ but also how to write secure software in low level languages... a skill many C/C++ devs lack, unfortunately.
Re:C++: A language for next generation web apps by techiferous on Tuesday January 26, 2010 @10:36PM (#1079684)
"because we all know it can work and that it will be faster"

Speed of execution depends more on the programmer's expertise than the language used.

Re:C++: A language for next generation web apps by jrockway on Wednesday January 27, 2010 @12:10AM (#1079819)
Not really true. I can write the same algorithm in Perl as in Haskell, and the Haskell always runs faster.
Re:C++: A language for next generation web apps by fhars on Wednesday January 27, 2010 @01:42AM (#1079977)
But then your expertise is not that different from your expertise. Your perl will probably still be faster overall than a beginner's haskell, not for the same algorithm, but for solutions to the same problem. Knowing which algorithms perform well for a given problem solved in perl is the most relevant part of expertise.
Re:C++: A language for next generation web apps by dualogy on Wednesday January 27, 2010 @12:44AM (#1079868)
So maybe he meant "on the expertise of the programmer" -- of the language/compiler...
Re:C++: A language for next generation web apps by anonjon on Wednesday January 27, 2010 @01:44AM (#1079984)
Chances are that the majority of developers won't find the most efficient algorithm to solve the problem.

(vs. the most efficient implementation of that algorithm... which is clearly going to be in a combination of C and assembly anyway).

Anyway, the guy using the good algorithm ends up with the fastest code. Different compilers will produce different quality of code.

Question is, if I am using C++ vs. a guy using Perl, will I ever reach the efficient algorithm? I might call it quits when I finally get something to compile and not segfault.

(Of course even this is kind of a strawman, because the perl guy can just reimplement in C++ when he figures out that he wants more speed out of his good algorithm).

Re:C++: A language for next generation web apps by fauigerzigerk on Wednesday January 27, 2010 @03:35AM (#1080142)
"Chances are that the majority of developers won't find the most efficient algorithm to solve the problem."

If that is so and the code does need to run fast or use little memory then the majority of developers would benefit from a fast language.

Very often, code doesn't need to run super fast. Memory usage and concurrency (the GIL) are greater issues with dynamic languages in my view.

Re:C++: A language for next generation web apps by jrockway on Wednesday January 27, 2010 @04:36AM (#1080205)
I don't get the constant complaints about the GIL. Letting your Python program run on 2 cores will make it 2x faster at best. Rewriting it in, say, Javascript or Lisp or Haskell or Java will make it run 2-50x faster on one core. After you get your 50x speedup, then you can worry about the 4x you'll get from buying 3 more processor cores.

(And oh yeah; it's only shared-memory concurrency that things like the GIL affects. If you have a job to do that wants to use 8 cores, split the job up into 8 parts and invoke your program 8 times. There's your 8x speedup.)

Re:C++: A language for next generation web apps by ramchip on Wednesday January 27, 2010 @04:53AM (#1080223)
> 2x faster at best

That's if you're CPU-bound. I don't use Python, but I made an image acquisition program in C++ which could be a relevant example. We wanted to save the images to disk in real-time (30-60FPS). Doing this in the acquisition loop would make the software unusable (the goal is video-rate confocal microscope imaging); it's far too long, and much of it is just due to disk writes being slow, not to the compression time. Using a thread pool was the solution, not because of an actual increase in speed, but because from the loop's POV the write went from blocking to non-blocking so the CPU stopped wasting time waiting for the disk.

We also wanted shared memory since there can be a lot of image data which is shared between the image compression & saving, display, and possibly statistics or filtering modules.

Re:C++: A language for next generation web apps by jrockway on Wednesday January 27, 2010 @12:29PM (#1080984)
Dunno about Python, but Perl has a library to do all disk writes in a separate (p)thread, so your main control thread never blocks on IO. (This is in addition to the usual event-loop tricks; I know Python can do nonblocking IO that way.)
Re:C++: A language for next generation web apps by fauigerzigerk on Wednesday January 27, 2010 @05:31AM (#1080246)
I can only tell you why _I_ am constantly complaining about the GIL. It's because I would like to use a Python/C combination for in-memory data analysis. C gives me the speed and memory efficiency and Python gives me the ease of use and the web stuff.

There is no 50x speedup to be had as it doesn't get any faster than C. The only significant speedup will come from parallelism. 8 cores this year, 16 next year and probably a 100 cores in a few years. Since I'm holding a lot of data in memory I can only run one process not many unless I implement each and every data structure on top of shared memory, which I'm not going to do because it's unproductive.

I cannot use Java or JavaScript or any language that doesn't have value types (i.e. structs and arrays of structs) with a well defined memory layout. I don't want to use Haskell because my problem doesn't lend itself to functional programming as it's inherently stateful. I feel I would have to fight the nature of Lisp to make it use as little memory as C. It makes no sense to use Lisp when I need to know how lists are laid out in memory.

The only realistic options right now are pure C, pure C++ or C#. Go does have all the right properties as well. It's very immature at this point though.

Re:C++: A language for next generation web apps by jbarham on Wednesday January 27, 2010 @10:11AM (#1080631)
Python C extension modules can release the GIL while they're running which allows for true concurrency. See this Google code search http://www.google.com/codesearch?q=python.org+lang%3Ac+Py_BE... for example usage.
Re:C++: A language for next generation web apps by fauigerzigerk on Thursday January 28, 2010 @04:09PM (#1085031)
I know this is possible. But I'm having trouble to imagine a web app design (or other network server) based on that idea. In order to use a lot of data in memory I would have to have a single Python process that gets called by nginx or apache. So that would be a bottleneck even before I get a chance to call my extension. And later there wouldn't be much code left that executes in the Python interpreter, which kind of defeats the purpose.

But I have to admit that I haven't fully thought this possibility through. Maybe you're right that it can be made to work.

Re:C++: A language for next generation web apps by anonjon on Wednesday January 27, 2010 @09:42AM (#1080573)
I guess my point was that the fast languages are generally not the ones that are good for developing the fast algorithms. It is harder to experiment in a language like C than it is in a language like lisp or perl.

The other thing to point out is that there is no reason for memory usage, concurrency or speed to be problems in dynamic languages. These are all issues with the implementations of compilers/interpreters that we are using.

It just so happens that dynamic languages have only recently come back into vogue, and we have forgotten (at least in ruby and python) all of the work that was done to create efficient implementations of dynamic languages.

Examples being how well Lisp stacked up against C as early as the 80-90s, projects like StrongTalk, stack based languages like forth... the multitude of papers on efficient scheme implementations.

Dynamic languages were declared 'slow' and therefore were dumped in favor of C by most programmers. This has caused a gap in the knowledge that we have about implementing dynamic languages. Which is a shame, because there is a lot out there for us to relearn.

Re:C++: A language for next generation web apps by fauigerzigerk on Thursday January 28, 2010 @11:57AM (#1084302)
There are some fundamental problems with making dynamic languages run fast. Being able to prove that some variable will never contain anything other than a 32 bit int allows the compiler/JIT to do things that it cannot otherwise do.

The only way to make dynamic languages as fast as statically typed languages is to selectively remove dynamic features. A few type hints can make a huge difference.

Re:C++: A language for next generation web apps by abrahamsen on Wednesday January 27, 2010 @06:05AM (#1080277)
Your experience with Python and Haskell has most likely made you a far better C++ programmer than you were before.
Re:C++: A language for next generation web apps by yummyfajitas on Wednesday January 27, 2010 @10:05AM (#1080618)
This is absolutely the case.

I'm now used to first class functions, currying, etc. C++ actually has them, hidden in the stl and boost::function. Whatever I can't do using those, I can usually do by creating a family of classes which only implement operator() (I've only needed to do this once or twice, and it might have been avoidable).

Due to using a language with native dicts (and syntactic sugar), they are now part of my vocabulary. This means I immediately reach for std::map or boost::unordered_map when it makes sense.

Similarly, python generators and haskell lazy lists have made view sequences as reasonable objects to generate and iterate over. Custom iterators are just the same thing with added verbosity.

If I never used higher level languages, I'd still be treating C++ as C with objects.

Re:C++: A language for next generation web apps by scott_s on Wednesday January 27, 2010 @11:17AM (#1080793)
In C++, I'm more likely to write a struct/class which implements operator() than an actual function. It lets me write code like this, which does mutate state, but I put it off as long as possible:

  xformerlist& lbrace = node.children.front().xformations;
  xformerlist& rbrace = node.children.back().xformations;
  fn_and<shared_variable> row_and_flat(&shared_variable::is_row, &shared_variable::is_flat);
  const sharedset& flat_ins = filter(row_and_flat, set_union_all(in, inout));
  const sharedset& flat_outs = filter(row_and_flat, set_union_all(out, inout));
  const sharedset& flat_all = set_union_all(flat_ins, flat_outs);
  make_conditions<gen_in<row_access> > make_gen_in_row(parcond, conds, local_depths);
  make_conditions<gen_out<row_access> > make_gen_out_row(parcond, conds, local_depths);

  append(lbrace, fmap(make_gen_in_row, flat_ins));
  append(rbrace, fmap(make_gen_out_row, flat_outs));
I imagine that code would give a lot of people fits. In my current project, I ran with a more functional approach to C++. I don't know if I'll keep everything I've used in this programming style, but I certainly will keep some of it.
Re:C++: A language for next generation web apps by joe_the_user on Tuesday January 26, 2010 @08:42PM (#1079517)
Oddly enough I'm back to C++ too, after Ruby.

One nice thing is; in a fast language, tests run quickly too.

Also, Python and Ruby don't have the equivalent of an ASSERT (you could roll your own but it's not standard practice).

Also, C++ has standard hash lists and complicated data structure are actually going to run quickly.

And while memory management can be a pain, you are doing it yourself so you can track down memory leaks rather than having them be inherent in the interpreter...

...as in Ruby AND Mono.

Re:C++: A language for next generation web apps by ubernostrum on Tuesday January 26, 2010 @09:17PM (#1079577)
Also, Python and Ruby don't have the equivalent of an ASSERT (you could roll your own but it's not standard practice).

Ahem:

http://docs.python.org/reference/simple_stmts.html#the-asser...

Re:C++: A language for next generation web apps by hazzen on Tuesday January 26, 2010 @08:51PM (#1079534)
C++ doesn't actually have a standard "hash list" (I assume you meant hash map or hash set?). Depending on your implementation, you either have hash_{map,set}, unordered_{map,set}, both, or something entirely different. tr1 specified unordered_{map,set}, but tr1 is only technically a proposal, not a standard.

I think a safe assumption is that tr1::unordered_{map,set} will be available in all implementations by now, but until C++0x is ratified and implemented by major compilers, you will run into different platforms having (possibly) different implementations. And lets be honest - even after C++0x has been implemented in major compilers, you will still have subtly different/buggy implementations.

edit: I had conflated {hash,unordered}_{set,map}. Fixed

Re:C++: A language for next generation web apps by queensnake on Tuesday January 26, 2010 @09:18PM (#1079579)
Nah, the committee isn't going to change unordered_set or unordered_map; they're struggling with far more urgent things, to finish the std off. Those have already gotten the full treatment, they have the usual std:: collection interface; what's to change?
Re:C++: A language for next generation web apps by grogers on Wednesday January 27, 2010 @01:06PM (#1081082)
Or you can use boost::unordered_set right now, in any compiler, whether it supports tr1 or not.
Re:C++: A language for next generation web apps by icefox on Tuesday January 26, 2010 @09:54PM (#1079624)
RubyOnRails is very test gunghu, but to run a hello world test takes seconds, anyone know why? This seems very odd. Is this one of those do what I preach, not what I do things?
Re:C++: A language for next generation web apps by techiferous on Tuesday January 26, 2010 @10:40PM (#1079690)
I doubt it takes seconds to test a hello world program in Ruby. However, to test a hello world Rails application is a different story, as you have to start up the web server, which takes seconds (even though it eventually just serves a simple page).
Re:C++: A language for next generation web apps by maurycy on Wednesday January 27, 2010 @03:31AM (#1080137)
Not necessarily the web server.

Standard `rake test:units` (or even `ruby test/units/model_test.rb`) takes the whole Rails stack so it adds up.

Re:C++: A language for next generation web apps by techiferous on Wednesday January 27, 2010 @10:58AM (#1080736)
You're right and I agree. But let's be careful not to equate Rails with Ruby. Rails tests may have a slow startup time, but Ruby tests do not and other Ruby web framework tests may not.
Re:C++: A language for next generation web apps by fauigerzigerk on Wednesday January 27, 2010 @04:53AM (#1080222)
Because if "performance doesn't matter" is repeated often enough people actually start to believe it, and if enough people believe it, it becomes false. Is there a name for this logic? :-)
Re:C++: A language for next generation web apps by Luyt on Wednesday January 27, 2010 @06:28AM (#1080294)
Confirmational Bias followed by a Self-fulfilling Prophecy. But you knew that and I think your question was purely rhetorical ;-)
Re:C++: A language for next generation web apps by capablanca on Wednesday January 27, 2010 @07:26AM (#1080340)
So, what is great, modern C++ code to read?
Re:C++: A language for next generation web apps by jbarham on Wednesday January 27, 2010 @10:48AM (#1080719)
It's a book but Accelerated C++ by Koenig and Moo has been well reviewed.