You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
What you said is good to know. But don't spit on those who have the skills and long experience to do it manually in assembly language, with very specific coding constraints.
It doesn't matter how specific your constraints are. Humans make mistakes and violate constraints. By delegating those constraints to the compiler, which only needs to have those constraints encoded once and then apply to all software, you improve the overall code quality.
In other words: you may think you'll never make mistakes, but you will. In assembler, your mistakes turn into exploitable bugs. In Rust, your mistakes don't compile. I'm going with Rust. And if you think you're too experienced to make mistakes, that's how you miss them :-)
You know nothing about my assembly machine coding rules and constraints, like forcing everything coded in FSM's. There are very simple but repetitive, iterative coding rules and constraints that can ensure you will make no mistakes, and if any, that they will be found in a snap.
Yes this is true. But it has the draw back that if your compiler is 200 millions lines of code like GCC, even free, you'll have an issue checking the compiler integrity all by yourself.
In general compiler bugs are rare, and are a lot less likely to result in exploitable code and a lot more likely to cause runtime issues that are easily detectable. You're going to avoid a lot more bugs using a compiler than you're going to introduce from the compiler itself.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
