397 karma · joined January 12, 2011
At 6:08am Eastern on Sunday, Linode's status page acknowledged big trouble "related to heating/cooling complications in the [Newark] data center due to a power outage."
While the majority were down for several hours, one customer's VPS didn't come back until around 9:30pm Eastern. Linode's status page still indicates recovery work is in progress.
This is by far the longest Linode outage I can remember.
While #hugops are definitely in order (I'd send the techs a pizza if I knew where to send it), I am also curious if others are still seeing servers down at this point.
"Write your frontend in JavaScript, application logic in Rust, and integrate deep into the system with Swift and Kotlin."
"Bring your existing web stack to Tauri or start that new dream project. Tauri supports any frontend framework so you don’t need to change your stack."
"By using the OS’s native web renderer, the size of a Tauri app can be little as 600KB."
So you write your frontend with familiar web technology and your backend in Rust, although it's all running in one executable.
I am curious if it would be all that much worse if your backend was also JavaScript, let's say in Node.js, but it certainly depends on what that back end is doing.
I'm interested to see whether the final feature set will be larger than what you'd get by creating a type-safe language with a pythonic syntax and compiling that to native, rather than building custom hardware.
The background garbage collection thing is easier said than done, but I'm talking to someone who has already done something impressively difficult, so...
onepostwonder.com
It's been running for over a decade, although the community has always been small.
It's currently invite-only, similar to how LiveJournal used to be, but drop tommybgoode@gmail.com a line and mention this post if you'd like to give it a try and I'll send you an invite, which will include invites to give others you'd like to hang out with.
As near as I could tell at the time, the MPO format is literally just two JPEGs directly appended in one file.
They are right though that wasmgc might have a bigger impact than wasm alone. Lots of attention is deservedly paid to Rust but people use garbage collected languages more.
Game state is kept in memory, the server is single process (Node.js as it happens), connections use websockets, it just works.
Does it scale? No. Could it scale with a similar approach? Sure, with some additional work: separate games could be distributed over many instances (a sharding strategy). There's no redundancy there, but it's a game, not a credit card processing system.
However, I do snapshot game state in JSON files on disk so that games are not terminated by every new deployment. In a single-process model, that's safe when using synchronous filesystem calls. Just don't try it in a multithreaded system. Though it may take many moons, you will eventually lose your "poor man's database" to a race condition.
Still, would I use this technique to host people's taxes? Hard no. I wouldn't even use it to host their blog posts. Durability matters for those use cases.
I first announced tome here recently and received a kind and encouraging response. Here's a progress update since then:
* Quite a bit of JS syntax highlighting. Check out the screenshot. Template strings were fun.
* Indentation is much more syntax-aware, taking into account {, [ and (.
* Indentation is not confused by comments or strings.
* Support for other languages can now be contributed, following the pattern set by languages/javascript.js.
I need to test it more, but it seems one thing I don't need to worry about so much is Unicode support, because I happened to make a good choice early on. tome represents the file as a two-dimensional array of (deep breath) grapheme clusters, as the UTF-8 experts call them. This means emojis and such "just work," as long as I don't forget and call `split` on a string somewhere.
I've updated the Plan section of README.md to cover where I'll be taking things next. I want to tackle parsing more fully, but I'm going to focus on day to day usability stuff for a while, as tome is fast becoming my daily driver.
I'm thinking about support for language servers. In principle it's the right move, in practice they seem like kind of a lot.
Contributions are of course welcome.
What would you like to see in tome?