I’ve seen a tablet for old people. The whole interaction is limited to NFC cards. Instead of having to open an app to start a video call, you put the Call Flipper card in a tray. On the other side I can send pictures which are then displayed for her.
My 95 grandma would never have been able to use a smartphone/tablet otherwise.
Well, have a look in the old Testament, specifically Leviticus 24:17-22.
19 If anyone injures his neighbor, as he has done it shall be done to him, 20 fracture for fracture, eye for eye, tooth for tooth; whatever injury he has given a person shall be given to him.
You know the part that is shared between Christianity and Judaism.
There is another Frankfurt. It’s lies on the river Oder. The same word for other.
So there is Frankfurt Main and Frankfurt Other.
Honestly, when I open a new application I normally want to interact with it now. Always drove me nuts , when I opened a Powershell window in a folder and then had to click on it again.
It’s art.
Both Boeing and Airbus are working on H2 Tech for Planes.
Remember when selecting something was done with the right mouse button in blender. That was great UX for beginners.
Turns out, if it’s a single person in their free time it’s slower. But at least if something isn’t working I can fix it myself.
I got something better for you.
namespace 🔵 = std;
using 🔢 = int;
using 💀 = void;
using 🕖 = time_t;
using 👌 = bool;
#define 👂 auto
#define 🎌 enum
#define 👎 false
#define 👍 true
#define 👹 "evil"
#define 💪 🔵::make_shared
#define 🍸 virtual
#define 🖥️ 🔵::cout
#define 🔫 🔵::endl
template<class 🔮>
using 📚 = 🔵::vector<🔮>;
template<class 🔮>
using 👇 = 🔵::shared_ptr<🔮>;
🎌 🐒 { 🐵, 🙈, 🙉, 🙊 };
🔢 🎲() { return 🔵::rand(); }
👌 😎() { return 👎; }
struct 🍴 { 🍸 💀 👀() = 0; };
struct 🍊 : 🍴 { 🍸 💀 👀() { 🖥️ << "🍊" << 🔫; }; };
struct 🍉 : 🍴 { 🍸 💀 👀() { 🖥️ << "🍉" << 🔫; }; };
struct 🍒 : 🍴 { 🍸 💀 👀() { 🖥️ << "🍉" << 🔫; }; };
struct 🍓 : 🍴 { 🍸 💀 👀() { 🖥️ << "🍓" << 🔫; }; };
struct 🍍 : 🍴 { 🍸 💀 👀() { 🖥️ << "🍍" << 🔫; }; };
struct 🍅 : 🍴 { 🍸 💀 👀() { 🖥️ << "🍅" << 🔫; }; };
🔢 main()
{
if(😎() == 👎)
🖥️ << "💩" << 🔫;
📚<👇<🍴>> 🍛 = { 💪<🍊>(), 💪<🍉>(), 💪<🍒>(), 💪<🍍>(), 💪<🍅>() };
for (👂 🍏 : 🍛)
🍏->👀();
return 🎲();
}
No. The code was discovered by a person who used to work on it back in the day. They don’t give it out, unless the decompilers have the permission to get it from the original rights owner. It’s however unclear who owns the rights. They tried to get the permission but all three companies that might own it, didn’t even answer.
This only half as bad as the emoji soup macros
You shouldn’t use tabs for alignment. It breaks for everyone with a different tab size.
What should I call it, when there isn’t anything GNU installed? Uutils? Llvm?
I don’t think the aur can switch the delivered script whether you are piping it into sh or not.
Yes, writing safe code is a skill. But for most skills you need someone to teach you. My suggestion is, think about it differently:
The compiler isn’t training wheels, but rather a senior dev, that quickly looks over your shoulder and tells you, hey you might have missed something here. You can at any point tell them, trust me bro for this part. They need at some points a comment in the form of lifetime annotations. They are pretty good, but not perfect.
To pick up your example. They don’t tell you, you need a new wheel. They tell you, you’re bike has disc brakes, but your new wheel is missing the disk. When you later hit a wall, because you couldn’t break, you can check where you just said trust me.
The difference is, you put up a sign “here be dragons” with unsafe. Certain operations break the garanties of rust, like pointer operations and Cells. So now you need to write a wrapper which upholds checks that they are not violated. If it breaks, you just need to check your unsafe code, instead of everything. Now only one person needs to deal with unsafe for everyone in a team to benefit.
Memory safety isn’t a skill issue. There is a reason they happen in all big projects like android or chrome and only reduced when introducing safe languages.
I’d rather have a compiler that tells me why my code was refused than a compiler which prints 100 lines of templates. Or a compiler, which tells me a pointer/reference is null instead of a compiler that knows, but it’s UB-NDR so it isn’t snitching. If the compiler tells me, hey here you could have a race condition, it’s one less bug I have to find with a debugger. A compiler that complains about uninitiated variables, instead of a compiler that gives me potluck as content.
Some of these are bonkers. The argument not to fix them because of backwards compatibility is even wilder. Which normal client would need the ability to get data for any other account that it hasn’t the Auth token for.
There also IDEs that start instantly.
They don’t ship a whole browser though.
Matrix still has it’s problems. All the meta data is still saved on every server permanently.
There is still space to improve from there.