jonstaab

Is it just me, or has "federated" come to mean just mean multi-tenant SaaS (maybe with some features that cross boundaries) that's also open source?

Great little takeaways. The early bits remind me of my own job history — I also worked on a fish processing barge, using a forklift and being constantly stymied by the elevator bottleneck. The next job I did, I also got myself fired to protest what I discovered to be an illegal internship.

I think Elisa learned more from the experiences than I did though, she seems like a very thoughtful person.

I love Steinbeck, but I had never heard of The Winter of Our Discontent, thanks!

I thought this was going to be a typical HN "build things instead" thing, but I actually love their take. Looking at the world around us lately I've been realizing more and more that "it's all in Plato"; his Republic is a book I read once in high school, but it's high time to re-read it.

What are some books you find your self going back to repeatedly (or want to)? My list:

- Domain Driven Design

- Ray Bradbury's short stories and Farenheit 451

- George Orwell's Down and Out in Paris and London, The Road to Wigan Pier

- Descent into Hell

- LotR, the Hobbit, and Narnia

- Hitchhiker's Guide to the Galaxy

- Psalms, Job, James

- The Rare Jewel of Christian Contentment

- Wendell Berry's Essays

- Winnie the Pooh

- Augustine

Guess you know what kind of person I am now.

There's some truth to this, but this therapeutic reduction does a disservice to the traditional (and fuller) practice of forgiveness:

> In the new therapeutic dispensation, however, forgiveness is all about the forgiver, and his or her power and well-being. We have come a long way from Shakespeare’s Portia, who spoke so memorably in The Merchant of Venice about the unstrained “quality of mercy,” which “droppeth as the gentle rain from heaven” and blesses both “him that gives and him that takes.” And an even longer way from Christ’s anguished cry from the cross, “Forgive them, for they know not what they do.” And perhaps even further yet from the most basic sense of forgiveness, the canceling of a monetary debt or the pardoning of a criminal offense, in either case a very conscious suspension of the entirely rightful demands of justice.

From: https://hedgehogreview.com/issues/the-post-modern-self/artic..., which I highly recommend reading, as it's super relevant not only to our personal lives, but to the cultural moment we find ourselves in.

