4

Mass pole here:
Big Endian or Little Endian?
camelCase or UpperCase?
Brackets on new line or same line?
Apple or Android?
Favourite language?
What language do you despise?
Age? (Don't mean to be creepy with this one, I have my reasons)

Comments
  • 3
    If only anything in life was binary
  • 1
    @Lahsen2016 same
  • 1
  • 3
    Hard to say.
    Uppercase
    First bracket on same line, end bracket on new line
    Android
    Python, Ruby, or PHP (can't choose)
    That one emoji programming language
    16
  • 1
    Big Endian
    UpperCase
    Depends, same line most of the time
    Android
    C++ (don't hate me)
    PHP
    18
    😊
  • 1
    Big endian
    Depends of the object/artifact
    New line
    Android
    C# (perhaps because it's my first (professional) love? 😂)
    VB/VBA/VB.Net, again, can't decide
    32
  • 3
    Little endian pretty much won, big endian for network protocols that need it.

    camelCase and UpperCase are both camel case. I got a preference for camel case to snake_case though but it depends on the language and whatever the project uses, or in the instance of a new project, whatever the majority agreed on. For example SQL should be UPPER_CASE_SNAKE_CASE.

    No preference regarding curly brackets, but as above, adopt whatever standard for the project/language.

    Android. iPhones are very nice, especially hardware quality wise, but the OS is too restrictive.

    At the moment I'm having fun with Go, it's refreshingly simple in the same sense C is simple.

    Any language that requires me to get an interpreter to run them. I probably dislike python most of all of them. People say that python is beautiful, but I think it looks ugly.

    37
  • 2
    - Little endian (seems easier on incremental math w/ arrays)
    - Camel case (seems neater)
    - New line (c++), same line (java)
    - Apple (more efficient environment to code)
    - any C++ compatible languages
    - JavaScript (since a lot of devs think they should use it for everything! WTF! Go to college!!)
    - 34

    What about you @SpencerBeige ?
  • 2
    @slar very elegant response ++ would probably love to code a project with you one day!
  • 1
    Thank you to everyone who has responded so far!
  • 1
    Little endian
    camelCase
    Same line
    Android
    Ruby
    Despise Java
    23
  • 1
    Don't know.
    camelCase
    Same line
    Android
    Python, (Java) *Beginner
    Don't know.
    20
  • 1
    Big endian
    camelCase
    Same line
    Android
    Python
    C++
    20
  • 1
    Not paying too much attention to this
    camelCase
    Start bracket on same line & end bracket on new line
    Android
    Java
    None
    20
  • 3
    @RamChandra @Splash and for those hung up on 'endianness'...
    https://en.m.wikipedia.org/wiki/...#
  • 0
    @SpencerBeige you yourself have yet to respond : /
  • 0
  • 1
    @greenhouse True.

    Big Endian
    camelCase
    Same Line
    Android
    C#, tryna learn haskell
    Swift, a language I somehow hate more than that emoji language.
    14
  • 1
    @greenhouse Beej explained it this way in his network guide 😂
  • 1
    @greenhouse i research it a little while ago & don't really understand about it & never pay attention to this
    Hhahaha, anyways thanks for the information
  • 7
    Why does this pole not include the most infamous one..

    Tabs or spaces
  • 2
    @kaguo @Splash I tried to simplify it a bit...

    if you have an array of memory addr and the entire array represents a single int (in base 10), then each mem. addr. (or arr index) holds a number in the 1s place, then 10s place, then 100s place, and so on...

    Suppose you want to perform addition on the number represented by the entire array...

    if you use 'little'... then arr index 0 will always be the 1s place, index 1 will always be 10s, index 2 will always be 100s, and so on...

    But if you use 'big' endian, then you will have to shift the int array index to the right every time you need to 'carry' (like if the number gets to be in the thousands or ten-thousands, etc.)

    Or in other words, index 0 will not always be the 1s place. Index 0 will change to 10s place, then to 100s, then to 1000s, etc.

    So to me, if you are doing low-level computing or bitwise conversions, it makes sense (or makes it easier) to store the number in little endian.

    Does that make sense to anyone else?
  • 1
    @SpencerBeige I can't stand swift, takes for ever to compile, there are no lambdas, syntax keeps changing (cost time and money), Apple let it go (open source) and let go of the dev who created it as well, and then tesla also fired that dev in the next few months! :p
  • 1
    @greenhouse i think i've got what you mean

    Is it like when we're using for looping function ?

    if we use for (int i = 0; i < size; i++) then we're a little endian user ?
  • 1
    @Splash I'm not sure I follow how forloops play a part... but see if you can follow this hand written example...
  • 1
    Little endian
    camelCase
    New line brackets
    Android
    Nodejs
    VB.net
    21
  • 1
    @Splash actually in your forloop example, with big endian... int i will constantly want to be -1 which is out of range... in which case you will have to change the position of what you set all the indexes to... but with little endian, you simply have to increment size to equal size+1... when performing addition on the number represented by the array... which is a lot simpler in error handling....

    lol if that makes any sense sorry... wish there was a whiteboard feature in devrant ; )
  • 1
    Big endian, but I don't really care
    camelCase all the way
    Same line for simple conditionals, new line for complex stuff
    Android
    Don't really have a favorite
    Portuguese
    19
  • 1
    BigEndian
    camelCase
    New line (C), same line (everything else)
    Android
    Golang & C
    PHP
    22
Add Comment