1,521 karma · joined August 13, 2015
A web developer who wants an app to load and render quickly will take advantage of the browser's characteristics. For example, loading compressed assets in the right order to get a short time-to-first-paint, updating styles without reflowing the page, using requestAnimationFrame to render animations at a consistent frame rate and play nicely with the event loop, etc.
Likewise, a systems programmer ends up learning the quirks of their OS and hardware. For example, loop tiling to take advantage of cache locality, reducing data dependencies to reduce pipeline hazards, using splice() to copy data on Linux to avoid context switching, etc.
It's all just programming. Even if the distance from hardware is different, the concepts are consistent. Historically, hardware has been under-documented, which I think led to the community glorifying low-level programming. But under-documented and buggy platforms are essentially universal nowadays, so I think the low-level vs high-level distinction is not very useful.
That's just it, right? Unicode support has always been a tradeoff between precise coverage/larger binaries and loose coverage/smaller binaries. I'd be excited to see the data size for collation+normalization get under 1MB.
The professor was forced to stay surface-level on the math, so the coursework was a task of glueing together code from scikit-learn. Unfortunately, the exams were much easier if you had the mathematical intuition.
The hypocrisy is real. It is definitely a real problem. If your field has confined itself in formalism without a consideration for HCI, you are doing yourself harm. Not only is the transfer of knowledge to industry and other domains harder, you miss out on equivalent but more accessible ways of expressing the same ideas.
[0]: https://zgcoder.net/ramblings/typesafe-printf/ [1]: https://fstarlang.github.io/general/2017/11/23/sprintfstar.h...
You'd need an overlap of
1. An appreciation of ML and its extensions.
2. A relatively deep understanding of Go's semantics, performance hacks w/ GC, type system quirks, etc.
3. Belief that this would be useful.
4. Knowledge of compilers.
5. Time on your hands. This is a blocker for me :(
Meanwhile, for reverse engineers, it's a dream come true to be granted any information whatsoever on the product they're reverse engineering. For some reason, programmers want to operate in the context?
Inference rules just transform the traditional format of
(A && B) -> C
into A B
---
C
This format allows you to stack rules on top of each other when writing out the derivation of some term, without running out of page space.People should instead be incentivized to centralize in their own local communities, i.e. their family, friends, coworkers, local businesses, community centers, etc... Accomplishing this will likely require effort on multiple fronts, from increased regulation over the tech sector, to creating products that empower communities to run these services themselves.
> I do not wish to install Python or Java on every computer. I have small form factor computers where I need to conserve space.
Now you have to install QEMU on every computer, in which case your options for portability dramatically increase.
Do you mean different OSes? AFAIK, Cosmopolitan isn't cross-architecture.
Even if Zig doesn't bring safety by default to the language, however, I think you could get it in practice by making the standard library enforce safety. Then, unless someone goes out of their way to write their own libraries from scratch and eschew all of the safety mechanisms, they would likely live in this safety bubble.
IMO, the future is bright, because all these layers are being re-thought. However, phrasing this as a debate over programming paradigms is a red herring. If coupling data and behavior is a useful mental model, we ought to accommodate that while giving the compiler more to work with.