>>109679303
he's right thoughbeitdesu
sounds like you need to pay more attention to your classes

tell us what you think it is
go on anon

>>109679358
>>109679378
>he's right
why are there so many of you with this misunderstanding
when looking at bits MSB is always on the left.
endianness is how bytes are ordered
take 1 google search and educate yourself

>>109679416
bytes are just little bits of data anon
don't get so worked up

File: hairpin critter.jpg (72 KB, 850x786)

72 KB JPG

>>109679303
one possible question is whether she explained it like that specifically so that the idea clicks for the slower students instead of her simply being mistaken about it
the better question is why the hell you're going into debt to study computer science in 2020+6

>>109679585
name 1 other field that is worth going into debt for because there is none everything that is bad about computer science is worse in every other field

>>109679416
>when looking at bits MSB is always on the left.
>endianness is how bytes are ordered
>>109679497
both of you guys dont understand it lmao.
endianess is how bytes are ordered.
This doesn't say shit about how you read single bits.

>>109679303
>he didn't get a scholarship in high school

>>109680915
>he hasn't heard of bit endianness

>>109679643
the bad about comp sci is no networking with nepo babies
there's a bunch of degrees that don't have that problem

>9k a semester
bruuuuuuuuh he ain't finna...nahhhh...

>>109679643
medicine and law

>>109679416
>endianness is how bytes are ordered
who said the writer orders them them in the correct way? you can't guarantee the ordering that some other system does, best you can do is hope and read it in the right way

>>109679643
if you live in the us, i would choose civil engineering or mechanical engineering.

computer science can hardly be called a good choice in the era of ai.

at the very least, programming is definitely dead, and the swe profession was the most popular among computer science graduates.

>>109679303
>and no one corrected her i'm paying 9k a semester to be here

mistakes by old professors are completely normal. for example, i studied in eastern europe, in one of the ex-ussr countries. it was 10+ years ago, but after the collapse of the ussr, universities in our countries suffered very badly. as a result, a professor could fail to show up for a lecture at all, could show up drunk (although this was rare, i encountered it), or could start telling jokes and vulgar humor from his youth instead of teaching the subject. sometimes the content of the course did not correspond to reality; for instance, you come to study some cs subject, and instead, the teacher (an annoying old man) starts overloading you with some complex mathematics that only pure maths students take, not cs monkeys. most of the professors themselves knew nothing about cs and could only tell you about pure mathematics, pure physics, or a bit of abstract theory. all applied cs subjects were usually taught poorly or were completely missing from the curriculum.

the good thing was that such education was completely free, and i paid nothing for it. living in the dormitory cost some money (around 100 usd per month), but it was much worse than student dormitories in western universities.

>>109679303
example of your professor using (lazy) implicit language, granted they're still incompetent for not clarifying for autists like you.

>>109682904
let me add more context
the topic was not endiannness
the topic was how to add binary numbers
and she said
>in big endian you would start from the left instead
just completely wrong

In 2012 my lecturer told me the PS3 was still the fastest CPU on the market its that nobody knew how to utilise it properly.

>>109682394
>medicine
>8+ more years of school more debt more competitive than CS
>law
>more school more debt more competitive
I would rather be unemployed upskilling in tech in my parents house than spend my entire 20s in school
>>109682757
>at the very least, programming is definietely dead
its comments precisely like these that keep me going. god damn you know nothing but whatever i should be happy you gatekept yourself

>>109682975
from what i know, the fastest xeon from 2012 would give you ~180 gflops peak in single precision with avx, which is still a little less than ~200 gflops peak for cell with 8 spe, so technically there is a very little bit of truth in what he said
this doesn't make cell the fastest cpu on the market, though, because it was dogshit for literally everything else, and for FP you'd rather use a GPU, as they're even more powerful

>>109679303
>>109679416
somehow I had this misconception too

>>109679643
Comp sci is still one of the better degrees but tech is gay and filled with retards that went in because of tiktok videos. Wish i did EE

>>109679416
on the left of what? ordered when/where? what the hell are you talking about?

people in a 100 level class being incorrectly pedantic on a single sentence a professor says makes me laugh.

1. how about you accomplish something first
2. her use of "read" is correct. Changing endianness changes how the number is stored in memory, and therefore changes the order you read the data. Please consult the first picture in this article

https://en.wikipedia.org/wiki/Endianness

You're there to learn, go learn and accept that you're wrong sometimes instead of being an internet coolguy.

>>109682997
...you know you don't have to become a doctor to get into "medicine"
There's so many jobs with much less schooling/training required.

