Take this with a mountain of salt since I've not at all an expert, but with a little help from AI, it seems like the exemption lives in 2023/1670 [0]. The LLM claims that this and the regulation you link are interconnected, with the recital of 2023/1542 explicitly linking them.
>Unless your device complies to MIL-STD-810G CN1 and has the certification to back it up your product will be required to add user replaceable batteries
Can you provide your source for this? If nothing else, it's very surprising to me that an EU regulation uses a US standard as the baseline!
Edit: Having done a bit of reading on the standard, it also seems like the regulation needs quite a bit of detail if it really does rely on the MIL-STD, since the standard only defines test procedures, not pass/fail criteria?
You have to manually install hooks in your local repository. They aren't propagated as part of the repo. Git has intentionally made hooks require a very explicit opt-in.
Muse this - train is a tool, just like a car, bus, bike, plane, drone or rollerblades.
Repeating "trains" in every transport context is unproductive. Each mode of transport requires certain density. Most US cities just don't have it. It's that simple.
It's not at all that simple. One of the neat things about trains is their permanence - once you've built one, you can fight for allowing increased density repeatedly until you win. That's what we've been doing in Seattle!
I'm really curious how old you are. The great grand-dad part makes you think you're my age or a bit younger, but then I grew up very middle class and I don't know if I've ever even seen a black-and-white TV.
From googling just now, color sales exceeded black and white by the 70s. However, new black and white models were still being introduced even into the 90s in the U.S., particularly in the budget or portable segments, and were still being sold new into the 2000s.
I'll imply those things. If you don't fit in the seat, you should have to buy two seats is a not very controversial opinion on the internet IMO. I think that opinion basically violates all of your "surely"s already.
Where do you draw the line? A 250lb person probably mostly fits in their seat still, but at some point a person is just physically going to take up two seats. Do you really think the airline should be responsible for flying them in business class (premium economy doesn't give you more width on most/all airlines)? Does it matter if their weight is due to a medical condition or just laziness? What if they're so big that even a first class seat won't contain them?
The issue is for the airline to solve, since they are the ones trying to make seats comically small.
Also, you have to include other attributes. E.g. Not my problem that you have freakishly long legs, if you have to prevent me reclining then maybe you should have to pay for premium economy. And what if you are broad shouldered? Same deal, not my problem, you have to stay inside the boundaries of your own seat.
I would rather we used regulation to make economy seats a bit larger. Call it a safety issue, since it is.
Except for "You make less money, often half.", which is a hell of a pill to swallow. As someone ~10 years into my software career, I'm pretty confident that even if I got laid off tomorrow and never found work as an engineer again, I'd still be better off now than if I had stuck with ME or EE as I originally planned.
You make more money, but the work is highly unstable. I find the "applying for jobs" process far more difficult than "doing the work" (especially in a small country where hiring freezes are highly correlated). If I could start again I would have gone overseas to do EE instead of switching to SW/FW. Now I intend to start a new career in another scientific field.
I never played any games like that, but simply giving the agent a clear exit criteria and instructions to check the exit criteria every time it thinks it's done on a complex task was often enough to keep it chugging away for most of a day on a single prompt in my experience. Per-prompt pricing just isn't sustainable period, even if everyone is acting in good faith.
I'm curious about the opposite: Why would anyone use the CLI when, at least with Copilot, the VSCode plugin is super tightly integrated with VSCode, meaning the agent can see everything I can see. There's no mismatch in linter calls where I can see a lint in the ide that the agent can't find for example. I've had this problem even using CC in their VSCode extension, so I can't imagine it's not an issue in the CLI as well.
I use the Claude Code VSCode plugin for 80% of my work.
I prefer it because I can look at the code (although not as often anymore) and config (very often!) easily.
It also lets me jump to previous conversations easily.
There are a few cases where the CLI makes sense. One big one is if you are running multiple simultaneous sessions on a remote server using Tmux to have them preconfigured when you reconnect is nice.
0: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A...
reply