Cool setup, but the choice of Obsidian is kind of weird in this context (in an interesting way, see next paragraph). Instead of opening a subfolder of the Hugo project in Obsidian, one could just open the entire thing in VSCode or a similar IDE, enjoy a good markdown editing experience, AND use git integration and the integrated terminal (and possibly set up automated tasks) to run your local testing and deployment workflows.
Note that Obsidian's markdown editing experience is _different_ from (but not necessarily better or worse than) what you'd get in a typical IDE. So while the choice seems weird to me, it absolutely makes sense if the author prefers the feature set that Obsidian offers. Being supported by so many different editors is one of markdown's strengths, after all, and this kind of editor-portability fits right in with the other parts of "Fully Owned" from the blog post.
I mean, Obsidian is just a markdown editor. You could keep an identical publishing setup and use any text editor on the planet :P
But I honestly despise writing raw markdown in an IDE. If I'm writing (not coding), I need it to be somewhat visual, which means I want WYSIWYG -- and Obsidian is an excellent markdown editor, even if you don't use the other features.
My reasons for not liking writing "raw" markdown:
- Long links take up too much space. I put it in text so it'd be hidden
- No syntax highlighting in code blocks
- Text wrapping/font is typically not configured for easy reading of text
- A ton of markdown features are for visual formatting. Highlighting, bold, underline, strike-through, inline code, etc. If you stay in raw IDE no-preview, you never get the visual benefits.
- When I'm using markdown, I'm often mostly reading, and doing some writing, but even when I'm writing, I'm re-reading what I wrote constantly. It's annoying to switch to preview mode. Writing mode in IDEs isn't a pleasant reading experience unless you do a lot of configuration. (depending on the IDE of course)
I mean, writing raw md is fine for tiny little things. But because reading & writing are so linked, I don't like separate modes for each. I want to write in the visual mode I read in.
I find it annoying that I can get stuck in a mode when I am editing and the app is trying to render at the same time (e.g. I write some backticks to make a code block and Obsidian tries to be smart and add the second set and it encapsulates a bunch of lines I don't want it to) but to each their own I suppose. Vscode for what its worth has a preview that you can keep open side by side to see the visuals as you edit.
Holy cow! 10 year old me learned word processing first with wordperfect. I looked for reveal codes in other processors for years after that and was always disappointed when I couldn't find it.
Young me was like "how can you edit a document if you can't see the codes?!" Still to this day I wish I had it in word processors.
Another benefit of using an IDE like VSCode for writing and publishing your blog is you can use the copilot AI to fill in the front matter details for you, easily add a table of contents, or add a cohesive structure of subsections. Don't forget the shift + CMD + v command to see see a preview within VSCode.
Hugo is a great choice for an SSG, I find it logical and intuitive. As for extending it with a CMS front end, I looked at Decapcms.org - formerly Netlify CMS - it gives you the WYSIWYG editor and you can hook it up to an asset management platform like Cloudinary for images.
BTW just checked Cloudinary pricing - generous free tier looks like plenty for most blogs.
That might be because Kagi currently has "only" 43,508 members, according to their live stats. That number might be too low for you to be able to expect someone in your personal circle to already be using and talking about it.
The number being this low isn't a bad thing, though. Kagi is already profitable and the number is growing, that's all that matters for now. There's a free tier that gets you 100 free searches (I'm testing it myself right now, haven't used it enough to really have an opinion on it yet).
Regarding your point b: Heavily disagree. Even ignoring HN's seeming love for Kagi, surely you must have noticed the narrative about how AI is fixing search? People asking ChatGPT or Bing instead of googling things? Why would they do that if they were satisfied with Google? Also, Google search quality worsening has been a common news headline for years now.
By only doing clones to get data from Github, you're losing anything stored in LFS. Run `git lfs fetch --all` inside each repo after cloning to make sure you have the large files, too.
The point is that OpenAI is not sharing the result of that training with us, nor even the training set. In other words, they are ignoring both "attribution" and "share-alike" parts of the license, claiming that it's not applicable because what they are doing is fair use, and so copyright is not a concern.
What's creeping me out is that there's zero mention of how the nano-texture display affects pencil use.
The nano-texture on the standalone display Apple offered a while back was very fragile (if I remember correctly)... I would imagine touching it, let alone dragging a pencil across it, could very quickly leave visible scratches?
If not - will this wear through Apple Pencil tips like they're made of rubber?
In addition to the already mentioned Command Palette, macro expansion is also available as a quick fix, either by clicking the light bulb icon when it appears, or triggering it via hotkey (Ctrl+. by default).
I forgot what people were calling it but this is almost exactly the same idea as that trend where you ask ChatGPT to generate pictures, continuously asking for "more" of some aspect of the picture (make this dish more spicy, etc), only hidden by the fact that instead of simply asking it to make the code more complex, they're naming specific (but in the end, arbitrary) steps of what ChatGPT would still interpret as escalation.
To me, pausing to reflect is less of a problem compared to getting distracted and losing my place or having to read the same paragraph over and over again.
Back when I had a 40+ minute train commute (and was working in the office all week, pre-pandemic), I used to listen to audiobooks on 1.5-3x, while also reading the actual book at the same time. That worked wonders for me, and it's easy enough to pause an audio book with headset controls to reflect on something.
Possibly, given people are (to some level of course) basically fine, having someone walk off with your phone unlocked could have pretty annoying consequences at a time when you'd really rather not deal with them
> That said, from now on I'll probably have auto-lock turned on when flying.
I think you are far far more likely to have a random cardiac arrest or stroke while you are looking at your phone than have it ripped out of your hands in an airplane. The former has happened to several otherwise healthy people I know and the plane thing happened to a few people ever.
Also do you turn it on while you are a passenger in a car or bus?
And yes, both oklch gradients look pretty weird while the oklab gradient looks nice (if you can accept it going through grey).