Ask Claude whether a man can be a woman. No matter what political side you're on, models are censored. I'd argue American models are a lot more censored/biased on a lot more topics, and especially on things that come up a lot more than some highly specific Chinese politics. Claude even refuses to translate song lyrics because of copyright.. I wish we could simply have uncensored models from all sides, but it's pretty clear that's not happening right now.
Honestly, I think that's a good thing. A lot of questions were either duplicates of existing questions, or close derivatives of them. If I had to guess, probably 90% of SO questions already had a solution somewhere on SO. AI surfaces these solutions much quicker, so you don't have to ask. Novel questions or bugs that can't be answered or fixed by AI still get asked, and mods have less spam to deal with. I fail to see the issue here.
Wasn't the entire goal of Ladybird to have an open and independent browser engine? Making it effectively closed to contributions makes it.. Not independent anymore. It's now dependent, on few people who work on it, just like any other closed-source or corporate-controlled browser.
The same thing happened when we transitioned from horse carriages to cars. I'm sure a lot of people were quite outraged. But aren't we glad it happened?
Sure, you're allowed to hate whatever you want. I never said they're not allowed to hate AI. I said they're gonna have a hard time in the future if they can't accept that the times are a-changing'.
These people are going to have a really hard time coming to grips with reality in the next few years. AI is here to stay, and it's expanding very rapidly. If you can't fight them, join them.
I've had pretty much the same experience with my AI chat app. Nothing works well. Markdown rendering is slow and laggy, streaming is slow and laggy, everything locks up the UI. I've tried at least 5 of the most popular text editor components for UIKit and SwiftUI on GitHub, and all were broken in one way or another, buggy, and slow as well. It's ridiculous.
Honestly, this kind of thing seems to work quite well with vibe coding. If I remember correctly, the Ladybird JS engine was "vibe-ported" to Rust as well, and it passed 100% of the original test suite, in addition to new Rust tests.
I kind of see your point, but I also kind of don't.
Sure, it would be great if you'd immediately get hammered with hundreds of requests and start make money quickly. It would also be great if it was a bit more transparent, and you could see more stats (what counts as "idle"? Is my machine currently eligible to serve models?). But it's still very new, I'd say give it some time and let's see how it goes.
If you have it running and you get zero requests, it uses close to zero power above what your computer uses anyway. It doesn't cost you anything to have it running, and if you get requests, you make money. Seems like an easy decision to me.
Please see my other comment here :) We do not collect any private data, and we never will. We only collect very generic and fully anonymized usage data, but that does not include typed characters, words, clipboard history, snippets, or anything else that could be considered private.
Hey, we're super transparent about the data we collect.
We collect zero data about your typed words, personal dictionary data, stored contacts, clipboard history and basically anything else that's privacy-sensitive.
What we do collect is very generic and fully anonymized metrics such as: Do you use a theme, did you modify the keyboard, did you add an emoji key to your keyboard, etc.
We are not interested in typed words or any private data. We just want to know how people use the keyboard in general (which features in particular), and that's all we collect. You can opt out at any time, and all collected data is automatically deleted every 30 days because we only keep a 30-day rolling window.
If you want to be extremely safe, you can also skip enabling full access for the keyboard, which makes it impossible for us to send data from the keyboard itself to the app. But as said, we don't actually collect any privacy-sensitive data (and never will), and disabling full access comes with a few other caveats because Apple put many basic features such as vibration etc behind the full access setting as well, for whatever reason.
Yeah, this is the great irony of it all. Germany really wants to discourage taking a car for "environmental reasons" and so on and does everything to encourage public transport.
But one thing is clear: I won't be bothered, robbed or even stabbed in my own car, and I also won't arrive in a different village lest I drive there myself. I won't arrive three hours late either, or have to stay overnight in some shitty Hotel because they couldn't find a replacement train.
The German public transport, like many other things in Germany, is an absolute fever dream for a "developed country".
All of these are incredibly obvious. If you have even the slightest idea of what you're doing and review the code before deploying it to prod, this will never succeed.
If you have absolutely no idea what you're doing, well, then it doesn't really matter in the end, does it? You're never gonna recognize any security vulnerabilities (as has happened many times with LLM-assisted "no-code" platforms and without any actual malicious intent), and you're going to deploy unsafe code either way.
[ my public key: https://keybase.io/splitty; my proof: https://keybase.io/splitty/sigs/lWVQRH_iE6_yoV6QCsRhCDUX-nOdGNuyp_G3rofnrB8 ]