I think every successful Show HN post ends up with a "thought this was about X" or "didn't look up the name first?" comment. Consider it a win! I don't think anyone will mistake a tool for putty with your tool, but you might share a google search page with it.
I don't think a modern flash would come after web app UI in the same way it once did. The niche this would fill would be in web games/interactive media I think.
Exciting! But I can't seem to find any where I can take a peek. It looks like a lot of UI is at least there, and the post makes some big promises about what's already done.
The vector icons in the side bar have the distinct cruft of LLM-generated SVGs, so just ideally hoping it isn't a quickly-made UI shell. The big claims about .fla import make me a bit skeptical. Though even so, we're not owed anything and I think it's a cool idea to share!
Is there a way to share brushes in the app/a brush sharing gallery? For sharing, I can see the "weekly" section from the homepage, which looks to be a weekly art prompt and everyone's go at it, which is really fun! But for the more artistically challenged (myself), it'd probably want to share a brush on it's own haha
I'm slowly easing into wider sharing, but you're really keying in on a dynamic I was hoping to grow within the community, of brush artists and pixel artists collaborating or sharing toys. For right now I'm storing my own brushes as little .txt files.
One feature that is quietly implemented, though - any png you save from MOSS also encodes its brushes. So if you share that png with someone else (or online somewhere!) it can be imported into MOSS with those same brushes and palette. I stole this concept from PICO8, which cleverly encodes all of the game data into a png file.
IIRC, iOS was forked from macOS (well... OSX), and they share a lot of internals. I think they could probably start up finder alongside springboard with some tweaking... but they'd much rather sell you an iPad AND a Mac!
When Jobs announced the iPhone in 2007 he said it was running OSX but what that actually means is anybody's guess. iOS is closer to macOS in functionality today than the iPhone's first OS.
I personally liked iOS and macOS being separate things because making a desktop OS also work on a touchscreen has wider implications than it sounds. That's why these days everything in Windows is blown up like Fisher Price software and way bigger than necessary for a mouse cursor. Seems like that's the direction Apple is headed in anyway with Tahoe.
What he meant was that it was running the non-user touching parts of OS X. It was possible to SSH to an original iPhone and install gcc and compile applications. It was sort of like OS X in a kiosk mode.
I would agree with you given we were talking about MacOS or Windows. Who knows, that may come later. If this was a more consumer-focused niche linux distro like SteamOS, I would also be concerned for the same reason.
But this is a general purpose desktop linux distro. A common, beginners-choice option, but still an option placing the user in a pretty rare breed. This isn't to game cheaply on a Steam Deck they bought, this is a choice to either build a PC ignoring the buy prompts for "Remember the windows license!", or choosing to overwrite the preinstalled OS on your laptop/PC.
The venn diagram of anus-scan-accepters and regular ubuntu users is simply two distant circles.
Based on "anyone disagreeing just dislikes the JS ecosystem", I feel like you might not want to grace me with a response, but I disagree /somewhat/.
Electron and web technology generally is certainly more performant than it once was, and I think people do malign Electron specifically a bit too much. VS Code continues to be the anti-example. It's always rather surprising it's just a web view, even on lower end hardware. (A several year old raspberry pi for example)
(Please note, I said "surprising it's just a web view", not "it's more performant than it could be if built differently".)
I think the main difference people tend to experience is a lack of care. I would say, for reasons I am NOT sure are causal, electron apps do seem to tend towards worse experiences on average in my experience. I think on the web, a quick flash of unstyled content or that ghost of the element you accidentally dragged instead of clicked are seen as just minor issues, because they're expectations of the web. If things go REALLY wrong, I have a whole rock solid toolbar above the app that lets me refresh if I think I'm in some infinite loop, or the URL bar I can look at if I'm not sure what page I was just redirected to. The back button promises to return me to where I was before. The browser is caging-in applications for me, so it's fine if they're a bit rowdy.
But using an application that is pretending to NOT be a web browser, seeing any web-quirk feels like I'm staring at rusted rebar in a cracked concrete bridge. The bridge still works, but now I'm aware of the internals of it and maybe that makes me feel a little more uneasy about standing on it. There is no back button if something goes wrong, and if there is, the app itself is rendering it. It's of course possible to hide that reality from me, but you need to care about sealing up all the cracks that let me see the rowdy internals.
To be fair, maybe that's just me that feels that way. And I do rather like the JS ecosystem.
Probably at least once a week, you're going to see someone drop something, press the wrong button on the elevator, try to push on the pull door etc. My own stress always peeks when I'm in public and trip up on something minor like that. If you just shout "hey you need help?" you're probably not going to make them feel any better and doubly worse if you just avoid eye contact and walk around them. When that happens to me, it can reaaaally sour a morning.
But saying "they really need to make these doors automatic, I dropped my coffee here last week!" and helping out if they want it has the EXACT opposite effect. Suddenly, it's not embarrassing any more, and you might have a little convo commiserating about what sucks. It's just a little bit of connection to make someone's day a bit better which is definitely a win-win and good way of breaking the seal on talking to folks.
There's also another more neutral option. Just give them the answer they need without the fluff. If they then want to thank you and chat it's their choice, but completely optional.
This is probably not the right approach most of the time, but it works well on the types of people who seem "serious" (not anxious or upset).
This is a really hard one to pull off. You have to determine that they really are that type of person and then just magically know what they want. It's really satisfying when it works though.
I've met some of the most interesting people I've ever known that way.
Build your own repertoire of expressions by picking what you like. You could even use AI to make lists of such phrases if nothing comes to mind. Take the ones you like and use whatever suits you. At some point it'll become automatic.
Just to toss on some info you might already know, the mention about grouping is related to group theory. [0] If a set satisfies those 3 axioms, there's some assertions you can build off that are common to all group theory sets, and having an identity element is one of them. It's weird that it's NOT zero, but in this case, infinity behaves LIKE zero. (Imagine going infinitely along the curve on the x-axis towards the open part of the curve, so therefore going infinitely up/down the y-axis. At somepoint, you're essentially have a vertical line between the original point, and your infinitely far away point, which points at the exact opposite side of the curve, which reflects back to the original point.) For natural numbers, zero is the identity, since X + 0 = X, in the same way P + infintelyfarawaypoint = P in this set.
To use a dumb analogy, it's polymorphism where your interface is something like regular old natural numbers: as long as your class behaves like natural numbers in some key ways, you can pass them to any add()/subtract()/multiply() functions relying on that behaviour.
reply