They're bringing up the phone release to a late August unveil and shipping this year, and the Material Expressive update will ship after that, so it seems a big one time shift to attempt to time it with hardware.
Btw, Mojo's development is a masterclass in language development and community building, it's been fun watching Chris go back to fix technical debts in existing features rather than proceeding with adding new features.
Modular (the company behind Mojo) uses it in production. I imagine that if they have any clients then those also use Mojo in production - albeit indirectly - since all the GPU kernels used by Modular are written in Mojo.
I've found that sometimes the first action doesn't even have to involve directly working on the problem, just trying to write down a series of actions you need to take in a todo list can unblock you mentally.
Sometimes I can trick myself into getting started that way.
The trick is to come up with a tiny goal and give yourself permission to quit once you reach it so it’s not like your overwhelmed by the full task.
The smallness of the task is important, but it’s even more important that you genuinely give yourself permission to stop when it’s done. If you don’t do that, it’s not “one small task”, it’s “step one in a big task” and you’ll keep procrastinating
For coding it’s a sequence of:
“Ill just get all the software and documentation open and organized”
“I’ll create a few empty files on a new branch”
“I’ll just stub out a few things I KNOW I’ll need”
…
For other non-code writing, I’ve occasionally been able to hack it in a similar way by writing progressively more detailed outlines.
For physical projects, sometimes it’s just about gathering supplies and organizing tools.
Go's error handling fade away after a month of consistent use, I would not risk backwards compatibility over this. In fact, I like the explicit error handling.
I wonder why it wasn't written in Swift. I mean, if you want to make an app targeting a specific platform and willing to invest time into a native language, might as well use the platform's official native language.
Apple only sees developers as a revenue stream to squeeze dry. Investing into Apple-only technologies is getting yourself into an abusive relationship. macOS is still a good platform, but staying away from Swift gives you an escape plan.
There's also no point having a native UI on macOS any more. Apple ruined it themselves by switching to flat design, and making their own UIs and apps an uncanny valley between macOS and iPadOS. There's no distinct native look-and-feel on macOS any more.
Obsidian is so useful to me, I don't mind paying for the sync to support Obsidian dev.
The notes being markdown is also very useful, I spend most of my time in a text editor, so I installed a Neovim plugin that works a bit like Obsidian [1]. So, for simple note-taking, I don't have to open Obsidian at all. It comes in useful when I need to use the massive collection of plugins, especially Excalidraw.
reply