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

That's not necessarily a good thing.

Try Safari. No browser is snappier or more power efficient.


Please don't give the pointy-haired boss ideas.


Does it have to be ads? :/


Of course, as that's where the money and power is, the only things SamA is in it for.

There will be equivalent models that are free. Likely, there will even be free ones without ads.

Free+ads can beat free without ads on pure incumbency, marketing and convenience. Most people don't use an adblocker, even though it's trivially easy to install.

Paid, however, can't beat free+ads. Too much friction.


Tesla has an 8 year battery and motor warranty.


All well and good but 8 years isn't that old for a car. I don't even look at cars that new. I start at 10+ years old. The drivetrain on any car should last 20 years if it's not abused and given reasonable care and even if you end up needing to replace the engine or transmission that's a few thousand dollars on an older car. What would a new battery on a 10 year old Tesla cost you? Can you even buy one?


Average lifespan of a car in the US is 16 years, warranty covers half of that.

Given the lowest acceptable threshold for capacity under some warranties (70%) and assuming linear degradation, a 16 year old EV would have 40% capacity (worst case). Given a typical range of 250 for EVs today, that would put you at ~110 miles on a charge.

Seems like it would be a fine car to me given the age. I'd also expect battery swaps to become more common as the industry ages, which will drive prices down.


> Can you even buy one?

I would like to think 1) that the answer is yes and 2) that the price in fact come down over time as battery tech gets cheaper, markets of scale, etc.

Maybe some startup needs to go into the battery replacement market for specific popular models of 8+ year old EVs.


After the wanton destruction of so many game studios earlier this year and now this, Microsoft / Phil Spencer can go fuck themselves. I have immediately canceled my subscription and I hope many more do as well.


That’s rather gross.


No, it means some people are doing it wrong either because:

1. They don't know how to do it the right way

or

2. They can't be bothered to do it the right way

#1 I can understand. We all make mistakes as we learn and grow as developers. #2 is just arrogance / laziness on the part of the developer. Compounding it by blaming the platform owner that clearly and explicitly told you not to go that route is gross.


[flagged]


From the bug report:

> It turns out Electron was overriding a private AppKit API (_cornerMask) to apply custom corner masks to vibrant views.

> ...

> By removing the custom _cornerMask override and associated logic, we allow AppKit to handle shadows with its default pipeline. This resolves the GPU spike while retaining shadows as expected.

I'd say that most often usage of private APIs is because:

4. it probably shouldn't be done at all


I don't know what the comment you're replying to said, but further down the thread:

> Electron's "_cornerMask" override was a dirty hack that was made in an effort to fix an ancient issue with corner smoothing.

So Electron used this private API to fix an issue that shouldn't have existed at all, as far as I can tell


I'll grant that their documentation isn't the best I've ever seen, but it is still on you if you reach for private APIs. Again, that is consciously choosing a shortcut you've been explicitly told not to use.


And there are people who's default setting is to hate/blame Apple because it's fashionable to do so and they are defending not just the use of but also overriding an API explicitly marked as private.

I don't get it.


Apple does also break public APIs, so it goes both ways. I will blame Apple when they are blameworthy and not when they are not.


It's not necessarily "blaming", more a combination of:

- Apple released macOS 26 - This version was in testing for many months - During this time, Apple has apparently not tested how Slack, VSCode, Discord, work - Or they have, but haven't bothered to reach out to Electron maintainers - The overriding of the private API was in order to fix a bug with a public one

Combine all of these and there is some onus on Apple for this. If you don't fix your broken public APIs, don't be surprised when people start using your private ones that do work.

But easily the worst point is that QA apparently is limited to their own applications only. Do they really care about the user if they don't test applications found on nearly every mac setup out there? Don't they use Slack internally?!


How come this only surfaces now? Surely large companies such as Microsoft and Slack apparently tested their products that use Electron with the public betas?


It's very hard to notice and very easy to attribute something else. The main symptom is your laptop heating up which is usually attributed to (1) You just have a slow MacBook, you should get a new one (2) During beta, "it's a beta and it's expected to heat up and be slow" (3) People not caring about temps because they use the laptop in clamshell mode

I believe this falls into the perfect definition of "slipped thru the cracks"


Wasn't this the thinking behind the massive overbuilding of fiber in the 90s?


Yes, this was the thinking behind the telco boom(or bust depending on who you ask), cloud in the 2010s too, was the same.


Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: