grokx

> Patch the Planet

I'm sure they named it after the "Hack the planet" slogan from the Hackers movie.

> 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.

Yes, I stopped reading here:

> $12 on the front. Whole-network compromise on the back.

Too bad since the topic on its own seems very interesting.

Mine is from 2013. There is no longer map updates for the built in nav system.

So I bought an Android auto / Car play module that integrates with the car touch screen. Now I have up to date maps and navigation for ever. :)

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 great thing is that it's almost fully compatible with Github actions, so migrating an existing CI/CD should not be too painful. If you plan to move, make sure to read this first: https://docs.gitea.com/usage/actions/comparison#missing-feat...

For sure, it requires a bit of maintenance, mainly for updates, but that's all.

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.

It seems that Twake is the result of Cozy Cloud joining Linagora: https://blog.cozy.io/en/from-7-july-your-cozy-cloud-begins-i...

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.

This made me think about the bagnole, which seems to target the same kind of market: https://kilow.com/en/pages/la-bagnole

I found this Raspberry Pi Zero based bike computer project: https://github.com/hishizuka/pizero_bikecomputer

This seems pretty nice in terms of features, but would probably need a bit of polish.

I can also recommend git flight rules: https://github.com/k88hudson/git-flight-rules

It saved my work a couple of times.

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.

What about several thousand engineers for Twitter then? =)

Regarding WhatsApp, I would say that 35 engineers is OK. Not so much, but not so few also.

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.

Kudos Romain for your work!

In the 00s, my dad had an issue with the infotainment system of its Peugeot 407 that would no longer boot.

An official Peugeot mechanic told him that it would cost something like 4200€ to replace the unit, so he asked me if I could have a look.

After a quick search, I found an update for his system, burn it on a CD, and put the CD into its car.

The system updated, and then would work normally. Problem fixed for one hour of my time and a CD.

Or maybe it is to disambiguate "vert chaud" (hot green) and "verre chaud" (hot glass) that are pronounced the same way. =)

They should have called it "LiberPi"! :)

My kids have the Cars movie version of the Mille bornes. In my mind, the Cars design ruins the whole game, it's no longer special to me. Plus it's really hard to tell the card types without looking carefully at the small logos in the corners. All the cards have cars on it! It just feel like any random cheap Disney board game.

I'm feeling old. :D

It's just that Android might be too much "heavy" for the actual hardware. I don't have any details, sorry. That's what I heard when I was working there.

I was not an employee so this could not be really accurate but, I would say:

- There was way too much bureaucracy.

- Software, security, design choices were decided by some kind of committee that didn't have sufficient expertise.

- Competition between teams.

- They wanted to do scrum, without knowing how to do it.

I think their actual expertise was focused on hardware design and manufacture (they build and assemble most of their hardware components in their own factory), and probably firmware devevelopment.

I worked as a contractor at Parkeon/Flowbird, on the next version.

IIRC, this one is called N² and runs a headless Android on a limited hardware, which explains the slowness of this thing.

The next version (called streetsmart) on which I worked 2 years ago is a real mess. It is based on Android 5.1 (Android 8 or 9 was available when the project started), and features a touch screen. There is absolutely no isolation between ticketing apps and maintenance apps (which allow among other things to withdraw the cash). A custom launcher gives access to one set of apps or another, depending on the current mode. An hardware token and a gesture allow agents to switch from vending mode to maintenance mode, but if one gains access to a shell, one just has to send particular intents to access to maintenance apps.

Some anecdotes:

- We shipped debug Android builds for internal testing (with root, adb enabled, etc) which somehow got sent to the customer, deployed on a public network and got infected by crypto miners. That triggered overheat of the CPU and reboots of the devices.

- Those are supposed to be deployed in Barcelona, I don't know if it's actually in production right now.

- Those were supposed to be deployed in NYC, but the deal got cancelled (not really a surprise to me).

- They run on a 12v car battery and a solar cell. I had a partial machine to dev (with no solar part), and I had to buy a car battery charger to power the battery.

The work itself was rather interesting (have you ever worked on a Android device that has a built-in printer and a cash machine?), but project management, collaboration between teams and vision were terrible. The main board seemed really well designed also.

I worked for a while as a contractor for Parkeon/Flowbird, and asked about the keyboard layout to a hardware manager there.

His explanation was that they did not use AZERTY or QWERTY because it wouldn't work for foreigners.

The good news is that most of the maintenance can be DIYed with a few inexpensive tools. Replacing tires, inner tubes, or brake pads is not really complex. Cleaning and greasing the chain is also easy, but must be done regularly to preserve the transmission. In the same way, tire pressure should be adjusted regularly to preserve tires and avoid punctures. Transmission replacement could be a bit more complicated and requires additional tools, but it's still feasible.

What I would leave to a pro is the suspension maintenance and break fluid replacement.