Live data from Hacker News

Dear Oracle, Please Release the JavaScript Trademark

tinyclouds.org

131–140 of 146 posts

Re: Dear Oracle, Please Release the JavaScript Trademark

#131
post #128

Earlier quoted context omitted.

They don't make any money from devs anyway. They sell their stuff to the business people who then force it onto devs. When I worked in government, we had some Oracle DBs. They were bought without consulting anyone who worked on the tech teams.

For large corporations and gov organisations I can see how that could plausibly be true... for everything else, not so much. At smaller companies the hierarchy is not so rigid or deep, and people are not so siloed, they must work together more closely and feel each others pain. I'm a dev at a such a small company, and in a position that I can make or highly influence such decisions. Oracle products will never be in o…

Hear, hear! Of course, if you're at a smaller company I expect the Oracle sales reps will be off hunting bigger prey, so that likely helps keep it out of your stack also...

Re: Dear Oracle, Please Release the JavaScript Trademark

#132

> Do not fall into the trap of anthropomorphising Larry Ellison. You need to think of Larry Ellison the way you think of a lawnmower. You don't anthropomorphize your lawnmower, the lawnmower just mows the lawn, you stick your hand in there and it'll chop it off, the end. You don't think 'oh, the lawnmower hates me' -- lawnmower doesn't give a shit about you, lawnmower can't hate you. Don't anthropomorphize the lawnmo…

[deleted]

Re: Dear Oracle, Please Release the JavaScript Trademark

#133

Earlier quoted context omitted.

They don't make any money from devs anyway. They sell their stuff to the business people who then force it onto devs. When I worked in government, we had some Oracle DBs. They were bought without consulting anyone who worked on the tech teams.

A business still needs to hire people to work on Oracle db. At my company they have trouble hiring for it. They resort to shared service orgs to provide DBA services. That means one DBA per 10-100 application developers. It’s awful. We do anything to avoid oracle because we can’t get a DBA to help us. Even use hadoop hive for non hive use cases. I guess my point is that these struggles eventually do reach the leaders…

When you're ready, EDB will be there to make the move as painless as possible :-)

Re: Dear Oracle, Please Release the JavaScript Trademark

#135
post #24
post #12

Can’t you just call it ECMAScript, or are they somehow different these days? Guy Steele told me once that Sun registered it with ECMA so they could tell people (governments?) that it was a registered standard and that ECMA was the easiest/fastest/most compliant way to get there. I’d always thought that ECMA was a weird place to register it.

Can’t you just call it ECMAScript We're at about the right point in the timeline to start calling it YavaScript which both solves the trademark problem and keeps us on the path laid out in prophesy.

YavaScript for the language, Yira for issue tracking. YetBrains for IDEs.

Re: Dear Oracle, Please Release the JavaScript Trademark

#137
post #100

Earlier quoted context omitted.

If I understand correctly it was a marketing thing (cof cof C#), but also the creators actually had plans to collaborate with Sun and (somehow?) integrate the language with Java.

Oh they did. You could call into the JVM from JS even in early 2010s Firefox. Called LiveScript, I believe.

yup, i wrote a dynamic simulation using this technique in the late 90s, using java to implement a rk45 ODE solver and js/html canvas for visualization and controls.

Re: Dear Oracle, Please Release the JavaScript Trademark

#139

Haha asking Oracle to give up legal rights. Good luck with that :) :) :) PS I never understood why they called it JavaScript since it has nothing to do with Java.

That was meant as a foundation to build some interview questions that might filter out the worst of the crowd.

Re: Dear Oracle, Please Release the JavaScript Trademark

#140
post #82

Earlier quoted context omitted.

Flash's ActionScript was also ab implementation of ECMAScript IIRC

That's one thing I never understood. For me they seemed like completely different languages. Now looking at history in Wikipedia, it seems that old version of ActionScript was based on old version of ECMAScript specification. And ActionScript 2 which introduced strict typing and classes (that look nothing like JavaScript) was partially based on ECMAScript 4(which was abandoned as being too different from previous ECM…

How do you see them as diverged? I've spent a lot of time thinking about AS, ES4, and working with modern ES, and if anything I see them as having converged. The largest feature of ES4 that ES3 did not have was classes, which were added in ES6. The second largest feature was optional static typing. Optional static typing is nearly a defacto part of the language (from a community/ecosystem point of view) with the popularity of Microsoft's TypeScript superset.
Post reply on HN