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

Uncucked languages

Name: Anonymous 2018-10-24 20:22

Any (((modern))) languages not infested with SJWs (no code of conduct etc.)? I like Crystal, but it literally uses CorawhineAda's code of conduct...

Preferably compiled/statically typed.

Name: Anonymous 2018-10-24 20:35

Agda and Idris.

Name: Anonymous 2018-10-24 20:52

>>2
he said uncucked, not unused

Name: Anonymous 2018-10-24 21:15

Ruby

Name: Anonymous 2018-10-24 21:18

>>4
ruby is dying, people are switching to python instead

Name: Anonymous 2018-10-24 21:26

>>5
Goot thing I never bothered to learn it.

Name: Anonymous 2018-10-24 22:26

>>3
Both are uncucked and unused, which make them objectively the best.

Name: Anonymous 2018-10-24 23:24

>>3
more used than crystal

Name: Anonymous 2018-10-25 5:12

>>1
Having a project with CoC written by SJW is a sign its run by spineless cucks and will be shut down easily. Its like a huge banner "We will sacrifice technical integrity for SJW compliance"

Name: Anonymous 2018-10-25 5:48

>>5
python is dying, people are switching to go instead

Name: Anonymous 2018-10-25 6:09

>>10
but go is a completely different language. statically typed, compiled, pedantic about formatting and imports, lol no generics, check my dubs

Name: Anonymous 2018-10-25 6:52

>>11
go is watered down python with multi-threading and static typing

Name: Anonymous 2018-10-25 6:53

>>12
it's also not as flexible, not as readable and far more boilerplatey

Name: Anonymous 2018-10-25 7:03

>>1
Why does a code of conduct preclude you from using a language? It has zero impact on development.

Name: Anonymous 2018-10-25 7:11

>>13
yes. intelligent prog rammers should use c# or d instead

Name: Anonymous 2018-10-25 7:11

Name: Anonymous 2018-10-25 7:14

>>15
I'd like c# (it's basically java done right) and f# (it's basically less french ocaml) if they weren't so tied to windows. is there even a decent IDE for them on *nixes?

Name: Anonymous 2018-10-25 7:15

>>17
only development is tied to windows

Name: Anonymous 2018-10-25 7:21

Name: Anonymous 2018-10-25 7:25

>>18
even if it's true (weren't even parts of stdlib non-portable?), I usually develop on *nix

Name: Anonymous 2018-10-25 7:30

>>19
bad

>>20
then use d

Name: Anonymous 2018-10-25 7:34

>>21
then use dubs

Name: Anonymous 2018-10-25 7:36

>>21
d seems to have nice metaprogramming features (especially when compared to sepples templates, rust macros and #include <void.h>) but the ecosystem is confusing

Name: Anonymous 2018-10-25 7:43

>>23
aren't they always confusing?
if you don't know some things about windows the c# ecosystem sometimes will seem strange as well.

Name: Anonymous 2018-10-25 7:50

>>24
c# ecosystem on windows is quite easy due to good tooling. d is a mess of incompatible compilers and language version, and it gets exponentially worse when you want to use it without garbage collector as even parts of the stdlib use it but it's not obvious which ones

Name: Anonymous 2018-10-25 7:56

>>25
didn't they solve that? i though that was only in the 2000s

Name: Anonymous 2018-10-25 7:58

Name: Anonymous 2018-10-25 7:59

>>26-27
it disables features that parts of the stdlib use, like classes and exceptions.

Name: Anonymous 2018-10-25 8:02

Name: Anonymous 2018-10-25 8:12

>>25
>D features not available with BetterC:

>Garbage Collection
>TypeInfo and ModuleInfo
>Classes
>Built-in threading (e.g. core.thread)
>Dynamic arrays (though slices of static arrays work) and associative arrays
>Exceptions
>final switch
>synchronized and core.sync
>Static module constructors or destructors
How is that confusing you brainlet?

Name: Anonymous 2018-10-25 8:14

>>30
These are D-level features.
C++ classes, C asserts, RAII and most of C++ stuff works.
Exceptions are not needed for most of it.

Name: Anonymous 2018-10-25 8:20

Retained Features

Nearly the full language remains available. Highlights include:

Unrestricted use of compile-time features
Full metaprogramming facilities
Nested functions, nested structs, delegates and lambdas
Member functions, constructors, destructors, operating overloading, etc.
The full module system
Array slicing, and array bounds checking
RAII (yes, it can work without exceptions)
scope(exit)
Memory safety protections
Interfacing with C++
COM classes and C++ classes
assert failures are directed to the C runtime library
switch with strings
unittest

Name: Anonymous 2018-10-25 8:28

>>31
It was more about how it is easily understandable which features can be used with or without gc, as they're all listed in >>29.

Name: Anonymous 2018-10-25 8:31

>>33
These (useless,except associative arrays) features are disabled. You would get a compile error.

Name: Anonymous 2018-10-25 8:39

>>34
They're not because we're using the gc because we're using d as a replacement for go Edited on 25/10/2018 08:40.

Name: Anonymous 2018-10-25 8:43

>>35
using go
cannot comprehend why gc is bad
calling people brainlets

Name: Anonymous 2018-10-25 8:44

>>30
it's confusing because it requires knowing which parts of the stdlib use those features, which is not something a user should be required to know. which other languages require you to know stdlib implementation details?

Name: Anonymous 2018-10-25 8:44

>>36
who are you quoting?

Name: Anonymous 2018-10-25 8:49

>>38
Enlightened Go Experts who somehow became dissatisfied with their perfect language.

Name: Anonymous 2018-10-25 8:50

>>37
Each month the runtime and stdlib made more and more free of GC usage, not for betterC but because its plain faster and doesn't waste memory. Edited on 25/10/2018 08:51.

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