decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
How about C++ with a gc on top and some good classes | 360 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
JavaScript != Java
Authored by: Anonymous on Wednesday, May 09 2012 @ 12:11 PM EDT
Dart is meant as a replacement for JavaScript, not Java. As an old comic goes,
Java is to JavaScript as ham is to hamster.

[ Reply to This | Parent | # ]

How about C++ with a gc on top and some good classes
Authored by: Anonymous on Saturday, May 12 2012 @ 07:28 PM EDT

If we are looking for an alternative to Java for use on Android etc., we could just go with C++ as it compiles to fast native code on most platforms, is available on most platforms etc.

The key limitations of C++ that need to be dealt with in such a project are:

  1. No garbage collection, however this can be bolted on by telling programmers not to store pointers in non-pointer variables nor pointers to (structures containing) pointers as void* or other types that do not indicate the presence of those pointers, and then using a tool that extracts the needed subset of the type information from compiler generated debug information in order to create some simpler binary tables of what memory the GC engine should treat as still-in-use pointers.
  2. No interpreter enforced behavior limits. This would be a problem on Windows Phone and Java ME feature phones, but Android (like Symbian before it) has already solved this by moving all enforcement to the process boundary and therefore allows unlimited native code in all programs without sacrificing security.
  3. No compile-once-run-anywhere bytecode. Microsoft's MSIL and UCSD p-code almost provide that in a strong form, and Dalvik could be extended with the missing instructions to support full-blown native like code.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )