jmitcheson

Umm this is amazing!

The company I work for displays large engineering drawings in the browser; right now we have to choose between manual png conversion and loading the vectors directly (each one has its own problems). I tried the snippet application with one drawing and it renders perfectly.

For our application we have a 'Google Maps' style viewport where you pan and zoom with the mouse, though. Right now I'm seeing if Gemini 2.5 Pro can refactor the snippet application to work this way. Did you have any plans for building another type of snippet application which works in the fashion?

tl;dr "inadvertent exposure to endocrine disruptors in utero"

There is a newsletter called 'The Rundown' but it's more on the consumer side of gen AI; rather than hard academic research

https://www.therundown.ai/

It could still be quite buggy with Oculus and Vive hardware. They have only enabled WebVR in "Cardboard" mode on mobile which has a much smaller surface area.

TL;DR is for people who forget "statement, explanation, example". Usually, they write some poorly formed paragraph and put a "TL;DR" at the end. Often, that TL;DR is simply the "statement" part of the paragraph that should have been at the very beginning anyway.

TL;DR: most people can't English anymore.

If anyone's interested in how the exploit works, here is my humble interpretation of the pastebin link:

jsaxton86's comment sets the scene nicely so I'll just copy it here:

"This family of JRE attacks is far too common. Basically, when an unsigned applet runs, the JRE tries really hard to prevent it from creating a ClassLoader object. However, if you manage to create a ClassLoader object, it's game over -- you can break out of the sandbox and do whatever you please."

The exploit is very clever, it never actually creates an instance of the ClassLoader object, but rather it uses Java reflection to call a particular method on a ClassLoader object, which was tricked into creation inside a separate exploit involving the JMX (Java Management Extensions) framework.

JMX has its own methods to instantiate classes, and a subclass of ClassLoader ("sun.org.mozilla.javascript.internal.GeneratedClassLoader") is passed in as a String; then the method defineClass is called via reflection in a way that deceives all the ClassLoader protection. Once this method is allowed to be invoked via reflection, it's "game over" as explained at the start.

http://pastebin.com/raw.php?i=cUG2ayjh http://www.oracle.com/technetwork/java/javase/tech/javamanag... http://www.cs.rit.edu/usr/local/pub/swm/jdoc6/com/sun/jmx/mb...

When I first saw this post, it was greyed-out from down voting. Now, it's at the top of the thread. This place is strange.

"Dr." is a title; "doctor" is noun which only ever refers to an MD.

When I'm doing front-end development, I love having a back-end guy who can flip the switch and turn it on.

It's probably related to a recent change in policy - http://www.kickstarter.com/blog/kickstarter-is-not-a-store

"-Product simulations are prohibited. Projects cannot simulate events to demonstrate what a product might do in the future. Products can only be shown performing actions that they’re able to perform in their current state of development.

-Product renderings are prohibited. Product images must be photos of the prototype as it currently exists."

At that point, you were way past the idea stage.

Just drag the tab out to its own window. Then you can minimize it and Chrome doesn't consider it to be in the background.

Random aside: I just noticed that after you drag the Gangnam tab out to its own window, then you can open other tabs in that same window, and it doesn't put the Gangnam tab in the background anymore. But if you put the tab/window back in the original set of Chrome tabs, then it will.

Hey there, I'm the developer of a browser based IDE called pixelJET. I was researching visual JavaScript debugging concepts to integrate into pixelJET when your post came up on HN.

It's not really a real world applicatoin yet, but if it helps, your post inspired me gave me some ideas for integration into the product. If I publish anything I'll be sure to give you a shout out :)

A couple of thoughts for the demo, it would be cool to see the actual JavaScript source code too, so you could get a feel for what the visualisation is showing you. Also, noting which functions were event handlers would be useful, although a bit tricky.

I know there are a million and one people offering arm chair suggestions, but IMO it's about time that HN got sub-forums and moderators.

