One underrated feature of Go and Julia: methods are defined without extra indentation. In e.g. Java they're inside the the class at the next indentation level.
Methods are so common and indentation is a finite resource. "Top level method" syntax is surprising at first though.
miniblog.
TIL that the HDMI specification is not public, so it's hard to write OSS drivers: https://www.phoronix.com/news/HDMI-Closed-Spec-Hurts-Open
An incredible 7 minute demo of APL, going from constructing an array to visualising Conway's Game Of Life, built incrementally without loops or temporary variables: https://www.youtube.com/watch?v=a9xAKttWgP4
I'm amazed to learn that there is now a marketplace for buying and selling good prompts to midjourney/ChatGPT etc!
You pay and you receive a prompt that generates good results. For example: https://promptbase.com/prompt/dismantled-anythings
PYPL: PopularitY of Programming Language https://pypl.github.io/PYPL.html is a nice PL metrics tracker that's an alternative to TIOBE.
It has a clear methodology and it carefully chooses keywords to avoid e.g. Python metrics being affected by interest in snakes.
I've released difftastic 0.46! In this release:
* Ada support
* Support for Arduino C++, better TOML handling, and a ton of upstream grammar updates
* Fixed several nasty corner cases with trailing whitespace or binary/UTF-16 confusion
https://github.com/Wilfred/difftastic/releases/tag/0.46.0
TIL that Rust has a (i) icon that shows relevant traits that a type implements. This is useful to understand that e.g. .iter() on a Vec<T> iterates with &T.
https://doc.rust-lang.org/std/vec/struct.Vec.html#method.iter
It looks like one of my bug reports was mentioned, so I'm delighted but wish I'd noticed earlier!
What piece of syntax has the most different meanings?
I realised today that `as` is extremely overloaded. It can be used for aliasing imports (Python), type casts (Rust), binding pattern match variables (OCaml), type assertions (Hack) and probably many others.
I'm fascinated to learn that there's a black market for GitHub stars: https://dagster.io/blog/fake-stars
E.g. they can be financially valuable if you're trying to raise money for your start-up.
Plan9: exploring a radically different operating system and UI design, running it on a Raspberry Pi: https://thedorkweb.substack.com/p/a-week-with-plan-9
In OCaml I can use Merlin to destructure `flavour ()` and it gives me the whole `match flavour () with | Vanilla -> ()`. It's nice.
In Rust I have to write `match flavour() {}` before rust-analyzer can autofill the match arms, which is more typing. I'm not sure why.
GitHub is adding a notion of a queue for pull requests, so you know if your PR is green relative to the PR that will land first!
Reminds me of Bors for Rust.
https://github.blog/changelog/2023-02-08-pull-request-merge-queue-public-beta/
It's surprisingly fiddly to parse unfinished multiline expressions in a REPL.
In Garden, my toy language, the parser distinguishes 'incomplete' from other others, so I can keep appending text and re-parsing until something useful comes out.
The Tomorrow Corporation has built its own game programming stack with live reload, time travel debugging, and even the ability to serialise the entire game state and replay it between testers!
https://www.youtube.com/watch?v=72y2EC5fkcE
Solving Fizzbuzz using Euler's totient theorem rather than conditionals: http://philcrissman.net/posts/eulers-fizzbuzz/
@nachobarrientos@emacs.ch Gosh, really? Helpful has reasonable unit tests IMO, although it definitely uses a bunch of obscure Emacs APIs.
The next version of difftastic will support Ada!
Are there any FOSS licensees that explicitly allow people to train AI models on the source code?
This seems like a useful addition, and there's already precedent with the "classpath exception" for the GPL.
On building a full-featured REPL, handling errors, and the different REPL APIs in the Clojure ecosystem: https://tonsky.me/blog/clojure-sublimed-3/
Displaying value information in an IDE is tricky.
For union types, it's more helpful to see the inferred type (Option<Player> versus null). For product types it's often nicer to see an example value.
For primitive types I almost always want a value (0 versus int).
Showing 141-160 of 235 posts