|
| 05 Mar 2016 02:36 PM |
It's 32bit at the moment (4GB), so why not become 64bit?
|
|
|
| Report Abuse |
|
|
h5s
|
  |
| Joined: 03 Jul 2014 |
| Total Posts: 1229 |
|
|
| 05 Mar 2016 02:39 PM |
| It doesn't exceed the requirements to be 64 bit yet. |
|
|
| Report Abuse |
|
|
chimmihc
|
  |
| Joined: 01 Sep 2014 |
| Total Posts: 17143 |
|
|
| 05 Mar 2016 02:43 PM |
Because people still use 32 bit machines.
|
|
|
| Report Abuse |
|
|
|
| 05 Mar 2016 03:29 PM |
"Because people still use 32 bit machines." "It doesn't exceed the requirements to be 64 bit yet."
These two are very dumb responses.
The main reason I can see is they don't want to put the effort into distributing two packages, as well as the bugs that can come with each. It's fine being x82 and won't ever have to change. |
|
|
| Report Abuse |
|
|
cntkillme
|
  |
| Joined: 07 Apr 2008 |
| Total Posts: 44956 |
|
|
| 05 Mar 2016 03:31 PM |
cody you're stupid, chimmihc's response is very relevant and your response is purely idiotic.
The fact that you said x82 even proves how little you know. |
|
|
| Report Abuse |
|
|
|
| 05 Mar 2016 03:55 PM |
| "It's fine being x82 and won't ever have to change" I might be wrong, but do you mean x86? |
|
|
| Report Abuse |
|
|
|
| 05 Mar 2016 03:58 PM |
no he means x69
Recommended username: WorthlessRay_revenge
|
|
|
| Report Abuse |
|
|
|
| 05 Mar 2016 04:22 PM |
Is there a clear reason to transition to 64-bit? Sure you get away from any 32-bit emulation the host system is doing, an expanded address space, and you get some extra space per word, but unless you actually take the time to rework some of your program's assumptions it may not benefit you substantially enough to spur a change.
Does ROBLOX normally run out of memory? Apparently not, users are still online. Is ROBLOX complex enough internally that making effective use of increased word size and register count (and associated miscellany) would be ridiculously expensive? Yes.
Assuming ROBLOX's engine uses any form of inline assembly, that would probably need to change (or branch during compilation) as well.
Most of us work on projects where simply recompiling for a 64-bit target would work, but as your code base becomes increasingly complex, and performance concerns grow near to heart, the transition can get a bit... hellish.
Also, has anyone checked the latest binaries? |
|
|
| Report Abuse |
|
|
U_7
|
  |
| Joined: 30 Dec 2014 |
| Total Posts: 21 |
|
| |
|
|
| 05 Mar 2016 07:07 PM |
| :) I always get 86 and 82 mixed up. |
|
|
| Report Abuse |
|
|
cntkillme
|
  |
| Joined: 07 Apr 2008 |
| Total Posts: 44956 |
|
|
| 05 Mar 2016 07:12 PM |
"Is ROBLOX complex enough internally that making effective use of increased word size and register count (and associated miscellany) would be ridiculously expensive? Yes." I feel like that wouldn't be much of a problem, since I doubt they'd end up changing the types (longs to longs longs, etc.). I guess in terms of stack alignment, there would be more "placeholder trash" on the stack to keep it aligned but if they think about compiling it as 64-bit, most 64-bit machines are modern enough to have enough memory that something like that shouldn't really matter (or so I assume).
I feel like the major reason might be your last point, and that there's just no point in wasting the effort if there isn't going to be that much of a benefit. |
|
|
| Report Abuse |
|
|
yung_one
|
  |
| Joined: 26 Feb 2016 |
| Total Posts: 19 |
|
|
| 05 Mar 2016 07:20 PM |
| The 32-bit vs 64-bit RAM limitation only applies to Windows itself. A 32-bit application can use more than 4GB/3GB of RAM. |
|
|
| Report Abuse |
|
|
Seranok
|
  |
| Joined: 12 Dec 2009 |
| Total Posts: 11083 |
|
|
| 05 Mar 2016 07:21 PM |
| I think zeuxcg talked about this once, it sounded like he thought it wouldn't be a significant performance increase so it's not really worth doing at this point. |
|
|
| Report Abuse |
|
|
|
| 05 Mar 2016 07:54 PM |
| inb4 people start going crazy that seranok replied to this thread |
|
|
| Report Abuse |
|
|
Baseness
|
  |
| Joined: 07 Oct 2015 |
| Total Posts: 1001 |
|
|
| 05 Mar 2016 07:59 PM |
SERANOK REPLIED!!!!!!!!!!!!! I'M GOING CRAAAAAAAAAAAAAAAAAAAZY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
|
|
| Report Abuse |
|
|
j_0sh
|
  |
| Joined: 05 Mar 2015 |
| Total Posts: 512 |
|
|
| 05 Mar 2016 08:00 PM |
Generally, unless you design your program from the ground up to be 64 bit, the time and money spent making your program 64 bit outweighs the often insignificant benefits.
~ A day having learned nothing is a day wasted. |
|
|
| Report Abuse |
|
|
j_0sh
|
  |
| Joined: 05 Mar 2015 |
| Total Posts: 512 |
|
|
| 05 Mar 2016 08:04 PM |
| Plus, there's the problem of having to ship a 32 and 64 bit version of your program. You could just ship a 64 bit version, but there are still kids using their grandma's old Dell that would rage because they can't play ROBLOX. |
|
|
| Report Abuse |
|
|
| |
|
|
| 06 Mar 2016 05:29 AM |
| good scripters always have other good scripters' backs |
|
|
| Report Abuse |
|
|
|
| 07 Mar 2016 02:38 PM |
?? Well, not really. If you apply that to programmers as a whole, definately no. Nice scripters always have each others bac
|
|
|
| Report Abuse |
|
|
LTB4
|
  |
| Joined: 05 Mar 2016 |
| Total Posts: 298 |
|
|
| 07 Mar 2016 02:47 PM |
I only know a little bit because I'm only 9 weeks into my technologies course, but here's the Pro's/Cons's I see.
Pro:
Due to being able to utilize more memory (4GB+ whereas 32 bit with any amount can only utilize only (around) 3.5GB), 64 bit windows (when running a lot of programs) compared to the other (32 and (lmao) 16 bit computers, eww) tend to run faster and more efficiently.
Cons:
They would have to port some stuff over to 64 bit most likely, due to the complexity of the clients (as was stated earlier, a very good point). Some people still run 32 bit computers, and some even 16 bit (EWW[2]!).
-LTB4 |
|
|
| Report Abuse |
|
|
h5s
|
  |
| Joined: 03 Jul 2014 |
| Total Posts: 1229 |
|
|
| 11 Mar 2016 07:19 PM |
| My first reply was meant to be sarcastic but ended up sounding very stupid. Oops. |
|
|
| Report Abuse |
|
|