>>109683609
the reddit retard is right.
endianess indicates how data is read.
op (known faggot, self evident) still thinks bits are read one bit at a time.
everyone else (known faggots, on account of being on /g/) knows CPUs operate on 32/64bit instruction sets that access memory in whatever chunks they like, up to 64 bits per clock cycle depending on the register being used. No need to store the minimal atomic data set as anything less than 1 byte (8 bits) even when supporting legacy ops.
as bytes are made of bits, this means endianess does indicate how bits are read.

>>109683669
Bit endianness is still a thing. I2C for example is most-significant-bit first.

>>109683685
shut up before I take your lunch money faggot

File: Screenshot_20260830_05282(...).png (313 KB, 793x995)

313 KB PNG

>>109679643
Pic related.

>>109679303
You sound like one of those know it all fuckheads who will end up working at McDonald's.

>>109682997
>its comments precisely like these that keep me going. god damn you know nothing but whatever i should be happy you gatekept yourself

i mean you no longer program with your own hands, agents write the code for you. for people who gained experience and grew to a middle level in the pre-ai era this is not as scary, but in your case this is a downside, because even if you get a swe job, you will still never learn how to write code on corporate-scale projects. as a result many hiring managers do not hire people who lack work experience from the pre-ai era. now an agent does all the routine work for you and as a result you will never be able to acquire a whole layer of knowledge and skills. and as a result you are less valuable on the job market.

>>109679303
She's correct. Endianess is where you start reading bits. If it's from left it's little endian and if it's from right it's big endian. You are confusing with how bytes are transmitted, but at a fundamental level endianess is where bit reading starts, not bytes.

>>109679303
To clarify computers read and write bytes, but serial interfaces don't, it's bits. That's where LSB vs MSB is bits, not bytes. Also not all devices have a byte that is 8 bits. That's just a convention that happened in Intel chips. Why am I referring to this? Because I'm willing to bet some gen z kid would laugh at the professor telling 10-bit byte is a thing, same spirit here of MSB vs LSB in bytes and bits.

Why is it called Big Endian when the biggest byte is at the START not the END?
> It's like you're breaking the big end of an egg, it's from a book
Oh makes perfect sense

I had to deal with Lsb0 vs Msb0 in a spec this year. Text said Lsb0 but the bit tables showed Msb0. And it was bitfield data so it was ambiguous and we had to look at live data to sort it out. It's all so dumb. At least tx fags have it sorted out: msbfirst or lsbfirst. They're probably EEs though so less brain damage than computer sCiEnCe.

>>109687150
>Also not all devices have a byte that is 8 bits.
You mean a 'word'. A byte means 8 bits always.

>>109679303
CS isn't a science you don't have to be rigorous correct. You can get there by hand waving.

>>109687445
No, I mean byte. A byte having 8-bits is a convention, and has an international standard, but you don't have to follow it. If you want to be super pedantic and precise, it's an octet, but of course you don't need to because everyone assumes byte = 8-bit. Word is specifically a CPU architecture decision while byte doesn't have to be. I am sure of this.

>>109683669
>>109687094
retarded faggots here is the full context
>prof is teaching how to add binary numbers
>says: "in little endian we start adding from the right bit. But in big endian you would start from the left bit"
this is objectively incorrect
>>109683609
>her use of read is correct.
no it's not. You would never start reading the binary representation of a byte from the left.
go learn and accept that you're wrong sometimes instead of being an internet coolguy.

>>109683669
>op (known faggot, self evident) still thinks bits are read one bit at a time.
in the context of adding 2 binary numbers you are reading one bit at a time retard
>>109687094
>Endianess is where you start reading bits.
nope.
0D = 00001101
in big endian 0D does not become
11010000
you are so confidentially retarded

File: retard.png (64 KB, 957x354)

64 KB PNG

so many gay retards here
>>109683609
this retard even links me the wikipedia page (he did not read)
I have to dunk on you 1 more time sorry fag
>Changing endianness changes how the number is stored in memory, and therefore changes the order you read the data.
that does not mean binary representation changes
>0D = 00001101
>0D does not become 11010000 in big endian
read the articles you're linking before speaking this is really embarrassing for you

>>109683669
Computers are not limited to memory access. Bit order does matter for I/O.

>>109679303
Why didn't you corrected her?

File: f.png (60 KB, 754x306)

60 KB PNG

>>109687094
>but at a fundamental level endianess is where bit reading starts, not bytes.
this is also just 100% wrong.
at a fundamental level endianness was created to distinguish the ordering of bytes
what the fuck are you talking about? why are you so confident spreading bullshit

the concept of bit ordering isn't even called "endianness" endianness has only referred specifically to bytes
i fucking hate this board

>>109688494
Not so.
https://www.rfc-editor.org/info/rfc2045/
It's just that we live in C's world and C stops at bytes.

>>109688494
You should read the originating document before posting again
https://history.rfc-editor.org/ien/ien137.txt
It's endian all the way down