Re: dchip is a D2 port of the Chipmunk2D physics library for 2D games

2013-11-09 Thread SomeDude

On Friday, 8 November 2013 at 05:04:45 UTC, Suliman wrote:

I did not refactor, it's a straight port.
Could you say how much code lines can be approximately saved 
after porting with refactoring?


This question doesn't make much sense. I guess one could write 
the same thing from scratch in D in half the LOC. But a reduced 
line count wouldn't be the only benefit, a more maintainable and 
safer codebase would be other benefits.


Re: Pragmatic D Tutorial

2013-10-13 Thread SomeDude

On Tuesday, 8 October 2013 at 00:29:34 UTC, Meta wrote:


"Sometimes D is criticised, because it is not simple language, 
in contrast to Go, Rust, Lisp, or Scala. However, a D 
programmer sees no problem and actually likes his big toolbox."


I wouldn't call any of those languages simple, except for Go. 
Maybe Go, C, Scheme, Python?


+1


Re: Article: Increasing the D Compiler Speed by Over 75%

2013-07-27 Thread SomeDude

On Friday, 26 July 2013 at 00:08:21 UTC, Leandro Lucarella wrote:

Walter Bright, el 25 de July a las 14:27 me escribiste:

On 7/25/2013 11:49 AM, Dmitry S wrote:
>I am also confused by the numbers. What I see at the end of 
>the article is
>"21.56 seconds, and the latest development version does it in 
>12.19", which is

>really a 43% improvement. (Which is really great too.)

21.56/12.19 is 1.77, i.e. a >75% improvement in speed.


This is certainly misleading, is very easy to be confused with 
a time
reduction of 75%, which one would expect to be 1/4 of the 
original time.

:)


No, a division by 4 of the total time would be a 300% improvement 
in speed. The article's title looks correct to me.


Re: [Phoronix] D Language Still Showing Promise, Advancements

2013-06-24 Thread SomeDude

On Friday, 21 June 2013 at 11:13:49 UTC, Paulo Pinto wrote:

It all depends what Mozilla and Samsung do with the language.

If you have powerful entities pushing a language down 
developers throats, it will get used. That is how many 
mainstream languages got where they are now.


--
Paulo



I wonder why hasn't any *big* corp backed up D so far.


Re: DConf 2013 Day 2 Talk 5: A Precise Garbage Collector for D by Rainer Schütze

2013-06-05 Thread SomeDude

On Wednesday, 5 June 2013 at 14:14:45 UTC, bearophile wrote:

Andrei Alexandrescu:


http://www.reddit.com/r/programming/comments/1fpw2r/dconf_2013_day_2_talk_5_a_precise_garbage/


Is this useful to make the GC precise regarding the stack too?

http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.19.5570

Bye,
bearophile


Here is the blog post deadalnix is referring about at the very 
end of the video:

http://www.deadalnix.me/2012/03/05/impact-of-64bits-vs-32bits-when-using-non-precise-gc/


Re: Shameless autopromotion : type safe tagged union in D

2013-05-12 Thread SomeDude

On Friday, 10 May 2013 at 19:23:45 UTC, Jesse Phillips wrote:
On Friday, 10 May 2013 at 17:56:14 UTC, Andrei Alexandrescu 
wrote:
A general note about posting to reddit: it often happens that 
posts from infrequent posters go to spam by means of some 
automatic rule. When that happens you need to message the 
moderators and politely ask them to manually instate the post 
because it's legit. Once you accumulate karma and all, your 
posts will be auto-approved.


Well that is stupid. It would be like StackOverflow closing 
questions of new users and waiting for people to vote to open.


My submissions now all go to the spam section even though I have 
more than 1300 karma of comment and 800 karma of submission. It's 
fucking annoying.


Re: DConf 2013 Day 1 Talk 2: Copy and Move Semantics in D by Ali Cehreli

2013-05-10 Thread SomeDude

On Friday, 10 May 2013 at 15:24:43 UTC, Jacob Carlborg wrote:

On 2013-05-10 16:38, Andrei Alexandrescu wrote:


