5 ms·

Do we know if he or the other oculus team members are still using racket?

by mathnode 7y ago

mepian 7y ago
If I remember correctly, Facebook told him to drop Racket and use JavaScript instead.
- NeonVice 7y ago
  Atwood's Law: any application that can be written in JavaScript, will eventually be written in JavaScript.
- andybak 7y ago
  Sounds like a damn shame reading the following: https://www.roadtovr.com/oculus-cto-john-carmack-will-demo-his-vrscript-language-at-connect/ https://www.roadtovr.com/oculus-cto-john-carmack-will-demo-h...
- jimbob45 7y ago
  I was hoping you'd be wrong :( https://twitter.com/id_aa_carmack/status/807797812700348416 https://twitter.com/id_aa_carmack/status/807797812700348416
- iLemming 7y ago
  That's not just sad, it is really strange. Seems enterprise would never learn from the mistakes of the past. Javascript is new Java - it's getting bigger every year, its syntax almost confusing and often feels inconsistent, sometimes it doubtlessly does utterly stupid things. Most experienced developers dislike the language. Beginner developers also find it confusing. Days of low barrier entry to JS are long gone. Clojurescript, Elm, ReasonML, Purescript, etc. there are multiple better options. Yet instead of embracing PLs that can fix many of the drawbacks, big enterprise keeps insisting on it. Sigh...
  - whywhywhywhy 7y ago
    > That's not just sad, it is really strange Doesn't seem strange at all for a company pushing a technology for mass adoption to choose one of the most common languages which possibly has the most eyes in the world on its performance metrics, keep in mind VR has to hit framerates up to 90fps.
    - iLemming 7y ago
      Facebook has already made that mistake with PHP. They are still paying the hefty price for that. Language popularity at a given time doesn't guarantee a higher ROI in the future. For the next couple of decades, CS experts will be debating over languages that optimized for programmer's productivity, optimized for performance and languages that offer correctness (probably via type systems and other mechanisms). Javascript today doesn't fit any of these categories, and although it is quickly evolving, it still hasn't shifted towards any of those sides. It has become more performant than initially, but yet not fast enough (e.g.: for native apps). Sadly the story is old, happened many times - happened to Joe Armstrong and Erlang at Ericson, that happened at MIT when they switched from Scheme to Python. It happens whenever companies ignore their engineers and arguments they make, but eagerly listen to their Marketing and Sales teams. Honestly, I would love to see faces of those stupid imbeciles who after hearing all John Carmack's arguments that tool X is making him very productive, later tell him that he cannot use that tool.

Do we know if he or the other oculus team members are still using racket?

mepian 7y ago

If I remember correctly, Facebook told him to drop Racket and use JavaScript instead.

NeonVice 7y ago
Atwood's Law: any application that can be written in JavaScript, will eventually be written in JavaScript.
andybak 7y ago
Sounds like a damn shame reading the following: https://www.roadtovr.com/oculus-cto-john-carmack-will-demo-his-vrscript-language-at-connect/ https://www.roadtovr.com/oculus-cto-john-carmack-will-demo-h...
jimbob45 7y ago
I was hoping you'd be wrong :( https://twitter.com/id_aa_carmack/status/807797812700348416 https://twitter.com/id_aa_carmack/status/807797812700348416
iLemming 7y ago
That's not just sad, it is really strange. Seems enterprise would never learn from the mistakes of the past. Javascript is new Java - it's getting bigger every year, its syntax almost confusing and often feels inconsistent, sometimes it doubtlessly does utterly stupid things. Most experienced developers dislike the language. Beginner developers also find it confusing. Days of low barrier entry to JS are long gone. Clojurescript, Elm, ReasonML, Purescript, etc. there are multiple better options. Yet instead of embracing PLs that can fix many of the drawbacks, big enterprise keeps insisting on it. Sigh...
- whywhywhywhy 7y ago
  > That's not just sad, it is really strange Doesn't seem strange at all for a company pushing a technology for mass adoption to choose one of the most common languages which possibly has the most eyes in the world on its performance metrics, keep in mind VR has to hit framerates up to 90fps.
  - iLemming 7y ago
    Facebook has already made that mistake with PHP. They are still paying the hefty price for that. Language popularity at a given time doesn't guarantee a higher ROI in the future. For the next couple of decades, CS experts will be debating over languages that optimized for programmer's productivity, optimized for performance and languages that offer correctness (probably via type systems and other mechanisms). Javascript today doesn't fit any of these categories, and although it is quickly evolving, it still hasn't shifted towards any of those sides. It has become more performant than initially, but yet not fast enough (e.g.: for native apps). Sadly the story is old, happened many times - happened to Joe Armstrong and Erlang at Ericson, that happened at MIT when they switched from Scheme to Python. It happens whenever companies ignore their engineers and arguments they make, but eagerly listen to their Marketing and Sales teams. Honestly, I would love to see faces of those stupid imbeciles who after hearing all John Carmack's arguments that tool X is making him very productive, later tell him that he cannot use that tool.