Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
p0nce
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
123 ms
·
841.
▲
by
p0nce
10y ago
If you need a feel of what the community values (apart from rants), have a look at the forums. https://forum.dlang.org/ D is backed by companies like Sociomantic and Weka.io that operates in high-performance domains.
842.
▲
by
p0nce
10y ago
Went from Delphi to Ocaml to lots of C++ to D. Basically I'm happier with the products I wrote in D so I keep using it. It's an almost schizophrenic language that always says "yes" when you ask if something is possible.
843.
▲
by
p0nce
10y ago
In D this is indeed known only at runtime, one of the decision was that "there should be only one type of pointers". immutable(T) doesn't guarantee it isn't in the GC heap from what I can gather. shared(T) could perhaps
844.
▲
by
p0nce
10y ago
You'll be okay.
845.
▲
by
p0nce
10y ago
Yes I thought GC write barriers were always implemented with memory barrier instructions. Probably a trap because the same word is used. Still I wonder how they are implemented then.
846.
▲
by
p0nce
10y ago
I meant "memory barriers". Atomics embed memory barriers.
847.
▲
by
p0nce
10y ago
And if I use only a bit of the GC, can I use only a bit of write barriers? Walter Bright was right about segmented stacks, I'm tempted to think he's right about write barriers too.
848.
▲
by
p0nce
10y ago
Let me amend then: "A fast copying collector _in D_ would require write barriers". Of course with other languages you can have GC without that limitation.
849.
▲
by
p0nce
10y ago
You can always use less of the GC, but there are no way not to use pointers. For example, I sell products in D which disable the GC completely, I certainly don't want write barriers.
850.
▲
by
p0nce
10y ago
I read this in http://www.infognition.com/blog/2014/the_real_problem_with_g... better ask the author of the article if you have a way for a better D GC. > To make fast GC it needs to be generational, but genera
851.
▲
by
p0nce
10y ago
The case against write barriers is pretty simple: the slowness of the GC can be workarounded, while memory barriers cannot. If they are needed, no other way to copy pointer values (which are quite pervasive in system programming).
852.
▲
by
p0nce
10y ago
A fast copying collector for D would require write barriers: using memory barriers everytime a pointer is written. This has a runtime cost. > which runs at every allocation. The article explains in great depth that this is not the case.
853.
▲
by
p0nce
10y ago
Most folks haven't tried D.
854.
▲
by
p0nce
10y ago
> what are the advantages of running GC only when allocations are happening, instead of running concurrently? That way you don't need a dedicated thread for the GC (current one is hijecked). > Is it burdensome for the programmer
855.
▲
by
p0nce
10y ago
That's definately important in France where some important tax cuts depends on your degree.
856.
▲
DConf 2017 talks announced
(dconf.org)
2 points
by
p0nce
10y ago
|
0 comments
857.
▲
by
p0nce
10y ago
At this point it is clear that software size increase linearly with the size of your software team, whatever the problem you solve. This affects every organization and is something that should be actively fight against. Having accidental,
858.
▲
by
p0nce
10y ago
Damn, I knew I was charging too little. Not only noone is complaining about price, but some explicitely says it's not expensive.
859.
▲
Goodbye Rust, and Hello, D
(z0ltan.wordpress.com)
1 points
by
p0nce
10y ago
|
0 comments
860.
▲
by
p0nce
10y ago
> How can we as a society fix this? Don't mate with irrational people.
861.
▲
by
p0nce
10y ago
Thanks for recommendations. Are your clients consumers or businesses though?
862.
▲
by
p0nce
10y ago
Reaching niche users in a cost-effective way.
863.
▲
by
p0nce
10y ago
D has no overhead syntax for CTFE, "comptime" is from the context.
864.
▲
by
p0nce
10y ago
- for the longest time I've wished to tweet to a subpart of my followers; Then only way to have that is multiple account right now. Let me follow "person X + #hashtag". - support multiple accounts on the website - Twitter ads
865.
▲
by
p0nce
10y ago
> games and realtime audio processing are an exception. Not necessarily. D has a garbage collector and is used in games already such as Quantum Break. I do audio processing and had to limit GC usage in audio callbacks of course, but it w
866.
▲
by
p0nce
10y ago
PCA of personality traits hints more at 3 dimensions rather than 5. Big five are practical but not completely uncorrelated.
867.
▲
by
p0nce
10y ago
I've always felt that the damage done by technical debt was abysmal and frequently underestimated. - opportunity cost for the product since you aren't fast enough to chase new revenue channels, this cost is almost invisible, - the
868.
▲
by
p0nce
10y ago
This is invalid since nothing in the compiler forces you to remove the .unwrap() so it's safe to assume it will not be done before production. The whole "but this is just for prototyping" is a logical fallacy, as you know we
869.
▲
by
p0nce
10y ago
Not trolling. I'm just trying to convey a simple point. https://news.ycombinator.com/item?id=13378183 As it cost me 20+ downvotes to make a rational conversation with you all, I will stop interacting with the Rust comm
870.
▲
by
p0nce
10y ago
My attempts so far: Rust is a systems programming language that runs blazingly fast, guarantees memory safety and provides correct concurrency. Rust is a systems programming language that provides uncompromised performance, convenience and
More ›