From what I've read, EVs mostly break with the engine, and recover quite some of the energy that way. To the point that I've read warnings about the breaks rusting here in south Sweden, and that you need to do some aggressive breaking now and then to clean them out.
With my EV I rarely, rarely use the actual brakes. It's almost all engine braking (with power recovery) -- this is how 1-pedal driving generally works in an EV.
Surely it isn't impossible to devise one-way data flows that provably work for remote sensing? And yeah then you have to send somebody to fix stuff if something is off..
Like something that would work but not not scale would be one computer writing data to an updating qr code and another reading it. Surely something like that can be made (and probably already exists?) on the cable level?
I jumped to mac with Tiger when they started using x86.
Around 2006 I believe.
It was always to become more comfortable with POSIX, but I liked it and have stayed. My current laptop is a 2019 MBP and as they are now phasing out Intel support I'm now buying a thinkpad and finally moving on to Linux. Macos has just become too annoying, and macs too expensive.
Try it on a flaky connection. Every menu (maybe any action of any kind?) makes a roundtrip to the server before displaying, with a very slow timeout.
It's crazy how bad it is.
Not just that, some actions spawn an entire Chromium instance. For example, any time you click on a music video (not a new thread, an actual full Chromium instance).
I think they've gotten worse about this as an organization over the last few years(?). Earlier this year an update to their mobile app introduced loading time, and resulting slowness, for opening menus that used to be ~instant. To me that smacks of once having known not to do that, but that knowledge having been lost (or priorities having shifted).
More specifically, I'm talking about tapping the '...' on a track for the options menu. That should be latency-free, and used to be.
I have a software degree and some work experience but have been doing other things for a decade or so.
I'm curious to try out some "vibe engineering" but it seems a bit daunting to get started, there are so many new tools available on top of the AI itself.
Are there good resources for somebody like me to get started, that'll guide me though how to think about prompting, and using CI and how go have the agent successfully write specs and tests and what-not. I don't mind paying some for a good course, but I find it hard to figure out which one would be worthwhile, or whether there are some youtubers that would be better to follow.
The best option at this point is to just sign up for a paid plan with either ChatGPT or Claude and then ask the model the same thing. My preference would be for ChatGPT and if you've been out of the game for a long time then using the desktop app might be the best choice https://chatgpt.com/codex/
Then try starting with voice mode (if you're comfortable chatting out loud) and just talk your way through it.
Build a sandbox, download Codex CLI or Claude Code or whatever and spend some time doing some creative stuff with it just for the sake of learning how it all fits together.
Pay attention to the inputs you provide and the outputs that they result in. Keep your bullshit detector engaged: Bots often lie.
If you get stuck, or it gets stuck, or you want prompting advice or whatever: Ask any frontier-level bot for help. Sometimes, it's very instructive to get help from Claude for an issue with Codex, or vice-versa.
Want better tools? Ask the bot to suggest some that exist. (None of the existing tools fit? Have the bot write new ones.)
All of this stuff is always in a state of flux, so even with the lies they'll do better at teaching than any fixed reference will. They're LLMs and processing language is what they tend to be best at... so go ahead and use that.
And remember: They're designed to behave kinda-sorta like humans, but they are not humans. They're just computer programs. If you don't like their output style, or they don't like your input style: Ask them how to implement rules that make them knock that shit off. :)
I've used both, and for me mullvad has worked a lot better. They seem more focused on VPN as core to what they do and don't leak data when reconnecting to a different server, and with proton I often experience that my connection stops working if my laptop gas been closed for some time, and the only way to make it work again is to reconnect to a new server. And then it leaks connections for a few seconds.
reply