Home
10 comments
shepmasterover 1 year ago
Primary maintainer of the Rust Playground here. I'm glad to see open source doing the open source thing!<p>I'll try to answer any questions from the Rust point of view, and it will be good to hear of any large differences between the two implementations.
评论 #37821430 未加载
评论 #37823682 未加载
评论 #37829377 未加载
junonover 1 year ago
Wow I've been out of the Java game too long it seems. This barely looks like Java.
评论 #37821887 未加载
评论 #37821825 未加载
pjmlpover 1 year ago
Looks quite nice.<p>If we are already by feature requests,<p>- JVM bytecode view<p>- JIT machine code view<p>- Select between OpenJDK, OpenJ9, Azul, GraalVM,...<p>- Enable code generation specific features per selected JVM implementation<p>Anyway only brainstorming some ideas, it is already quite nice as it is.
评论 #37822273 未加载
apignottiover 1 year ago
[Shameless plug]<p>We have just renewed our fully-client side take on the "Java playground" concept, powered by CheerpJ<p><a href="https://javafiddle.leaningtech.com/" rel="nofollow noreferrer">https://javafiddle.leaningtech.com/</a><p>AWT and Swing apps work as well, which I believe to be quite unique.
评论 #37821911 未加载
CrendKingover 1 year ago
A big mistake about all these Playgrounds is that it forces the "Source Code Pro" monospace font (or any specific font) rather than respecting user's monospace font choice in the browser. Programmers tend to be picky about the font choice, which you can easily judging by just how many these fonts are out there competing. There is really no aesthetic reason to do such a forcing, and even you do have political or financial reason to do so, it's extremely easy to block remote font anyway. So stop doing it please, or at least provide a checkbox to disable it.
评论 #37837472 未加载
0JzWover 1 year ago
github link here: <a href="https://github.com/McCue-Software-Solutions/java-playground">https://github.com/McCue-Software-Solutions/java-playground</a>
38over 1 year ago
huh, Java can just do "void main" now? or is the playground omitting some boilerplate? that was one of my main reason for never touching Java/C#, too much ceremony just to write a basic program.
评论 #37822163 未加载
评论 #37822307 未加载
dj_gitmoover 1 year ago
My corpo firewall is blocking because of what seems to be a TLS issue.
评论 #37821307 未加载
评论 #37821493 未加载
avgcorrectionover 1 year ago
I'm guessing this is the fork <a href="https://github.com/bowbahdoe/java-playground">https://github.com/bowbahdoe/java-playground</a>
评论 #37821475 未加载
goranmoominover 1 year ago
So for people (like me) who were surprised by how modern the Java code looked like… here are the following features/JEPs involved in the Java code:<p>Finalized features:<p>- JEP 395: Records, finalized in Java 16: <a href="https://openjdk.org/jeps/395" rel="nofollow noreferrer">https://openjdk.org/jeps/395</a><p>- JEP 409: Sealed Classes, finalized in Java 17: <a href="https://openjdk.org/jeps/409" rel="nofollow noreferrer">https://openjdk.org/jeps/409</a><p>- JEP 441: Pattern Matching for switch, finalized in Java 21: <a href="https://openjdk.org/jeps/441" rel="nofollow noreferrer">https://openjdk.org/jeps/441</a><p>Preview Language Features:<p>- JEP 430: String Templates, preview language feature since Java 21: <a href="https://openjdk.org/jeps/430" rel="nofollow noreferrer">https://openjdk.org/jeps/430</a><p>- JEP 445: Unnamed Classes and Instance Main Methods, preview language feature since Java 21: <a href="https://openjdk.org/jeps/445" rel="nofollow noreferrer">https://openjdk.org/jeps/445</a>
评论 #37822337 未加载
评论 #37822741 未加载