I agree, it's by far the best mobile keyboard I've ever tried. I especially love the shortcuts for copy/paste/select all/cut which send the actual Ctrl-C. I can finally use terminals! :-P
I can't see what's wrong with that (you choose whether to accept suggestions or not), but you can always blacklist predictions by long-pressing on them.
FUTO keyboard actually has an option for this (enabled by default) called "Smart key-hit detection". It adjusts hitboxes based on dictionary predictions for what you just typed.
Back when I was using QWERTY with Microsoft SwiftKey, I used to swipe a bit, but it never really felt comfortable for me. I've tried swiping again after switching to Colemak on my phone and everything is so close together that the accuracy is very low. I wonder if this model will help improve accuracy on other layouts too (or even languages!).
I hope FUTO does start caring about language support, because for example their AI powered text prediction is only available for English. I'd happily train a model for them in my native language if they provided instructions on how to do so. And I'd help with swipe typing too.
I'm Greek too and I got 81 (well technically I misclicked one in a hurry, would've been 82). It did help a bit though. Surprisingly enough I've learnt many of the more advanced words from technical blogs!
Yep, I've used both. Desktop mode isn't exactly there yet, but hopefully with the general availability it will get with Android 17, it'll smoothen out. As for the Linux terminal I ended up sticking with a fork which provides a few extra features (https://github.com/outlawsanzhang/koiTerminal)
Depends. One of the reasons I stopped using Spotify was because its offline mode refused to work when my device had all radios off (who even thought of this?). Once I turned on Wi-Fi, even without connecting to a network, it would load immediately.
Yes IPC is definitely a security hole, but because the two apps communicating need to both explicitly support it (I really doubt there'd be an exploitable vulnerability here of all places), it's a much smaller concern. Here I'd mainly worry about apps like Google Photos talking to Google Play Services. GrapheneOS has mentioned they'd like to implement IPC scopes to isolate apps, just like contact scopes and storage scopes.
Funnily enough, the Huawei P30 Pro I was using previously (back when these things could run Android with GMS) had network toggles for all apps. They weren't in the permissions menu, as they were meant for data saving purposes but you had the additional granularity of choosing if an app could access mobile data or Wi-Fi separately.
That solved the problem of ads in games much better than DNS :D
I guess that makes sense, since it's pretty new. OpenSnitch is great software in terms of functionality but I find the UI lacking. If LittleSnitch can keep the same functionality, while improving the UI, I'm switching. My other current concern here is that the LittleSnitch UI is just a Webview and I think it would be much better if there was a native option (ideally GTK-based for me, but Qt would also be acceptable). Webviews are slow and full of bloat.
This is excellent, both educationally and from a UX standpoint! I've tried multiple times to read explanations on how transistors work and bounced off, but this time I think I've finally understood how to use them, at least practically. I feel like this is a great continuation of https://nandgame.com which taught me quite a bit about how small circuits combine to form something big (although I never finished it, I hope to finish this one at least). Another thing that I find interesting, is that while it is clearly developed primarily by AI, the result is exceptionally better than nearly every other AI-assisted project I've tried.
Some suggestions:
- What I miss from NAND Game is the challenge of optimizing for efficiency. You'd build a component and it would let you know if it could be built with fewer NAND gates and you'd try to simplify the circuit. For example, while I did "NAND it" with 4 transistors, I did "The dual" with 5 and given the explanation I got afterwards I could have used one less.
- This definitely needs to get better on mobile
- The description for the first level using BitLine and BitLineBar (I think that was the Sense Amp?) doesn't really explain what it's supposed to do and I had to deduce it from the truth table.
The same argument could be said for other age verification methods. Nothing stops a kid from getting their older cousin to verify their identity for something and it will never be possible to prevent this.
Owned by Russia? How'd you reach that conclusion? Just take a look at the sanctions imposed on them and the US support for Ukraine in the war.
Also: it seems you've fallen into the "Russia is our enemy" propaganda trap.
IMO ever since the EV3, LEGO's robotics hardware has been on a downfall, being much less open and more focused on "connect it to your tablet with Bluetooth to do some basic programming". They also offer less ports and sensors and I think there aren't any custom sensors either. If you can find an EV3, it's the best thing you can get.
> By far the best part is how tied to specific versions of Ubuntu each ROS release is, just getting all the packages installed and running requires sacrificing a cat while chanting Hail Mary backwards in Latin.
100% this. I had a very, very miserable time setting up two systems and trying to get them running a version that was supported. The worst part is SBCs that stop getting OS updates and become permanently locked in to a specific version. Which also forces the rest of your hardware to use the same version. Using a Jetson Nano with Ubuntu 18.04 in 2022 was lots of fun...
Last year I met a couple of university students working on a robot and out of curiosity I asked what they were using as a microcontroller and the software stack. They were running ROS. When they said they still hadn't upgraded to ROS 2 yet, I could feel their pain...
As someone who has been learning robotics as a hobby for a decade, my advice is: forget all the buzzwords and what the industry is using and start small instead.
I started robotics at a young age and began with small builds with LEGO motors and sensors, getting a feel of how each one works and how to interact with them with code. Then I got to much more advanced programs with LEGO Mindstorms EV3, learned about things like PID controllers practically and even started taking part in some competitions. Next, I went to writing actual code (as opposed to block-based programming) on microcontrollers like the micro:bit (and a few years later the Raspberry Pi Pico). I deepened my knowledge of how electronics work and learned how circuits work. I eventually got into a team with a few friends and we built a human-size robot combining 3D printing, a bunch of circuitry, ROS, 2 SBCs, Arduinos, a LIDAR and OpenCV for face/object recognition. This took years of learning step-by-step to achieve.
This is obviously not the path you'd take, robotics was what brought me into programming and you're probably going for the opposite.
You're not going to build a perfect robot or electronic device from the start and you shouldn't try to either. Get a microcontroller that's newcomer-friendly and play around with it. A micro:bit mostly emphasizes on the end result, with a built-in display and sensors and many plug-and-play modules to get you going. A Raspberry Pi Pico is much more flexible, but also requires you to learn about wiring and doing more things yourself. If you prefer coding in C, go for an Arduino. An ESP32 is also a good choice. It's a good idea to get a 3D printer and learn CAD in parallel, as it's a great way for a hobbyist to create actual tools that are more than a bunch of wires.
Once you get enough experience and confidence in your skills, you'll want to get into more advanced projects. Use your knowledge to plan them out, research and learn the technologies you're going to use (you can't learn everything beforehand and each piece of hardware is something different) and enjoy the journey from prototype to finished project.
And by the way (you didn't mention it but other comments here are so I'll give you an opinion on that), ROS is nearly always overkill for hobbyist robotics projects :D