Two a week.


Is there a reason for this?


It's good to keep people busy with D. ;)
There have been way to many Go posts on reddit lately. :D


Re: D 1.076 and 2.061 release

2013-01-13 Thread SomeDude
On Thursday, 3 January 2013 at 08:25:41 UTC, Dmitry Olshansky 
wrote:

1/3/2013 12:22 PM, Russel Winder пишет:

On Wed, 2013-01-02 at 13:59 -0800, Walter Bright wrote:
[…]

I finally threw in the towel and don't use Ubuntu to play 
music anymore.


I threw in the towel on Ubuntu when Unity came out as the 
default UI.



Going OT but can't agree more :)


I rather like lubuntu (LXDE).

I like minimalist interfaces, I don't care about bells and 
whistles, I want things that plain work, that's all. I don't use 
Linux for multimedia, only for programming and work. So it runs 
in a VM on my laptop, and the simpler the better. With this 
philosophy in mind, I'm quite satisfied. The only thing I regret 
is, lubuntu is not a LTS release unfortunately.


Re: A look at the D programming language by Ferdynand Górski

2013-01-13 Thread SomeDude

On Sunday, 13 January 2013 at 16:00:27 UTC, SomeDude wrote:

On Monday, 7 January 2013 at 12:16:04 UTC, thedeemon wrote:

On Monday, 7 January 2013 at 11:31:46 UTC, bearophile wrote:


There is also Rust.


I had the impression that Rust was at embryonic stage where it 
changes all the time, can't really live by itself and is not 
born yet. It's an interesting project but not a language one 
would use today for real work. Or am I mistaken?


Yeah, my impression is it's still pretty embryonic, especially 
on the library side.


Also we don't know how well it performs, although it looks like 
the design is intended to perform reasonably well.


Re: A look at the D programming language by Ferdynand Górski

2013-01-13 Thread SomeDude

On Monday, 7 January 2013 at 12:16:04 UTC, thedeemon wrote:

On Monday, 7 January 2013 at 11:31:46 UTC, bearophile wrote:


There is also Rust.


I had the impression that Rust was at embryonic stage where it 
changes all the time, can't really live by itself and is not 
born yet. It's an interesting project but not a language one 
would use today for real work. Or am I mistaken?


Yeah, my impression is it's still pretty embryonic, especially on 
the library side.


Re: D 1.076 and 2.061 release

2013-01-02 Thread SomeDude
On Wednesday, 2 January 2013 at 19:42:13 UTC, Jonathan M Davis 
wrote:

On Wednesday, January 02, 2013 03:20:27 Jonathan M Davis wrote:

On Wednesday, January 02, 2013 10:19:54 bearophile wrote:
> Jonathan M Davis:
> But many months
> have passed between those two versions, many bugs have being
> removed, several features have being introduced, and so on 
> (just look at the difference in the zip size between the two 
> versions),
> so it's better for the users to be aware that some probably 
> some
> user code will need to be fixed or improved to run on the 
> 2.061.



- Jonathan M Davis


Just for D2, 330 issues closed for this release !
Talk about a huge amount of work done.

Congrats to everybody, 2013 is looking good !


Re: DConf 2013 on kickstarter.com: we're live!

2012-10-23 Thread SomeDude

On Tuesday, 23 October 2012 at 14:26:21 UTC, Adam D. Ruppe wrote:

On Tuesday, 23 October 2012 at 14:15:22 UTC, deadalnix wrote:

1/4 of the money raised in 2 days.



I expect the speed will slow down significantly because most 
the D followers would have already seen it in the first couple 
days...


Yeqh, but I haven't pledged yet :o

Promise I will :)


Re: GC vs. Manual Memory Management Real World Comparison

2012-09-11 Thread SomeDude

On Tuesday, 11 September 2012 at 10:28:29 UTC, bearophile wrote:

SomeDude:

It's a bad solution imho. Monitoring the druntime and hunting 
every part that allocates until our codebase is correct like 
Benjamen Thaut is a much better solution


