A fair enough. That sucks major balls
The real deal y0
A fair enough. That sucks major balls
Nice. Id instantly stop using those apps. But it looks like it just checks if dev settings are enabled. You can disable them again after unlocking bootloader you know :D
Til then, stuff works on my phone/lineageos but i thought they only checked for root because then things can go haywire and become unsafe then.
Unlocked bootloader should be fine. Now rooted android is a whole different beast…
Pre-locked bootloader times ive had multiple android devices be passed to me that were malware infected that changed the rom in a way that even a factory reset would not remove the malware. Locked bootloaders made it so the rom needed to be signed and unaltered on boot, fixing this. Root access also means apps can use and access api’s in android that it normally cant, changing settings and things inside android it shouldnt. What do you think happens when malware comes in? :p
Imo, i agree what you said. bootloaders should remain locked but you should be able to somehow, in the bootloader, be able to add the os’ signature/keys to the bootloader’s trusted stuff like how secure boot on a pc keeps os signing keys and verification stuff inside the tpm.
This way you can install lineage os for example, tell bootloader to trust it, and lock bootloader again so nothing can be changed anymore.
I wouldnt take this from user input, as that is controlable by malware, but rather come from the OS itself. Maybe even during installation, idk
This is a very complex topic that is very hard to draw the line on.
As a technical person who follows hacking and security news i can understand google introduced the api and warnings, as phones are getting hacked and unlocked bootloader or root can be abused to keep your malware going, and has been abused in the past.
But as a user of fairphone/lineageOS, who tells google, apple, meta, … all of them to fuck off when i can, this scares me. The lockdown of devices can and is going too far. Hell, i even consider samsung’s android ui changes to be going too far, as it changes a shit ton of stuff and really is not a stock android experience. It locks users in their environment…
Maybe they wrote their own emulator
I think you have things wrong. Any other languages can have libraries be distributed as some format that would allow applications to use it, be it linux/gcc and .a files ( which are actually archives with elf/object files of the code ), or a full on library like .so/.dll.
Rust can only do .o/.dll and only have it expose like a c library afaik. Even .net has improved on the .dll and includes all its language features in it. Rust has none of that. Its not true that libraries not rebuilding are only for closed source. Its also ease of use/access and less problem prone. What if i build my library using a different version of the compiler than you and your application? I could have no problems building my library, while you cant build your application because the library i made gets rebuild and errors.
These errors happen and are all because there is no stable interface/abi and all other languages have overcome this.
Also, by default, nothing in c is rebuild unless it needs to. Thats why the intermediate .o ( elf object ) files exist, so it only has to do the relinking and not recompile and thats why .a archive/libraries in c work, because it doesnt recompile. Unless you meant the fact rust can rebuild part of a file, without recompiling it completely?
I think you dont fully understand how c compilers ( gcc specifically ) work when using multi file projects ( and not just doing gcc input.c -o output.exe
) just how i dont fully know how the rust compiler works. Also, anything using IL will always have an abi, because how else will it jump from code to IL code, so its obvious that rust to wasm will have to abide by that haha.
Be it c wasm, c# wasm or rust wasm calling one another. Wasm is wasm, and you only need an exposed interface to call or include the other wasm ( c#/blazor having NativeFileReference
in the csproj )
Again, i like the idea of rust, but it has a long way to go to be viable atm. And it has many pitfalls to avoid so it doesnt become the hot mess that is any framework based on node.js
I know that exists, but whats the point of that? You loose all advantages of rust when you use the library then because it cant predict application state with the library code. There is a reason all those rust libraries are compiled locally when you compile a rust application. Its a major lacking point for rust, and as long as it lacks that its dead in the water for big projects.
Again, i like strong type stuff and i like the ideas of rust but it is not grown up enough for me
What is this abi and standard calling methods you speak off? Are you a rust-non-believer or some shit! Rewrite it all in rust, no questions asked!
( i too like the ideas of rust, but without a decent abi or not constantly changing interface, its useless to me. I dont want to rebuild all code, including libraries every time i update 1 library in my application )
Saaaaame. But sometimes even strongly typed stuff wont break on compilation time
Its funny cause its true. I often design tests to be “if a case/enum value is added this test will explode and tell them to add code here”
Their source code repo contains a copy of libogc for wii/gc builds because they were annoyed at us. And i do mean a copy. Not a reference, or a sub-module, a full on copy that they build before building the wii/gc executable.
Their own issue, as long as we dont get reports of their broken shit…
Then there are the multiple times they cloned emu repos and butchered them into cores. Or the fact they force the core interface on emulators making them bad.
Retroarch is a nice project from a far, but the closer you look, the more you see huge ass cracks in the project, held down with duct-tape
Oh nice, didnt know that. Thanks for the info!
Now, if proton could be used outside if steam…
No way to extract what the launcher does and use it as launch options in whatever youre using to launch the game?
Oh sweet summer child. Capcom is on a very sharp edge imo.
Their games are solid, but everything around it is utter god damn dogshit.
Sf5? Beta was very solid, was fucked up before release. Also had a terrible microtransactions system.
Sf6? Very very solid base game, but to get all character and stages since last year + the game you have to pay +160 euro.
Re4? Very solid remake, but prepare to loose performance on pc due to dunovo despite it being a single player game.
Re: the village? Very solid game, but better pay shit up and also loose performance despite ALSO being a single player game.
Megaman: mega who?
Monster hunter : safe, for now. Monster hunter wilds looks amazing and loads of fun, but watch them fuck it up somehow…
I like capcom a lot, have always supported them despite shit decisions and a few near bankruptcies but its the microtransactions/usage of dunovo and other weird ass decisions is making me hold back on buying their stuff atm…
I know, hence why i said youre not wrong but the example was wrong :p
Also, its more complex than that. Some teams can, some cant. And if they can it all depends on what project or context. The business world isnt that cut and dry hehe
Not saying youre wrong, but you took the wrong project as an example hehe.
Visual code is not open source. Its core is, but visual code isnt.
The difference is what visual code ships with, on top of its core.
Its like saying chrome == chromium ( it isnt ).
Visual code comes with a lot of features, addins and other stuff that isnt in the core.
.net debugger for example, is not found in vscodium ( build of the vscode core ). And there is more stuff i cant think of now but have come across.
Source: been using vscodium for a few months instead of vscode
Kinda the reason i dont like kotaku tbh. They do such things very often and it always feel like they are taunting or flexing and it comes over as really douchy to me