shafte

6 ms·

1.
by shafte 3y ago
> Those people/use-cases don't care about the GIL. This is not true. The primary funding and motivation for the GIL removal work comes from the numerical computing community. The PEP ( https://peps.python.org/pep
2.
The Grand Unified Theory of Documentation(diataxis.fr)
140 points by shafte 5y ago|57 comments
3.
by shafte 6y ago
I'm curious: what's sorts of things were bad about libtorch? What did you see in this release that you thought was an improvment?
4.
by shafte 6y ago
That doesn't seem very fair. They link a docs folder and an overview document, neither of which require that the user read code to get a good idea of the library's contents. That said, the code is also reasonably well commented as
5.
by shafte 6y ago
Perhaps you missed the "What's in it" section while skimming the readme? :) >Because of folly's fairly flat structure, the best way to see what's in it is to look at the headers in top level folly/ directory
6.
by shafte 6y ago
EternalTerminal[1] was mentioned in a comment below. It supports port forwarding, and other goodies like native scrollback, at the cost of latency on laggy connections (because it doesn't do full terminal emulation). If that tradeoff s
7.
PyTorch 1.4: Custom mobile builds, distributed model parallel, Java bindings(github.com)
39 points by shafte 7y ago|4 comments
8.
by shafte 7y ago
Watch David's talk coming up ( https://www.facebook.com/pytorch/ ), it will contain some answers :)
9.
by shafte 7y ago
Aside from its merits as a database, SQLite is also a great example of good documentation[0], thorough testing[1], and focused development. It's something that all library maintainers should study and try to learn from. [0] https:&#x2
10.
by shafte 7y ago
I don't know if it's correct to characterize Github's model as a power grab. The design of Github definitely pushes things in a more centralized direction, but I think that approach is superior in many cases and it's not
11.
by shafte 7y ago
Not really related, but a quick plug for the work that Mercurial is doing to port substantial portions of its main binary to Rust: https://www.mercurial-scm.org/wiki/OxidationPlan My understanding is that they want to
12.
by shafte 8y ago
This is so awesome. Makes me really excited for the future of PyTorch—being able to define symbolic deriviatives in a python subset is super cool
13.
by shafte 8y ago
The best explanation is coincidence, I think. I have direct knowledge of two of the incidents in the past few weeks, and they have completely unrelated causes. Sometimes you just get unlucky!
14.
by shafte 8y ago
I think it's cool to see projects like this! It's sort of like an "alternate history" for a C++ programming model. I agree that it doesn't seem immediately useful for most projects, but that's okay :) I hope th
15.
by shafte 8y ago
Glad to see the team really embrace the nitty-gritty of keeping the open-source community healthy. React Native is a project with a lot of potential that's taken a few high-profile lumps this past year. Being an OSS maintainer can be d
16.
by shafte 8y ago
I'm not second-guessing the technical that the Times made here (I'm sure it made sense given their constraints), but I do wonder if these kinds of in-house general-purpose languages will die out eventually. Some of the comments in
17.
by shafte 8y ago
This is a great piece of software development history! Very interesting to see what things the industry seems to have improved on (somewhat) and what things we still struggle with. Things we have improved: - Developers are generally expecte
18.
by shafte 8y ago
Breaking changes are highlighted here: https://github.com/pytorch/pytorch/releases#breaking-changes
19.
by shafte 8y ago
I'd be interested in a direct comparison with similar efforts undertaken by existing frameworks; for example Torch Script[1], which aims to produce a language which shares a syntactic frontend with Python while getting all the goodies
20.
by shafte 8y ago
I'm so glad this this article (unlike so many other representations of Jeff and Sanjay's work) does not overlook Sanjay's contributions. I don't know what it is; maybe Sanjay is a weird (read: non-English) name, maybe it
21.
by shafte 8y ago
> What model of human cognition are you claiming is "incorrect"? And is it the one presented by Marcus, or are you strawmanning? The model of human cognition I'm referring to is the hybrid connectionist-symbolic one that M
22.
by shafte 8y ago
I seem to have missed the Twitter spat that precipitated this essay, but I don't quite buy the larger argument he's making. We should judge approaches to AI based on their results, not on their conformance to a (vague, incorrect,
23.
by shafte 8y ago
I actually like the new website. I think the primary barrier to Rust adoption now is something along the lines of "my organization doesn't use it"—this website is clearly geared toward persuading CTOs or administrators. It&#x
24.
by shafte 8y ago
This is cool. I especially appreciate the disclaimer at the end: >> We can’t stress enough how important it is to measure your applications and the tools used to measure those applications. In general, hardware-oriented data-structure
25.
by shafte 8y ago
A REPL is an incredibly useful tool for all sorts of development, "real" or not. But I share the author's frustration with intros to functional programming that take advantage of a REPL to provide small, context-less examples
26.
by shafte 8y ago
For explaining personal technology to the masses, it has to be Walt Mossberg. The guy basically invented the commentary + review format that most mainstream publications use today. For how much people in the industry wince when they heard s
27.
by shafte 8y ago
I think people tend to focus on specific symptoms of bad code (duplication, in this case) without thinking about what makes good code. Ideally, we'd like our code to be: - Mutable (i.e. easy to modify - Understandable - Good at doing w
28.
by shafte 8y ago
As I said: UTC is a reasonable choice, except for the fact that most of your employees do not live in UTC and doing mental translation is annoying.
29.
by shafte 8y ago
To be fair, you are not including more advanced operators, like positive/negative lookahead/behind (which is the specific example the article uses), capturing and non-capturing groups, greedy vs non-greedy kleene stars, etc. As yo
30.
by shafte 8y ago
This is fairly common for large tech companies that started in that timezone. The decisionmaking process goes something like this: 1. You MUST use a single, consistent timezone. Using the local timezone is a mess: is it the user's loca

More ›