The problem I see with that is that if a huge number of people take that route and happily (let's assume) live their lives without working, they lose access to the ability to participate in a meaningful way in the economy by producing something of value; if they're not producing value, no one is going to value them, and they'll eventually be locked out of the new, smaller elite group that controls the means of production, and the power that goes along with that.

Is this another edition of "falsehoods programmers believe about quinoa"?

I wrote a tiny multimethod library for Janet: https://github.com/staab/janet-multimethod

The stack traces have so far been really clean and helpful.

Janet's purported focus is that it's easy to embed in a larger C program. I haven't really seen that in practice, but I have used the C api to write some language extensions, and it is a joy. In comparison with Clojure, I much prefer using either C or janet to using Java and lisp side by side; with Clojure running on multiple hosts now the differences in language semantics between clj and cljs are just annoying.

As far as language features, I miss a lot from clojure: immutable/persistent data structures, protocols, not to mention concurrency primitives. But Janet's approach to performance and design is "do less". With the C api you can easily add bindings to some C library that provides a desired feature. But even without that stuff, Janet is for me a python-killer, if not a clojure killer.

Edit: at any rate, I think it's not meant to be a competitor to Clojure, its similar syntax just often invites the comparison. It's much more fair to compare it to Lua.

Technically correct, but irresponsible

Interesting, but over-sensationalized. To quote the article, "Even before the new report, some scholars believed that most to all of the post-2002 fragments were modern fakes."

The headline uses the word "all", but is talking about 0.0002 of the dead sea scrolls. "at the Museum of the Bible" is a bigger qualification that it initially appears.

It's not proselytization, it's a restatement of the central doctrine of Christianity, undergirded by the doctrine of the Trinity which is pretty germane to relationality, and most commonly argued for from John, especially chapter 1.

They got Idaho wrong. Hell's Canyon is cool and all, and has some really unique geological attributes, but it doesn't hold a candle to the Sawtooths.

That's the whole problem of quantam physics, isn't it

Reading about the idea that relationality is fundamental to existence, it's hard not to think of John 1: "The Word was with God... No one has ever seen God; the only God, who is at the Father's side, he has made him known." Salvation is simple: knowing the creator, the source of existence.

And (I'm looking at you Shopify), VR/AR is not going to solve this.

A lot of negative comments here, so I'll offer my 2c.

I agree that their initial post was deceptive, and inexcusably so. But the spammy tactic I think is outweighed by their total devotion to understanding their customers. Maintaining over 300 simultaneous conversations, just to get an insight into their users is a herculean, and praiseworthy, effort.

The takeaways and tips are useful too, if you're thinking about starting a bootstrapped company. They're not pitched as "do this and you'll succeed", they're pitched as "here's what we did, you do you", which I appreciate. I'll borrow some and ignore others when I start my own venture.

EDIT: curious why I'm being downvoted

We very nearly built our app's printing subsystem on Google Cloud Print, but went with PrintNode instead. So glad, PN has been great to work with.

It's a common Jewish taboo: https://www.chabad.org/library/article_cdo/aid/1443443/jewis...

That wouldn't be too hard, though you'll have to take a different approach to loading the content than I did here.

I made this project for myself, so I'd be unlikely to use much else for reading/quick reference, but if you find the xode helpful, you're welcome to dork it! You migh also check out: https://www.notion.so/About-Theographic-bb40cb93b1ac43bd9825...

In one sense, they're not copyrighting the Bible itself, just the years of scholarly and commercial work that was put into making the ESV. Paul (and Deuteronomy) says "Do not muzzle an ox while it is treading out the grain".

On the other hand, it's hard to argue that Bible publishers' spammy newsletters and aggressive copyright protection amount to much more than Simony.

I'm keeping my scope very small - feel free to fork and modify though!

Probably the rate limiting thing, I kicked their leaky bucket pretty hard.

Yep, looks like I got rate-limited. Good old HN hug of death. I've just added a caching layer, so maybe it'll recover soon.

Edit: should be good now.

Personally, I've found notion unusable because of its performance problems, and how it forgets where you are in the list view every time you open a card. Try creating 10 lists with 15 cards each, and then browse the far right column. Impossible.

I recently wrote my own thing for personal/work organization and I am way happier.

I'd contend Twitter's problem isn't infinite scrolling, it's eschewing chronological sorting in favor of algorithmic. There is no objective order to most content on twitter, so deep linking to a place in the feed is impossible, whether you use pagination or infinite scroll. Which is why infinite scroll works - it solves the problem of defining what page 2 even is. Not defending algirithmic sorting of course.

I've seen this argument more and more lately, and it's starting to bother me because some places work great with infinite scrolling (twitter, serial comic strip viewers).

This article offers a small disclaimer at the end, but otherwise says things are impossible, when they simply aren't. #1 is easily solved by removing offscreen content once it's been scrolled past, and autoloading in both directions. Numbers 3-4, 8, and 9 (several of which are redundant complaints) are definitely the worst part of infinite scroll websites, but are pretty easily fixable with client-side routing.

The problem is people implement infinite scroll in terms of finite-scrolling documents, when there are a number of other dynamics to take into account. It's like saying "Don't make video games because you can't play them with a remote".

Is anyone else getting timeouts with their heroku postgres instances? My dynos are healthy, but pg isn't. The status page doesn't mention anything about that.

Edit: it seems the postgres instances are running on amazon ec2, so that's probably why they're down. Edit: they're failing over postgres instances now, so we should be back up soon.

Maybe it has something to do with the domain I work in, or maybe it's just a problem with how software is done, but the expectation in my industry that there ought to be a relationship that comes along with the software.

Also, Open Source is not an answer to the last question. The majority of software users don't have the technical expertise to evaluate the safety of a given OSS, even if there's a community established around making recommendations — but even then, that's a trust relationship too.

Edit: maybe I should be more open minded. How is OSS a substitute for trust? Is it a redirection of trust to a group whose interests are aligned with yours? How do you facilitate that network without putting too much burden on the user? Are there any good examples of working OSS that involves non-technical end users?

Ironically, I opened this in a new tab just before going on a two hour saga of fighting Chrome's autocomplete behavior and losing. That particular decision of Google's is so painful to deal with, and I'm not alone, this issue is well worth skimming through, just for fun: https://bugs.chromium.org/p/chromium/issues/detail?id=587466

It's been three years since they broke autocomplete="off", and in the meantime forms are less secure (for multi-user computers), user-friendly (e.g. when the web app provides its own autocomplete, which then gets hidden by Chrome's), and error-prone (when the same field means different things in different contexts, like when filling out a customer's address rather than your own).