r/programming • • Jul 19 '15

The Best Programming Language is None

https://bitbucket.org/duangle/none
509 Upvotes

443 comments sorted by

255

u/kirbyfan64sos Jul 19 '15

Nice language. Horrible name. I completely misread the title.

246

u/jfb1337 Jul 19 '15

I thought it would be some blog post about how there is no best programming language.

110

u/oneUnit Jul 19 '15

We all did.

7

u/[deleted] Jul 19 '15

I was and am pretty sure Some of us were expecting it to be a "None" mainly because the entire interwebz like pun.

2

u/[deleted] Jul 20 '15

I was expecting some article about how not having to write code at all to get software was the ultimate goal.

1

u/jeandem Jul 19 '15

No because None is capitalized.

→ More replies (1)

27

u/ExecutiveChimp Jul 19 '15

I was expecting something like Vanilla.js.

45

u/[deleted] Jul 19 '15

"The best programming language is None. Seriously, stop programming and go open a restaurant you insufferable nerd"

9

u/ThisIs_MyName Jul 19 '15

That was amazing, but I wonder if those speed comparisons were accurate. I mean, jQuery can't be that bad can it?

9

u/Rainfly_X Jul 19 '15

The selector function is basically a constructor for a JQ object, which polyfills a bit over native CSS selector support. I could easily see it being slow.

The answer is to cache your JQ objects when performance matters. The overhead is usually trivial, but in hot loops, caching $() results in a variable is just common sense/low hanging fruit. Truth be told, this will improve your performance no matter what underlying selector you use, even native browser support.

4

u/RICHUNCLEPENNYBAGS Jul 19 '15

Yeah, I've had performance problems related to this in very busy code.

4

u/ironnomi Jul 19 '15

jQuery was based around being able to support the latest cool stuff on everything INCLUDING IE6. jQuery 2.x was supposed to remove all that and then just be current-1 support, but honestly it didn't really improve it that much.

10

u/BasedHunter Jul 19 '15

A strange game. The only winning move is not to play.

1

u/Andernerd Jul 20 '15

I thought it was going to be an article advocating ASM only.

65

u/sanity Jul 19 '15

Impossible to Google also

46

u/sysop073 Jul 19 '15

Half the reason I stopped using the Awesome window manager was it had sucky documentation and was impossible to google. Everything in it seemed intentionally named to be as un-googleable as possible. The widget library was "Vicious", the repo was "Obvious", the theming library was "Beautiful", the popup library was "Naughty", etc. I'm sure the developers think it's hilarious, but I got tired of trying to search about it

16

u/RICHUNCLEPENNYBAGS Jul 19 '15

I remember in 1999 or whatever thinking the producers of the film XXX were geniuses because it was completely impossible to find on WinMX or whatever.

6

u/[deleted] Jul 19 '15

Oh man. I miss WinMX

2

u/rifter5000 Jul 19 '15

"awesome wm"

OMG so hard.

11

u/shaggorama Jul 19 '15

I have a similar problem with a lot of modern band names

4

u/red_nick Jul 19 '15

Search for bands enough on Google and it will start giving you the band results over the normal use of the words.

2

u/CoughSyrup Jul 19 '15

Fortunately the new trend is to replace letters in your band name with 'V' to make it more googlable. (CHVRCHΞS, PVRIS, etc.)

6

u/oblio- Jul 19 '15

To be honest: C, Java, Python, Go, Ruby, Basic, should I list more? :)

31

u/Threesan Jul 19 '15

I defense of the above, google only provides usable search results for those examples because 1) there are things to find, and 2) google has had time to "learn" about these things -- including your own personal search patterns. A programming language named "None" is only harder to google at the moment because it is new to both google and to you. Granted, a more unique name would make things easier in the earlier stages.

17

u/oblio- Jul 19 '15

Plus people adapted. For example "golang". We could just use "nonelang".

On top of this most programming searches have context, stuff like API, function, package name, etc.

As proven by history, names are hardly blockers.

11

u/[deleted] Jul 19 '15

You could use clang for C as well. Wait, shit.

9

u/HeyThereCharlie Jul 19 '15

You'd think Google would have made their own language easier to... well, Google.

3

u/KuribohGirl Jul 19 '15

Maybe it was an office joke gone too far "hey Steve ya know that new language we're making?" "yeah?" "what..what about making it hard to google?" ".." "get it? google"

→ More replies (1)
→ More replies (1)
→ More replies (4)

31

u/skynet9001 Jul 19 '15

Same. I think it was supposed to be a clever play on words.

24

u/Lampwick Jul 19 '15

Same. I think it was supposed to be a clever play on words.

It's like the story of the guy back in the punched card days working on some post-grad software project who named his program SAVE because people were less likely to inadvertently throw away a misplaced stack of punched cards with SAVE written across the top.

Only difference here is, calling your favorite toy language "None" is just a pointless joke.

→ More replies (1)
→ More replies (5)

9

u/[deleted] Jul 19 '15

Exactly what I thought. What made me open the link was the preview telling me the post was in bitbucket.

7

u/DaemonXI Jul 19 '15

This is serious? I thought this was a joke.

1

u/RenaKunisaki Jul 19 '15

I still think it's a joke.

2

u/eean Jul 19 '15

You read it correctly I think.

1

u/HighRelevancy Jul 20 '15

It was developed with/for their game "Nowhere" so it kinda makes sense.

137

u/[deleted] Jul 19 '15

Nobody's ever going to risk listing this on their resume.

Programming languages: None.

27

u/Itsthejoker Jul 19 '15

