it’s not worth it to me. the battery life is a huge feature, and it does feel like Asahi development has slowed. i have enough computers to tinker with. i bought my Macbook specifically to be an entry point into my other machines, i.e. from the airport or brewery or coffee shop.
maybe when it makes sense to buy a new laptop i’ll find some time and motivation to contribute, but just using Asahi doesn’t really appeal to me.
i completely understand. as a Rust developer that uses Neovim, i have some hills like that too. and if i was more of an OS dev and/or had the time i might be interested to help improve the platform. my last attempt was a Thinkpad, but i had to have an external mouse for that thing, the fans were causing me to fail stealth checks, and the battery was basically a UPS.
i know a laptop that’s amazing in almost every aspect except that it doesn’t run Linux. the Macbook Pro. to me there’s barely any real comparison to be made unless Linux or Windows or the keyboard layout is a hill worth dying on to you.
i have servers and my gaming PC on Linux, but i wouldn’t trade my Macbook with its unified memory, incredible battery life, best in class touchpad, and top notch screen for anything else. Windows is dying, and chip designers (outside of Apple) seem more interested in cashing in on AI than providing a user experience. i was excited to see what Qualcomm would do, but it doesn’t seem like OEMs or Windows are particularly interested in supporting that platform as a next leap forward, while Intel is bleeding on the side of the road and AMD is constantly side-eyeing Nvidia. i think it would be peak irony for Nvidia to come out of left field with a desktop class ARM processor that’s Linux native, but that’s a pipe dream. what the ecosystem needs is a real competitor to Apple that is more focused on desktop machines than enterprise contracts. maybe RISC-V Frameworks will break out in a meaningful way. but it just seems like anything else these days in a compromise based on some biased preference or moral judgement.
anyway all that said i’m glad there’s an ecosystem of people who are stubborn enough to work on this platform. i have my own stubbornness, but i just don’t have the motivation to apply it here
this is why i moved from Arch to NixOS. now i know what system packages are installed and can even leave comments in the config to remind myself what the heck cyme does, for instance
without checking, Gates’ wealth is probably tied up in a lot of MS stock, and he could probably walk into the office and ask the intern to get him a coffee. but yeah i think mostly retired.
Linus is still active is maintaining the Linux kernel.
i would start by seeing what the actually API response is. i haven’t used OpenWebUI, but to me this looks like some kind of error response from the server. you could use an API tester like Bruno.
also check your Ollama logs to see if it’s getting the request and any other output there.
if you really want to stick it to Google you have to go for Firefox or something derived from it. Chromium gives Google a ton of leverage to push features to all of their downstreams. not sure what engine these are using, but i also prefer to use Firefox because it’s open source. if these were open source you could easily see which engine they’re using.
it’s so much worse than the normal search. i would search for “dog” or “pasta” or “house” and get a pretty good result, but this conversational shit is just plain worse. and the “conversational” aspect is useless
pretty common misconception about how “AI” works. models aren’t constantly learning. their weights are frozen before deployment. they can infer from context quite a bit, but they won’t meaningfully change without human intervention (for now)
is there such a thing as “legitimate criticism” against an entire race of people? this writer is bonkers, and you can tell from the intro. seems like the actual content of the post was buried beneath the first paragraph where a rare few would find it. maybe it was wrong or illegal to fire this guy for being a racist asshole (being a state funded org or something?), but couching it in this narrative of “cancel culture” and “a violation of the first amendment” has fashy vibes to me. institutions should be allowed to control the narrative set by their employees. i understand that as part of my company my words reflect on them, and it’s up to their discretion whether they want to continue to associate with me based on the things i say. you have every right to say racist shit on your favorite fascist-owned platform, but everyone else has the right to tell you to fuck off.
also big downvote for posting this in a technology community
it’s just a lot of complexity, especially if you’re targeting only Android. it’s single threaded and not native to the platform. you’ll be behind on platform versions and have to find shims for everything. you’ll run into weird issues for which the fixes are not supported by the native platform. the more layers you put in between you and the native runtime, the more things can go wrong
Android Studio and Jetpack Compose is going to be the path of least resistance, but i’d need to hear more requirements to make a real recommendation (besides try to avoid React Native unless you have a really good reason)
not really. using WASM as your full stack for your front end is just adding to the complexity and jank. WASM is there for compute heavy stuff. you can use it that way if you want.
i know i’m in the minority here so i’m not going to bury myself in this hole, but i do think those are addressable problems. many of them have been addressed. replacing Javascript is exactly what i’m talking about.
it’s fine as far as laptop keyboards go. i’ve pretty much given up on laptop keyboards being really satisfying. i use a mechanical when possible