HNHacker News
TopNewBestAskShowJobs

evanelias

3,028 karma · joined June 6, 2012

NYC-based software engineer. Founder of skeema.io. Formerly a member of Facebook's db automation team and engineer #4 at Tumblr.

Email: evan @ skeema.io

submissionscomments
evanelias··on Too dangerous or just too expensive? The real reason Anthropic is hiding Mythos
Take another look at this blog's index https://kingy.ai/category/blog/ and click through more posts, and pay attention to the post dates.

Do you really think this singular author is writing multiple excessively-long blog posts about AI per day? There are ~650 of these posts over the past 18 months. And over on LinkedIn, the author describes himself as a "Specialist in Digital Marketing, Videography / Video Editing, Search Engine Optimization, Social Media, and B2B Sales."

YMMV but this post and entire site absolutely screams "slop" to me.

evanelias··on Leaving GitHub for Forgejo
Reading means downloading. Downloading is equivalent to making a copy. To make a copy of a copyrighted work, you need a license, unless your activity is fair use. Licenses have terms and conditions that must be followed, such as retaining attribution in all derivative works.

That said, FOSS licenses are non-exclusive. Regarding the original upthread topic of GitHub's copilot training, iirc GitHub's terms and conditions involve granting them a license in order to host your code. Depending what else is in those terms, they may have had the ability to use all hosted code for LLM training through that license, instead of the FOSS licensing on any given Open Source repo. But that would only apply to GitHub/Microsoft, not third party scrapers.

evanelias··on I hate the recent open-source rise
> I also agree that there is a place for other licenses. It's better that there's space for kinda-open, rather than it being open vs completely closed repositories.

That's good to hear, sincere apologies for assuming otherwise. There are a lot of folks on HN who take a much more extreme view there, and I seem to have incorrectly conflated them in the "open source" vs "Open Source" debate.

> having to explain the difference to folks between what it meant to be "open source" vs "Open Source", and the fact that a lot of folks generally don't understand the difference and some of the nuance

This speaks to the core naming problem though: the original OSI folks should have picked a better term! They thought "Free Software" wasn't a good term in part due to the gratis vs freedom confusion (totally agreed here), and yet they picked another equally-confusing term to use instead, that had a pre-existing generic meaning which wasn't related to specific license terms in any way.

evanelias··on I hate the recent open-source rise
Totally agreed. They don't have a trademark, and their superfans have no right to tell people how to capitalize or punctuate the term.

I also get the sense that the author has an inherently negative view of non-OSI-approved "source available" licenses -- and in particular the Business Source License, which he uses as a counterexample twice.

Yet, OSI cofounder Bruce Perens helped improve that license and specifically said "I feel it’s worthy of my endorsement. The new BSL will be a good way for developers to get paid while eventually making their works Open Source." [1]

Why do so many vocal people in the Open Source world have a much more extreme worldview than even an OSI cofounder?

[1] https://web.archive.org/web/20250629110730/https://perens.co...

evanelias··on I Will Never Use AI to Code
> The final sentence says it all

Not sure if the article was edited later, but there are five sentences after that one, expanding on the author's reasoning for their position.

> Next time, lead with that.

The post is titled "I Will Never Use AI to Code"... whether you agree or disagree with the author's position, he's certainly not burying the lede here.

I also can't help but notice the author isn't telling other people not to use AI, he's merely stating his own preferences and articulating his reasoning in depth. Why attack him for expressing his personal preferences in how he goes about his own work, which presumably does not affect you in any way?

evanelias··on Incident with Issues and Webhooks – Resolved
"smaller custom data centers into public cloud" is talking about their Azure migration, so "multi cloud" would almost certainly mean extending a presence into AWS and/or GCP (or maybe others like OCI).

I'm sorry but I really don't see how you're drawing conclusions about this meaning a move off of Ruby and MySQL entirely. That's a huuuge logical leap away from what is written in this post, and you originally stated it in a way that indicated this was a fact.

evanelias··on GitHub Is Down
We can clearly draw a conclusion that their availability is getting worse, but that's not what your original comment claimed.

You said "I can't really remember any significant downtime before the Microsoft acquisition and the data supports my memories", but my memories differ (as do other commenters), and the accuracy of the supporting data seems questionable.

evanelias··on GitHub Is Down
What part of the wording gives you that impression? On these topics, the post literally just says the following:

"bottlenecks that appeared faster than expected from moving webhooks to a different backend (out of MySQL)"

"Similarly, we accelerated parts of migrating performance or scale sensitive code out of Ruby monolith into Go" (in a paragraph specifically about "critical services like git and GitHub Actions")

Both of those sound highly targeted to me!

evanelias··on Incident with Issues and Webhooks – Resolved
I'm skeptical about that page's accuracy. For example, if you go to the breakdown tab, it shows Actions having 100% availability when the graph starts (Apr 2016), yet Actions didn't even exist until late 2018, and wasn't GA until a full year after that. So if the math behind the "average" tab is treating NULLs as 100% uptime, this just isn't a correct measurement.

The page also notes it obtains its data from the official status page, but big tech companies have been known to under-report outages. My general sense is they've gotten better about this in recent years; if so, that means historical data will give an erroneously rosy picture of uptime.

evanelias··on Incident with Issues and Webhooks – Resolved
> migrate their codebase to a new language[2], continue to drop their inhouse ops for Azure resources and get off MySQL

The recent blog post you're linking to mentioned moving data only for webhooks off MySQL, not all relational data used by the entire site; and moving "performance or scale sensitive code out of Ruby", again not the entire codebase.

Do you have an official source suggesting these migrations are more comprehensive than that?

evanelias··on Open source does not imply open community
> it's a little hard to use their name but argue I'm not "one of them."

That's fair, but personally I can't see any reasonable fault with using "open source" in a way that strictly follows the definition in the OSD, and not this intangible unwritten social norm / movement stuff. If they wanted that to be a core part of it, it should have been in their definition to begin with.

And even religiously following their definition for licensing is a bit ridiculous, because they didn't actually invent the term in the first place. Originally, "open" source code was generically understood to mean "the source code is available" without any implications about licensing, let alone community or social norms. For a lot of irrefutable evidence around this, see https://dieter.plaetinck.be/posts/open-source-undefined-part...

So the OSI folks took this previously-generic term and popularized their definition for it, creating a movement around it. They even attempted to trademark it, and were explicitly rejected due to the term being too descriptive/generic.

Nonetheless, I personally avoid calling software "open source" if it uses a non-OSI-approved "source available" license, but that's purely because the many OSI zealots are very vocal, and they defend the term purely through social pressure.

evanelias··on Windows quality update: Progress we've made since March
If a decent number of people migrate away, it would definitely show up in aggregate: Windows Update traffic, for example. Or sales of Windows-specific software/subscriptions. It doesn't require correlated tracking at an individual customer level to see the broader trend.
evanelias··on Open source does not imply open community
> open source should not imply open community, even if that's what the originators of the movement intended.

I'd take this a step further and say the intention of the originators of the movement is somewhat irrelevant, because that movement essentially retconned a bunch of pre-existing licenses and concepts.

Consider the MIT license, which is OSI-approved but substantially predates the "open source movement" (as do many other popular OSI-approved licenses). This license was created not to foster collaboration, but rather simply to avoid legal overhead for software that wasn't expected to have much financial value: https://en.wikipedia.org/wiki/MIT_License#History

Nowadays, because this license meets the OSD and is OSI-approved, people like GP come across any MIT licensed project and inherently assume the developers are part of the "open source movement" and should follow its social contract. Frankly, that's just BS and we should call it out accordingly: license choice alone does not logically imply anything about following a social movement.

evanelias··on Open source does not imply open community
Considering that Free Software predates Open Source, and many popular OSI-approved licenses also predate Open Source, how can you justify your core claim upthread:

> The people that see open source code and assume that it is being developed collaboratively are not being unreasonable – that’s the purpose of the open source movement. If that’s an inaccurate assumption for your software, then that’s fine – but it’s you that is breaking social norms, not them.

It sounds like you think anyone who selects an OSI-approved license, and makes the code publicly available, is somehow explicitly opting-in to the Open Source movement, and users should "reasonably" expect collaborative development as the default. Is that accurate? Because it seems completely nonsensical to me, especially considering the licenses predate the movement.