Why do you think such hunt is better than letting the compiler 
tell you what parts of your program have the side effects you 
want to avoid?


Bye,
bearophile


My problem is you litter your codebase with nogc everywhere. In  
similar fashion, the nothrow keyword, for instance, has to be 
appended just about everywhere and I find it very ugly on its 
own. Basically, with this scheme, you have to annotate every 
single method you write for each and every guarantee (nothrow, 
nogc, nosideeffect, noshared, whatever you fancy) you want to 
ensure. This doesn't scale well at all.


I would find it okay to use a @noalloc annotation as a shortcut 
for a compiler switch or a an external tool to detect allocations 
in some part of code (as a digression, I tend to think D 
@annotations as compiler or tooling switches. One could imagine a 
general scheme where one associates a @annotation with a 
compiler/tool switch whose effect is limited to the annotated 
scope).
I suppose the tool has to build the full call tree starting with 
the @nogc method until it reaches the leaves or finds calls to 
new or malloc; you would have to do that for every single @nogc 
annotation, which could be very slow, unless you trust the 
developer that indeed his code doesn't allocate, which means he 
effectively needs to litter his codebase with nogc keywords.


Re: GC vs. Manual Memory Management Real World Comparison

2012-09-10 Thread SomeDude
On Wednesday, 5 September 2012 at 12:28:43 UTC, Piotr Szturmaj 
wrote:

Benjamin Thaut wrote:
I do object pooling in both versions, as in game developement 
you
usually don't allocate during the frame. But still in the GC 
version you
have the problem that way to many parts of the language 
allocate and you

don't event notice it when using the GC.


There's one proposed solution to this problem: 
http://forum.dlang.org/thread/k1rlhn$19du$1...@digitalmars.com


It's a bad solution imho. Monitoring the druntime and hunting 
every part that allocates until our codebase is correct like 
Benjamen Thaut is a much better solution


Re: Language Interview Questions

2012-09-01 Thread SomeDude

On Friday, 24 August 2012 at 14:32:56 UTC, Jesse Phillips wrote:

On Friday, 24 August 2012 at 11:51:02 UTC, Rory McGuire wrote:
Oh, wow. My messages used to get blocked if I sent from the 
wrong address,

perhaps it was a different list.

Thanks,


The forum.dlang engine has some spam checking, but I don't know 
what it is and there are many other ways to post to the NG.


That Lena Singh should be IP banned, it's the second time at 
least she's been posting spam. She did it here:

http://forum.dlang.org/post/whfgmclvfoocpmzyi...@forum.dlang.org


Re: 2.060 on reddit

2012-08-03 Thread SomeDude

On Friday, 3 August 2012 at 19:44:22 UTC, bearophile wrote:

Caligo:


When are allocators going to be ready?


Direct experience shows me that once things are in Phobos, it's 
not easy to fix their interface/API. Andrei fears of breaking 
changes, so even small API improvements of Phobos stuff written 
last year are refused. See as example:


http://d.puremagic.com/issues/show_bug.cgi?id=8467

So Phobos stuff once created is almost set in stone. This means 
that in practice the Phobos APIs should be perfect on the first 
try. So better to not rush things, and do things right.


Bye,
bearophile


"When in doubt, leave it out." says Joshua Bloch
http://www.youtube.com/watch?v=aAb7hSCtvGw



Re: Introducing vibe.d!

2012-05-03 Thread SomeDude

On Wednesday, 2 May 2012 at 22:18:12 UTC, bls wrote:

Am 01.05.2012 23:46, schrieb Sönke Ludwig:

I made a post with Steve Teale's MySQL driver as an example:
http://vibed.org/blog/posts/writing-native-db-drivers

There were some hidden gotchas, but I hope the current port 
doesn't

break anything from the original code.


Looks good. Unfortunately I spend some time with MongoDB and I 
have to say : Amazing db. I thought key/value databases are 
just toys. At least regarding MongoDB is was completely wrong.


It does have its scaling problems, though. As soon as RAM is 
full, performance drops drastically, as it's essentially a disk 
backed in memory database.


