Or do you have a better idea of what the plan exactly is?
1,334 karma · joined January 28, 2023
Or do you have a better idea of what the plan exactly is?
This was actually a feature: by having the phone split in pieces, it would spread the kinetic energy and prevent worse damage.
- merge some commits independently when partial work is ready.
- mark some commit as reviewed.
- UI to do interactive rebase and and squash and edit individual commits. (I can do that well from the command line, but not when using the GitHub interface, and somehow not everyone from my team is familiar with that)
- ability to attach a comment to a specific commit, or to the commit message.
- better way to visualize what change over time in each forced push/revision (diff of diff)
Git itself already has the concept of commit. Why put this "stacked PR" abstraction on top of it?
Or is there a difference I don't see?
The point is that it is resistant to censorship, it is pseudonymous, and so on (all the other bitcoin attributes apply)
You have to lock your bitcoin on the main chain in a script that shares the bitcoin between you, and another lightning network user (typically a hub)
The trick is that a lightning transaction happen by signing transactions to the other party that changes the way the bitcoins are split, without broadcasting it to the main chain. You only broadcast to the main chain when you want to unlock the bitcoin. Broadcasting an earlier transaction will result of you losing the found because subsequent transaction contains secrets that allow the other party to take them.
So there is now a fork: https://github.com/gpui-ce/gpui-ce/ But I don't know if that's sustainable.
Try Xilem if you want to experiment with new, experimental way to build UIs in Rust.
So I'll wait until some big projects do it. For example, the day the Rust project moves away from GitHub I'll seriously consider. (Because I use Rust)
"Can't" or "won't"? The UI process is not usually the part that need certification.
> Slint has a similar license
Indeed, but Slint's open source license is the GPL and not the LGPL. And its more permissive license is made for desktop apps and explicitly forbid embedded (so automotive)
No, it is not:
- People use for/while loop, for example, instead of the "low level" 'goto'
- C compiler compute pointer aliasing, assume operations don't overflow, etc., in order to optimise your code: What you write doesn't translate directly to assembly.
- Some low level operations cannot even be represented in pure C (without using __asm__ extension escape hatch)
Did anyone say that? I think the point is not that it is not "close", but that C is not equivalent to ASM: C has its own abstractions, and there are things you can do on assembly that you can't express in C.
The other low level languages such as C++, Rust, Zig, ... are equally close since you can express the same things. In some respect they are even closer since they got more features builtins that modern assembly can now do that was not part of the design in C. (SIMD, threading, ...)
Modern languages also have extra abstractions that makes programming easier without compromising on the cost. There are more abstractions than in C, but they also are optional. (Just like you could use goto instead of while or for loop, but you're happy this abstractions exist. We could also use functions pointer in C++ instead of virtual functions, but why would we if the language provide tools that make programming easier, for the same result)
Not much worse than car. You can get studded tyres.
But yes, the cold can be inconvenient without proper clothes.
Many European companies would stop to a halt as they can't access any documents they have "on the cloud" or maybe can't even access their own phone or computer.