I have no doubt that @jwiegley will do a fantastic job as Emacs maintainer! Exciting times!
miniblog.
Some subtle shadowing gotchas in Rust: https://users.rust-lang.org/t/surprising-item-shadowing/3494 (fortunately the compiler warns you in this circumstance)
Swift Intermediate Language: https://llvm.org/devmtg/2015-10/slides/GroffLattner-SILHighLevelIR.pdf interesting design choices include parametrised basic blocks and stack vars by default.
I'm increasingly seeing email as an anachronism. Shared, searchable group messaging or IM are usually what people actually want.
Emacs' ignore-errors is a nuclear option. When in doubt, use condition-case to show what error you're expecting or bugs will lurk.
Emacs tip: if something evaluates to a number, Emacs shows all possible interpretations of it e.g. 97 (#o141, #x61, ?a) (octal, hex, ASCII)
"developers prioritize expressivity over correctness" -- Empirical Analysis of Programming Language Adoption https://lmeyerov.github.io/projects/socioplt/papers/oopsla2013.pdf
Word to markdown to asciidoc: using an effective GitHub workflow for writing Pro Git
Blogged: Even More BF Optimisations
Emacs tip: If your instance hangs and won't respond to C-g, you can use `pkill -SIGUSR2 emacs` to force emacs to stop whatever it's doing.
It's really hard to build an effective online anonymity tool. Despite this, boiler room scams seem to have no trouble hiding phone numbers.
Nifty Emacs package of the day: list-environment https://github.com/dgtized/list-environment.el . It gives a pretty view of environment variables with editing.
I'm all in favour of exploring syntax design, but sometimes I wish an ASM syntax had won. I see (and muddle) both AT&T and Intel frequently.
An exciting proposal to add inlining reports to LLVM: https://lists.llvm.org/pipermail/llvm-dev/2015-October/091687.html Inlining is crucial for optimisation so transparency is great.
If you work with a programming language long enough, you will see every feature abused at some point.
Showing 4,981-4,995 of 7,583 posts