jsmith12673

Didn't geohot leave Comma like ~2 years ago

I can corroborate this. My family was involved in a chemical manufacturing business in India from the 60s onwards. My understanding from what my family tells me is that the 80s and early 90s is when a lot of these base manufacturing inputs became readily available.

I've had to use Google Sheets a lot recently, and it doesn't hold a candle to excel. There are a lot of basics missing esp. when it comes to charting.

But I don't like excel much either. If working with spreadsheets was a bigger part of my day job, I'd switch to excel

Janky LSP support is easily Sublime's biggest weakness. Hope they fix it in ST5 if that ever happens

I also paid for ST3, but I switched to ST4 for the hardware accelerated rendering. I don't like their licensing policy anymore, so I just dismiss the purchase signs. I want to get my company to pay for it because paying 100 USD _again_ is just absurd for me.

I have no plans to switch off though. This is still a heck of a lot faster than the alternatives

Rare to find a fellow ST4 user these days

Hmm I haven't, will give it a try!

I was curious about how many inserts Postgres could handle so I made a synthetic benchmark to measure it.

Try BetterSnapTool.

As others have mentioned, this feature is patended. `BetterSnapTool` is $3 is for a lifetime license and does what you'd expect coming from XFCE/windows etc.

Signal is a not-for-profit organization.

I can only speak for myself, so to me this technique is kind of like how they did colour photographs in the 20th century [1] - taking multiple photographs from the same perspective with different filters.

For that reason, I would argue that these are 'true' photographs. Sure, things have been differently exposed, maybe some ultraviolet light has been brought into the visual spectrum; but for all intents and purposes, the light from the subject(s) hit the lens(es) at the same time and the composition is true to what actually happened.

Now, with all that being said, there are many famous photos that are actually composites [2] and what makes 'a true photograph' is still hotly debated.

Digital processing is such an integral part of modern photography that trying to decide what makes a 'true photograph' is bound to get messy.

[1] https://petapixel.com/2014/03/10/incredible-color-photograph... [2] https://www.youtube.com/watch?v=2NeyTEO_JP0

It's possible that Xbox serves as a loss-leader for introducing/keeping people in the brand.

For kids who may only have chromebooks at school, and macs at home, an Xbox may be the first time they make a Microsoft account. That account then goes on to accumulate digital assets and stays with them until much later when they're ready to make bigger financial commitments.

Anecdotally, for the past few years, gaming has been the only reason for me keep a Windows device around at all.

I'd argue that even as engineer 2, or VP of whatever, you're still replaceable.

Outside whatever thin veil of prestige your job offers you, the larger world couldn't care less about what you do or what you make.

> recruiters are bottom-of-the-totem-pole, lowest-common-denominator, bottom-feeders

Recruiters are just people just doing their jobs. It's a shame that you've labelled a diverse group of people so heavy-handedly.

Similar experience here.

The only setups I can use for >1month are the Kinesis Advantage and MX Ergo, or the butterfly keyboard and trackpad.

I've chocked it up to the super low travel keys and not having to put any force on the trackpad.

Besides that I've tried the MS Sculpt keyboards plus all sorts of mechanical and chiclet keyboards. None of them have been comfortable

Don't have much to add, but want to say thanks for sharing those blog posts, they were interesting reads.

The slack CTO's comment about choosing RDBMS because 'familiarity' is interesting. IMO it's a gamble. I've seen it happen with my company when being a latecomer to containerization.

When it came to picking a container management tool, it was a tossup between k8s, Nomad, or just saying to hell with and running those containers ourselves on EC2 instances. Having run our stack on bare metal for year = we were really pretty good at it. There was a surprising amount of automation that could be ported over.

Eventually we picked k8s, and coincidentally, our usage grew more in 6 months than it had in the last 2ish years. So all in all, the gamble paid off.

... but I like to think there's another world where we picked the 'its familiar option' and things still worked out. If our traffic hadn't grown the way it did, we would never have felt the pain of having to manually scale out our systems - or basically write an in-house version of Kubernetes.

