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.
It’s possible to stream from jellyfin without an account. Jellyfin should not be connected to untrusted networks, like the internet. Several API just don’t check the key or don’t require one in the first place.
What should I call it, when there isn’t anything GNU installed? Uutils? Llvm?
Here is some more context. Are they biased? Probably in some shape or form.
Could be improved by swapping hours and minutes. They are more important after all.
Also that way the time isn’t in order anymore.
I don’t think the aur can switch the delivered script whether you are piping it into sh or not.
Riddle me this.
A cop shoots a black guy, because he’s black, what does he get?
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.
Police stealing money from citizens. Civil forfeiture.
For a program at work the scripting language is Delphi and the Documentation is not available. If you want to know something call the support. CLI is not an option.
It’d be really useful to have a CI run, but that is never going to happen.
I don’t like the interface for setting up flows. Feels needlessly complicated.
Lineagos can be flashed on some android TV sticks
There are different kinds of free. Free beer, free speech and free weekend are three different kinds of free that software can have, but not necessarily at the same time.
Just imagine spending 4k€ on a graphics card only to find it’s partially defect.
Bethesda Fucked over the composer for doom eternal including financially and shitting unfairly on his reputation.
You can import and export your followed communities.
In a company you always have people that don’t generate value itself, but are needed so you can freely work, like the IT.
The green part should still be smaller. However you can seize that part by going freelance.