Hacker Newsnew | past | comments | ask | show | jobs | submit | mtndew4brkfst's commentslogin

Seems to be pretty substantially AI-assisted during its development.

Well, survivorship bias means that Elixir is loudly populated by AI maximalists now. Just go look at the last several years worth of US/EU Elixirconf talks schedules, it's maybe a third of each cohort and included in keynote slots.

How is that survivorship bias

Because people who enjoyed working with Elixir otherwise but don't want to participate or support that kind of environment have mostly left when the trend became clear. So the folks who are sticking around are the ones who are neutral-to-positive on AI. This means explicitly or implicitly surveying that group for opinions on AI's place in development work, such as while designing a conference schedule, are going to be missing most of those voices who might once have objected. It will continue to skew harder towards favoring AI in the future with most of the possible sources of more-critical opinions leaving.

That to me seems to match the definition of survivorship bias quite well?


Maybe selection bias.

Now we watch this viewpoint proliferate thousands and thousands of times over, even if it's less commonly stated so baldly, and yet people still wonder where the doomer viewpoints stem from?

Yes, but I am full in on simulation hypothesis, and people are going to enter the matrix... willingly.

https://nexivibe.com/intj.html


While some of the ideas in this do resonate with me (or at least they're entertaining), it's unfortunate that's it's so obviously LLM generated. And some parts of it, like the INTJ exceptionalism, reek of LLM sycophancy, which then turned into to some kind of god complex...

observation a: Document title is about a minority's rightful supremacy

observation b: document says "this is not political" then dives into persuasive speech

conclusion: this document was written by the bad guys


i just actually read that and it is possibly the most morally abominable screed I've come across in a long time. Shocking that its acceptable to share in polite company

I find Mergiraf pretty pleasant to use and frequently pretty helpful as a time-saver. Handles TOML and Rust for me, and I have way fewer manual interventions, especially after supplementing it with rustfmt rules to not do a bunch of merged use statements in one go. Easy to configure as a jujutsu tool as well.

https://mergiraf.org/


The ones in my neighborhood are full of religious evangelism titles or bad self-help books.


I cannot and will not advocate the burning of books, but I did get a 13 volume collection of Ann Coulter books... And they did burn well. 415F.


I can't see how Amazon is incentivized to avoid making any changes that break compatibility for their imitators, so long as their first party SDKs continue working. Standardized feels like it should be suffixed with "as long as Amazon doesn't ever feel like evolving the product further".


There is a lot of software that directly implements the HTTP S3 API. That API is also documented by Amazon.

E.g. the last implementation I saw was by DuckDB https://github.com/duckdb/duckdb-httpfs/blob/main/src/s3fs.c...


I think my point doesn't really land. I was trying to express the idea "S3 is not a standard where AWS is the reference implementation, it is a successful commercial product with many many copy cats".

Their only real inherent commitment here is to whatever backwards-compatibility expectations are being set for their first-party SDKs. If they fulfill that but other vendors can't or won't follow suit, the outcome is gonna be different than it would be for an actual standard rather than an assumed one. There is no meaningful leverage for the third parties to exert to force a community-favored outcome if Amazon decides otherwise.


If amazon changes the API they've angered their entire customer base that relies on the API. Sure, some will stick around if they're fully entrenched by the ecosystem, but others will be able to leave, and they will, because hey, S3 is a standard-ish API.


It would be pretty shocking for Amazon to break the S3 API at this point. There is a huge 3rd party ecosystem that would be affected. For example, in Rust land the object_store crate is at least as popular as the official SDK.


You're probably thinking of Actix and the unsafe/TechEmpower thing? I've never seen Axum involved in any notable drama.


Yeah that one.


Yeah; but that was 6 years ago - from way back in 2020. Was it really that traumatic for people?


That was part of Rust Evangelism Striking Force meme genesis.

And then we have the whole reflection drama with the author going back contributing to C and C++ ISO work.


That was just the community pressuring actix to take safety more seriously after the author dismissed safety risks and was proven wrong.

It had nothing to do with fighting over which language is best lol


I have no idea about timeline, progress, or suitability, but IIUC the Tauri folks are exploring integration with Chromium Embedded Framework:

https://github.com/tauri-apps/cef-rs

https://github.com/tauri-apps/tauri/issues/14963#issuecommen... and following comments

https://github.com/tauri-apps/tauri/issues?q=CEF


For some people cua-mode being opt-in and very difficult to discover organically will be a larger barrier for comfort and learning than normal/insert modes and motion commands could ever hope to be.

(10 year evil-mode user who moved to Neovim for other reasons, chiefly performance/LSP nativity/plugin ecosystem vitality)


You just need learn C-x C-s (save) and C-x C-c (exit) to be able to edit files on the command line. It's kind of like nano, except has syntax highlighting.


Animated server logos, colorful /gradient and tonally-varied usernames & avatars, the super emoji or whatever they're called, etc all feel like they're pushing more towards Twitch chat than anything else. Which as another commenter remarked, is essentially aligned with their original and biggest target demographic.


I like those things tbh. A lot of it helps make things more visually interesting, and other users more distinctive.


> Animated server logos, colorful /gradient and tonally-varied usernames & avatars

Fair, but all of these things are user controlled. If you're using Discord for work or something, presumably you don't have a bright flashing animated server icon and avatar, your server doesn't have gradient roles, etc.

The super emoji are spot on though, those are fun but were really dumb from the get-go, and waste space in the reaction UI.


It’s also their method of making money which is locking cosmetics behind subscription or purchases.

Other option would be to limit core features for non paying users.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: