goddamnit, read for a solid 5 minutes until I realised the rest is paywalled, sigh. No pasty facts isn’t worth another subscription. I have many other interesting things to do
That’s a shame, though I do see that it is difficult to make any money from what it is. I’m glad they didn’t sell it to someone big for all the user’s data, though it is still early
It's owned by Automattic, isn't it? I assume they're simply keeping the lights on for whoever wants to use it.
For about a year I've noticed that it tends to quit on its own on my Mac. Whenever I need to look for a note I realize the app is inactive and I need to re-launch it. Then it works perfectly well, until somehow, at some point, it quits without me realizing.
It's sad that they're not fixing it, and that eventually it probably won't work with newer Mac OS and iOS versions. I should start looking for a way to migrate off of it.
It makes me miss the shareware era, back before races to the bottom and free corporate giant competition had all but eliminated any kind of profit margin on simple, but thoughtfully designed and well-built software.
How many of us have had ideas for little utilities and such that were never followed through on because the chances of even breaking even on them was so low? I know I have several.
In the UK I've not been able to find high wattage (10-20W) LED lightbulbs with high CRI, some don't even mention it in listings, let alone SSI, which I have never seen.
Where are you seeing these? Is this industrial/commercial suppliers?
except chess is a solved problem given enough compute power. This caused people to split into two camps, those that knew it was inevitable, and those that were shocked
Since no-one mentioned the Cynefin framework yet: Notice that there's a little fold at the bottom centre of the diagram: Chaotic (unknowable unknowns, etc) things will always resolve themselves to simple states.
Fires will eventually burn out, the result will be simple to understand. Simply your business won't exist anymore.
There are more nuanced examples but I believe the above explains the principle.
The Key is to handle things early, before the most probable/default resolution, if its one you're not happy with.
No-one uses that original OOP at all, no-one sane anyway.
The way its used now is for dependency injection. All your logic is in services that are injectable and unit tested. All your data is in simple immutable DTOs.
All the OOP tricks, classes, instances, interfaces, polymorphism, its all good for wiring up your logic, replacing bits at runtime. No-one actually models their domain with pure OOP. Urgh, that would be awful.
But also to echo other commenters, this isn't interesting insight...
not original commenter, but I have. Either through their manipulation, or just being in the same place, doing the same things. Didn't like them as a person, but they were decent to me, so some sort of reciprocation happened, didn't last though.
It's almost the same argument, but backwards: You think they are a good person, so you want them to do well. Because they are good, they also want you to do well. Same result, but intentions are backwards.
Not only that, banks are generally pretty diligent about that sort of thing and have enough customers and resources that if their website is misconfigured someone is going to report it immediately and they're going to fix it immediately. Which means that a certificate error on a bank site is suspicious.
Whereas a certificate error on a disused blog is pretty much what you'd expect from a disused blog.
reply