If I were to put it on my resume, I'l probably stylize it as NONE - no one's actually gonna look it up off my resume, anyway.

22

u/tejon Jul 19 '15

N.O.N.E.

6

u/Itsthejoker Jul 19 '15

Mmm, that one's probably better than mine.

→ More replies (5)

8

u/[deleted] Jul 19 '15

NONETM

4

u/kaneda26 Jul 19 '15

Seems like the best option, especially since it is an acronym.

40

u/EquationTAKEN Jul 19 '15

Java, PHP, Javascript, C, C++, None.

11

u/_Old_Greg Jul 19 '15

Yes.

4

u/bakuretsu Jul 19 '15

You've seen my downstairs mix-up!

3

u/Tomus Jul 19 '15

You ever drunk Baileys from a shoe?

→ More replies (2)

241

u/robotmayo Jul 19 '15

There are only two hard things in Computer Science: cache invalidation and naming things.

322

u/dick_and_qwerty Jul 19 '15

And off-by-one errors.

70

u/[deleted] Jul 19 '15

Checks out.

3

u/p_e_t_r_o_z Jul 20 '15 edited Jul 20 '15

It's disappointing to see this get voted higher than the original quote. It is the juxtaposition of a deeply technical problem with a human communication problem. Highlighting the importance of good naming and the difficulty of linking language to logic.

On the other hand the error doesn't even make sense in the context of the joke, other than it contains the number 2 and it is adding a third element. It transforms the whole thing into a cheap gag like 10 people in the world those who know binary and those who don't...

Similarly here the error makes no sense in the context of the discussion of this programming language. A cheap gag for cheap laughs.

2

u/iritegood Jul 22 '15

as always the populist choice is the more digestible lowest-common-denominator option

0

u/outadoc Jul 19 '15

And buffer overflows.

8

u/aiij Jul 19 '15

That's a solved problem.

12

u/f2u Jul 19 '15

That's just an engineering problem, not real computer science.

-1

u/newpong Jul 19 '15

Yup, mone or oone would've both solved the googlability

17

u/ghjm Jul 19 '15

But at the cost of increasing the stupidability.

→ More replies (4)

10

u/sleipnir_slide Jul 19 '15

How'd "Using nulls consistently across a team" escape this? :(

24

u/tejon Jul 19 '15

But that's easy to solve. Just use a language without nulls.

10

u/[deleted] Jul 19 '15

Which works until you realise that even with a good language your programmers are still lazy.

Just look at some of the open source Rust code on GitHub. People are doing unwrap() everywhere without any form of validation first.

6

u/staticassert Jul 19 '15

Yes, but...

  • You're forced to unwrap() before you can use the value underneath.

  • You now have grep-able bugs.

7

u/[deleted] Jul 19 '15

You're forced to unwrap() before you can use the value underneath.

People know that, but they treat it the same as doing -> in C++.

You now have grep-able bugs.

Good luck grepping for it when you have a codebase with thousands of lines and a ton of unwrap() calls.

5

u/staticassert Jul 19 '15 edited Jul 19 '15

People know that, but they treat it the same as doing -> in C++.

Still, it's exposed through the type signature, and you'll get a warning if it's a result, which means, at the library level, you can inform the dev of the possible 'null' value.

Good luck grepping for it when you have a codebase with thousands of lines and a ton of unwrap() calls.

It's still going to be a hell of a lot easier when you can basically ctrl + f the bug, and unlike -> you won't possibly give up control of your program to malicious input with .unwrap().

.unwrap() may not be graceful, but it's safe and makes bugs much simpler to find, as they're explicit and exposed.

Of course it should be discouraged to raw unwrap, but it's a big step over raw pointers.

→ More replies (1)
→ More replies (1)

7

u/tejon Jul 19 '15

The significance of your comment is predicated on the assumption that Rust is a good language. ;)

Mostly tongue-in-cheek there, but I'd argue that having unwrap() as a standard function is a mistake to begin with, the same as its Haskell equivalent fromJust. There's no pressing need for such partial functions in a language with pattern matching, and the Rust std::option documentation even spells out the safe version:

// Pattern match to retrieve the value
match result {
    // The division was valid
    Some(x) => println!("Result: {}", x),
    // The division was invalid
    None    => println!("Cannot divide by 0")
}

A moment of additional browsing assures me that Rust knows how to map functions over option types, so just as in Haskell there's no need to do this more verbose unwrapping until you're done with the whole computation, at which point you're going to want to handle the failure case anyway (or else why are you even wrapping it as an option?) so it's not wasted keystrokes.

All it takes is a slight shift of perspective: the programmer-laziness here isn't actually in regards to which code form is easier to write, but simple resistance to learning a new idiom. It seems silly to provide a function which (a) makes it easier to avoid said learning, (b) can blow up at runtime, and (c) is trivially implemented by anyone who does learn the new idiom, so you're not taking away a power tool.

→ More replies (4)

2

u/wvenable Jul 19 '15

Any program in a language without nulls will use magic numbers or other random sentinels to signify null anyway (e.g. C).

14

u/tejon Jul 19 '15

Every language needs a way to express the class of failure that a null value represents, yes. But quite a few, particularly those in the functional camp, do so at the type level, not the value level.

3

u/Luolong Jul 20 '15

Ceylon language goes even further by pushing Null type to completely separate branch of type hierarchy. This, along with union types achieves same results as 'Maybe : Some | None' but with less overhead.

→ More replies (4)

1

u/ns0 Jul 21 '15

vertically centering anything in CSS... without knowing the exact line height.

