- Collected media https://the-next.eliterature.org/collections/2
- A catalog introducing this software to a print audience https://archive.org/details/voyager-360-catalog/mode/2upa
351 karma · joined October 15, 2012
- Collected media https://the-next.eliterature.org/collections/2
- A catalog introducing this software to a print audience https://archive.org/details/voyager-360-catalog/mode/2upa
In practice, it works quite well. Here's more info:
https://marijnhaverbeke.nl/blog/collaborative-editing.html https://marijnhaverbeke.nl/blog/collaborative-editing-cm.htm...
Forms and submissions are mostly a web convention. I too think that's more natural, but there are a lot of existing contexts like settings where the expectation is that making the selection doesn't require an explicit "save" step.
Designing for visionOS - https://developer.apple.com/design/human-interface-guideline...
Inputs: Eyes - https://developer.apple.com/design/human-interface-guideline...
Principles of spatial design - https://developer.apple.com/videos/play/wwdc2023/10072/
Create accessible spatial experiences - https://developer.apple.com/videos/play/wwdc2023/10034/
While I don't think there will be a mass adoption by people willing to put on goggles throughout the day, it's clear that a lot of Apple's ecosystem is being directed toward environmental and situational computing, and the SDK backs that up. Using gaze detection to focus on more than one device in a room, surfacing certain interactions in specific rooms, and low-lag screen mirroring from devices are all pretty high-cost investments that are likely to find uses in other products. I look forward to what kinds of "continuity" type features this tech introduces.
https://www.shopmoment.com/products/wall-mount-for-magsafe/s...
https://www.exploratorium.edu/ronh/SLOM/0301-The_FAX_Machine...
Does this mean that Step Functions and CloudFormation will adopt this library? Both already have similar visualizations.
Do you envision any extension points to the way engines are implemented that could better enforce boundaries? In our engines, there was nothing that referenced another engine's resources, leaving the main application to handle route mapping and ActiveRecord associations between app models and engine's models.
I feel like the use-case for engines has long been around supporting framework like functionality (Devise, Spree, etc), but I wonder if there are changes to be made that better support modularization for large apps.
I'm curious to know more what sorts of challenges they have around managing dependencies across engines — I think what we were doing was fairly vanilla Rails, and we didn't have the opportunity to run into those sorts of issues.
I wonder if something like Rollup or NCC could be used to create a single-file Javascript dependency in the general case that is only used for vanilla Webpacker builds, and relying on the individual packages could be something left for when you need to customize the Webpacker build.
Judging by some of the Hey developments, it's possible we could see a much more lightweight JS integration in Rails in the future:
http://worrydream.com/ClimateChange/
The investment is not only in the machinery, but in tools to model, observe, and predict efficiency.
One reason Lispers find macros so beautiful is the simplicity of writing macros using the exact same list processing functions. The code-is-data thing is reinforced through the fact that the AST is one-to-one with the syntax.
It doesn't get much better than William Steig — all of his books give kids the tools and analogs to confront complex emotions and overcome fears. Amos and Boris is my favorite, The Real Thief is excellent if they're a little older.
It's an interesting question whether the tendency to overcomplicate a largely static site by implementing it as a single-page app should be attributed to the average developer or to the creators of the library though.
Personally, I feel the best way to learn is by experience and by exposure. By seeing similar code in different contexts, you can learn why React programs tend to rely on certain patterns. To that end, working through something like How To Design Worlds (http://world.cs.brown.edu/1/) or the Elm guide (https://guide.elm-lang.org/) will give you points of comparison that will help you better articulate what you decide to do in React.