rirze

I really hope the community gets together and creates a better browser extension. Vaultwarden + that would be perfect.

I agree with you; I've developed in Python for most of my career and a lot of Python criticism is malformed.

That being said, I'm starting all new large development work in Rust. Python is hard to reason about due to its dynamic nature in large codebases. And if I'm enabling strict typing everywhere, I might as well use a typed language and get a performance boost. Obviously, this is only because I'm the sole developer and using AI to improve productivity.

Work settings are completely different and one has to be a team player to find the language that works for everyone.

Then your domain problem you’re trying to solve doesn’t benefit from Rust.

Sounds like your work doesn’t need Rust and that’s ok.

But don’t generalize.

> they need to hallucinate the data they wanted to imagine instead.

Isn't that what they were doing before AI anyways? It's natural, then.

"Yes."

This.

Every 6 months, I reevaluate how well LLMs can model from scratch or can modify existing files.

It's very superficial (atleast the last time I tried it). I'm guessing if/when LLMs crack visual reasoning, they might be able to do it.

It was also the most prominent ecosystem for "software-for-one". Lots of custom-bespoke, "it works for me" packages that were only created for personal use.

A lot of graduation ceremonies have restrictions on how you can decorate your cap. I would be surprised if this was allowed.

It's too decentralized for my taste IMO.

I like using radicle.xyz instead.

Thank god. I left that job 9 months ago so that's good to hear.

Sucks that it's `(Beta)`, but progress I guess.

Edit: Nvm, I found the asterisk; Full HA requires Gitlab to make Praefect Kubernetes-native and that is not done yet. [1]

[1]: https://about.gitlab.com/blog/gitaly-on-kubernetes-generally...

While hosting internal services for 4 years, Gitlab was the only service that ran hybrid. Wish they could get their act together and focus on actual engineering again.

If anyone at Gitlab management is reading this; getting your microservices to run fully stateless in a Kubernetes cluster should the #1 goal. No disclaimers about potential risk. It's been 5+ years. Get it together. Stop bolting on minor package management features no one is going to end up using anyways.

I didn't think it was sarcastic till I read your comment, upon which point, I got confused and read it twice to make sure it wasn't sarcastic.

Nevertheless, it is refreshing to see nuanced positive energy. I agree that AI is going to be the great multiplier.

This take is too premature. We forget that AI is seamless for contexts that are in the training datasets (popular programming languages, open source libraries, well-documented algorithms, etc..).

It is very obviously hallucinogenic when it comes to new programming languages, new domains, and uncommon/poorly documented contexts. And AI is very poor at (3D) spatial visualization (making AI assisted CAD development incredibly hard).

AI is not capable of genuine logical thinking from fundamentals yet; these are highly trained, curated models.

It's hard to make hooks work here, since the default approach it's using is call the URL directly.

I think it's better to have a repo-level skill instead, titled something like "connecting_to_db.md" and demonstrate exactly how to connect. Codex has been pretty good at referring to skills but it depends on context at the end of the day.

It's researchers trying to contrive an example for why their research effort deserves a budget every year.

Of course their example will be detached from reality. But it doesn't matter.

Yah, that comment is odd.

Sysadmins, Devops engineers will the be the last ones replaced by AI. The context window for their problems are huge.

Unless you define Sysadmins and Devops as fiddling with YAML all day, which might be the case here.

That's not my point at all.

When you have 6 stanzas to perform a dynamic if/else branch, the underlying system if flawed.

Models can overcome the complexity of ansible-- I argue that they shouldn't be. Ansible is a flawed framework.

Right, my bad. Illegal business don't exist.

Any other obviously bad-faith questions?

Whether something is illegal or not has no bearing.

Righteous minds will figure out workarounds in the face of being told "they cannot/should not do <this one thing>".

All you need is one contrarian.

Yeah, you’re gonna eat your words when you do something that’s not “install this package” and “create this user”.

For anything dynamic and sufficiently complicated, ansible is horrible. Pyinfra is much better.

I’m finding great success having Claude design and review code but having codex actually implement it.

All you need is one and a good business model.

Modern adblocking emerged exactly in the same way. The majority of people who use adblock have no idea what current techniques and methods are used.

Damn they really nerfed valkyrie. I loved that class.

This, seriously.

The backend could be git on an SSH server, but if you have a slick design and 100% operational uptime-- you'll capture 80% of the developers using Github currently.

No one wants to do it-- but it's foundational.

It's also very hard to appease everybody; from visual design to operational smoothness.

That's a bit selfishly-expressed.

Private repos provide nothing to the site by definition. The value model here is, you must pay for private repos, either by paying a subscription or hosting your own node and bearing the related costs.

Yah, this is huge. I imagine this is partly fueled by the recent government backlash against Anthropic for not bending down to their whims. Allowing OpenAI models to be hosted by Bedrock basically fast-tracks (sanctioned) ChatGPT usage across all agencies and clearance levels.

Keep working on it. Warp has to overcome much of it's historical bad decisions. They announce becoming open-source, but they don't have trust yet.

> Appreciate the candid take. Warp is great.

Sorry but I can't read this statement in a tone is not absolutely dry sarcasm.

Warp is a masterclass in how to have a great product statement, very nice UI and completely ruin it with greed, closed-source, and by not listening to your customers.

I don't know who at Warp got replaced and wants to "fix" things, but they have a lot to overcome. At this point, it might not even matter-- another product written from scratch might have better success.

It might surprise you to know that most (senior) engineers who review don't read every line of code. They have visual pattern-matching from years of experience and depend on that. A good question is, is that enough? I don't know, but the point is that this is already a established practice.

Also, I will not doubt OP's experience. He has published a good set of Emacs packages that are very capable for the niches they occupy. Certain packages are even foundational dependencies in the Emacs ecosystem.

If OP "vibecoded" a critical package, I'm sure he would take it upon himself to ensure it high quality.