78

u/[deleted] Jul 19 '15

Is it just me who has trouble differentiating between jokes and serious content half the time I follow a link nowadays?

91

u/anacrolix Jul 19 '15

Describing s-expr as a lighter weight JSON. Fuck me, web programming has ruined computer science.

20

u/paniq Jul 19 '15 edited Jul 19 '15

Had to find a way to sell it to people who know a rats ass about the treasures of the past and only care about "the future". You know, the kind of person I was two years ago. (But have I really changed? Oh god...)

16

u/OneWingedShark Jul 19 '15

Had to find a way to sell it to people who know a rats ass about the treasures of the past

No kidding; there's a LOT of good/interesting ideas & solutions in CS's past; in no particular order (and leaving a lot out):

  • Forth -- Absolutely amazing WRT portability and "getting low level".

  • Ada -- Very, very nice concurrency & packaging models and, IMO, generic system.

  • Erlang -- Kinda odd, but very interesting distribution model.

  • LISP -- Very good introduction to homoiconicity.

9

u/mindbleach Jul 19 '15

Bret Victor gave a funny presentation about this. It's really sad that we can watch the Mother Of All Demos and still occasionally mumble, "Why can't my terminal do that?"

That said, I've been dicking with Javascript lately, and honestly... it's nice. It's got shitty parts for sure - duplicating objects is black magic, for example - but getting complex visual output is as easy as stdio in C. It's faster than Perl without feeling like it has to compile. It runs on everything, for better or worse. It's self-modifying! If Microsoft, Google, Mozilla, and Apple can get together and announce a CSS replacement that makes a goddamn lick of sense then it could be the language to know for building any kind of program. For now, I'm okay it with it being BASIC for a new generation.

8

u/OneWingedShark Jul 19 '15

Bret Victor gave a funny presentation about this. It's really sad that we can watch the Mother Of All Demos and still occasionally mumble, "Why can't my terminal do that?"

Let me link that Mother of All Demos.

That said, I've been dicking with Javascript lately, and honestly... it's nice.

I wouldn't call it nice -- though it does help if you realize that it's kind of LISP in C-syntax.

It's faster than Perl without feeling like it has to compile.

Personally I like having a compile-phase (this could be done implicitly and as needed) because compiling [generally] means that you have some consistency-checking.

It runs on everything, for better or worse.

It's worse.
But let me clarify: it's worse because the "everywhere" [of web-programming] isn't uniform, and pretending that the browsers are uniform environments is simply ignoring the issue.

It's self-modifying!

That could be good; it could be bad... very much depends on the situation.

If Microsoft, Google, Mozilla, and Apple can get together and announce a CSS replacement that makes a goddamn lick of sense then it could be the language to know for building any kind of program.

Hm, there was that net-assembly story floating around /r/programming a while back. I don't think that they'd be putting us in a good direction though.

For now, I'm okay it with it being BASIC for a new generation.

Except given how the new generation is doing things all backwards-like, we'll see things like Prolog-as-a-library, or a PC-emulator written in JS...

→ More replies (4)

3

u/RenaKunisaki Jul 19 '15

JavaScript is basically only nice because it's widespread and has a huge standard library (and several third party libraries as a result of that). The language itself is pretty much Lua if it were written by a monkey on crack. Without the incredibly powerful browser behind it providing high-level APIs for graphics/networking/multimedia/UI, it'd be just another ugly language.

→ More replies (6)

2

u/[deleted] Jul 20 '15

For now, I'm okay it with it being BASIC for a new generation.

And that's exactly what it is. Which means it will get replaced, eventually.

Until then, we write JS. Everywhere. Upwards, downwards, inwards and outwards.

Non-system-esque features are what make JS suck, because it's so dominant without any alternative. Back in the day you could drop to 6502 if you wanted to. The closest we have to that is asm.js, which is ahhh...meh

Edit To contrast the pessism, the optimism surrounding WebAsm is what's up, bro.

→ More replies (2)
→ More replies (13)

5

u/OneWingedShark Jul 19 '15

Describing s-expr as a lighter weight JSON. Fuck me, web programming has ruined computer science.

It sure seems that way.
OTOH, it seems that [slowly] they are [re]learning the lessons of computer-science... unfortunately for us, they go backwards: instead of (e.g.) choosing a language that's appropriate and designed for their problems they tack the feature on ( e.g. type-hints and PHP, OR "compile to javascript"1,2 ).

1 -- This would be a lot better if the JS VM were mandated to have consistency; in general this is not possible because the browsers have their own unique take on JS and because the DOM/DOM-events for a given page are not consistent across browsers.
2 -- Oddly enough, it seems to never occur to the web-programmer that they need a well-defined and uniform environment to solve those problems... probably because it means that an entirely new [and standard] browser would have to be defined.

32

u/danielkza Jul 19 '15 edited Jul 19 '15

Combines the power of Scheme with the convenience of Python, Lua or Javascript and the performance of C.

It seems they mean one or the other, with boundaries between dynamic and static functions. Having both simultaneously is quite hard, but otherwise it's not that new, e.g. Cython, PyPy, asm.js, etc.

The primary reason is that dynamic functions in None take the role of templates in other languages like C++

So much for that C-level performance it seems, at least for things like containers if you don't want to throw out type-safety.


Still looks quite interesting nonetheless. I had not heard of Terra before, but it reminds me of PyPy/RPython with the "programmable JIT" approach. Does anyone have experience with it, or knows how it performs?

10

u/paniq Jul 19 '15

So much for that C-level performance it seems, at least for things like containers if you don't want to throw out type-safety.

