The better example for this design principle is the big green button on copy machines. The copier has many functions, but 99% of users don't bother with 99% of them.
That's a good button on a copier or a microwave. Not on a CNC mill, CAD software, text editor, chemical plant, tractor, knife... basically any object in the world that doesn't have one obvious function.
Can you elaborate on or cite a source as to why this practice is incorrect? The Nitecore D4 battery charger supports recharging of this and other sizes of Li-ion batteries (in addition to NiMH), so I am skeptical that it is inherently dangerous.
I guess an exposed battery is more susceptible to short circuit. Imagine you have this in your pocket while in a heavy rain. Battery could short circuit due to water creating conductive connection between battery terminals. It would heat up quickly an maybe even start burning. Still, I prefer 18650 to these flat, lasagna-type cells which swell and can be pierced by any sharp object. Even though the latter has built-in protection and the former doesn't.
I'm skeptical that new materials like this will meaningfully drive down the demand for virgin plastic packaging. The problem is not just the absence of good alternatives; it's the fact that plastic is the fossil fuel industry's backup plan for the global transition to cleaner energy sources.
That is: in preparation for a decrease in global demand for energy from fossil fuels, the industry is ramping up production of plastic to compensate so that it can maintain profitability (instead of, you know, just slowing down the extractive capitalism). Plastic production is set to triple over the next few decades as new facilities are built to support this transition.
Selective access to a set of user-specified photos is a native feature of iOS. Any time an app prompts you to choose some photos from your photo reel, you are first given the option to explicitly choose which photos the app even has access to.
This thing comes across so pretentiously, but they have some really novel CSS ideas I might try. The idea of making selector based on [style*="--bgc:"] and using that to set background color like style="--bgc: red" is not something that I would have thought of.
Happy you enjoyed it. Most of my creations just build on and with Startr.Style. It's a tight alternative to Tailwind's mess of classes. I especially love how directly it translates to pure styling yet allows us to have responsive design eg add the -md suffix to --bgc to specify background colors for tablets and up.
When I work on Modernism or any of the other experimental pages on https://startr.style I don't do it with any pretension but out of a love and familiarity of code and what the web can be. As child I traded helping out at a local computer store for time exploring Gopher and then Mosaic's window to the web.
I think what gets me is there's 6 paragraphs in a row that either start with "Modernism" or have it in the first sentence, and it comes along with words like "transcends", "echoes", "essence", "exude", "crafts." They're good paragraphs by themselves and make good points, I just think that together they come out a little breathless, and maybe some consolidation is in order :)
I notice from your profile that you haven't submitted your site to HN, I think you should do so, I think it would generate some interesting discussion.
In my perspective, for truly "self-contained", "portable" and "self-updating" and even "un-hosted" web apps, the only option nowadays are prehistoric data-URIs, that are slowly losing abilities anyway (basically can live only as bookmarks or direct URL pastes, and their only persistence option is location #hash that needs re-bookmarking):
data:text/html;charset=utf-8,<body id=b onload=b.innerHTML=decodeURIComponent((l=location).hash.slice(1)) onkeyup=document.title=b.innerText.split('\n')[0]||'.' onblur=try{history.pushState({},document.title,'\u0023'+b.innerHTML)}catch(e){l.hash=b.innerHTML} contenteditable bgcolor=darkslategray text=snow link=aqua vlink=lime style=text-align:center>#Hello, HN!<br><br>Do you like this %E2%9D%9Dun-hosted%E2%9D%9E app?<br>With persistence<a href="https://news.ycombinator.com/reply?id=44944112">%E2%80%A6?</a>
Your prediction is about a hardware product, and your examples are both software products (one is a browser and another is a mobile OS, both of which are platforms for running other software, and thus extremely well-suited to the task of reporting user data back to Google).
I'm not an expert, but baking telemetry into the hardware (or at least the kind of telemetry that I assume Google is interested in) seems like skipping a few levels of abstraction, and thus more trouble than it's worth.
> baking telemetry into the hardware (or at least the kind of telemetry that I assume Google is interested in) seems like skipping a few levels of abstraction, and thus more trouble than it's worth.
This isn't really a practical way of doing it. Google Play and Google Play Services having privileged access is more than sufficient.
Great concept. But author, if you're reading this: a piece like this could be so much better with a quick summary of what it does somewhere in the first two paragraphs. Something like:
"I've leveraged my home automation system to limit my access to social media to 15 minutes at a time, no more than once an hour. Using the built-in adblock feature, my router black-holes DNS queries to social media by default—which I can now disable temporarily by pushing the button on any one of several smart outlets around my house."
How is the latency? All mainstream chat apps have low-enough latency that a live conversation feels fluid and natural, whereas I frequently encounter situations where I have to wait up to five or ten seconds for an email to come through. That kind of latency would kill the experience IMO.
> I’ve tested Delta Chat with my own mail server, which uses Postfix and has everything configured for public e-mail, like DKIM signing, spamd, IP blocklist checks and so on, and each message took about 2 seconds from one device to another. Using a public server it sure feels below 300ms, so there is room for improvement when self-hosting a dedicated chatserver.
In my test, both clients were ~80ms away from the IMAP server, but the server was delivering to itself. I’m also not sure if the port 587 has an idle/keepalive mechanism, or if it has to go around the entire TLS handshake at each message.
I don’t think 2 seconds is bad, most of my contacts will take at least triple that to read and type in an answer, so not a big deal.
in my experience the "latency" for a person to reply to a message is always higher than the latency for a message to arrive. in fact, some latency is good. gives you a break to think.
For a little history on this design, see https://athinkingperson.com/2010/06/02/where-the-big-green-c...
reply