cbovis

I've never really found Macrumors to be all that click-baity. My guess would be a reference point targeted at their particular demographic.

Reading the article on your iPad Pro? Now you know roughly how heavy the Vision Pro is going to be.

I don't know if "transformed my life" would be the right term but I always harp on to colleagues about my Polycom. I was skeptical when originally buying it but the purchase has ended up being one of my favourite things on my desk.

My laptop is docked and closed so using the built in mic and speaker isn't a great experience on remote calls. I don't like the experience of using headphones for a call because of the effect they have on how I perceive my own voice.

With the Polycom on my desk I just join a call, have everything set up automatically and get a great speaking/listening experience. Connectivity issues have been extremely rare and I can't remember the last time I needed to mess with settings unlike my Airpods which feel 50/50.

I personally have the Plantronics P7200 but there's many good options out there. Plus points for being able to expense it to my employers work from home allowance.

Even the text which is underlined isn't a link lol.

Spain is also similar. We recently locked in a 2.65% for 5 years but 15 years around 3% was also available. That 15 year came with early repayment penalties though.

This just looks like a hostel to me that's amenable to long-term residents. Nothing out of the ordinary about the bed setup compared to other hostels.

Because cod made it that way.

This has been my experience in the past with a heavily snapshot covered codebase. Class names can change, the structure of your HTML can change, the underlying CSS can even change and the end result is still the same because you were just refactoring. At a large enough scale it can be painful to have hundreds of snapshots break for a simple change - especially when you add required code review by others into the mix.

Currently figuring out a strategy for introducing testing into an already large codebase and being very cautious of snapshot tests because of this. Experimenting with visual regression testing but early indicators suggest it could get very expensive if we're not careful about what is covered.

More usage doesn't necessarily equate to more value when it comes to software, you could easily argue the opposite.

What a bizarre brand launch...

* Primary logo in top left of web changed to X

* Favicon still old Twitter logo

* Search bar says "Search Twitter"

* Meta title still says Twitter

* Tweet terminology still in use

* Footer updated to © 2023 X Corp.

* Dialog for upgrading to Twitter Blue now has a blue X logo but copy refers to Twitter Blue

* Communities still called Twitter Communities

What's the plan here and why so inconsistent?

Regarding offline payments perhaps what they mean here is that you as the wallet holder don't need network connectivity but the merchant does?

As a developer consuming design files in Figma on a regular basis something that bugs me often is not being able to drop images into comments.

For a tool designed for visual collaboration it feels like a sizeable oversight that for me at least hinders workflow pushing me into other tools rather than keeping conversation contained alongside the files being discussed. Any plans in this area?

My favourite quote from this site when researching Jeddah airport in the past:

"I have personally had one immigration officer FALL ASLEEP while checking my documents. He actually left his post to go splash water on his face, but then fell back asleep immediately upon return." – a traveller

Feel like there's an "Ask HN: How do you approach a solution you are not sure has a problem?" counter thread opportunity here.

Have you considered NextJS middleware to decorate with request logging?

https://nextjs.org/docs/pages/building-your-application/rout...

Seeing steam rise from the streets in NYC blew my mind. I'd always assumed it was just done for dramatic effect in the movies.

Dans gist is referring to needing a routing layer to map something like `/blog/my-latest-article` to `/blog/[article].html`. This is the same of any non-React SPA.

If I have `pages/blog/index.tsx` in my NextJS app this will get output to `blog.html` and can be deployed like a static site without further top-level routing.

I actually disagree here pretty heavily and think that this doc is due to the bar for competent developers going down in recent years (due to the rise in necessity for more developers of course). There's almost an expectation that powerful tooling should be dumbed down.

The entire doc is written around two common problems:

* You don’t need Effects to transform data for rendering * You don’t need Effects to handle user events

Both of these problems do not occur if you take the time to understand the tooling React gives you. The events point should be a given, that's just React 101 (and yet they have to spell it out to people...).

You don't end up using useEffect to transform props/state and generate new state if you understand that those things are just variables and you can instantiate new variables using them inside the scope of the component function.

"But that's inefficient because of how re-rendering works".

Great, you understand how re-rendering works but haven't gotten familiar with the useMemo hook. Come back when you've gotten familiar with the primitives available to you in React and how they can all work together in different ways, there's not that many of them!

This doc reads to me like a DIY store publishing an article about how you shouldn't hammer in screws even if it kinda seems like you could if you didn't take the time to understand hammers, screws, and nails. It's sad that it needs to exist but that's the current state of engineering.

"For example: you have a callback function declared as an expression, that the useEffect hook calls. The linter will say "oh this is an expression, therefore it needs to be declared as a dependency". But it doesn't, because looking at the code as a human, you can immediately see the function never changes."

Can you elaborate on this? In my experience this isn't the case. If a function is declared outside of the component scope then it won't trigger a lint error. If it's defined within the component scope and not wrapped in useCallback then it does in fact change on every render and the lint error is being raised for good reason.

To be fair the puzzle never explicitly states anyone would eat anything. Perhaps the lion simply can't stand the thought of being alone with a cabbage and kicks it in the river.

The key is understanding the constraints and what would be an acceptable amount of bending whilst keeping to the spirit of the game.

It's never explicitly stated that you can't take things back with you so that's your "aha" loophole. Throwing all three of them across at the same time because it turns out you're a giant wouldn't be in the spirit of the game.

"matter 2 years later when you try to grok why something is the way it is"

Sounds like the perfect use of an inline comment rather than change history?

Feels like a bit of a cheat answer but... my wedding ring.

Take a look at Airalo if you haven't already. They have an India option which doesn't require KYC. $13 for a 30 day 3GB eSIM.

Yeh that's my bad, I was getting them mixed up.

Given some manufacturers are experimenting with subscription models on car features (see Mercedes with heated seats) I don't hold much hope the touch screen only controls will be disappearing any time soon.

Much simpler to remove something from a digital UI in a way that the consumer knows what's happened than it is to disable a physical button and leave the customer wondering why it no longer works.

I'm in a small town just outside Barcelona and although it's not widespread because we don't have many restaurants here there is one place which does this which is particularly frustrating...

One restaurant which serves burgers, tacos and pizza. None of it particularly great but nice if you're feeling lazy. Problem is they split across three brands on Glovo for each food category even though it all comes from the same place.

If one of us feels like burger and the other fancies tacos you gotta pay two deliveries. That is unless you pay for a subscription of course. Someone mentioned elsewhere in this thread that Doordash officially endorses these "virtual restaurants". I wouldn't be surprised if they like the idea that it might push people to premium subscriptions to access free delivery so they get a diversity of food options.

The NFTs will still exist and be tradeable outside of OpenSea even if OpenSea itself disappears because they live within a smart contract.

TIL.

For anyone that might be curious: https://code.visualstudio.com/blogs/2021/09/29/bracket-pair-...

As others have mentioned, Zoho Mail is a great option. It's marketed towards business but pricing is family friendly.

iPhones have Driving Focus built in now (https://support.apple.com/en-us/HT208090) which is a good start but I expect anyone who is happy to use their phone at the wheel will disable this pretty quickly.