Re: Combine Coroutines and Input Ranges for Dead-Simple D Iteration

2012-05-02 Thread SomeDude

On Tuesday, 1 May 2012 at 08:26:45 UTC, Nick Sabalausky wrote:
A little write-up I just did on something I thought was pretty 
cool:


Combine Coroutines and Input Ranges for Dead-Simple D Iteration
https://www.semitwist.com/articles/article/view/combine-coroutines-and-input-ranges-for-dead-simple-d-iteration


Call me stupid, but I've absolutely no idea what you're doing. 
What problem does the InputVisitor solve ? What are the current 
solutions ? What is the intent of your code ? What are the 
supposed advantages ? Your article says nothing about it.


Re: Jumping on the bandwagon - DDCPU-16

2012-04-28 Thread SomeDude

On Sunday, 22 April 2012 at 20:13:01 UTC, Paulo Pinto wrote:


My latest issue with Java is the trend to add annotations 
instead of keywords, like @Override, or the new type 
annotations like @NotNull and so on.


Its slowly going to annotation hell.


Yeah, I can see that too.


Re: Video: Generic Programming Galore using D @ Strange Loop 2011

2012-04-20 Thread SomeDude

On Thursday, 19 April 2012 at 00:11:29 UTC, Andrej Mitrovic wrote:

On 4/18/12, SomeDude  wrote:

On Tuesday, 17 April 2012 at 08:00:36 UTC, Denis Shelomovskij
wrote:


It's pity that a video is read-only and it isn't easy to fix
slips of the tongue like this one. Maybe some notes can be
added?

Anyway, these (Andrei's and Walter's) videos are too good to
not list them on the site.


I've cleaned up the wiki a bit and added them:
http://prowiki.org/wiki4d/wiki.cgi?WhySwitch


You could actually add them here and link to it:
http://prowiki.org/wiki4d/wiki.cgi?Videos
I made that page a long while ago but I didn't really know 
where to

link it from, so I just put it in the first tab I found (The D
Community: http://prowiki.org/wiki4d/wiki.cgi?NeighborHood)


Thank you, I didn't know this page.




Re: Video: Generic Programming Galore using D @ Strange Loop 2011

2012-04-18 Thread SomeDude
On Tuesday, 17 April 2012 at 08:00:36 UTC, Denis Shelomovskij 
wrote:


It's pity that a video is read-only and it isn't easy to fix 
slips of the tongue like this one. Maybe some notes can be 
added?


Anyway, these (Andrei's and Walter's) videos are too good to 
not list them on the site.


I've cleaned up the wiki a bit and added them:
http://prowiki.org/wiki4d/wiki.cgi?WhySwitch




Re: Pull requests processing issue

2012-04-18 Thread SomeDude

On Wednesday, 18 April 2012 at 09:00:59 UTC, Trass3r wrote:
I think the problem of ~100 open pull requests needs to be 
faced better. People that see their patches rot in that list 
probably don't feel rewarded enough to submit more patches.


So true. I won't do any further work if it's in vain anyway.
Also I regularly have to rebase my one cause of conflicts, 
which is annoying.


I really wonder what Walter's doing. Is he still running the 
whole testsuite instead of relying on the autotester?


Well, I've seen at least one regression in D.learn from 2.058 to 
2.059 and that doesn't give me much confidence in what random 
people are doing when they are submitting their patches.


So instead of bitching about what Walter's doing, people should 
be more careful what THEY are doing.


Re: D on AtCoder

2012-04-17 Thread SomeDude
On Saturday, 14 April 2012 at 17:03:37 UTC, Masahiro Nakagawa 
wrote:

On Saturday, 14 April 2012 at 12:14:34 UTC, Trass3r wrote:

I and other D programmers begged AtCoder team to support D.
In the result, AtCoder supports D (dmd 2.058) officially.


Now get them to update to 2.059 so you will get UFCS ;)


Yeah. I continue to help the AtCoder team :)


2.059 introduced at least a regression.
Stay with 2.058, and hopefully get host.lyric, the guy who's 
first in the Google CodeJam qualifications in your team. :)