|
@slava_pestov | |||||
|
Strong type systems, memory safety, automatic memory management and so on have had zero effect on software quality, because all the extra slack was consumed by new features instead
|
||||||
|
||||||
|
Renaud.lienhart(_:)
@layoutSubviews
|
1. velj |
|
From experience, these make a significant difference in medium to large teams, where juniors / newcomers feel more confident working a codebase without the fear that they’ll trigger a chain reaction of load-bearing tech debt bugs.
|
||
|
|
||
|
🌌🧠 as a service
@NeoNacho
|
1. velj |
|
Think of all the promotions though
|
||
|
|
||
|
Ben Pious
@BenPious
|
1. velj |
|
Generic monomorphization and type inference can prevent this by increasing code size and compile times until it is impossible to add new features 🙃
|
||
|
|
||
|
Paul Cantrell
@inthehands
|
1. velj |
|
I’m reminded of some (I heard about it so perhaps apocryphal) finding that drivers compensate for safety features on cars by driving faster, intuitively gravitating toward a more or less fixed nonzero accident rate no matter how safe their vehicles.
|
||
|
|
||
|
Adam Zethraeus
@adam_zethraeus
|
1. velj |
|
Don’t be so cynical! It allowed companies to lower their hiring bar and pay less too!
|
||
|
|
||
|
Marcel Weiher 🇪🇺
@mpweiher
|
1. velj |
|
And the higher productivity of dynamic languages also goes towards more features.
🤷♂️
|
||
|
|
||
|
BobArmstrong
@BobArmstrong
|
1. velj |
|
So get CoSy @CoherentSystems . Go straight to APL level expressive power in open to the chip Forth to make what you need as lean as you need .
At the APL level CoSy's modulo indexing makes memory errors something you almost have to work at .
|
||
|
|
||