heavenlyhash

12 ms·

1.
by heavenlyhash 5mo ago
I've come to realize (I think) that this actually does have a lot to do with waterproofness ratings -- a legibility trap. I notice that Fairphone excludes headphones from their latest devices, and attributes it to the necessary of do
2.
by heavenlyhash 7mo ago
I want to like this, and it's directionally good work... But it's hard to see this as very useful unless we also start to see some increases in legibility, and ways to make sure these optimizations are being used (and that textual
3.
by heavenlyhash 9mo ago
I'm an advocate for "both". - `Option<T>` and `Result<T,E>` at core; - `?T` and `T!E` as type declaration syntax that desugars to them; - and `.?` and `.!` operators so chains like `foo()?.bar()!.baz()` can be wri
4.
by heavenlyhash 9mo ago
Language explorers looking for lower level languages like this may also want to take a peek at the V language. https://vlang.io/ I won't say with confidence either is better than the other; but I think both are worth
5.
by heavenlyhash 9mo ago
This is a delight to read. I've been doing a survey of languages over the last several days, and Odin is one of the more interesting ones... but looking at the OS and FS related parts of the standard library made me back away at high
6.
by heavenlyhash 9mo ago
That is roughly the number of new requests per second, but these are not just light web requests. The git transport protocol is "smart" in a way that is, in some ways, arguably rather dumb. It's certainly expensive on the se
7.
by heavenlyhash 10mo ago
Really depends on where you're from. OP already mentioned in his area it's phonetically mostly "ew". I'd say a lot of germanic areas also do something I'd describe as "oi". That'd also make one
8.
by heavenlyhash 1y ago
Ah, yes, the KDE people are definitely the people I trust most to deliver a reliable system and not go crazy chasing incongruent rewrites of things while abandoning what works... /s
9.
by heavenlyhash 1y ago
My 2c (opinions may vary, etc, etc): I think that doing percent-encoding shenanigans is going to be widely perceived as "ugly" and will severely hamper adoption. I'd reconsider. I think it's quite likely that people are
10.
by heavenlyhash 1y ago
soo..... what's the guidance for when package names include a slash? such as approximately everything in golang, which very often matches e.g. "github.com/*" as a package name? Do would PURL suggest that "github.com
11.
by heavenlyhash 4y ago
Warpforge -- project website: http://warpforge.io / https://github.com/warptools/warpforge -- is a project I work on that's heading a bit in this direction. Hashes in + build instruction = hashes
12.
by heavenlyhash 4y ago
I want to see more things like this emerge too. I think one of the bigger barriers is that terminals don't really have a component reuse boundary. What I mean by that is: in the browser, you can always put more HTML inside a div tag, a
13.
by heavenlyhash 5y ago
Hey good news -- you might be interested in Warpforge: https://github.com/warpfork/warpforge It's heading in exactly that direction. In fact we specifically want to start using Starlark for module declaration (mi
14.
by heavenlyhash 5y ago
You may be entertained by WarpVer: https://gist.github.com/warpfork/98d2f4060c68a565e8ad18ea481... It's not SemVer(tm). That's it. That's the whole pitch. There's also a section specific to golang,
15.
by heavenlyhash 5y ago
> Crev is an actual _code review system_ as opposed to typically practiced _code-change review system_. You have my attention!
16.
by heavenlyhash 6y ago
That fund affects day to day life a lot less than you might expect, FWIW. It's not like we get to just... spend that; it's somewhat comparable to saying "the New York Stock Exchange contains over $foobar dollars per citizen&
17.
by heavenlyhash 7y ago
Layout is sort of the center of questions I have about it too. There's a few built-in layout options: https://godoc.org/fyne.io/fyne/layout ... but not many; I think it'd be a stretch to say it's go
18.
by heavenlyhash 7y ago
I really like Mural and am definitely cheering for them. They really get UX. It's hard to explain how fluid and useful their product is until you try it. Nothing else I've experienced comes close for: - quickly and meaningfull
19.
by heavenlyhash 7y ago
Computationally? Think something like "NP hard", except the "verifier" function isn't even plausibly cheap either. Experimentally from the real thing? I'm not even sure we know how many new pieces of technolo
20.
by heavenlyhash 7y ago
Sure, but grep the fine original article for the word "privacy". It's not present. HN is discussing HN's tangentially-related feelings more than HN is discussing the article. I'm not surprised, but I'm certain
21.
by heavenlyhash 7y ago
It's useful all the time in serialization and marshalling systems. You end up with very nice code if you can keep a separate stack for each of e.g. your json parser and its paired object unmarshaller. The nicest outcomes are with coro
22.
by heavenlyhash 7y ago
I find it very interesting that the comments here on HN so far are predominated by discussion of "privacy". The article is about anti-trust regulation. These are different things. Regardless of what you might think about the pri
23.
by heavenlyhash 7y ago
I agree with this and thus often find the term "IC" itself unfortunately prone to being misleading.
24.
by heavenlyhash 7y ago
> Nearly all the countries that call themselves "democratic socialist" are in fact capitalist, with strong welfare states. Well, then, there you go: that's the meaning of the word, then. Or at least it certainly is to a l
25.
by heavenlyhash 7y ago
I agree with the "we won't do all the things" thesis, and that it's probably wise to acknowledge that and plan accordingly around that self-knowledge. Almost everything else in the comment after that seems a bit off-kilt
26.
by heavenlyhash 7y ago
I think that's part of the dry humor, here.
27.
by heavenlyhash 7y ago
I think I'd more or less agree with that. For example, one of the questions I generally ask in a meeting room that's considering this topic, and has for example microservices in flight, is: "Are you willing to put in the work
28.
by heavenlyhash 7y ago
Be careful not to mistake Google's use of a monorepo with consideration of whether $DAYJOB or $FOSSPROJECT should use a monorepo. Google has a lot of tooling and some very thoroughly-considered and reinforced policies and cultures
29.
by heavenlyhash 7y ago
> (I might suggest the underlying problem in this code is relying on inference too much, but the threshold for "too much" is difficult to communicate to users.) This is a very outstandingly interesting line out the whole writ
30.
by heavenlyhash 7y ago
Super agree. What would it take to make that a reality, though -- without, like secure's sibling comment says, blowing up the text matrix? Which things would you make standardized (or conventional) to make switching easier? What things

More ›