Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

Weakly typed languages

Name: Anonymous 2019-01-27 8:36

Why do they even exist? Whatever advantage they claim to give is more than offset by runtime unpreictability caused by typos and bad design that's not picked up at compile time.

Name: Anonymous 2019-01-27 10:59

I can usually type up a code monthly at best.

Name: Anonymous 2019-01-27 13:04

What do you mean ``weakly typed''?

Name: Anonymous 2019-01-27 13:45

Because they're convenient.

Diff this:
var y = "Hello World";
var x = y.Substring(0, y.Length - 5);
Console.WriteLine(x);


to this:
y = "Hello World"
x = y[:-5]
print(x)

Name: Anonymous 2019-01-27 13:48

>>4
This has nothing to do with typing. It's just explicit vs. implicit declaration of variables.
Explicit is better by the way.

Name: Anonymous 2019-01-27 14:49

>>4
Are you retarded or trolling?

Name: Anonymous 2019-01-27 15:36

>>1
Weakly typed is a term used by people who have no clue about language design and type theory, in addition of not having a definition that makes sense. A better term would be "crappy languages".

In any case, these languages are popular because shitty things tend to be popular in general. Consider Java and Islam for example.

Name: Anonymous 2019-01-27 16:48

>>7
like C and scheme?

Name: Anonymous 2019-01-27 21:24

>>8
Yes, but the thing is, people tend to consider Scheme as strongly typed. Again, such terms make no sense.

Name: Anonymous 2019-01-28 6:36

They exist because people made them.
They get used because users choose them.
It's probably a good idea to not make more of them.

Name: Anonymous 2019-01-28 6:58

>>1
strong and weak typing has nothing to do with compile-time or runtime, you mean dynamic vs static. weak typing a shit, but there can be weak typing done statically - for example, C will do a lot of implicit casts. on the other hand, FIOC will complain about implicit casts but it will do so at runtime because there's not compile-time checking there. but in general your're are right, strong static typing is preferable as long as the types can be inferred. why the fuck isn't there a Lisp/Scheme dialect with strong static inferred types? the only one with a reasonable type system that I know of is Typed Racket but its inference is shit and any more general function requires abominations like this weird foldl: https://docs.racket-lang.org/ts-guide/types.html#%28part._.Non-.Uniform_.Variable-.Arity_.Functions%29 also check'em

Don't change these.
Name: Email:
Entire Thread Thread List