moltensyntax

No unit tests? :)

> Significands are fixed point, and fixed point adders, multipliers, and dividers on these are needed for arithmetic operations... Hardware multipliers and dividers are usually much more resource-intensive

It's been a number of years since I've implemented low-level arithmetic, but when you use fixed point, don't you usually choose a power of 2? I don't see why you'd need multiplication/division instead of bit shifters.

We as humans have a lot of intuitive tools for knowing whether a source of data is trustworthy. AI could possibly approach this ability given enough training... we'd need to do something like add a "trust" score to every node in the graph.

Yes, this is possible, depending on the codec and container. I have done similar operations with h264+mp4.

It's good to be able to edit video without losing quality.

Are you sure you need sub-keyframe precision? In h264+aac+mp4, for example, if it's not keyframe aligned, the result is usually a stalled video frame for a split second, but since the audio continues smoothly, it's not that noticeable.

If you know the exact codec settings that were used to encode the video, you can create new pieces to be fit losslessly together. Otherwise, it is more difficult.

Contact me on twitter at @downpoured and I can describe more.

This article again? In my opinion, this article is biased. The subtext here is that the author is claiming that his "lzip" format is superior. But xz was not chosen "blindly" as the article claims.

To me, most of the claims are arguable.

To say 3 levels of headers is "unsafe complexity"... I don't agree. Indirection is fundamental to design.

To say padding is "useless"... I don't understand why padding and byte-alignment that is given so much vitriol. Look at how much padding the tar format has. And tar is a good example of how "useless padding" was used to extend the format to support larger files. So this supposed "flaw" has been in tar for dozens of years, with no disastrous effects at all.

The xz decision was not made "blindly". There was thought behind the decision.

And it's pure FUD to say "Xz implementations may choose what subset of the format they support. They may even choose to not support integrity checking at all. Safe interoperability among xz implementations is not guaranteed". You could say this about any software - "oh no, someone might make a bad implementation!" Format fragmentation is essentially a social problem more than a technical problem.

I'll leave it at this for now, but there's more I could write.

This should now be resolved, Safari should work fine.

It looks like Safari implements regular expressions slightly differently, and it leads to the parser behaving differently. Hope to be addressed by the end of the week.

I liked Runtime Revolution. I wish the broader coding community would taken environments like this more seriously, is the text editor sacred? I left the platform before they added more mobile+online support, I'll have to see what they have added recently.

I'm still kind of awestruck by this. Hosting an OS inside a browser. It's great as a time capsule to perfectly see the past. But because it's an emulator, it would be difficult to add a more modern feature, like ViperCard's share-url-to-stack and save-stack-as-json.

The closest I could get so far is to set the browser zoom to 200%, click in the url bar, and hit F11. Looks pretty good in Chrome.