Good call. Perhaps I should have said newer.
Recent @shortformblog Activity
Good call. Perhaps I should have said newer.
It’s worth noting that this is a bit more powerful than Pine64’s other hardware releases, in part because it’s using the same base chipset as its Quartz64 SBC, released earlier this year: https://wiki.pine64.org/wiki/Quartz64
I just got a hold of my childhood 386SX (not the exact machine, the same model) and I’m working on slowly, but surely, getting it set up. So it’s fascinating to learn new things about it like this. Great piece.
I’ve used Maestral a few times and find it works best with narrower folder limits—I ultimately went with the official Dropbox client for my M1 but I use it on an x86 machine in which I only need a handful of folders.
The creator is doing good stuff.
While I see others disagreeing with this, I do find it really interesting and think that this in an interesting angle to dive into—how musicians in other countries prepared for MTV without even realizing it.
It’s worth noting that Olivia Newton-John was well-known to American audiences thanks to Grease and the fact that she already had a longstanding music career in the U.S. by the time MTV came along, but certainly it might have helped with the production values on “Physical.”
Personal Computing on an Amiga in 2021
214 points • 138 comments
Clearly he designed an example from scratch to underline his basic point, which makes sense because he’s making a point about user interface design. There are only a handful of languages in there—presumably an actual list will have more.
What a silly reason to not use something.
Good eye. Probably should be made more clear in the readme, because it’s the obvious question that came up for me.
The developer of Hello would disagree with you: https://medium.com/@probonopd/hellosystem-three-layer-ux-des...
Given that there’s 20 years of “behind,” and many of those machines are no longer getting updates, what’s the harm? The dev learns something and the community gains knowledge from the project.
I was once critical of ReactOS for similar reasons, but I’ve realized just how beneficial that project has been to OSS as a whole. Even if they fail they will uncover a lot of interesting stuff if the project continues long-term.
Agreed; and to be clear, it’s great if both evolve separately. Building MacOS analogues is a great goal for BSD-based projects, especially given all the old machines that could use them, and I think will attract new folks to that community.
Airyx’s developer may want to say hello to the developers of Hello, who are doing something very complementary to this with UX—and are quite far along already. https://hellosystem.github.io/docs/
Keep me posted. Would love to see a revival of The Deck.
Please let me know when you expand in that way as well. I would love to look into it.
Tumblr users lash out against its beta subscription feature
2 points • 0 comments
Even though Jakob Nielsen is very much still alive, he’s rolling in his grave.
I found using the editor confusing and not at all following my expectations for what an editor should do. (To start with, a displaying cursor or some sort of cue of where to start typing, would be nice.)
I would suggest spending more time polishing the writing experience because that matters a lot to writers and when it’s not there it can be an immediate turn-off. Look at tools like iA Writer or Gingko for ideas.
This is probably also reflected by the fact that they stopped patching it relatively early in its life. Three years of patches for what is effectively an internet-connected hard drive, presumably one that its target audience is going to be using for many years as something that “just works,” reflects a disinterest by Western Digital in living up to its own sales pitch.
FWIW: The reason why they aren’t easy to automatically remove is because they are often put in manually by editors.
Hi, I run a long-form newsletter. I send it out twice a week. I spend many bleary nights putting content together for it, and its pieces occasionally appear here on Hacker News. I do a lot of research for it—and pay lots of money for tools to access that research. I often do interviews. It often brings in contributors. Those contributors are paid.
It has an RSS feed as a service to readers. But it was built as a newsletter because I specifically wanted to experiment with that form and felt that I could do interesting things with it.
Since I started it six and a half years ago, a couple interesting things have happened in the sector: One, the interest in building a business model around blogs has shifted over to the newsletter space. And two, people who wouldn’t have paid to access a blog now are willing to pay to access a newsletter.
I like to keep my content open to a large amount of people, so I rely on newsletter sponsorships as a business model, but my advertising approach is very minimal compared to other publishers. I’m not particularly aggressive with my signup form—I run it at the top of my front page and put a pop-up option at the bottom of the article, and sometimes I implement an occasional interstitial when an article seems like it’s doing very well and I want to catch the user’s eye.
But I don’t do as much as I could. It probably could be larger if I did.
But this isn’t about me. This is about this comment. Which is to say: This is a really cruel thing to say about newsletters. I know a lot of creators who put hours of work into their newsletters each week on top of full-time gigs, grinding it out with the goal of hoping to do something with that newsletter.
It also ignores the business realities of the newsletter space. Trying to build a blog into a business is really tough these days (it was back then too, something I know because I was blogging back then). But newsletters have created a path of opportunity for those who want to build things independently.
And while I will never claim that the work they do is perfect, it’s certainly not blog spam.
So I request, hey, maybe research the space before you use such a broad brush. Thanks.