Scott Meyers wants to bring default zero-initialization to C++, mentions TDPL for precedent

[deadalnix via Digitalmars-d]

On Sunday, 22 November 2015 at 03:28:42 UTC, Dicebot wrote:
> And something like Erlang does all of the above at much better 
> performance and quality of implementation. Most importantly, 
> though, you completely ignore the performance overhead costs 
> that matter for most companies that are not Facebook.

Erlang makes state terrible to work with (but doesn't bound state 
to a request). PHP has request local state. The model is very 
different. One of these models is way easier to work with.

I also didn't went into this as it was irrelevant to the scaling 
argument, but having rapid iteration is key, especially for UI 
work where automation is hard. Erlang doesn't fit the bill.

Last but not least, Erlang has a foreign syntax, so ramping up 
devs is harder.

Back on PHP, there are many other aspects of the siloed requests 
model that provide benefits that erlang simply cannot provide.

> Reimplementing main points from abovementioned list (primarily 
> isolation and request-local allocators) can be done with pretty 
> much any decent language and potentially save huge amount of 
> money on server costs.
>

Well one can recode the runtime to get these behaviors. Or one 
can focus on delivering value to customers.

That's one damn thing that the D community need to get burned 
into their brain. "You can avoid using the GC", "You can use 
addr2line to get line number in your stacktrace", and so on are 
cheap excuse for delivering crap.

There are good plateforms that come with shit language out there. 
We have a good language with a shit plateform (let's be honest 
one second). Facts show that 1/ win over 2/ 100% of the time.

Writing how bad 1/ is in the 2/ forum is simply an exercise in 
finding excuses to not look where it is ugly.

> Scaling implies not only being able to increase the load 
> without system redesign but also doing it efficiently - both in 
> server and maintenance costs. PHP is rather bad at both.

No, performance, efficiency and scalability are disjoint things. 
Scalability is about how much more resource are needed to serve 
how much more requests.

I'm living in the real world, where at least half or the request 
you make to a webserver are handled by PHP. Arguments are cheap 
when facts refuse to match.