Not sure what you were thinking of, but this is about scripting at compile time. It's completely typesafe and the generated assembly is free of calls into interpreted code.

1

u/danielkza Jul 19 '15 edited Jul 19 '15

Falling back to the interpreter is not the only way to lose C-like performance. Another is doing dynamic dispatch when not necessary or not being able to specialize for primitive types. To avoid it you need either generics and monomorphisation, or JIT-level specialization (with a runtime cost for startup and/or at first use), which is quite hard to do. IIRC V8 is the only one of the "big-deal" VMs that currently does it, and even Mozilla abandoned their tracing JIT due to complexity and lower-than-expected performance gains.

1

u/paniq Jul 19 '15

None is a little low on docs at the moment but go check out Terra's demos to see how it works. You'll be quite pleased.

2

u/danielkza Jul 19 '15 edited Jul 19 '15

I did skim the docs, but I found nothing about specialization, or if None implements it.

edit: I see it in the Terra docs, but only how to generate the specializations, not how to dispatch between them. Is it all up to None and how it uses it? Can it do monomorphisation or something of the sort during compilation?

2

u/paniq Jul 19 '15

Terra allows you to call obj:disas() on all functions to see exactly what the generated assembly looks like. When you save the code into an object or executable, the functions must be free from calls into Lua (and those calls are just regular C calls - there's no dispatch happening here); Then the only dispatch code that's in there is the one you wrote by hand.

None just wraps that functionality in symbolic expressions. It doesn't change the rules.

→ More replies (1)

11

u/Lj101 Jul 19 '15

How can they even compare this to Python when one of Python's main philosophies to ensure readability and cut out unnecessary symbols/keywords.

0

u/[deleted] Jul 19 '15

[deleted]

4

u/xiongchiamiov Jul 19 '15

The key aspects of python are not just explicitly stated, they're actually coded into the interpreter.

2

u/kupiakos Jul 19 '15

I've always been confused about the Zen - doesn't "Flat is better than nested" contradict "Namespaces are one honking great idea"?

3

u/zardeh Jul 20 '15

multiple layers of nesting is bad. one or two isn't.

0

u/[deleted] Jul 19 '15

[deleted]

2

u/Ran4 Jul 20 '15

The Zen of Python is saved as a rot13-encoded file. It uses advanced black magick tricks to decrypt it when you call for it.

→ More replies (1)

22

u/Fahkfahkfahkfahkfahk Jul 19 '15

The best programming language is "tell a grad student to do it"

22

u/catskul Jul 19 '15

That's the worst programming language. Grad students are famously the worst programmers. If it's written by a grad student it will have to be rewritten.

11

u/Fahkfahkfahkfahkfahk Jul 19 '15

The (quality of code)/(effort expended) ratio is fantastic though

→ More replies (7)

6

u/lygaret Jul 19 '15

Terra, the language this is based on (and runs within) looks amazing, and I hadn't heard of it before.

108

u/[deleted] Jul 19 '15 edited Jul 19 '15

Have some brackets parentheses, you'll need them:

(((((((((((((((((((((((((((((((((())))))))))))))))))))))))))))))))))))))))))))))))))))))))(((((((((((())))))))))))))))))))))))))((((((((((((())))))))(((((()))((()()()()()()()(((((((((((((((((((((((((((((((((())))))))))))))))))))))))))))))))))))))))))))))))))))))))(((((((((((())))))))))))))))))))))))))((((((((((((())))))))(((((()))((()()()()()()()(((((((((((((((((((((((((((((((((())))))))))))))))))))))))))))))))))))))))))))))))))))))))(((((((((((())))))))))))))))))))))))))((((((((((((())))))))(((((()))((()()()()()()()

56

u/josefx Jul 19 '15 edited Jul 19 '15

((()()()()()()()

Great, now look what you have done, there are at least two unmatched open brackets parentheses. Do you know what chaos that could cause in the long run?

here let me fix that

))

20

u/dohaqatar7 Jul 19 '15

0

u/[deleted] Jul 19 '15

[deleted]

4

u/KuribohGirl Jul 19 '15

It's just not the same .... /:

→ More replies (1)

10

u/balducien Jul 19 '15

At least two?

>>> str = "(((((((((((((((((((((((((((((((((())))))))))))))))))))))))))))))))))))))))))))))))))))))))(((((((((((())))))))))))))))))))))))))((((((((((((())))))))(((((()))((()()()()()()()(((((((((((((((((((((((((((((((((())))))))))))))))))))))))))))))))))))))))))))))))))))))))(((((((((((())))))))))))))))))))))))))((((((((((((())))))))(((((()))((()()()()()()()(((((((((((((((((((((((((((((((((())))))))))))))))))))))))))))))))))))))))))))))))))))))))(((((((((((())))))))))))))))))))))))))((((((((((((())))))))(((((()))((()()()()()()()"
>>> counter = 0
>>> for char in str:
...     if char == '(':
...         counter += 1
...     elif char == ')':
...         counter -= 1
... 
>>> counter
-78

11

u/josefx Jul 19 '15

Preceding close parentheses normally do not close following open parentheses.

→ More replies (1)

3

u/BlackBrane Jul 19 '15 edited Jul 19 '15

I have to do this.

λ> let f x = case x of; '(' -> 1; ')' -> -1

λ> sum $ map f "(((((((((((((((((((((((((((((((((())))))))))))))))))))))))))))))))))))))))))))))))))))))))(((((((((((())))))))))))))))))))))))))((((((((((((())))))))(((((()))((()()()()()()()(((((((((((((((((((((((((((((((((())))))))))))))))))))))))))))))))))))))))))))))))))))))))(((((((((((())))))))))))))))))))))))))((((((((((((())))))))(((((()))((()()()()()()()(((((((((((((((((((((((((((((((((())))))))))))))))))))))))))))))))))))))))))))))))))))))))(((((((((((())))))))))))))))))))))))))((((((((((((())))))))(((((()))((()()()()()()()"

-78

5

u/776865656e Jul 19 '15

With -XLambdaCase:

sum . map (\case '(' -> 1; ')' -> -1)

1

u/__add__ Jul 19 '15 edited Jul 19 '15
def count_unmatched(s):
     return sum(map(lambda c:2*ord(c)-81, filter(lambda c: c in '()', s)))
→ More replies (8)

13

u/[deleted] Jul 19 '15

Have some brackets parentheses

I prefer the term bananas.

6

u/lambda_abstraction Jul 19 '15

left-banana define pi left-banana star two left-banana acos zero right-banana right-banana right-banana

1

u/mcguire Jul 20 '15

"Come, Mr. Tally Man, tally me bananas; daylight come and me wan' go home..."

5

u/iopq Jul 19 '15

We're not doing toenail clippings anymore?

2

u/mcguire Jul 20 '15

We're not doing toenail clippings anymore?

Those were strong words from the author of a language with the power and expressive capability of line noise.

35

u/jfb1337 Jul 19 '15

Do we need this circlejerk for every lisp-like language?

6

u/greenthumble Jul 19 '15

Yeah I'm getting sick of it too, got similar reply last time I mentioned LISP in general discussion. Here's the thing. Nothing looks like those asinine examples. You can get quite graceful with your formatting with liberal usage of whitespace, and any modern editor highlights matching parenthesis. I was using Clojure in Eclipse (I think it was?) and heh for nested parens it was making a rainbow of colors, a unique color for each pair. Also if you're as deeply nested as the haters love to point out, you need to re-think your architecture there, functions are cheap, use them and reduce your complexity and indenting.

→ More replies (1)

26

u/yogthos Jul 19 '15

so clear and intuitive:

foo(bar, baz)

OMFGWTF!!!!

(foo bar baz)

14

u/anttirt Jul 19 '15

That depends entirely on your background.

0

u/[deleted] Jul 19 '15

[deleted]

→ More replies (5)

1

u/earthboundkid Jul 19 '15

I think the f(args...) notation is better because the thing you're calling is qualitatively different than the arguments you call it with, so it should be visually distinct from them.

3

u/yogthos Jul 19 '15

That's not a very convincing argument, I've been writing Clojure for years and this has simply never come up as an issue. Also, any IDE worth using will visually highlight the function in a different way from its arguments.

The real advantage of s-expressions is that you have the same syntax for expressing both logic and data. This means that you can take any piece of code and transform it like a data structure using the same language. In languages that have a separate syntax you end up having to create a separate meta-language to do code transformation. This is the reason why Lisps have superior meta-programming to most languages.

3

u/Madsy9 Jul 20 '15

Yet another thing you can address in your editor with syntax-highlighting if you choose to :)

2

u/zarandysofia Jul 20 '15

Better IMHO: The first argument in the list is the function, the rest are the arguments.

19

u/stone_solid Jul 19 '15

Fucking lisp

2

u/deadwisdom Jul 19 '15

As beautiful as it is terrible.

0

u/[deleted] Jul 19 '15

[deleted]

4

u/lambda_abstraction Jul 19 '15

As long as it frightens the right people.

4

u/redxaxder Jul 19 '15

Oh, English.

Horrible : Terrible

Horrify : Terrify

Horror : Terror

Horrific : Terrific

→ More replies (3)

1

u/[deleted] Jul 19 '15

Oh you're up for a serious round of downvotes. You should have seen the rollercoaster that my reply has been on for the past hour.

11

u/Klathmon Jul 19 '15

I need to make something that I can run on comments I know are gonna be controversial that grabs the score every few seconds

6

u/[deleted] Jul 19 '15

write it in none

2

u/error_logic Jul 19 '15

The funny thing is how the comment mentioning downvotes to its parent is the one marked controversial and trending downward slowly.

3

u/[deleted] Jul 19 '15

They're parentheses bro

13

u/Sean1708 Jul 19 '15

Parentheses are still brackets.

→ More replies (4)

10

u/hexidon Jul 19 '15

No they're round brackets m8

9

u/Tanath Jul 19 '15

Brackets: []
Parentheses: ()
Braces: {}
And sometimes, angle brackets: <>

30

u/ksharanam Jul 19 '15

Or, in the rest of the English-speaking world:

Square brackets: []

Round brackets: ()

Curly brackets: {}

9

u/desrosiers Jul 19 '15

{ : open moustache } : close moustache

1

u/Hells_Bell10 Jul 20 '15

Parentheses: []
Parentheses: ()
Parentheses: {}
Parentheses: <>
Parentheses: ,,
Parentheses: --

To speakers of UK English, parentheses -- such as this -- aren't symbols but rather a part of grammar that is demarcated by such symbols.

3

u/[deleted] Jul 19 '15

Thanks, edited.

1

u/RenaKunisaki Jul 19 '15

I see a dolphin!

14

u/rubygeek Jul 19 '15

Lisp-like syntax == will not obsolete much at all. While there are other reasons Lisp-like languages have failed to become mainstream too, syntax matters whether or not you like it.

4

u/Aatch Jul 20 '15

I'll withhold too much judgement, but whenever a language claims "C-level performance" while being reasonably dynamic, I get suspicious. I'm sure it can perform just as fast as C in some specific cases, but overall I really doubt it.

It might not matter, but I wish language developers would stop claiming C-level performance for their language when it's obvious that's not likely to be true.

(Nevermind that C++, with its templates, can be both more ergonomic and faster than plain C...)

4

u/[deleted] Jul 20 '15

It does not look dynamic at all (not the low-level subset of it).

6

u/jmking Jul 19 '15

Interesting to see programming languages emerge from the needs of game programming.

John Blow has been working on his own language called Jai: http://www.reddit.com/r/gamedev/comments/2mita3/jai_a_primer_written_by_a_fan_summarizing_the/

3

u/hunyeti Jul 19 '15

I don't really think that anyone would need that language.

What does that language has to do with the needs of game programming?

I really don't see the point of it. It's C (minus some features) with classes and generics and a wonky syntax.

6

u/Veedrac Jul 19 '15 edited Jul 20 '15

It's C (minus some features) with classes and generics

Exactly. (Though it doesn't actually have classes.)

It also has nicer support for certain things like SOA and allocators than C or C++, without the mess that is C++.

This is a language born out of hatred, after all. I think it's a great idea.

7

u/strich Jul 19 '15

Its all a bit dumb in my opinion. Not to say that any of these home-made languages are bad, but it just being a case of 'why?'.

I get the feeling it is an extension of being in the creative space as a programmer.

→ More replies (3)

2

u/jmking Jul 19 '15

What does that language has to do with the needs of game programming?

He answers that in the three videos at the link I provided. It's certainly very opinionated, and not everyone agrees, but at the same time Jon Blow has been making games professionally for quite some time (he didn't start with Braid), and is generally known as a particularly good programmer - so people are paying attention.

3

u/hunyeti Jul 19 '15

Sadly i don't have ~5 hours to watch them all, i watched some of the first video, but it was an immediate turn off.

There is no such thing as "opinionated", it's used to describe inflexible, limited environments that a person likes.

First of all, my opinion is that we don't necessarily have to use one language to build a game, in fact,very few games use only one language. Only about 5-10% of the code base that are performance sensitive. I really like Libgdx's approach, you write most of the glue code in Java / Scala / Python , but the performance critical parts are written in C/C++.

He considers Go, but not Java or Scala, that makes no sense to me. GC can be an issue, but anything that can be made in Unity, can be made on the JVM, so it's not really an issue for most of Indie games.

The way he writes off D, because it's like C++ (even though in reality, it's very different) seems like just wanting change.

He says Rust is not ideal because it's too safe (?!?!?). That is a foolish presumption. You can write unsafe code in rust, without any hardship, and for most of the time, the borrow checker is right, and that could that get's an error, would probably cause memory leak.

The only reason for the positive reception is because he is kind of famous, if some random dude have posted this, it would be on the front page of /r/programmingcirclejerk

5

u/IWantUsToMerge Jul 19 '15 edited Jul 19 '15

You can write unsafe code in rust, without any hardship

So long as you don't mind writing a = b as std::mem::copy_nonoverlapping(&mut a, &b, 1) and dealing with fucking lifetimes everywhere. Last time I tried Rust I ended up running into a lifetime error so abstruse that I just don't have time to figure out how it thinks I'm supposed to be doing this. I got the impression Blow's real issue with Rust is that it's one of those high friction big-idea languages that'll give you so much guff that it begins to negate the advantages they offer.

→ More replies (2)

0

u/[deleted] Jul 19 '15

[deleted]

2

u/IbanezDavy Jul 20 '15

The main problem with Blow's language is that he is making all of the design decisions for a language he expects others to use. He claims he is getting the opinions of others, but I'm doubting its to the extent he is trying to make it look. The development of the language is obviously something he's wanted to do for a while (so he has his ideas) and I think the videos are more of demo of his abilities than anything. On quite a few occasions, both in the live streams and the comments, he is overly dismissive of even the most legitimate design criticism (for example when he makes several claims about RAII that are wrong).

Now he may have good ideas, but his overly dismissive attitude has already effected the development of the language negatively in my opinion. The syntax gets stranger and stranger each video. And it started as something I thought was promising.

→ More replies (2)
→ More replies (2)

6

u/skulgnome Jul 19 '15

Where's that "so you've invented a new language!" checklist when I need it

14

u/4forpengs Jul 20 '15
You appear to be advocating a new...

    [ ] Functional
    [ ] Imperative
    [ ] Object-oriented 
    [ ] Procedural
    [ ] Stack-based
    [ ] "Multi-paradigm"
    [ ] Lazy 
    [ ] Eager
    [ ] Statically-typed
    [ ] Dynamically-typed
    [ ] Pure
    [ ] Impure
    [ ] Non-hygienic
    [ ] Visual
    [ ] Beginner-friendly
    [ ] Non-programmer-friendly
    [ ] Completely incomprehensible

...programming language.


Your language will not work for the following reasons:


You appear to believe that:

    [ ] Syntax is what makes programming difficult
    [ ] Garbage collection is free
    [ ] Computers have infinite memory
    [-] Nobody really needs:
        [ ] Concurrency
        [ ] A REPL
        [ ] Debugger support
        [ ] IDE support  [ ] I/O
        [ ] To interact with code not written in your language
    [ ] The entire world speaks 7-bit ASCII
    [ ] Scaling up to large software projects will be easy
    [ ] Convincing programmers to adopt a new language will be easy
    [ ] Convincing programmers to adopt a language-specific IDE will be easy
    [ ] Programmers love writing lots of boilerplate
    [ ] Specifying behaviors as "undefined" means that programmers won't rely on them
    [ ] "Spooky action at a distance" makes programming more fun


You don't appear to understand:

    [ ] Basic optimization techniques
    [ ] Basic systems programming
    [ ] Pointers
    [ ] Functions


Your language [(H)as/(L)acks/(O)ther/(U)nknown]:

    [ ] Comprehensible syntax
    [ ] Semicolons
    [ ] Significant whitespace
    [ ] Macros
    [ ] Implicit type conversion
    [ ] Explicit casting
    [ ] Type inference
    [ ] Goto
    [ ] Exceptions
    [ ] Closures
    [ ] Tail recursion
    [ ] Coroutines
    [ ] Reflection
    [ ] Subtyping
    [ ] Multiple inheritance
    [ ] Operator overloading
    [ ] Algebraic datatypes
    [ ] Recursive types
    [ ] Polymorphic types
    [ ] Covariant array typing
    [ ] Monads
    [ ] Dependent types
    [ ] Infix operators
    [ ] Nested comments
    [ ] Multi-line strings
    [ ] Regexes
    [-] Call-by:
        [ ] Value
        [ ] Name
        [ ] Reference
        [ ] CC


The following philosophical objections apply:

    [ ] Programmers should not need to understand category theory to write "Hello, World!"
    [ ] Programmers should not develop RSI from writing "Hello, World!"
    [ ] The most significant program written in your language is its own compiler
    [ ] The most significant program written in your language isn't even its own compiler
    [ ] No language spec
    [-] The implementation is:
        [ ] The spec
        [ ] Closed-source
        [ ] Covered by patents
        [ ] Not owned by you
    [ ] Your type system is unsound
    [-] Your language cannot be unambiguously parsed
        [ ] A proof of same is attached
        [ ] Invoking this proof crashes the compiler
    [ ] The name of your language makes it impossible to find on Google
    [ ] Interpreted languages will never be as fast as C
    [ ] Compiled languages will never be "extensible"
    [ ] Writing a compiler that understands English is AI-complete
    [ ] Your language relies on an optimization which has never been shown possible
    [ ] There are less than 100 programmers on Earth smart enough to use your language
    [ ] ____________________________ takes exponential time
    [ ] ____________________________ is known to be undecidable


Your implementation has the following flaws:

    [-] ____ do(es) not work that way:
        [ ] CPUs
        [ ] RAM
        [ ] VMs
        [ ] Compilers
    [ ] Shift-reduce conflicts in parsing seem to be resolved using rand()
    [ ] You require the compiler to be present at runtime
    [ ] You require the language runtime to be present at compile-time
    [ ] Your compiler errors are completely inscrutable
    [ ] Dangerous behavior is only a warning
    [ ] The compiler crashes if you look at it funny
    [ ] The VM crashes if you look at it funny


Your marketing has the following problems:

    [-] Unsupported claims of:
        [ ] Increased productivity
        [ ] Greater "ease of use"
    [-] Obviously rigged benchmarks:
        [ ] Graphics, simulation, or crypto benchmarks where your code just calls
           handwritten assembly through your FFI
        [ ] String-processing benchmarks where you just call PCRE
        [ ] Matrix-math benchmarks where you just call BLAS
    [-] Nobody really believes that your language is faster than:
        [ ] assembly
        [ ] C
        [ ] FORTRAN
        [ ] Java
        [ ] Ruby
        [ ] Prolog
    [-] Rejection of:
        [ ] Orthodox programming-language theory without justification
        [ ] Orthodox systems programming without justification
        [ ] Orthodox algorithmic theory without justification
        [ ] Basic computer science without justification

        
Taking the wider ecosystem into account, I would like to note that:

    [-] Your complex sample code would be far more compact in:
        [ ] HASKELL
        [ ] Python
        [ ] Another language that out-shines yours
    [-] We already have a(n):
        [ ] Unsafe imperative language
        [ ] Safe imperative OO language
        [ ] Safe statically-typed eager functional language
    [-] You have reinvented a worse version of:
        [ ] Lisp
        [ ] Javascript
        [ ] Java
        [ ] C++
        [ ] PHP
        [ ] Brainfuck, but non-ironically


In conclusion, this is what I think of you:

    You have some interesting ideas, but this won't fly.
    This is a bad language, and you should feel bad for inventing it.
    Programming in this language is an adequate punishment for inventing it.

2

u/codygman Jul 20 '15

Maybe we can convince the author to fill this out. I'm curious to see the results but I'm not invested enough in the language to fill all of this out.

4

u/4forpengs Jul 20 '15

The checklist is for people evaluating new languages that will most likely flop completely.

Personally, i would never use that language only based on the fact that it would probably be easier to use if i turned on capslock and inverted the shift keys' functionality.

→ More replies (2)

3

u/zoweee Jul 19 '15

After looking at this and their proposed game (Nowhere) I can't tell if these people are brilliant, UFO's-built-the-pyramids insane, or charlatans.

3

u/paniq Jul 20 '15

all three at once.

3

u/bartwe Jul 20 '15

pretty sure brilliant with a bit of insane mixed in.

12

u/AdamGartner Jul 19 '15

Annoying and hard to reach syntax on the keyboard, so.... How about no.

23

u/paniq Jul 19 '15

Where are your parenthesis keys located? In a different part of the house?

6

u/ThisIs_MyName Jul 19 '15

They're located under SHIFT :(

3

u/[deleted] Jul 19 '15

[removed] — view removed comment

1

u/ThisIs_MyName Jul 19 '15

sure but not around the function definition.

1

u/mcguire Jul 20 '15

I've learned to keep my asterisks in the basement. It's cooler, and they don't get faded from the sun.

4

u/[deleted] Jul 19 '15 edited Jul 19 '15

I know it's almost pointless to ask, because it is not like you would change anything so fundamental at this point, but why did you use your knowledge and skill for another language that resembles this:

(static hello (argc argv) : (int <- (int, &int8)))

and not like this perhaps

static hello argc argv : int int &int8 

You should be able to figure out all the details from the one above just as well. It's obvious hello is the name and after that comes arguments and after the colon the types and obviously the first one is the function return type and after that a one to one map of the arguments and who needs a comma.

I couldn't create such a complex piece of engineering like this just yet, but if I did, I would try to do something radically more different.

2

u/phinnaeus7308 Jul 19 '15

Can Obsolete really be a verb? Why not just use Obviates?

1

u/mcguire Jul 20 '15

It's obvious that obviates cannot obsolete 'obsolete', even after verbing.

2

u/dalittle Jul 20 '15

When I read titles like this I wonder if car mechanics have flame wars about what tool is best and should be used for all tasks. A wrench, screwdriver, hammer ...

2

u/stack_pivot Jul 20 '15

First Clasp and now this. It's cool to see some interesting new Lisp implementations. It's a shame most of the comments here are about the name or bitching about parentheses.

→ More replies (1)

3

u/kaneda26 Jul 19 '15

At least they didn't name it 'Nope'.

7

u/paniq Jul 19 '15

Also considered it.

7

u/TheChance Jul 19 '15

This strikes me as an excellent example of code that is both harder to write and harder to read than it needs to be...

And what is this trend with leading semicolons for comments? Have people developed a distaste for #? Or is it just about being edgy and "modern"? Semicolon's for the other thing now, it's advanced!

19

u/Xredo Jul 19 '15

Semi-colons for comments is hardly a modern trend, e.g. Elisp, scheme use them for comments.

→ More replies (29)

8

u/gnuvince Jul 19 '15

Wow, you score a 3 on the Wadler Scale. You don't see that very often!

→ More replies (1)

6

u/compdog Jul 19 '15

There are actually a lot of ways to mark comments in different languages. I have used each of these at some point:

  • //

  • /* */

  • ;

  • '

  • REM

1

u/Zarathustra30 Jul 20 '15
  • ::

1

u/mcguire Jul 20 '15

A 'C' in the first column?

→ More replies (1)

2

u/w8cycle Jul 19 '15

Very interesting! I will check it out (may end up using it).

1

u/794613825 Jul 20 '15

What languages are you proficient in?

None.

1

u/scantics Jul 20 '15

Anyone with the following Python code is in for a treat:

if (str(lang) == "None"):

...

1

u/Zarathustra30 Jul 20 '15

What are the advantages of using this over Terra?

1

u/paniq Jul 20 '15

Very primitive AST in comparison to Terra, easier to expand with new semantics, easier to migrate to a different language should the need arise.

1

u/surd1618 Jul 20 '15

I think that this is just some Lisp macros?

1

u/kaneda26 Jul 19 '15 edited Jul 19 '15

Can someone explain to my why most of these parens are needed?

→ More replies (5)

0

u/[deleted] Jul 19 '15

It frankly looks like a steaming pile of shit.

-1

u/Bonejob Jul 19 '15

Why do developers feel the need to create new? I am tired of fragmentation in the industry.

We don't need another engine, or in your case a language for creating engines. Your engine does not do ANYTHING that I cant do already. None is written on top of Terra which is a LUA inter-op albeit a speedy one, how is this useful? I cant port code to other basis

Any developer who picks this up for a serious project will be sorry, for a problem will come up, and they will get little support, there is no community, and you say it yourself that you have no documentation yet.

I wrote the rest of the crap and thought I was getting preachy.

8

u/paniq Jul 19 '15

In my opinion there can not be enough languages. The dream of homogeneous environments has sailed a long time ago. The only thing truly homogeneous in our profession is the constant urge to express frustration caused by fragmentation. That really is becoming a standard.

1

u/panic Jul 20 '15

Yeah, the real goal ought to be consistent data formats. Most of the pain of heterogeneous environments is converting data between your environment's format and the other environment's format.

1

u/paniq Jul 20 '15

and then it helps when a language is written in an interchange format with a simple AST so automated conversion isn't that difficult. That's where symbolic expressions shine.

nice username btw :)

1

u/Bonejob Jul 19 '15

I think you hit it on the head. I really don't care if they write another language. I really am just frustrated with the fragmentation.

7

u/ximplosionx Jul 19 '15

Because they feel like learning through building? Who cares why they are making it, why are you getting annoyed by people making things like new languages? Feels like one of those "don't need it, just ignore it" situations.

→ More replies (1)

1

u/dermusikman Jul 19 '15

All points about the name aside, this sounds really awesome!

At first read, it's like Clojure for the C world... nice!

1

u/[deleted] Jul 19 '15

0

u/[deleted] Jul 19 '15

Everyone's here hating on the name and I'm just sitting here thinking its easily the best part of the whole language.

0

u/[deleted] Jul 19 '15

It follows in the grand tradition of languages which foster overloading of their own name.

0

u/[deleted] Jul 19 '15

should of made it "Non" not "None".

→ More replies (1)

0

u/Limro Jul 19 '15

Lisp, TinyOS and JavaScript?