When you come across a random project using an OSI-approved license, there's no way to know the developers' motivations for selecting that license, if they haven't explicitly stated it. Your default seems to be an assumption that they're opting in to the "open source movement" and all of the social norms that you wrap up in that, but your assumption can be completely wrong, and that doesn't mean the developers are "breaking social norms" of a movement that they never subscribed to in the first place!

evanelias··on The X-Files has made me nostalgic for a time I never experienced
> the poster's lament that he's nostalgic for a time he never knew is one I've heard a _lot_

For sure; the 2011 film Midnight in Paris is a great comedic exploration of this feeling as its central theme. (well, if you can set aside any well-justified reservations about writer/director Woody Allen.)

evanelias··on We gave an AI a 3 year retail lease and asked it to make a profit
Literally the two sentences immediately following that quote are "For now. As we continue down this path, however, humans will not be able to stay in the loop and such guarantees will be intractable."

Personally I find the entire tone of the article to be creepy and disturbing.

evanelias··on Keycard – inject API keys into subprocesses, never touch shell env
I assume other processes running as the same user can still freely read the environment, for example using `ps -Eww` on Mac or inspecting /proc on Linux, right? If so, that's an easy way for a rogue process to bypass the local encrypted vault entirely.
evanelias··on Allbirds, Inc. Announces Expansion into AI Compute Infrastructure
Yeah these are definitely some good examples of startups doing major abrupt pivots after a few years. But I was hoping to figure out if there were any successful examples of established, well-known brands doing it. (For comparison to the original topic, Allbirds was founded 11 years ago and is post-IPO.)
evanelias··on Do you even need a database?
> still supported RAW 5 years ago

I seem to remember Oracle 10g was first released over 20 years ago? It has been EOL for much longer than 5 years...

evanelias··on Allbirds, Inc. Announces Expansion into AI Compute Infrastructure
That makes me wonder, are there any major examples of this kind of abrupt pivot actually succeeding?

Nintendo was a much more gradual product shift that makes sense in retrospect: playing cards -> tabletop games and toys -> video games.

Or another gradual example was Tandy Corporation, which went from making leather crafts -> general crafting/DIY to electronics crafting -> Radio Shack and Tandy computers. That one's funny because the original leather business was spun out and still exists.

But abruptly going from shoes to AI datacenters, or iced tea to blockchain, etc I really wonder if there's any non-scam precedent of that abrupt shift actually working for a major known brand?

evanelias··on Open Source Isn't Dead
It's SaaS though. You don't have access to the binary to decompile. There's only so much you can reverse-engineer through public URLs and APIs, especially if the SaaS uses any form of automatic detection of bot traffic.
evanelias··on Cal.com is going closed source
If I understand correctly, their primary product is SaaS, and their non-DIY self-host edition is an enterprise product. So your neighbor wouldn't have access to the binaries to begin with.
evanelias··on Cal.com is going closed source
It's not a "project" though; the business Cal.com Inc raised that VC money. Their open source repo did not raise the money.

Did they ever promise to keep their codebase FOSS forever, in a way that differs from what they're already doing over at cal.diy? If not, I don't see why it would be reasonable to expect them to spend a huge amount of money re-scanning on every single commit/deploy in order to keep their non-"DIY" product open source.

evanelias··on Do you even need a database?
Your article completely ignores operational considerations: backups, schema changes, replication/HA. As well as security, i.e. your application has full permissions to completely destroy your data file.

Regardless of whether most apps have enough requests per second to "need" a database for performance reasons, these are extremely important topics for any app used by a real business.

evanelias··on The AI School Bus Camera Company Blanketing America in Tickets
Oh how random, that's near where I grew up, and almost certainly in the school district I went to.

As for why the sidewalk abruptly ends, normally it's due to a border between municipalities: some of the municipalities in the area don't have sidewalks at all, and confusingly several of them have Lansdale postal addresses despite not actually being part of Lansdale proper (which does have sidewalks).

But in this specific case I think it's Upper Gwynedd Township on both sides of the bridge, so who knows.

I haven't lived there in decades, but sorry about your ticket in any case!