So in that sense, I'd guess that maybe some teams have the bad habit of playing the same side of the coin everytime. It may be prudent to stay conservative when picking a Datastore, maybe it's would be smart to pick a risky technology for your app servers? (and vice-versa)

Could someone comment on why exactly this a poor design for their backend? Genuinely curious, I don't have any real world context on systems like this.

For this to be effective you'll need:

- Global agreement and partnership, since you need to decrease temperature globally to make a dent

- Convince everyone that injecting aersols into the atmosphere is the only alternative to catastrophic warming (view in contrast to convincing people of the efficacy of vaccines etc.)

Both of these are incredibly challenging undertakings, even without trying to address the issue of continually acidifying oceans.

And yet, sadly I feel like this is the only most realistic option out of them all.

That's news to me. Guess I won't be ditching my QC25's soon/or ever

In my experience, large sales team = pushing hard into B2B

This survey is incredibly suspect ... as the author themself states, there's an inherent bias for non-american brands.

I find it surprising the FCA and GM cars are topping the list, while being notoriously unreliable in the car community.

Also worth noting that both Toyota and Ford have been ranked as worse than industry average.

I'm not saying that Tesla(s) don't have quality issues, but this survey seems pretty meaningless.

I'll add that my Bose headphones have also always have trouble in the wind. That's to that there not be something wrong with the airpods/bose, but Sony's have a distinct advantage

Your conclusion strikes me as a bit defeatist. Managed systems might be 'better' for users now, but in the long term, they leave users with almost no agency, and that becomes a great opportunity for companies to abuse their position of power.

I also thing think that saying that something is annoying is dismissing what is actually a pretty dark pattern. What comes to mind is how modern day censorship works the internet. If you outright block someone's ability to visit a example.com, they will spot the censorship and try to find workarounds. If on the other hand, you simply introduce a 5% packet loss to example.com, people will blame the _website_ and not potential censorship.

What's to stop Microsoft for adding another 5 minutes of hassle to install chrome or firefox? You couldn't sue them for it, but it would be enough to destroy every other browser on the market.

iirc you can still get the true mileage through an OBD connector right? Might not apply in Vietnam, but I think it might be the case in NA

If the TLS client isn't a webbrowser, it doesn't have to use the list of trusted roots provided by the underlying system (be it OS or browser).

Certificate Pinning is the solution you'd look to if you have a clients that cannot securely ship with root certificates/cannot pick the root certificates they will use to validate a certificate when initiating a TLS connection.

Edit: I should add that I am not a mobile developer, so I don't actually know if the 'bring your own root CA' method is supported by the corresponding TLS libraries. But I know that this is possible 'in general'

Don't have an article on hand :/ just something that I've played around over with over time.

Which part is confusing? Maybe I can try to clarify/give examples where helpful.

You create a Root Self Signed Certificate, and then deploy leaf certs signed by that root to your API.

Then deploy your client apps with the certificate of your self signed root.

Assuming that your root is safe, no attacker will be able to generate a cert that will be accepted by your client.

Economics noob here: the paper concludes that past automation is predicted by 2 key factors: pay and employment. What does that mean exactly?

Are they saying that higher a job pays, the more likely it is to get automated? Or the other way around?

Also what does 'employment' refer to exactly? Is measuring how well the demand for labour is being met in a certain job?

Interesting, thanks for sharing!

I'm assuming your team is using vault for PKI, but is there a similarly happy path for issuing certs without Vault.

I started off just using `openssl` but it all felt very janky, and I didn't really have any idea how CRLs should be setup

Thanks for reaching out! Since I have the chance I'll add - Nomad is pretty awesome, and I love the work your team is doing.

My org looked at Nomad at a time when there was a lot of pressure from above to deliver something as soon as possible. Two weeks just weren't enough to full lay of the land ¯\_(ツ)_/¯

Funny thing is even if I could plug in my own service discovery into Nomad, I would probably chuck it away and replace it with Consul after a few weeks anyway haha