Set
and Map
would be more useful if they were compatible with JSON. I see a lot of people using an object as a dictionary or an array as a set because of that.
Set
and Map
would be more useful if they were compatible with JSON. I see a lot of people using an object as a dictionary or an array as a set because of that.
Sometimes it’s the only option or the preferred option.
I haven’t. Maybe someday I’ll be willing to, but not today. It’s a hassle and extremely intrusive to provide my bank statement and photo ID to a company whose security I don’t trust.
That’s usually how I pay if someone requests money. Venmo is owned by PayPal but my account there works just fine.
I thought about that, but they ask for enough info that they’d be able to identify me. And then they’d probably ban me. At least right now I have the option of restoring my account, even though I have no intention of doing so.
You live in a city, but most of the store chain’s customers live in the suburbs where gas is a major expense and fuel perks are a big incentive to shop at a particular store.
The store isn’t trying to promote fossil fuels. They only care about customer loyalty. Besides (they might rationalize), their customers have to buy gas somewhere so why not from us?
The one that’s not shown: Standalone Passwords app
deleted by creator
True, it’s a private (not local) IP. It could easily have connected to a remote system, as their proof-of-concept did.
This code execs cmd.exe
and pipes output to and from a hardcoded IP. That’s pretty weird. What’s running on that IP? How does the extension know something is there?
It looks like VS Code has no review — human or automated — or enforced entitlement system that would have stopped this or at least had someone verify it was legit.
Are you sure about that? Dial tone is a sound you hear before dialing, not the sound you hear when you press a key.
Their findings included an extension that opens an obvious reverse shell.
The Fisker Ocean has solar panels on its roof. It can add 4 or 5 miles a day if fully exposed to the sun.
Not enough to matter. It’s a gimmick.
If you don’t have an EV, you may think that EV owners are worried about range, and they’d welcome any increase. I have not found this to be true.
It’s more like having a car that starts every day with a full tank. You’re never going to burn through that in a single day. Pretty soon you don’t care about range, efficiency, or pay much attention to the battery meter. It only matters if you’re on a road trip, which for me is a couple times a year.
I would not want to give up a nice full-roof sunroof for a few extra miles a day.
Thanks. That’s good to know.
Use this shortcut from Ricky Mondello, the lead for Apple’s password development team.
I get the feeling they wanted to do a Passwords app for some time but needed to get, probably executive-level, buy-in to get it done.
Apple will get bad PR about this: they are “Sherlocking” password managers. 1Password will write a blog post about how this is actually good for them because now password management is mainstream; 3rd party password managers will decide to focus more on the enterprise market; Microsoft will come out with a competing password manager that re-uses the name of a previous product and is bundled with Edge, etc. How it always goes.
Any USB-C headphones work.
Do I sense a bit of sarcasm here?
Imagine the bed is a clock. The 12 o’clock position is at the head — I don’t think anything else makes sense. That makes it unambiguous.
The positions are 3 o’clock and 9 o’clock.
Did you mean White Castle?
Come Sail Away by Eric Cartman
Edit: Although perhaps there’s a more famous version. Nothing sticks out.
There also needs to be some way to indicate that a JSON construct is a Set, Map, plain object, or array. You’d want a date/time type as well.
Without breaking existing JSON parsers, the way to do that is to add metadata like a
_type
field to an object, or to add a “sidecar” object like superjson does. Which works but is ugly IMO.Then there’s BSON, YAML, JSON Schema, and the one we don’t mention ₓₘₗ. To my knowledge all of those could be extended in a way to support new types, but require the producer and consumer to both understand and follow whatever convention you use. They lack the universal interchangeability of JSON.