One other ironic wrinkle: iirc students have to walk to school if there's a route under 1 mile long with continuous sidewalk coverage. And that spot where you got ticketed is right about a mile from the high school. So if that bridge actually had sidewalks, maybe there would be no need for a bus stop in that location where you got the ticket.

evanelias··on The End of Eleventy
> if one offers something for free under a GPL or MIT license, claiming to do so for the betterment of humanity, only to later retract it

I would wager that an overwhelming majority of people who choose FOSS licenses do so without ever making any grandiose claims about the betterment of humanity. Yet upon any suggestion of a license change, if the project is popular, they get attacked for being a lying scheming rug-puller all the same.

> that person is an entitled liar who released proprietary software while using openness and generosity as a marketing strategy

Why do you automatically assume they're a liar, and not just someone whose circumstances or opinions changed over time? Or just responding to changes in the competitive landscape or business cycle?

If you release FOSS software, it seems your only socially acceptable options are to keep future versions FOSS forever, or abandon the project entirely if/when your circumstances no longer permit FOSS development. How is that state of affairs beneficial to anyone?

> Proprietary software is fine.

I agree, but our industry also has a vocal minority of open source purists, who treat anything using non-OSI-approved licenses as toxic waste -- even software using a quite generous source-available license.

For B2C software, that situation is manageable: the purists simply won't touch the software, and will loudly pan it on forums like HN, but plenty of others will try it if it's useful.

But for B2B software, it's more problematic, since there are enough open source purists out there that most tech companies employ at least a few, influencing corporate policy about acceptable licenses. If a new B2B software product has no OSI-approved FOSS edition at all, the purists tend to majorly tank adoption, which hugely impacts the business viability of the product.

So if you're bootstrapping a new B2B infrastructure product that doesn't lend itself to SaaS, what license do you pick? If you go FOSS, you severely limit the economic viability of your own work. Or if you go non-FOSS, you severely limit adoption, which then has the same outcome.

> That comes from some combination of the project looking not worth a cent, probably not working (at least not for the use case intended), payments being a big step

If it was just about money/payments, then non-OSI "source available" licenses would be far more popular, especially ones that allow the software to be used free/gratis for all situations that don't directly compete with the software creator. Yet instead the widespread attitude towards these licenses seems to be far more mixed. How do you explain that phenomenon?

evanelias··on The End of Eleventy
Yeah, I really don't understand why some developers have an extreme compulsion to constantly deprecate and rename things like this, causing massive upgrade headaches to users.

In addition to Hugo, it happens constantly in GoReleaser. In both cases, they're excellent tools, but the unending renaming spree is just awful. Weirdly, both are in the Go ecosystem, which generally values backwards compatibility.

evanelias··on The End of Eleventy
I haven't kept up with it in recent years, but I know it remained popular in Japan for many years longer than elsewhere. AFAIK since 2011 it has been developed by a Japanese company, who acquired Six Apart's former subsidiary there, as well as the brand name.

It's also interesting that so many people in this thread are saying "What I really need is a SSG that also works as a CMS with a GUI" -- that's literally what Movable Type excelled at. Especially versions 4 and 5, which had a FOSS edition. A number of major US media sites were powered by it for years. However because it was written in Perl, that became a huge negative point as Perl fell out of use in the industry.

evanelias··on The End of Eleventy
Ironically, one of the original major reasons WordPress became popular was its dynamic nature. It dethroned Movable Type, which was an extremely powerful and extensible static site generator.

It's wild to me that this post's timeline makes no mention whatsoever of Movable Type, and at one point it links to another author's post titled "A Complete History of Static: The Beginning to WordPress Headless" which also makes no mention whatsoever of Movable Type. Now I feel old :/

evanelias··on WA income tax clears House after 24-hour debate
Sorry but I'm not spending an hour doing math on employee counts just to satisfy an HN commenter. There's no universe where it is sane and reasonable to have 4 separate highly-paid school superintendents in a 3-town area (towns feeding into the regional HS) with total population of only 25k, especially as these schools don't even rank particularly well.

And that's not even accounting for the principals. Think of it this way: if a country's navy has only a single boat, does it really need both an admiral and a captain?

← PreviousPage 3 of 34Next →