I'd like to see a /startup or similar, moderated by entrepreneurs to set the tone of what posts or comments aren't welcome.

For that matter, a /front-end would be cool too. HTML/CSS/JavaScript demos posted here grind my gears so much; the comments are all negative and totally not constructive.

Nice work, it looks really good.

One minor (and I mean really minor) design thought: in the section near the bottom "Selected Projects", there are grey buttons and blue buttons; in the close proximity of the blue buttons, the grey buttons sort of look like they are inactive or disabled, at first. I put my mouse over them and figured out they were indeed active links, but maybe someone non-technical might not do that.

Do you mean that it would be too much of an engineering burden, or that they wouldn't trust Kaspersky?

In any case, such a thing could become mandatory one day, if the so-called "cyber war" on oil/utility/manufacturing continues.

Yeah I'm in Australia too :). Melbourne. I saw "Underground" on TV and became bored very easily. I read two paragraphs of the text version that you linked and I was hooked! Makes me wish I was 20 years younger. I suppose we have our own movements now, but the physical computer bazaar's and the culture sound awesome.

I think I down-voted you by accident. I meant to upvote! Clumsy mouse movements. Great link.

You're being a bit disingenuous by not mentioning the inbuilt protections that the HTML5 Fullscreen API offers.

"Also, any alphanumeric keyboard input while in full-screen mode causes a warning message to appear; this is done to help guard against phishing attacks. The following keys are the only ones that don't cause this warning message to appear (...)"

(https://developer.mozilla.org/en-US/docs/DOM/Using_full-scre...)

The article and demo are nice though. Good work.

Thanks, we'll increase the timeout. Clicking a menu item on the slider will stop it from moving :)

It might not sound like much, but the differentiating factor is pretty much that it's all inside the browser. You get a professional live coding setup, and instant hosting environment, and all you need is a browser. You can access it anywhere; don't need to set anything up to use it; and it's the same setup on any computer or device you happen to be using.

Right now, web development is carried out with an array of disparate tools which vaguely connect to each other, if at all, plus you have to know how to set them up. pixelJET is not trying do anything new, or anything that can't be done by some existing combination of tools, but it brings them all together in an easy to use package, available anywhere in the world, on any browser.

That's definitely the sort of vision we have for the product.

Full iPad support is not ready yet but should be coming soon.

A bug is currently preventing the code editor from loading on the iPad browser. Quickfire (the panel down the bottom, that replaces the browser debugger) will load fine, but the interface is slightly awkward to use because it is not touch optimised yet.

Wow, the paul irish! Hi...

That's totally right and it's a very cool feature, although that will only help you if you are using Chrome. One of the things I wanted was for the product to work on any browser, and without any plugins.

Thanks. We have a text editor though; not sure if you saw it. If can operate from a separate window, and it hotswaps all the HTML/CSS/JavaScript you code, without any lag.

Our code editor is actually the open source "Ace editor" (http://ace.ajax.org).

Of course, not everybody wants to code inside their browser, and that's fine. For those that do, we aim to make pixelJET the best way to do that.

That's something we're still trying to work out ourselves. As for professionals, the aim is to replicate a certain existing workflow, but move it to the web. That workflow is design file > HTML template > ??? (cms template, etc.)

A lot of people just use a text editor, their browser and firebug, so we want to serve those people but with a much faster and streamlined experience.

That's a really good question, one that I spent a lot of time thinking about before I started. Basically the way that they deal with changes to the page is fundamentally not suited to persisting the changes back to text. It would take a lot of hacking :)

Thanks!

Hi, thanks for the comment about the editing. The main problem this solves is that the Chrome Dev Tools/Firebug don't save your changes back to your source code. For people who do alot of front end development, they code some adjustments (sometimes many at once) but then have to 'recode' those adjustments in their css file. This is error prone and slow, and sometimes this has to be done dozens of times per day!