It can be really hard to find good free resources: for-pay providers are much more motivated to promote themselves.
I found it really hard to find quality stock images, and eventually found unsplash. This week I found pixabay too.
I'm sure this also happens in other domains.
miniblog.
One thing I've really come to appreciate from working on type checkers:
There's a crucial difference between the type system and checks you can do on type-inferred code.
E.g. using a bottom type is totally well-typed, but users expect warnings:
x = exit(0);
Digital Ocean still growing at 20% YoY and targeting profitability in 2 years: https://techcrunch.com/2020/02/20/digitalocean-raises-100m-in-debt-as-it-scales-towards-revenue-of-300m-profitability/
I'm a happy DO user but I like to know about the profitability of the services I use.
Wonderful, empathetic discussion of open source dynamics, emotional associations and mindset: https://blog.burntsushi.net/foss/
The dhall survey has a ton of interesting feedback from users about why they use the language, what they use it for, and areas that need work. https://www.haskellforall.com/2020/02/dhall-survey-results-2019-2020.html
It's a really great way of learning what needs polish on the official website too!
Nifty, you can run Coq in a web browser with a notebook-style interface! https://x80.org/rhino-coq/
Here's an IDE feature I think should exist:
A *random* file finder!
Rather than doing a range of static analyses (typical lint issue count, typical number of functions per file), just randomly sample!
It's less overwhelming and prevents recent feature bias to code cleanliness.
Open source can be used by companies to commoditise complementary products. It makes sense for them.
There's nothing stopping others doing the same though! You run the risk of others trying to commoditise your value add.
I wonder if this has happened?
Slow progress towards self-driving cars, despite early optimism: https://www.vox.com/future-perfect/2020/2/14/21063487/self-driving-cars-autonomous-vehicles-waymo-cruise-uber
(Human fatalities are 1 per 100,000,000 miles driven, and no manufacturer has driven that much yet!)
Using status for group chats *with audio* to create a sense of presence: https://pragli.com/blog/using-audio-channels-to-signal-status/
I'm excited to see GitHub developing a CLI for managing tasks and pull requests: https://github.blog/2020-02-12-supercharge-your-command-line-experience-github-cli-is-now-in-beta/
There's been an impedance mismatch between the extensive web UI and the minimal git UI.
Your choice of top level domain (e.g. .com vs .biz) can really affect the performance of your first page load! https://bunnycdn.com/blog/is-your-fancy-new-domain-hurting-your-performance-gtld-benchmark/
Applying an SMT solver to find missed optimisation opportunities in LLVM's arithmetic tooling: https://blog.regehr.org/archives/1714
Lessons learned from writing a linter/static analysis tool for shell scripts: https://www.vidarholen.net/contents/blog/?p=859
(Preserve positions, use error codes and document them, and there's a tradeoff between beginner mistakes and advanced mistakes!)
Fascinating teardown of the deeply FOSS smartphone, the Librem 5:
https://arstechnica.com/gadgets/2020/01/librem-5-phone-hands-on-a-proof-of-concept-for-the-open-source-smartphone/
Angular 9 is out! It's striking how much web framework design is compiler engineering. Type safety, dead code elimination, IDE tools and (lovely!) error reporting polish.
https://blog.angular.io/version-9-of-angular-now-available-project-ivy-has-arrived-23c97b63cfa3
Pharo 8 has been released: https://pharo.org/news/pharo8.0-released
Much improved git integration, a better class browser, and a huge uptick in polish since moving to GitHub! You'll even find my name on the release notes for some tiny patches :)
'cargo bloat' can tell you what the biggest dependencies or functions are in your binary! https://github.com/RazrFalcon/cargo-bloat
Not only does this help you ship smaller files, it can also produce faster compiles!
Until 2012, calling an arbitrary C function was considered safe in Rust! https://github.com/rust-lang/rust/issues/2628#issuecomment-9384243
I've met a bunch of lovely Haskell programmers, but I'm always surprised by the range of PL interests they have.
(1) Some are particularly into lazy evaluation. I get it: you can do some really elegant code for some problems. I've enjoyed this in other PLs too.
Showing 321-340 of 378 posts