https://github.com/huangyz0918/TankLogo/blob/master/README.m...
298 karma · joined January 22, 2015
https://github.com/huangyz0918/TankLogo/blob/master/README.m...
I think zig is quite a good candidate to fill that niche. It is very compatible with C, but it offers meaningful improvements while still being very picky about what goes into the language.
Here's the playlist with all of those videos if anyone else is interested: https://www.youtube.com/playlist?list=PLQVvvaa0QuDeETZEOy4Vd...
Zig is designed so that you can still peogrammatically deal with a failing allocation, as does well-written C, but it does not have a ownership system like Rust.
Typically with a re-used IV the same plain text will lead to the same cipher text, which can be an issue.
On the other hand with a re-used nonce you can basically recover the xor of two plain texts from two cipher texts. This leads to plain text very quickly and is a much more serious issue.
I am not affiliated with the project, only supporing it on Patreon, so I cannot speak about the designer's intentions with Zig specifically.
Generally in language design, if something works the same way as in other languages, that's great. You can re-use the keywords/syntax and build on peoples prior knowledge. However if you have some feature that actually works quite a bit differently from other languages the syntax should probably be different. Otherwise people might feel at home right away on a superficial level, but actually get bitten by the surprising ways in which the new thing works differently to the one they are used to later.
I was worried people would get too fancy with C++. Probably it would have been fine if we would have taken away most of the language.
It turns out the problem with C in that setting was that good C code seems to require a lot of ceremony and conventions for things like error handling and modularity.
I hope that Zig (https://ziglang.org) will become a viable alternative in that space. It's quite a small language, more comparable to C than to C++ or Rust. It's meant to result in similar LLVM bitcode as well-written C, while being highly compatible with C and and giving you some extra safety guarantess over C as well.
The idea was to outbid real ad networks and serve yourself bogus no-op ads while paying the websites you visited through their usual channels.
Does anyone remember reading about this as as well? What happened to that project?
If you want the typical user on Windows to run updated software, your software has to at least entice updating if not auto-update straight away.
Not solving this whole distribution mess is by far the worst downside of Windows as a platform. Not getting malware when installing software on your Windows PC is hard.
This is great if memory managment and high performance are a big concern for you, if they are not you might want to choose a language like Go or Node which allow you to gloss over such details until they really become an issue.
Do not fix problems you do not have by throwing Rust at them, but feel free make the climb of learning it to expand you horizon. :)
There may not be a solution in sight for making robots deal with badly marked roads for example, but we might be able to just sidestep the problem with better road markings or more conservative handover-to-human protocols in areas with improperly marked roads.
Probably that was too far off topic by me.
I'd be interested if people got banned or something like that for modifying games when they were clearly not hacking/cheating/cracking/impacting the experience of others.
From DSfix for Dark Souls I know that it can be fine with them if you hook function calls to improve rendering for example.
I imagine you also have to distinguish between Steam and VAC (anti-cheat) integration.
The glass back is ridiculously impractical and makes the Tab4 8 Plus slip down from furniture a lot.
If anyone wants to get that tablet make sure to get some sort of case for it. Otherwise it's a decent device and Android feels very close to stock except for a few unnecessary Lenovo apps you can't remove and the software update app which seems to be customized unnecessarily and a little poorly as well.
Aside from that it sounds like a cool idea.
Is that right?
If there is a permission that violates the trust between the system and an app using aforementioned APIs all bets are off. This is similar to why rooted devices are bad for security.
The only way to not have those things visible for the user of your library is to only use one package in your implementation.
When Jigsaw was delayed I was playing with the idea to create a project called shitty-jigsaw, which would just merge all of the packages in a module and change the access modifiers to be more restrictive according to some module definition.
So far it seems to me that they sometimes provide an oversimplified analogy which they revise in a later chapter.