HNHacker News
TopNewBestAskShowJobs

carussell

2,674 karma · joined September 22, 2009

I don't HN anymore.
submissionscomments
carussell··on Why SQLite Does Not Use Git
The problem is not that Git supports staging partial changes. The problem is that Git has shoehorned a tool that "at some point you're going to want"—to help you deal with a rare occurrence—into the default workflow, forcing you to deal with the overhead of staging every time.
carussell··on Porting the Unity Engine to .NET CoreCLR
Xamarin ships for iOS. It does AOT compilation from CIL to native.
carussell··on The web sucks–you just don't know it (2004)
Aside from the many great soundbites in it, the thing I like most about this article is that its author is Sean Barrett, whose background is in game development and as a traditional, pre-Web client programmer. (See [1].)

Usually, the same way that ecosystems stratify around languages, opinions in questions of tech advocacy tends to stratify based on developer background. Most of the progression in web standards that the author is against has been bolstered by the attitude from people that hail from his background. (Roughly, that camp's attitude tends to resemble something like, just give the developer the ability he or she needs in order to do what he or she wants.) It's the exact attitude that gave rise to developer-first QOL improvements like WebAssembly and many other things that have popped up in the nearly 1.5 decades after this was written.

This is notable because that camp's overriding perspective is the exact opposite of the author's own grumble about "your experience interacting with the web could be vastly better, but browser authors are instead caught up in enhancing the abilities of content creators". I.e., the author prioritizes a user-first perspective, recognizing that the developer-first mindset has almost always been in conflict with his ideal vision for the Web, despite his own background.

There's also the really great breakdown of Web content as type #1 vs #2 vs #3, which predates similar descriptions that I'd only seen start to become independently written about in the last several years—probably after 2011 or so.

In my opinion, this essay is as on-the-nose, as brutal, and as important as Maciej Ceglowski's similar and often referenced takes ("Legends of the Ancient Web", and "The Website Obesity Crisis").

1. http://nothings.org/gamedev/how_i_found_myself_in_the_game_i...

carussell··on Ask HN: What human language features could be useful for the writing of code?
> Could articles[5] be used to do things like pass variables or instantiate objects?

I wrote about something similar to this (called "type-named objects") in a post last year[1]. The idea is that for small utility methods, you shouldn't have to interrupt your main flow of thought to come up with names for your formal parameters; in fact, you shouldn't even have to name your locals. If you're working in a language with a (perhaps already verbose) static type system, you can just leverage that.

So, for example, instead of this:

  appendNode(node: Node): void {
    this.tail.next = node;
    this.tail = node;
  }
... you can do:

  appendNode(Node): void {
    this.tail.next = the Node;
    this.tail = the Node;
  }
This does introduce some precedence/binding gotchas that I go more into. But that hints towards further improvements. From the aforementioned post, you could end up with a language that allows:

  the ControlMessage's id := defocus
Or, if you add support for "passive voice" to your language:

  id from the ControlMessage := defocus
Completely unrelated, but related to the use of "the", Carmack wrote a tweet[2] that I've got embedded in the comments of a project of mine.

> I have moved to naming global singletons with a The* prefix -- ThePacketServer, TheMasterServer, TheVoip, etc. Feels pretty good.

Since then, I stopped creating "proper" singletons altogether. Instead, it'd be a quasi-singleton, where I write a `MasterServer` class, and then bless an instance as `TheMasterServer`. Application code will always import, refer to, and otherwise operate on the latter, but tests are free to instantiate their own. This is especially useful if you have implemented some sort of developer switch in the UI that allows you to launch an embedded test harness within a live, running instance of the app. In that case, you don't exactly want your tests to be fiddling with your "real" singleton.

1. https://www.colbyrussell.com/2017/02/16/novel-ideas-for-prog...

2. https://twitter.com/ID_AA_Carmack/status/575788622554628096

carussell··on A Virtual Machine
I didn't mean to suggest you do this for every chapter. Just something in the vein of, "In case you haven't been following along already, since I last blogged, I've completed several chapters of Crafting Interpreters."
carussell··on Decentralization Dilemma
I used to think so, too. Over the winter, though, someone here on HN pointed me towards Beaker Browser and Dat. (For a completely unrelated problem. Turns out, it works pretty well as a solution to this problem, too.)

It seems likelier that a P2P web based on Dat (or something like it) will gain adoption in the large before getting embedded devices manufacturers (a) to willingly take on the role required here, and (b) to get it right, which are each big asks on their own. There's also the hidden third problem (c): getting the masses to actually go out and upgrade a piece of hardware that would actually support this kind of thing. It's a lot easier to just download a new browser (or an update for their current browser) and sign up for a service that will act as an always-on peer on your behalf—for exactly the same reason that the centralization of the Web happened in the first place.

carussell··on A Virtual Machine
You should drop a note on your blog about the new chapter(s). I'm subscribed to your blog's RSS, but not the one for craftinginterpreters.com—because a feed for the latter doesn't actually exist.
carussell··on System Shock 1 source code released under GPL
The fix that needs to be made here is in Git, which fails to process line endings in a sane way (and includes a bunch of insane, poorly documented config options that approach the problem completely sideways).
carussell··on System Shock 1 source code released under GPL
You're pulling things out of your ass. I'm interested in comments like yours. At some point between reading the previous comment and responding to it, you must have had some thought that goes, roughly, "Hey, I'm just going to make some shit up now and post it." Right? How else does it happen?

Apple's is not the only ecosystem that settled on carriage return. Who do you think was around for them to deliberately break compatibility with in 1977? Kildall?

carussell··on Oracle Wins Revival of Billion-Dollar Case Against Google
> A Ninth Circuit decision [...] in favor of Google would not have created any obvious circuit split and wouldn't have upset the status quo of the software industry.

Go on, finish the thought, and make your conclusion explicit. Because by any reasonable reading, you're suggesting that the Supreme Court would not have granted Oracle's petition if Google prevailed in the Ninth Circuit. And yet you start by saying that this isn't your argument. Be explicit.

carussell··on Oracle Wins Revival of Billion-Dollar Case Against Google
First: No, I didn't leave anything out. Review the link I included in my last comment. Hold on to the Federal Circuit as a personal stick in your craw if you want, but I didn't leave it out.

Second: That's a stretch. To argue that the case would have stopped at the Ninth Circuit is to argue that because the Supreme Court denied Google's petition to reverse the Federal Circuit, then they would have denied Oracle's petition to reverse the Ninth Circuit. That's a junk argument.

carussell··on Oracle Wins Revival of Billion-Dollar Case Against Google
You don't get to define "for their own reasons" to mean something else just so that you have a something to argue about. Doing something for one's "own reasons" means that the decision is theirs to make, in contrast to being legally compelled to act in a certain way. It doesn't mean acting in a way that nobody else would, nor acting in a way that nobody else would agree with.
carussell··on Oracle Wins Revival of Billion-Dollar Case Against Google
So you cut my comment off right at the part where I've pre-emptively addressed your entire criticism, and then you write out a paragraph detailing this criticism anyway because your position is contained squarely within the very part of my comment that you chose to leave out?
carussell··on Oracle Wins Revival of Billion-Dollar Case Against Google
> They still can under GPL, but that means complying with GPL, which they evidently did not want to do.

Not true. Android has been exactly that since 2016. Harmony is dead (killed at the ASF, even), and Android is now using OpenJDK.

carussell··on Oracle Wins Revival of Billion-Dollar Case Against Google
Today, Google is using the Oracle-approved form. They already switched Android from Harmony to OpenJDK in a previous release.

Since then, this suit has been about (a) deciding whether Google is guilty of wrongdoing in the past, and (b) what the extent of the damages should be for that historical wrongdoing should be, if any.

The outcome here doesn't really have any impact on the future of Android (except if Google wanted to factor the suit into their decisionmaking for their own reasons).

carussell··on Oracle Wins Revival of Billion-Dollar Case Against Google
Settling out of court at this point would not be a good result, since the most important thing that will come out of this is the legal precedent.
carussell··on Oracle Wins Revival of Billion-Dollar Case Against Google
That's not weird, either. What would have been weird is a finding that they're not copyrightable, given that it would have been completely at odds with the statutes and case law we have concerning copyright.

The point is, nuance matters. If you're physically attacked and defend yourself in a way where you end up killing the guy, you claim that your actions were justified. You don't go to court claiming that killing people is just not a problem.

Here's how this case should go:

0. Oracle sues Google for copyright infringement.

1. Courts find that the design of APIs is an expression resulting from substantial creative decisions far above the low bar we already have for precedent, and therefore they're copyrightable.

2. Google defends themselves on the claim that, creativity notwithstanding, merely implementing a public API should not subject an implementor to the consequences of copyright infringement, and that there are no damages owed here.

And by every indication, we're right on track.

https://news.ycombinator.com/item?id=10949839

And it looks like you're moving the goalposts and shitting out two-second replies, anyway, so I'm done commenting further here.

carussell··on Oracle Wins Revival of Billion-Dollar Case Against Google
That's an interesting way to characterize it.

When the Supreme Court was considering Google's petition to hear the case, the court asked the White House to voice an opinion—where by "White House administration", you mean the Solicitor General.

That's not "weird"; that's a normal part of the job.

https://en.wikipedia.org/wiki/Solicitor_General_of_the_Unite...

carussell··on Oracle Wins Revival of Billion-Dollar Case Against Google
The whole subthread focusing on the Android VM is completely irrelevant. The entire argument at this point has to do with the inclusion of the Java APIs. Not even Oracle or the appeals court are harping on Google's custom VM.
carussell··on Godot at GDC 2018
- Mono's license prior to the Microsoft/Xamarin acquisition was LGPL, which is open ended and doesn't allow e.g. discriminating against Unity; Unity would not accept it under those terms

- Xamarin did offer a commercial license to Unity; Unity would not accept it

- MS began to release their own .NET implementation under the kinds of license terms that Unity wanted years ago, but Unity didn't budge

- In the meantime, MS then relicensed Mono itself—the .NET implementation that Unity actually wanted—under the kinds of terms that Unity wanted, but still Unity didn't show signs of moving until very recently

The whole it's Mono's fault that Unity sucks was essentially a successful PR attempt for Unity to disclaim responsibility for their shortcomings, with the (maybe not unintentional) side effect of directing public ire towards Mono for not doing enough free work (to benefit what was already one of the industry's most successful companies!)

carussell··on Rent out GPUs to AI researchers and make ~2x more than mining cryptocurrencies
> How do I know you actually ran what I paid you for and not just generated random data that looks right in the shape I wanted it?

See https://pfrazee.hashbase.io/blog/nodevms-alpha

carussell··on Open Speech Recording
It's clear that you're arguing at this point just to argue. There's no reason to even respond.
carussell··on Open Speech Recording
Notwithstanding the original comment about it probably being a better idea to contribute to Common Voice (it is), this comment is off the mark.

- Common Voice does have a TOS. It's here:

https://voice.mozilla.org/en/terms

- You're equivocating on the word "may". You're reading it as declaration of intent—i.e., as a synonym for the word "might" and def 5 as listed on Wiktionary[1]. In reality, it's being used in line with the most common tendency for things like TOS, RFCs, etc, which is as a synonym for the word "can", i.e., to acknowledge what one is allowed to do (in this case Google), as in def 2.

1. https://en.wiktionary.org/wiki/may#Etymology_1

carussell··on You probably don't want to run Firefox Nightly any more
> Participate [...] in the bug trackers.

For anyone looking on and thinking of following this advice, please don't treat Bugzilla like GitHub, where advocacy and general discussion is the norm. Bugzilla is for code reviews and for people who are otherwise working together so they can coordinate and get things done. It's not an open solicitation for people to jump in and voice their opinions about general project directions, etc. If you do try to use Bugzilla the wrong way, you'll likely be warned about generating too much noise and possibly banned.

Please do continue using social platforms like blogs, comment sites like this one, etc. for posting opinion pieces and weighing in. That's where general commentary belongs, and it'll be much more effective to boot, if you're interested in getting people's attention or changing minds.

carussell··on Self-driving Uber car kills Arizona woman crossing street
That's not at all what happened here (least of all because I'm not the person who was trying to advance an argument).
carussell··on Self-driving Uber car kills Arizona woman crossing street
While you're admonishing people for their comments and employing stealth implicature like, "let's make sure Uber releases detailed data", do you think that maybe you should include a prominent notice disclosing your (and your former colleagues') ties to the industry that Uber is operating in—most importantly as a competitor?
carussell··on Backblaze cuts B2 download price in half
Kyle Drake (neocities.org) dedicated an entire talk[1] to this topic, "High Volume, Bandwidth Heavy Infrastructure on the Cheap"

https://www.youtube.com/watch?v=-i6wvix6buI

carussell··on Socialhome: a federated personal profile with social networking functionality
> an email contact of yours should be able to [...] find your social network account ocdtrekkie@mastodon.cloud [...] The link between email account and social network account could be checked periodically

This is how the keybase sigchain works. (And I do mean "works"—as in, it's available now and real people have been using it.)

PS: Your HN profile doesn't contain any contact info.

carussell··on Show HN: Hearth – A Dropbox-like, IPFS-powered personal website publisher
This is not true. See the remarks about the DatArchive APIs in my original comment. You can also look at Fritter[1], which is a prototype Twitter clone built as a Dat web app.

It's true that there are some types of web apps that exist on the traditional (HTTP) web but that cannot be made as a Dat app, but it's also true that there are a class of apps that could be built with Dat but that cannot be built on the traditional web.

1. dat://fritter.hashbase.io

carussell··on Show HN: Hearth – A Dropbox-like, IPFS-powered personal website publisher
> It's pretty much the same security model as regular web content, as you mention.

I can't say much about IPFS, but this is not quite true of Dat. The Beaker team is working on a complementary set of APIs to read and write to Dat archives, so you could have, say, a TiddlyWiki-like site that can update itself.

It's always been a big problem that the security of file:// URIs is unstandardized. I can publish a repo, for example, that includes some tests/runner.html. You could open it Firefox to run the automated tests, but Chrome will choke on it because Chrome doesn't allow XHR for file:// URIs. The only way around this is to either put it online or run a local webserver (e.g., `python -m SimpleHTTPServer`) and access it through localhost. This is perverse. Dat is solving this in a way that's very similar to what would happen if file:// got first-class attention from the browser makers. If it's in a Dat, it doesn't actually matter if it's on your computer or hosted somewhere. All that matters is that you have the content.

This might not be exciting to HN types who are comfortable and willing to go rent some DigitalOcean instance and put up with administering it, but this will have a huge impact on the long tail of businesses—both small and large—that are quietly chugging along on little more than Excel and email (maybe the odd SharePoint installation).

On the other hand, developers should be excited about this, too, because it means they can start building apps that are _actually_ serverless (compared to Amazon and Google's definition). We're back to where we were in the 90s: you can go write some neat client software and share it with me, without having to think about the headache of needing to run a server in perpetuity just so that it can continue being useful.

← PreviousPage 2 of 34Next →