HN user

satyanash

375 karma

https://satyanash.net

reach me at satyajeet at kanetkar dot co dot in

Posts11
Comments81
View on HN

On Firefox, newlines in code blocks are broken for this website. This causes the page to scroll horizontally to accommodate all the code blocks. The code is all wrapped in a single line.

narrative only got picked up because people needed a reason to demonize evil corps

Either they aren't evil in which case they're being demonized, or they're already evil in which case demonization is redundant.

Keeping aside the motives of people, what is clear is that scale effects of AI cannot be ignored. An AI "learning" millions of pieces of content in a short span is not the same as humans spending time, effort and energy to replicate someone's style. You can argue that its 'neural nets' in both cases, but the massive scale is what separates the two.

A village is not a large family, a city is not a large village, ... and all that.

having positive branching first

This is advice I've never seen or received. It's always been the latter, exit early, etc. Languages like Swift even encode this into a feature, a la if guards.

"Why did you decide to merge Keras into TensorFlow in 2019": I didn't! The decision was made in 2018 by the TF leads -- I was a L5 IC at the time and that was an L8 decision. The TF team was huge at the time, 50+ people, while Keras was just me and the open-source community. In retrospect I think Keras would have been better off as an independent multi-backend framework -- but that would have required me quitting Google back then.

The fact that an "L8" at Google ranks above an OSS maintainer of a super-popular library "L5" is incredibly interesting. How are these levels determined? Doesn't this represent a conflict of interest between the FOSS library and Google's own motivations? The maintainer having to pick between a great paycheck or control of the library (with the impending possibility of Google forking).

Optimising for the wrong metric, and what do about it, is an important issue.

All metrics are wrong, some metrics are useful. Finding the useful one and then recognising when it ceases to become useful is the hard problem.

No talk of the license on the frontpage. Visiting the GitHub repo tells me it is 2-clause BSD license. It's high time we had a GPLv3 web browser, otherwise, this risks the same fate as the rest of the browsers with proprietary forks.

This of course comes at the cost of not being able to support non-free parts of the web standard such as DRM.

Known Meta Sites 2 years ago

Just because these hostnames point to FB IP addresses does not mean they're owned and operated by FB.

    > 0-1.fb.me
    > 0-7.fb.me
    > ...
This lists a bunch of subdomains, ideally only the second-level domain names that can be owned by FB should be listed. Because anything under that is obviously FB.

Consider git – it only ships the diffs, yet it produces whole and consistent repositories.

IIRC git does _not_ ship diffs. It copies whole files even for the tiniest change. The compression layer handles the de-duping, which is a different layer.

Allocate four digits for the year part of the date: a new millenium is coming -- David Martin, Norristown Pennsylvania

2038 is 15 years away right now; this article was published 15 years before 2000.

I'm essentially a believer in You Aren't Gonna Need It — the principle that you should add features to your software — including generality and abstraction

YAGNI is not a principle. It is a contextual thumb rule. A codification of expert intuition. Exceptions to thumb rules are quite the norm. Conflating thumb rules with principles is a sign of sloppy thinking. Often engineers will misuse terminology thinking that it "doesn't matter". But it does. Think twice before claiming that something is a principle. The words you use highly influence your thought process[0].

[0] https://en.wikipedia.org/wiki/Linguistic_relativity

This looks like a large scale domain modelling problem for the movie production process. This is the last place I was expecting an overlap between computer engineering and film-making.

But it is not surprising given that large parts of film-making are now supported by software, which has a tendency to direct the evolution of terminology and concepts.

After a cursory glance at the model, it starts with a fairly generic set of primitives: Task, Asset, Participant, Context and Relationship. It then creates further instances based on this idea.

I'm sure other industries could also benefit from collaborative modelling of their problem domains like this.

Signal and Telegram seem to be the popular alternatives

taking your own argument into account, using "popular alternatives" is probably not the right criteria here.

Telegram is not E2E by default, so the name shouldn't even appear in any list of recommendations.

This person really just needs to lean into Emacs harder.

hehe, +1

leaning into it harder means understanding it better, the internals, why it works and why it does things the way it does.

Now only if our phones were lisp machines.

Dockerized Nextcloud + Postfix + Dovecot + Strongswan + OpenLDAP + SpamAssassin running on an ARM machine.

Sounds mostly alright, although it seems you cannot buy it without the $99/yearly subscription, which makes me wary.

Sure, a static IP and domain registration is good, but it ought to be an optional addon.

It was deemed the problems were bigger than the new possibilities. I mean, we could speak Finnish/English just fine and there was usually no need for any other languages.

It also excluded a large part of the world from participating on IRC. Maybe if it was more proactive, IRC would have a larger role to play than it does now?

Another example is punycode. unicode URLs are super unreadable, so no wonder the rest of the earth's population doesn't care enough about the open web, the importance of URLs vs Apps.