I can’t even think what that would be called, TBH. It’s hard to search for.
2,117 karma · joined May 10, 2019
<a rel="me" href="https://hachyderm.io/@PeterBronez">Mastodon</a>
I can’t even think what that would be called, TBH. It’s hard to search for.
The feature is in Alpha. They use the Ultimate tier as an early testing group. One thing you’re paying for at that tier is access to stuff like this fresh out of the lab.
Hono - [炎] means flame in Japanese - is a small, simple, and ultrafast web framework for the Edges. It works on any JavaScript runtime: Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, Netlify, AWS Lambda, Lambda@Edge, and Node.js.
That’s more complicated than “buy an electric car to save the planet!” but it’s less wrong.
His conclusion, in his words:
“Increasingly, I’m feeling that our honeymoon with electric cars is coming to an end, and that’s no bad thing: we’re realising that a wider range of options need to be explored if we’re going to properly address the very serious environmental problems that our use of the motor car has created. We should keep developing hydrogen, as well as synthetic fuels to save the scrapping of older cars which still have so much to give, while simultaneously promoting a quite different business model for the car industry, in which we keep our new vehicles for longer, acknowledging their amazing but overlooked longevity.”
Love to see version control on all the things! Wonder if the version control features would be more robust if implemented in Doltgres.
[0] https://azure.microsoft.com/en-us/products/ai-services/ai-se...
Now, maybe that’s how it already works, but I have no confidence in it.
Details here https://gitlab.eclipse.org/eclipse/asciidoc-lang/asciidoc-la...
Edit: yeah it’s managed through the Eclipse Foundation now. They’re slowly working towards a formal spec, haven’t hit 1.0 yet.
Details here https://gitlab.eclipse.org/eclipse/asciidoc-lang/asciidoc-la...
The home assistant speakers aren’t making enough money to justify the large teams behind them. Thus we’ve seen significant layoffs on those teams in the past year.
BigCos are looking for other ways to reduce costs. Killing features is one way to do it.
There have also been situations where a feature is removed because of legal action; lawsuits alleging the features violates a patent.
Live updates givith, live updates taketh away!
Revolution Cooking sells $280 and $350 toasters. They have touch screens, dozens of modes optimized for different kinds of bread, gluten-free mode and 7 toastiness levels. One of my colleagues has one and loves it dearly.
It appears to be a US design firm that uses contract manufacturing:
“we developed a proprietary alloy, a new, more efficient component design system, and intelligent heating algorithms that adjust in real-time.”
“Tom assembled a team of world class engineers, designers and product marketers in Boston, MA, where Revolution Cooking is headquartered today.”
Last time I tried Nix on MacOS it did not end well. Maybe I’ll try this in a VM and see how it goes…
# Tactical Feedback
On iOS, my password manager doesn’t recognize the Nino app with the Nino.app domain, so autofill doesn’t work at login. Not a problem, just a little friction.
Breaking problem on iOS: I cannot type the letter “m”. It appears to trigger a keyboard shortcut that toggles a reorder paragraph block mode. I had to abandon Nino and finish this write up in Notes.
In iOS Nino Doc, it’s not obvious how to “Select All —> Copy”. Moving from Nino to Notes I had to copy each paragraph block individually.
Concur that it would be good to have some templates or something to orient on first app open. I tried “Notebook” first because I assumed it was like “Notepad”, a very light text editor. Seems to be more like a Jupyter notebook?
Maybe an easy way to address this would be to add a tag line for each document type. Just a couple words to orient folks beyond the name. Perhaps add a “compare to X” as well.
# Strategic Feedback
First, the “too many tools” problem is real. Lotus Notes was good. There is appetite for consolidation in some large enterprises.
It’s impossible to get a big organization to switch over to this directly. You need to target smallish teams (10s of people) that can make their own decisions.
Security is everything. Recommend you review Sandstorm’s capability security model. That was the most promising productivity revolution I’ve seen in a while. It failed in part because they expected other people to write applications to their security model. If you can deliver the fine grained security AND a broad swath of functionality, you have something really special.
End to end encryption is excellent. Let me bring my own keys.
Some more specifics on security:
Block level security would be a killer feature. Especially if it goes beyond RBAC to ABAC. In my world, you frequently want to share a document with someone who is only authorized to view part of it. Automatically redacting the parts they aren’t supposed to see would be amazing. Then allow those blocks to be reused, with the same security labels, in many different contexts and app paradigms?
Honestly it would be amazing and I could sell it.
Next thing on security is data sovereignty. Absolutely respect going single region GCP to start. However, self-hosting will be an immediate ask in my world. Several tiers of this, all of which you can absolutely up charge for.
First, single tenet instances. Give me assurance that when bugs show up, they won’t leak my data to other customers.
Second, enterprises will want to run it within their VPC/Tenet that they already use / trust / audit. The major cloud vendors have regions focused on different industries, you need to be able to run there without calling home to your central instance.
Third, direct self hosting. Especially for smaller teams with poor connectivity back to the cloud. Can I run this on a NUC out of a trailer to help coordinate disaster recovery efforts? Can I host it in a VM on dedicated hardware where I understand the cost, capacity and backup story? Google and Microsoft can’t do this, so you can differentiate. See Next Cloud for a good approach to this.
Finally, interoperability. You have many different app views into the core block abstraction, but there will always be other tools and databases in play. Make it super easy for those external things to read and write blocks. Don’t write the integrations - just expose the API.
Good luck!
Personally, I’d love to do contract management with a system like this. Each clause could be a block with its own version control history. Easy to query a subset of them into a spreadsheet or slide deck. Main challenge is that all the lawyers will want it in MSFT Word for tracking changes during negotiations, so need to seamlessly interoperate with .docx
https://github.com/charstorm/llmbinge/blob/main/llmbinge/src...