this post was submitted on 28 Jul 2024
1297 points (99.0% liked)

Programmer Humor

19623 readers
28 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
1297
Brace Style (sh.itjust.works)
submitted 3 months ago by sjmarf@sh.itjust.works to c/programmer_humor@programming.dev
156 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] Hack3900@lemy.lol 34 points 3 months ago (3 children)

I kinda like it..

[–] VonReposti@feddit.dk 12 points 3 months ago* (last edited 3 months ago) (2 children)

I think you'll like Ruby. It has mostly done away with braces and code blocks end with end, e.g.

def create
  unless admin redirect_to new_session_path and return
  
  @product = Product.new product_params

  if @product.save
    flash[:success] = "New product has been created!"
    redirect_to edit_product_path(@product) and return
  else
    flash[:error] = "Something went wrong!
    render :new
  end
end

This is working code that I simplified a bit from an old project of mine.

[–] olafurp@lemmy.world 12 points 3 months ago (2 children)

Ruby syntax is nice although I prefer python way of enforcing indentation instead of adding "end"s. Personally I just want a statically typed language with enforced indent as syntax.

[–] VonReposti@feddit.dk 7 points 3 months ago (2 children)

Funny, the forced indentation is what I hate about Python. If you think a missing semicolon can be hard to catch, don't ever think about a missing whitespace :p

The end keyword really isn't a big deal for me. I find it to be a good way to easily spot the end of a method. But if you wouldn't like it I'd still find it a good compromise to avoid syntax issues due to whitespace.

[–] hglman@lemmy.ml 5 points 3 months ago (1 children)

i can count on one hand how many times ive had white space issues in 15 years of using python. its just not an issue

[–] 0ops@lemm.ee 3 points 3 months ago

Same and agreed, especially if you keep your functions small and focused as you should. 3-5 indents is nbd to keep track of, and if you need more than that... No you don't, refactor.

I've had way more hangups with brackets then indentation, personally, not that either is a super frequent issue, but I'm indenting anyway, so brackets are redundant and just another thing I have to keep track of

[–] JackbyDev@programming.dev 4 points 3 months ago

} helps me easily spot the end of stuff. end just blends into the statements.

[–] JackbyDev@programming.dev 1 points 3 months ago

Just add a linter to your build lol. Now if it's indented wrong it breaks!

[–] barsoap@lemm.ee 2 points 3 months ago* (last edited 3 months ago)

That's just Algol instead of B. Most languages use the one or the other, then there's sexpr-based languages (lisp, scheme), lua (technically Algol but not needing semicolons while also not needing newlines so it's definitely special), and layout syntax (Haskell, or, if you want a bad implementation, python).

[–] olafurp@lemmy.world 11 points 3 months ago

Who's going to write the extension so that they are all hidden and automatically inserted?

[–] bss03@infosec.pub 4 points 3 months ago (1 children)

Might check out the Haskell layout rules.

Basically, when you leave out the '{' then Haskell uses your intendation to insert ';}' on later lines between the leading whitespace and the first token.

There some really old Haskell code out there that lines up the '{;}' characters on the left under block-introduction keywords.

[–] barsoap@lemm.ee 4 points 3 months ago

It's not just old Haskell code that's how you write Haskell if you want explicit braces. Well, mostly generate, but it's still the idiomatic formatting (and when you generate you always generate braces because it's easy to get layout subtly wrong when generating).

Haskell also does the whole

data Foo = Bar
         | Baz
         | Quux

foo = [ Bar
      , Baz
      , Quux
      ]

thing, makes sense to apply it to braces especially as they're seen only very rarely. Single-line, yes, but not multi-line.