krilnon

Awesome! It's surreal to see a familiar name making such a neat app. I saw this earlier today and had a small moment of triumph since I'm terrible at solving sudokus myself. A few people visit kF every once and a while; feel free to stop by!

Are you the same yeldarb as the one from kirupaForum?

I'm excited to see that Alex Warth is involved with this. In my late undergrad days, I was really excited by his OMeta language. It turned out that I'm actually really bad at writing PEGs (or even ANTLR grammars), so I wasn't the best candidate for advancing OMeta into common use, but the idea is really compelling.

There was a funny discussion on an MIT mailing list this summer when an (apparently) tone-deaf email was sent out by MIT Professional Education entitled "4 Ways You May Be Enabling Hackers"... which warned about the dangers of cybersecurity-style hackers.

RMS's response was:

> These MIT professors ought to know better than to smear us hackers by using the word "hacker" as synonymous with "security breaker".

Writing valid XHTML was good practice for writing valid XSLT. Browsers would definitely choke on invalid XSL. I remember spending a fair amount of time looking at that pale yellow Firefox error screen that would point out invalid XML documents during my XSL days.

It's been a while, so I'm not completely sure this is true, but I think any XHTML within an XSL document also had to be valid XML (that would also validate against the XHTML schema), so you couldn't get away with as much as you could with rendering a plain XHTML page.

There's an official specification for what and how a program that claims to be a JVM implementation should operate given Java bytecode. So someone writing a language that compiles to Java bytecode would typically either target the specification (and test on as many implementations as they felt necessary), or target a specific implementation like HotSpot and ignore the rest.

From the article:

> I have a working prototype of a JavaScript VM that is highly optimized for NGINX’s unique requirements and we’ve begun the task of embedding it within NGINX Open Source.

> I wrote the sorting algorithm in as3isolib

Oh neat. I don't recognize your username, but I submitted the first entry in the logo contest for that library in 2008, which ended up being fairly close to the final logo.

> Flash is certainly alive and well.

There's plenty of developer activity, but I'm pretty sure Adobe only has a life support team maintaining most things now.

AS4 was cancelled, so Falcon was the last notable language change. Most of the AoT iOS/Android targeting stuff was completed years ago, so now AFAICT it's just being kept compatible with new releases.

FP12 was supposed to be a huge jump, but now 12-17 (and the accompanying AIR APIs) have come and gone without pushing things forward meaningfully.

You're right about Fireworks. Some people do like to use the Flash authoring environment for general web graphic work, even though that's not its primary intent. A friend of mine still uses it for all of his web tutorials and book diagrams. (Flash has tools for exporting single frames in a variety of image/vector formats.)

You're right to point out the cultural divide w.r.t. tooling. It just seems to me that when two different people come up with pretty identical names for something and focus an essay/paper on that name, then there's likely an opportunity for some sort of cross-pollination of ideas.

Ah, great; thanks for pointing out that it has changed. The last time I looked at Rust in detail was mid-April, so I hadn't seen that.