Was just pondering this idea and posted this in the post topic for discussion. 

Each Maple finished version of Maple may still have certain bugs that will not be updated for that version, so I am suggesting (I think anyone could implement it) that if there is a workaround, one could wrap it up in something I would call a patch package updateable by us users we could update here on mapleprimes.  It would be good for people who haven't upgraded or can't upgrade due to costs etc...

For example, there was recent issue with pdsolve that was fixed quite quickly in the seperate updateable Physics package.  Things could be done similarily that might work with other workarounds using this patch package idea. 

If anyone thinks this is good or even viable idea then lets implement it.  I envisioned it with just this one rule to follow - the name of the patch package would reflect the version we are patching (ie. with(patch12) or with(patch2016) for Maple 12 and Maple 2016 respectively etc...)  We could make these patch packages available in this post or start another.

As I said, I'm just throwing the idea out there.  Thoughts?

It seems a large number of people, when initially using maple, wrongly deduce that for example sin(60) is the sin of 60 degrees and not the sin of 1/3 Pi radians.  I believe mathematica's default is degrees.  When a student compares an expression to another but forgets to realize a value is read as radians and not degrees they are perplexed when Maple returns false and Mathematica returns true.

As a suggestion, under tools->options allow a user to be able to change how maple reads values within trigonometric funtions as either radians or degrees.

Most times when someone computes the sin(60) what they really mean in Maple..
is sin(convert(60 degrees, radians))

It appears google doesn't know about the haversine formula.  Huh?  Well at least google can't draw the proper path for it.  I typed in google "distance from Pyongyang to NewYork city"  and got 10,916km.  Ok that's fine but then it drew a map

The map path definitely did not look right.  Pulled out my globe traced a rough path of the one google showed and I got 13 inches (where 1 inch=660miles) -> 8580 miles = 13808 km .. clearly looks like google goofed. 

So we need Maple to show us the proper path.
 

with(DataSets):
with(Builtin):
m := WorldMap();
AddPath(m, [-74.0059, 40.7128], [125.7625, 39.0392]):
Display(m):

Ok so you say that really doesn't look like the shortest path.  Well, lets visualize that on the globe projection

Display(m, projection = Globe, orientation = [-180, 0, 0])

Ah, now it is clear
Pyonyang_to_NewYork.mw

Here's a little procedure to fish out data from the Simbad database.  Some star names may not work if the page Simbad brings up is not completely filled, but it should work for most queries.

Download star_database_-_simbad.mw

I found this http://www.atlasoftheuniverse.com/50lys.html and wondered how to do it in Maple. With a bit of data file editing I came up with this.  All stars within 50 light years that are visible to the naked eye.

The modified data file and the maple worksheet below

stars3.txt

Download Stars50LY.mw