www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Not clickbait so don't read it if you don't want to

reply Stefan Koch <uplink.coder googlemail.com> writes:
I found a great line in Charles Blooms blog.

```
More generally, this programming pattern of finding clever 
complicated ways to hide the fact that your systems are overly 
bloated and slow is just not the win. You will only make the 
failure cases less common but more ugly.
```

This is exactly one of the main problems with a lot of D code I 
see day to day.
(Which is mostly poor attempts to spend up the DMD compiler.)
Nov 15 2021
next sibling parent Ola Fosheim =?UTF-8?B?R3LDuHN0YWQ=?= <ola.fosheim.grostad gmail.com> writes:
On Monday, 15 November 2021 at 21:24:20 UTC, Stefan Koch wrote:

 This is exactly one of the main problems with a lot of D code I 
 see day to day.
 (Which is mostly poor attempts to spend up the DMD compiler.)


In applications, Phobos or the compiler? Maybe some examples, so 
we have something to discuss?
Nov 15 2021
prev sibling next sibling parent reply Imperatorn <johan_forsberg_86 hotmail.com> writes:
On Monday, 15 November 2021 at 21:24:20 UTC, Stefan Koch wrote:

 I found a great line in Charles Blooms blog.

 ```
 More generally, this programming pattern of finding clever 
 complicated ways to hide the fact that your systems are overly 
 bloated and slow is just not the win. You will only make the 
 failure cases less common but more ugly.
 ```

 This is exactly one of the main problems with a lot of D code I 
 see day to day.
 (Which is mostly poor attempts to spend up the DMD compiler.)


This is why I like the Erlang philosophy.
Nov 16 2021
parent reply Stefan Koch <uplink.coder googlemail.com> writes:
On Tuesday, 16 November 2021 at 09:32:41 UTC, Imperatorn wrote:

 On Monday, 15 November 2021 at 21:24:20 UTC, Stefan Koch wrote:

 I found a great line in Charles Blooms blog.

 ```
 More generally, this programming pattern of finding clever 
 complicated ways to hide the fact that your systems are overly 
 bloated and slow is just not the win. You will only make the 
 failure cases less common but more ugly.
 ```

 This is exactly one of the main problems with a lot of D code 
 I see day to day.
 (Which is mostly poor attempts to spend up the DMD compiler.)


 This is why I like the Erlang philosophy.


I am not familiar, what are you referring to?
Nov 16 2021
parent bauss <jj_1337 live.dk> writes:
On Tuesday, 16 November 2021 at 12:14:12 UTC, Stefan Koch wrote:

 On Tuesday, 16 November 2021 at 09:32:41 UTC, Imperatorn wrote:

 On Monday, 15 November 2021 at 21:24:20 UTC, Stefan Koch wrote:

 I found a great line in Charles Blooms blog.

 ```
 More generally, this programming pattern of finding clever 
 complicated ways to hide the fact that your systems are 
 overly bloated and slow is just not the win. You will only 
 make the failure cases less common but more ugly.
 ```

 This is exactly one of the main problems with a lot of D code 
 I see day to day.
 (Which is mostly poor attempts to spend up the DMD compiler.)


 This is why I like the Erlang philosophy.


 I am not familiar, what are you referring to?


Probably referring to:

```
Erlang has “fail-fast” philosophy that means processes do what 
they are supposed to do or fail. i.e. Process must obey single 
responsibility principle. It should be possible for one process 
to detect failure in another process and we should also know the 
reason for failure.
```
Nov 16 2021
prev sibling parent sighoya <sighoya gmail.com> writes:
On Monday, 15 November 2021 at 21:24:20 UTC, Stefan Koch wrote:

 ```
 More generally, this programming pattern of finding clever 
 complicated ways to hide the fact that your systems are overly 
 bloated and slow is just not the win. You will only make the 
 failure cases less common but more ugly.
 ```


I would say it resembles the core of commercial development quite 
good ;)

But I think it's the problem of legacyness, ugly workarounds are 
cheaper to implement than to solve the underlying problem.
Apr 23 2022