Blurb: WANIX takes WebAssembly to the next level. Edit, compile, and run WebAssembly from a WebAssembly UNIX-like environment entirely in the browser. Written in and using Go as a runtime, WANIX draws from Genera and Plan9 to provide a local-first operating and development environment of the future.
It's written in Go, and has a Go compiler available at runtime.
> I have reverse engineered secret security algorithms used by the CIA and can break any message they encrypt. As proof, here is the last few lines of an implementation of their encryption function in Lisp
The joke misses the mark because Lisp code usually coalesces all the parentheses in the same line at the end of the block. It does make sense for Ruby, though.
Start with a list of positive integers, (e.g. [7, 5, 3]) and your goal is to make the same list, in reverse ([3, 5, 7]).
Operations:
1) Split an integer into two smaller integers. (e.g. [7, 5, 3] → [6, 1, 5, 3])
2) Combine (add) two integers into a larger one. (e.g. reverse the last e.g.)
Restrictions:
1) You can never make an integer greater than the largest integer in the original list.
2) You can never make a move that results in the same integer appearing in the list more than once.
I haven't tried it -- I installed the VF2 Debian fork in April 2023 or so, then switched to SID, and I'm still on that. I think Ubuntu 24.10 will have a lot better support; mainline support for the VF2/JH7110 is almost complete for 6.6: https://rvspace.org/en/project/JH7110_Upstream_Plan
> Killer micros of today are a lot like flourescent lights -- cheap to operate, prevalent, and expensive to turn off. To see a machine standing idle, when you were raised as a child to "use cycles efficiently" is a gut-wrenching experience. Just remember Alan Kay's prediction: In the future, computers will come in cereal boxes and we will throw them away.
March 20, 1990. I haven't found a source for Alan Kay's prediction.
Various fortune files attribute the quote to Robert Lucky. I would guess that it was misattributed to Alan Kay since quotes often get attached to famous people.
"In the future, you're going to get computers as prizes in breakfast cereals.
You'll throw them out because your house will be littered with them.
-- Robert Lucky"
Or this one, from a service I worked on a couple of years ago:
sequenceDiagram
Title: Service Signup
autonumber
User ->> App: User enters email address and password
App ->> Server: Makes API call to register the user
alt is not registered or already registered
Server ->> App: Sends a token for authenticated API calls
App ->> App: Generates unique ID
App ->> Server: Makes API call to link user's account with unique ID
else some other error
Server ->> App: Returns [TODO: add error cases here] error
App ->> User: Display error
end
I hated drawing diagrams with a mouse, but when I found mermaid, I started using sequence diagrams everywhere.
> Diagrams are low value window dressing.
It's about communication, as the article said. The people who needs the diagrams the most are often not tech-savvy.
I've used mermaid and lots of other tools. Mermaid is my quick and dirty tool of choice lately, actually. I sank a lot of time in using mermaid to get some sequence diagrams. They suck both visually and the process of creating them is also terrible. But it gets the job done as far as ass-coverage is concerned.
The example above tells me that you have a bog standard login thingy that behaves exactly like a login thingy should work (no surprises there). A great way to fluff up some document where you state that your login thingy should be a thing in your thing. Great example of why diagrams are a waste of time. There is zero useful/surprising information in there. Plenty of things I would challenge though. Why does the app have to generate the id for example? What's wrong with the email address as an id?
So not only is it uninformative, it's probably wrong.
> Great example of why diagrams are a waste of time.
I need something for the tech people, and I need something for the money people.
The diagram gives my target audience (again, non-tech people) an overview of the system. There were sequence diagrams for all the functionality we wrote code for. Technical specs and documentation were also written up, but the money people won't bother to wade through that to understand how it works; the dev team can read that.
> Why does the app have to generate the id for example? What's wrong with the email address as an id?
The example was extracted from a project I worked on a couple of years ago. I obfuscated what the "id" field is on purpose. If it helps, think of it as the unique device identifier used to send push notifications.
> So not only is it uninformative, it's probably wrong.
