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

If I'm torn about anything for Tor 15, it's that the cadence didn't align with a minimum of Firefox 144 as base.

Why?

View Transitions support being implemented in 144 is a very big deal and pushes the web forward for native transition animations.

In the next two or three versions before the end of 2025, Anchor Positioning will also be a big deal.

So, congrats on Tor 15, but Tor 16 will bring a massive improvement for Tor!


Tor is not the same as Tor Browser. You mean Tor Browser 15 :)

The current version of Tor is 0.4.8.19: https://gitlab.torproject.org/tpo/core/tor


Thanks for correcting me!


> View Transitions support being implemented in 144 is a very big deal and pushes the web forward for native transition animations.

Pushes forward into deeper misery for the visitors of such websites.


Tor uses the ESR (Extended Support Release) version of Firefox.


I thought the provided video did a good job describing what's coming.

Here's the referenced article: https://arstechnica.com/tech-policy/2025/10/apple-and-google...


This article is a good reminder of another one from late last year: https://csswizardry.com/2024/12/a-layered-approach-to-specul...

In the above article, Harry gives a more nuanced and specific method using data attributes to target specific anchors in the document, one reason being you don't need to prerender login or logout pages.

<a href data-prefetch>Prefetched Link</a>

<a href data-prefetch=prerender>Prerendered Link</a>

<a href data-prefetch=false>Untouched Link</a>


Since last year, I've finally finished two WordPress plugins I wasn't able to completely figure out, I've built new tiny apps that I previously would be stuck on, I am improving existing projects that I have up to Github now, and more. I think my abilities are enhanced by probably 25-50%.


Middle management for software engineering has gone through a paradigm shift. The trend for businesses is flatter structures, manager roles with more responsibilities and this reality largely includes being as deep in the code as direct reports.

Since 2023, most roles I reviewed or interviewed for were player/coach roles, often close to 50/50 split. In my last EM role, I was hired for exactly this.

I found very few EM roles that are primarily managing with only "being in the code"; I can count on my hands out of hundreds of Engineering Manager roles. Probably closer to 95% or more EM roles require hands-on technical work similar to Tech Lead roles.


I have noticed this as well, and if you're interviewing at a startup, it's almost guaranteed to be a highly technical position. Either a hybrid EM/Tech Lead role or a hybrid EM/architect role.


True in my experience as well — and I think it’s a good thing but companies are way behind in preparing people to fill these roles.


60 minutes did a segment for this type of treatment at WVU Rockefeller Neuroscience in West Virginia. It's intriguing.

https://www.cbsnews.com/news/neurosurgeon-works-to-slow-alzh...


I watched that last year. It's very interesting research and seems effective not just for Alzheimers but for treatment of addiction as well. I'm seriously counting on this treatment for any family members who may end up being diagnosed with it later in life.



I could have written all of this myself. It exactly mirrors how I progressed to the same conclusions. Very well said!


PHP 8.x == TypeScript


Phpstan == TypeScript


A terrible typescript


I would say an actively harmful TypeScript. Just a couple of days ago, I had bug in production because apparently the union of two types is not the intersection but the sum. It exploded because one type had a method that the other didn't. That's an absolutely horrible footgun


My journey into building computers and networking were partly driven by Anandtech. I bought and sold quite a few things on the forums, too. I always thought Anandtech was one of the higher quality tech publications. RIP to one of the best.


I'm glad to hear the forums are still going to be around. They certainly aren't as popular as they once were but I still consider myself a part of that community and enjoy conversing with the old timers once and awhile.


I started with Part 4 intentionally, it stands alone from the other three.

This article is a damning call out of the web development industry and how we've gone down a bad path for the Javascript-first landscape of websites and services.

Part 1: https://infrequently.org/2024/08/the-landscape/

Part 2: https://infrequently.org/2024/08/object-lesson/

Part 3: https://infrequently.org/2024/08/caprock/

If you want to join the discussion, he's releasing each article via his Mastodon account or RSS feed.

https://toot.cafe/@slightlyoff


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

Search: