> Yes, make the battery 2x bigger and include the compute in that.
You can't move the compute away in a headset. I have worked for an XR OEM, and when you are designing a headset, you want the compute to be as close as possible from the cameras and displays, to achieve the lowest possible latency and avoid motion sickness for the users.
Even moving the compute to the back of the headset was not considered viable by our HW team. And we haven't spoken about the bandwidth required for all those cameras and UHD displays.
A better way to reduce the weight of the AVP would have been to remove the (useless IMO) front holographic screen, and to replace most of the glass and metal by plastic. And maybe move the battery pack to the back, to get a more balanced headset.
Like the author, we self-host our git repos at work with Gitea, and it's working very well and brings a rather large set of features you'd expect from a GH alternative.
A few years ago, I started again to attend regularly to concerts, and often in small / mid size local rooms, with an audience from perhaps 50 to a few hundred people.
Those are much more meaningful to me than those giant stadiums where you watch the band on giant screens. These thoughts will seem obvious, but smaller spaces with a limited audience are really warmer. You feel much closer to the artists, you are sharing emotions, sometimes the artist comes playing or singing in the middle of the audience. Things happen! A guitar string breaks, a drum falls, the singer goes out of tune. This is real live music!
When I studied compiler theory, a large part of the compilation involved a lexical analyser (e.g. `flex`) and a syntax analyser (e.g. `bison`), that would produce an internal representation of the input code (the AST), used to generate the compiled files.
It seems that the terminology as evolved, as we speak more broadly of frontends and backends.
So, I'm wondering if Bison and Flex (or equivalent tools) are still in use by the modern compilers? Or are they built directly in GCC, LLVM, ...?
That is also my feeling, at least from a part of the GrapheneOS community. I have seen them despising and bullying /e/OS, Debian, F-Droid, the Linux kernel... Too bad for this project, that is amazing, to have such toxic folks.
Open source communities should help each other, and work together, not fight.
If only UX/UI people spent their time optimizing their code rather than polishing their animations.
Sorry for this rant, but hell, the web, the apps, everything is so sloooow and bloated. Make it instant! I just want to do my things, not to wait for drawings to draw!
Not really, despite the repo being named MentraOS, this repo seems to include only some mobile apps (that either run on a phone or on the glasses), some server code, and some SDKs.
Mentra glasses are likely running on a fork of AOSP, which is not in this repo.
Right, most probably closed-source just like Android wear. Even manufacturers may not have access to the source code, they would just put their stuff in the vendor partition.
A good friend of mine works for a manufacturer that make watches running on Android Wear, and closed-source system updates pushed by Google turn OS-level regressions (like battery consumption issues) into nightmares. So they are switching back to their own AOSP-based OS.
I would argue that EVs are just the tip of the iceberg.
>The race is on to decarbonize road transport and get drivers to switch to electric vehicles (EVs).
Actually the race is on to decarbonize all the things (at least here in France). My wife works at RTE (Réseau de Transport d'Electricité), which is the grid company here. She makes studies for customers that require more power, so she basically see where new power lines could be placed, whether a new high voltage station is required, etc.
These last years, she noticed a rise for such demands, as the whole heavy industry has been decarbonizing their processes: chemicals, metallurgy... Coal and other fuels (used for heat production for instance) are being replaced either by electricity, or by green hydrogen (so even more electricity).
As a Genymobile employee, I'm happy to see this on HN! We use scrcpy internally also, it's really handy sometimes when we need to debug display issues with our Android emulator (Genymotion).
Romain is truly a talented developer, and deserves the success of scrcpy. If I remember correctly, scrcpy was also bundled with Genydeploy (an Android device provisioning solution) at the time.
You can't move the compute away in a headset. I have worked for an XR OEM, and when you are designing a headset, you want the compute to be as close as possible from the cameras and displays, to achieve the lowest possible latency and avoid motion sickness for the users.
Even moving the compute to the back of the headset was not considered viable by our HW team. And we haven't spoken about the bandwidth required for all those cameras and UHD displays.
A better way to reduce the weight of the AVP would have been to remove the (useless IMO) front holographic screen, and to replace most of the glass and metal by plastic. And maybe move the battery pack to the back, to get a more balanced headset.