"The phrase the Rust team members like to use is that they’re trying to make the best 90’s era programming language they can."
Thoughtful comparison between Rust and Haskell.
https://www.fpcomplete.com/blog/2018/11/haskell-and-rust
miniblog.
Excellent deep dive on how Rust has polished its compiler errors for async:
https://blog.rust-lang.org/inside-rust/2019/10/11/AsyncAwait-Not-Send-Error-Improvements.html
Rust's model of async-await is really interesting. They chose a suffix syntax (`foo.await` instead of `await foo`) because it composes better!
The evaluation model is also lazy: creating a future does nothing until it's awaited. https://blog.rust-lang.org/2019/11/07/Async-await-stable.html
Sentry is moving to license that prevents others from offering paid services.
It's stricter than AGPL, which allows others to host if they share source. It's really interesting to see a license that becomes more open after a certain period!
https://blog.sentry.io/2019/11/06/relicensing-sentry
In 24 years of Perl on CPAN, you can see a clear trend to spaces over tabs!
From https://squareperl.com/en/tabs-vs-spaces-in-millions-of-perl-files
In 24 years of Perl on CPAN, you can see a clear trend to spaces over tabs!
From
Reading the future with Emacs, or why M-n is useful in the minibuffer:
https://engineering.collbox.co/post/working-faster-in-emacs-by-reading-the-future/
(An excellent Emacs tip, which works in deadgrep too!)
The RustSec database is organised and thorough. It's much harder to have memory vulnerabilities in Rust, but they do happen!
https://rustsec.org/advisories/CVE-2019-12083.html
Wonderful Strange Loop talk demonstrating Comby, a very simple parser with an elegant pattern language for large scale refactoring.
https://youtu.be/JMZLBB_BFNg
@amiloradovsky@functional.cafe If he hadn't understood my shortened version, I'd have ended up saying that :)
Wonderful Strange Loop talk demonstrating Comby, a very simple parser with an elegant pattern language for large scale refactoring.
https://youtu.be/JMZLBB_BFNg
Thoughtful article exploring upfront design versus evolutionary design, and contrasting with Worse Is Better.
The comments on the post is an impressive set of tech people too.
https://yosefk.com/blog/what-worse-is-better-vs-the-right-thing-is-really-about.html
I sometimes have problems with technology terms or acronyms that I've only seen written and don't know how to pronounce.
For example, I recently chatted with a Scheme user about R^5RS. Fortunately he understood "R5"!
Python has always been a batteries included language, but some modules support obsolete 80s tech! There's now serious discussion of removing them: https://www.python.org/dev/peps/pep-0594/
Cute usage of chpwd() in bash to convert directories into a simple text adventure game: https://belkadan.com/blog/2019/08/go-east/
How do you prevent "trusting trust" attacks with malicious compilers?
You don't need a trusted production-grade compiler. It's sufficient to have a really limited trusted compiler or even an untrusted compiler provided the triggers don't overlap.
https://www.schneier.com/blog/archives/2006/01/countering_trus.html
A nifty blog post showing all the websites designed by the author since the late 1990s. It's remarkable how distinct the different web design eras are!
https://battlepenguin.com/tech/a-history-of-personal-and-professional-websites/
Incredible post showing the reverse engineering of a Fitbit style device, so you can reflash it with custom software: https://rbaron.net/blog/2018/05/27/Hacking-a-cheap-fitness-tracker-bracelet.html
GitHub READMEs work exceptionally well for projects which only need a single page of docs.
Transitioning to a hosted, multiple page documentation structure is hard though. I've dabbled with a few tools but not found a clear favourite yet.
A snake game implemented entirely in the browser element inspection interface! https://matthewrayfield.com/goodies/inspect-this-snake/
A wonderful example of creative computing.
Showing 1,681-1,700 of 7,508 posts