chabad360

Iirc there was a link posted at the end of the talk?

Edit: I just realized I was thinking of the patchwork demo.

Either way, after using a Remarkable for years, I've wanted something that actually tried to make use of the "digital" part of digital paper. When I came across you guys a few years ago, I was hooked (tbh, would love to work for you guys). So seeing the playbook demo was very exciting.

One of the coolest demos I've seen out of Ink N' Switch in while (tbh, it's seemed like they were really cooking for the year or so).

Unfortunately, it seems they live demo they published is missing a number of the demos they featured in the talk (and its unclear how to do your own things), so it's a little hard to evaluate this more deeply.

I find staycations to be the same thing as a vacation but at home. Especially if you liv in more touristy places (NYC for instance), there's plenty of vacationy things you can take while not leaving more than 10 miles from your house. I like going to the beach or to my parents or what not (even going on trips), but I still need something to keep my mind busy. I hope that sums up the difference well.

Yes. This is my favorite way to vacation, and I'm glad someone has found a better name for it. I do not enjoy simply sitting around idle and occasionally going on a trip, I end my time off feeling drained and need a vacation from my vacation. One year, I had an itch to try my hand at Godot and game programming, and I saved it for my next vacation. I'd never felt more relaxed after a vacation, it's the same as what the author describes: I like being intellectually stimulated, I just needed a break from work, not from trying new things.

This article has helped me figure out some of what made that work, and has given me some ideas of how to try to capture that again.

Learning Rust and writing userland drivers for my audio interface's built-in DSP.

While the language itself doesn't seem very interesting (which is perhaps the point). The idea of building a new language on top of the CLR runtime feels very wise. Instead of a new language suffering from a lack of ecosystem, you get everything else that's already built, even in other (CLR-based) languages. This does leave me wondering what the trade off is. Do you sacrifice any potential language features for CLR compatibility? Or provided you can get it compile, it will run?

Also, are there other language ecosystems with a similar capability?

While I think this is good advice, I do think one can make the given writing more accessible by adding small details, like expanding acronyms the first time you use them. Or providing a link to introductory reading for a given topic, or just explain yourself. I've found that sometimes I was being too terse when describing something, and it made it hard for everyone to understand, not just beginners. But it took my less-technically-inclined friends to point it out because they were unable to understand it at all, as opposed to those who could understand it a little.

This post appears to be a newsletter with links to some of their recent posts. Admittedly nothing super interesting stood out to me this time. But I am still waiting very impatiently to hear more about PlayBook, which is supposed to be their ultimate interactive paper product with all the learnings from their previous experiments and research.

Widgets are possible to do with Flutter, but you have to implement them natively and do a bunch of FFI for passing data. I went cross-platform from the start because I have only so much time, and it's much easier to write 95% of the code once instead of twice.

I would like to offer that as a feature. There are some companies that sell access to connected car APIs, so I would probably go through that route.