Hacker Newsnew | past | comments | ask | show | jobs | submit | bmicraft's commentslogin

The author may feel like this is true, but she probably probably doesn't care for the Kafkaesque nature of the system and doesn't stand to profit from their misery either.

Or don't and adjust it in the sketcher? If you name your constrains you can just reference them directly elsewhere.

I think that's much easier as you don't have to go back and forth with a spreadsheet.


Tracking down individual values in the sketcher can get annoying too. Just depends on the complexity of your part

You can name them if you want, and the names will show up in the properties of the operation, and you can reuse the values in formulas.

There's a lot of options, and I think a lot of it is a matter of taste/experience what to use


The main problem with PHEV is, that's it's comparably small battery will age very poorly because it will both: a) do more charge/discharge cycles per distance driven, and b) get charged and discharged closer to 0 & 100% making the battery age even faster.


I'm not sure where you're getting this idea from, but my PHEV (BYD Shark 6) doesn't drop below 22% battery as the engine is there to charge the battery, not propel the vehicle.

I also believe that most pure BEV drivers would charge their cars daily to mitigate the risk of range anxiety.


> I'm not sure where you're getting this idea from, but my PHEV (BYD Shark 6) doesn't drop below 22% battery as the engine is there to charge the battery, not propel the vehicle.

> I also believe that most pure BEV drivers would charge their cars daily to mitigate the risk of range anxiety.

(not parent poster) I got the perspective from people that wanted to help other people, but stopped repairing PHEVs:

- https://evclinic.eu/2025/09/27/if-you-drive-a-hybrid-may-god...

- https://evclinic.eu/2025/01/19/ultimate-ev-ice-and-hybrid-co...

- https://evclinic.eu/2025/12/04/2021-phev-bmw-ibmucp-21f37e-p...

The difference with BEV charging is that the battery is much bigger and it's a core component (it's properly serviceable), so I can charge it at 60%, keep degradation at bare minimum, and still have 270km of range. With a PHEV you'll need to always charge it 100% to fully use that EV range, so the battery will degrade way faster due to way more cycling.


Cool. Thanks for demonstrating you have no idea of my usage. I charge every second day as I don't drive far or often. Sometimes I go 3 or more days as I'm actually trying to burn petrol to seat the seals on the pistons of my engine/generator.

Plus my 30kWh battery is Lithium Iron Phosphate. Your BEV is likely a Lithium-Ion? Regardless, I should get 3,000-5,000 full charge cycles on my battery. As long as I charge it to 100% once a week I should be golden.

I have a BYD dealership 25km from my house and a 6 year/150k KM warranty. I'm pretty sure people work there, they definitely were when I visited. Given that I'm pretty sure there are people repairing PHEVs.


I'm happy that your usecase is a conscious one, that doesn't completely remove the issues of two powertrains to maintain and a smaller battery. BYD is better than average in this regard, and 30kW battery seems big enough that I agree with you, deep/frequent cycling is less of an issue.

Unfortunately that is not the experience for the average driver of a PHEV. Most people buy by brand, not by specs, so the average result is what you see in the links of EVClinic - 80`000km cars with fried batteries that cost more to replace than the resale value of the car itself (and again, as also noted by EVClinic IIRC, BYD is better than average in regard to repairs and parts cost).


I've had some very bad ram (lots of errors found when tested) and consistently the only thing that actually crashed because of it was Firefox.


That's what named pipes do.


Some kind of elegant unixy syntax would be nice

[ ... Inputs ] | command | [ ... Outputs ]

Basically select(1) as a cli syntax.

I've done quite a bit of unix historical work ... Not enough for a talk at the CHM but decent enough that I have interviewed dozens of people.

I really think some basic stuff was just left in a hacky state and we never revisited the primitives right.

I've been trying to do that in my own projects

For instance I should be able to do something like

Command || processor

And not have processor hijack the input without hacky pty stuff. I am intentionally using || here.

There's lots of use cases to this: llms are the best, logging, rendering text, readline, translation, accessibility, it'd be a very useful primitive and it's impossible to do without a full pty wrapper or some kind of voodoo heuristic wrangling.

Currently you have to do things like this https://github.com/day50-dev/ESChatch/blob/main/eschatch.py#...

It should be easy

I know that some esoteric shells do it but I want everything to be traditional with better i/o features


They don't. They're single reader and, if I remember correctly, sequential single writer.


The Galaxy S5 was only 8.1mm including camera bump, removable battery and IP67 rating.


Is it? I can see the broiler glowing, so at least a decent chunk is close to visible light.


An alternate intuition pump, at least if you're old enough to remember incandescent bulbs: consider how bright a 1000-watt bulb is, compared to how bright (in the visible spectrum) the 2-3000 watt oven element gets.


Look up the emission spectrum for a body at the temperature of a typical oven element: yes, it starts emitting some light that is visible, but the bulk of the energy is still in the IR band.


I think that's the most, if not only relevant part to base your decision on


There was a story here the other day, bitlocker keys stored in your Microsoft account will be handed over.


This has been known for a while, though I don't know if your typical layperson was aware until recently. People need to remember that any access a company has to a device, so does LE with a warrant. Even moreso once you get into federal resources and FISA courts.


Which windows does by default and makes it hard to turn off


You created an account to shill for a product?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: