Mozilla Pitches New Developer Language Rust
Mozilla has released version 0.1 of its Rust compiler and programming tools.
According to the Mozilla Foundation and the release post, Rust is "a strongly-typed systems programming language with a focus on memory safety and concurrency." In its nature, Rust could be seen as a future competitor for Google Go.
Version 0.1 is announced as an "alpha release" but is fairly complete with features that include multithread task scheduling, interface-constrained generics, typestate predicates, and stack growth. The compiler works on Linux (x86 and x86-64), Mac OS (x86 and x86-64), as well as Windows (x86). The developers said that features and the documentation still needs to be completed, standard library APIs will be changed, language-level versioning does not work and app performance is below its target. The 0.1 release is intended for use by early adopters.
Creator Graydon Hoare, who has been working on Rust since 2006, is now asking interested developers to start using Rust and test its features and capabilities.
- A Wireless Carrier's Challenges in Managing Data Demand
- Gmail Logo Was a Rush Job With Two Totally Different Fonts
- Motorola's Droid 4 Will Cost $199.99 Subsidized?
- Casio's Super-tough G-Shock Smartphone Looks Indestructible
- Report: Samsung Galaxy S III Unveiling Has Been Delayed
- Canadian Teenagers Send Lego Man into Near Space
- Nintendo Spills Beans on "Nintendo Network," NFC Support
- Facebook May Go IPO on Wednesday
- Apple Retakes Smartphone Lead in Q4, Samsung Wins 2011
- Reminder: President Obama Speaks on Google+ Today
- Verizon Shared Data Plans Coming Soon?
- Apple Sued Over Accelerometer and Bubble Level
- Microsoft Confirms No New Xbox in 2012
- These Suspenders Are Designed to Improve Posture
- GymPact Makes You Pay (Literally) For Not Working Out
- Microsoft, Facebook, Google, Others Join Forces to Fight Phishing
- Chrome Surpasses 30 Percent Market Share For The First Time
- Report: Facebook Filing $5B IPO on Wednesday
- Piracy Isn't Such a Bad Thing, Says Maker of Angry Birds
Interesting, would love to see if this will impact FF memory hogging.
Interesting, would love to see if this will impact FF memory hogging.
umm... it isnt?
chrome eith i think 150 tabs eats up about 4gb of memory
ff with 500+ tabs is only eating 1gb
Depends what is being viewed in the tab. Has nothing to do whether its chrome or ff. As long as the browser cleans itself up after using the memory... but that still has alot to do with item being run inside the browser.
the problem with these languages like rust and dart are that they are owned by the browsers firefox and google respectively. this being the case competitor browsers are slow to adopt, if at all.
the great thing about flash is that it is owned by a single company, adobe... therefore the flash player runtime runs the same across multiple platforms and browsers whereas with these other languages including html5 and javascript the rendering is implementation specific so you have to deal with how it is going to render across all browsers and platforms. we are moving the opposite way technologically.
most compiled languages used today never heard of the internet when they were born, and it is more like fitting a square peg into a round hole. Sometimes it is better to start from scratch than bang you head trying to make something work the long way around.
should be fast (low dependancy/bloat), and easy to learn and understand... and can be used in multiple operating systems.
Go? Rust? no idea
but a few years ago nobody thought you needed anything more than IE as a browser.
Depends what is being viewed in the tab. Has nothing to do whether its chrome or ff. As long as the browser cleans itself up after using the memory... but that still has alot to do with item being run inside the browser.
actually it does, tabs in chrome use separate processes which means more memory consumption
umm... it isnt? chrome eith i think 150 tabs eats up about 4gb of memoryff with 500+ tabs is only eating 1gb
Um 5 tabs open in FF= 450MB plus 40MB for plug in container. Those same tabs open in IE9 216MB, Maybe they should fix FF from crashing all the time from Flash still and being a memory hog first.
Um 5 tabs open in FF= 450MB plus 40MB for plug in container. Those same tabs open in IE9 216MB, Maybe they should fix FF from crashing all the time from Flash still and being a memory hog first.
I have 11 tabs open in FF and it is taking up 362MB RAM, like another poster said the content in the tabs do make a difference, as for flash I have yet to see FF crash from flash in the many years I have been using it.
As for IE9 those same 11 tabs is using up about 403MB RAM so umm seems each browser uses different amounts of RAM for different pages.Seems you cannot compare them since it will always vary some will do better then others depending on the sets of tabs open.
Irony that Firefox doesn't manage memory too well.
actually it does, tabs in chrome use separate processes which means more memory consumption
maybe, maybe not
separate processes give you benefits too. More benefits than having one large process.
I always wondered how we end up with so many different standards.
Thanks for finally clearing this up !
:-)
I don't know of anyone that knows how to program in Go. Some devs took a look at it when it came out, but you just can't develop for a single browser.
As for memory usage, FF does seem to use less memory than Chrome, however FF just doesn't give any of it back when you close tabs. If I start to run out of memory in Chrome I just close a few tabs, in FF I have to close the whole browser. There are times when I've had a single tab open in FF (after closing a bunch) and its still using 2+ GB of memory.