FA20CLUB 11 month engine build review *****FAIL*****

[Ryan P]

Oh yeah I am well aware, I am not nearly disciplined enough for C. It's incredibly interesting but I'll just stick with Java and python haha. I need the JVM to keep me in line

[King Tut]

I learned my parallel processing in C. The good ole write a program to create a server and a client that sends requests to the server.

[hunter3232792]

make this happen in miami!

[Ryan P]

One of these days ill take the time to learn C. I'm self-taught so I'm just starting to get a handle of data structures and coding conventions. That being said it's best I stay away from pointers and such and allow the jvm to clean up after me haha.

Sent from my SPH-L710 using Tapatalk

[wparsons]

Originally Posted by King Tut

It isn't that hard, and I love that we have CPUs with tons of cores and all the popular software programs are still single threaded.

I think you're mixing up multi threaded with designed for multiple cores (parallel processing). You can easily have multi threaded applications on a single core. Modern OS' also try their best to spread load out over multiple cores, but that's entirely seamless to the application. The application can do things to help the OS, but it isn't necessary.

Originally Posted by jamesm

I should have specified 'in C' lol. Everything is easy with the higher level stuff .

You sir are too hardcore

Originally Posted by King Tut

I learned my parallel processing in C. The good ole write a program to create a server and a client that sends requests to the server.

That's what we did in school as well, a "taxi" dispatcher program that had multiple "people" (clients) calling the "dispatcher" (server).

Originally Posted by Ryan P

One of these days ill take the time to learn C. I'm self-taught so I'm just starting to get a handle of data structures and coding conventions. That being said it's best I stay away from pointers and such and allow the jvm to clean up after me haha.

Sent from my SPH-L710 using Tapatalk

It's not just pointers, there's no such thing as a string in C either! Like having arrays of a dynamic size, not in C! If you know Java you'll be quick to pick up the syntax of C, but the logic to do efficient and correct dynamic memory management is a bit of an art.

It's been so long since I've used C, and I've become SO used to all the handy libraries C# has, I would have a hard time going back.

[jamesm]

i know c very well... it's not 'fun' in the traditional sense so i only use it when necessary. i heart ruby... very much. i write anything i possibly can in ruby, then use native c extensions where necessary. they play together very nicely and together give you all the power and flexibility you could ever ask for.

[King Tut]

Originally Posted by wparsons

I think you're mixing up multi threaded with designed for multiple cores (parallel processing). You can easily have multi threaded applications on a single core. Modern OS' also try their best to spread load out over multiple cores, but that's entirely seamless to the application. The application can do things to help the OS, but it isn't necessary.

I am not confusing anything. My point is still that in this day and age of multiple processors and multiple cores, we still aren't utilizing multi threaded programming nearly enough. If an application is running a single process/thread, then that can not be spread out over multiple cores. The best it can do is utilize 100% of one of the cores.

[King Tut]

Originally Posted by wparsons

It's been so long since I've used C, and I've become SO used to all the handy libraries C# has, I would have a hard time going back.

I do all my current programming in Visual Studio using C#. It would be hard to go back to the days of programming C using PICO on a Unix box, haha.

[jamesm]

Originally Posted by wparsons

I think you're mixing up multi threaded with designed for multiple cores (parallel processing). You can easily have multi threaded applications on a single core. Modern OS' also try their best to spread load out over multiple cores, but that's entirely seamless to the application. The application can do things to help the OS, but it isn't necessary.

'green threads' and actual hardware threads are two entirely different things. concurrency != parallelism.

for instance:

10.times do |i|
  Thread.new do
    puts "doing something the #{i.ordinalize} time"
  end
end

creates a concurrent operation, but not a parallelized one in MRI ruby. in jruby it would be both because jruby is built on the jvm and supports hardware multithreading, where MRI only supports green threads. it's an important distinction.

TL;DR - you can run multiple 'green' threads on a single hardware core and achieve concurrency, where parallelization requires multiple hardware threads (and bespoke cores to run them on).

OK now back to toni screwing brandon over...

[wparsons]

^^ That's what I was getting at, just MUCH better explained than what I said

[wrxgoose]

o.O from jackass to coding. i love this site. lol

[sosick]

So has anyone gotten their money back from him?

[SirBrass]

Originally Posted by sosick

So has anyone gotten their money back from him?

My guess is that it's going to require something starting with "class action" to do that.

I'm on my phone so if I make mistakes, blame Sportsguy83

[sosick]

Originally Posted by SirBrass

My guess is that it's going to require something starting with "class action" to do that.

I'm on my phone so if I make mistakes, blame Sportsguy83

Hope they do becuz its alot of bs what ppl have been through