It works fine for the point that they were making.
Which is that the fact that restaurants have to certify for food safety training and pass regular inspection is perfectly reasonable, and allows those who aren't experts in those areas, or want to continually inspect kitchens to dine out in confidence & conveinience. (or at least vastly reduced risk).
There should be some equivalent, safe, experience in the technology space. Especially given how powerful a tool of liberation it is.
Of course, who controls that, and the ability to turn off those safeguards is important for many many other reasons and... also a question of liberty. And so I think it is a difficult conflict to resolve elegantly.
But it's an interesting thing to raise, because so often when they do enforce those controls - the outcry is 'bank won't let me do what I want with my money!'.
Not such a stones throw from - 'tech company won't let me do what I want with my device!'
Im not making any specific point. But perhaps thats indicative that the solution needs to be holistic, or just that security is hard XD.
Everything in that account has appeared in the last 6mo. Very unnatural commit activity, and clearly contradicts the claim that this is their first OS project. Is linked to a faceless YT channel.
This is quite common already, where they’ll offer a higher performance tier, but that power only comes from the engine control unit, no physical differences.
It makes even more sense in EVs where you don’t have to be concerned with the performance of supporting components to the engine.
The difference here, is that it’s a subscription, not a one time upgrade, and as a result, not an upgrade you can sell on.
I don’t know what it is about how my brain works, but I have absolutely no memory for keybinds (and envy those that do), so I love that it just lays them out in the UI.
Only customisation I make is to turn off the borders.
Would love if built a similar, visually guided, experience for nvim.
Interesting. Coming from Spring to Ktor, being able to easily inspect the internal workings has been one of my favourite bits!
It’s ‘advanced’ kotlin in there for sure, and takes some learning of the internal plumbing, but having everything not hidden behind annotations has been great.
Just a CMD+click on whatever Ktor DSL/plugin API your using and you can immediately start to follow along / debug what it’s actually doing.
I’m personally not convinced by the theory of ortho.
It seems to stem from the idea that stagger is a hangover from the typewriter, in which it was required to make room for the mechanics, and that if we didn’t need to make them like that, we wouldn’t have.
Hence the keys should be lined up so your fingers just move up and down.
However I think this has 2 problems.
1) Most ortho keyboards have 5 columns for 4 fingers.
2) In stagger I use different fingers to strike the same letter dependent on what the preceding letter was, so that I almost never use the same finger twice in a row. You can’t do this in ortho if the 2 letters are in the same column, leading to more repeated strikes from the same finger.
Which I would expect is both slower and more straining.
But maybe my technique is weird, or haven’t given the ortho enough time.
(if you like ortho, good for you, not trying to spoil your fun, just musing)
Thanks - I figure its step away in terms of target platform.
I meant a little more in the way that software is packaged and run. My understanding is that theres a similar mechanism for storing and linking shared libraries that means multiple versions can go exist and be independently linked depending on the requirements of the calling package.
Is it similar to NixOS? Recent convert, would be interested to read a comparison to fuchsia from someone in the know of both.
If it’s anywhere close Google might be sat on a huge opportunity to tread the same ground while solving the ergonomic issues that NixOS has. (I’ve never been more happy with a distro, but I’ll admit it took me months to crack)
There’s no doubt better docs will help improve the state of Android Apps.
But this is about stemming the flow of shovelware into the store, (todolist tutorial no 800000, but I changed the name) where the problem isn’t that devs lack the tools, it’s that they simply have no serious intention of maintaining their product.
If you can’t find or don’t have enough belief in your own app to find 20 people to download it for free, is it fair to promote it in a way that my gran might come to rely on it.
It’s not nice to be exclusionary, but end users having to pick through that stuff just isn’t great for the platform. There might be a better place for hobby code.
Meanwhile we know that these mixers are being used enmasse to sell exploitative content, fund terrorist organisations, evade tax, run scams, hacks, the list goes on, and on, and on, and on.