• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

is javascript going to develop a C-style memory management problem?

 
Ranch Hand
Posts: 189
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Since web workers have to be explicitly managed by the developer, I can foresee memory management issues looming on the horizon. Is this a sufficiently worrisome issue, or am I just being paranoid?

- Phil Shanks
 
author
Posts: 25
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I won't say you are paranoid because we've learn in the (short) history of the web that if 'something might break - it will' :)
IMHO, we don't have the same problem as in C because our JS run inside a sandbox in the browser. There are many limitation that the browser enforce us (=web developers) and we've made some progress in areas like CORS: https://mikewest.org/2011/10/content-security-policy-a-primer
It will be interesting to see what are the measurements that browsers will take to make sure this powerful feature won't be abuse.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic