/prog/ - Programming

Well, Go is designed in a way that makes it harder to write some forms of bad code.

That would require some notion of what good code is - which depends on the context. That is, the language. It's possible to attribute some objective properties to good code. But the lion's share of it is subjective and unquantifiable.

It's a rather circuitous argument at that point. The language forces you to write good code within that language's context? I mean… that's what all languages strive to do.

This has a necessary corollary that you should just seek the language/context that fits what you see as good code.

>>2289

What I'm still missing is a feature to tell the compiler what subset of the language can be used in application code and in library code.

So let's suppose that there are no inherently bad languages and consider a language which gets bashed often, like C++.

If /prog/ agreed on a "good" subset of C++ and a style guide, and then wrote a compiler obeying the rules of /prog/ C++, would this be a "good" language?

>>2289

>Are there any languages which practically force you to write good code?

Scratch, maybe?

>https://en.wikipedia.org/wiki/Scratch_%28programming_language%29

Even there though, I'm sure it's possible to write bad code.

>say H

>say e

>say l

>say l

>say o

>…

>>2297

Good subset of C++: space, newline, semicolon.

>>2289

Ada?

>>2298

>say H

>say e

>…

Perhaps a good general rule is that a function shouldn't be called twice in a row. Although then there's the matter of detecting:

(in pseudocode)

define sayH as "say H"

define saye as "say e"

sayH

saye

>>2290

>>2310

What sorts of things do these languages force you to do/prevent you from doing?

>>2300

Insert other languages where I said "C++".

Perl because it's too convoluted to just try some random things and see if it works. You need to understand it to a relatively high degree to write it.

>>2289

Haskell, usually won't even compile if you write some types of bad code.

>>2319

Rob Pike made Go a higher level version of Plan9 C, presumably he wanted to prevent low level C spaghetti and overengineered C++ on insanity. It also comes with a tool that autoformats code for you, which I guess is more cosmetic.

>>2466

>the Haskell enforces good code meme

>>2297

C but with classes

>not using Ada

So after about a month, people's justifications for various languages have been:

Perl - Forces you to know what you're doing because otherwise you're fucked

Go - Forces you not to write spaghetti or C++-tier code

Haskell - Forces you to write code that compiles :^)

Haskell… most of the bad code is rejected

Scheme… you have to try really hard to do it

Python forces you to use good indentation practices.