HN user

flounder3

280 karma
Posts0
Comments45
View on HN
No posts found.

One traditional enterprise goal of 40% utilization was to cover DR/failovers, so one region could take on 100% of traffic from another, with 20% headroom.

I'm curious about the granularity of contracts around granting/selling excess capacity. Are they short term? Can the owner evict those workloads (with a penalty)?

Muscle memory for folks who have been doing it since before -i was an option. I still instinctively type `sudo su -` because it worked consistently on older deployments. When you have to operate a fleet of varying ages and distributions, you tend to quickly learn [if only out of frustration] what works everywhere vs only on the newer stuff.

`sudo su - <user>` also seems easier for me to type than `sudo -i -u <user>`

How many hours have you spent with the latest Tesla FSD in congested neighborhoods or unprotected left turns at sunset? It may be "good," but it's not even remotely close to the current Waymo experience, especially when it comes to abnormal situations. I am continually blown away by how Waymo behaves (spent 3 hours in them this past week). I'm rooting for Tesla, but it is nowhere near Waymo as of today.

OP's 9to5mac article states:

  Also under the agreement, Google’s model will reportedly run on Apple’s own servers, which in practice means that no user data will be shared with Google. Instead, they won’t leave Apple’s Private Cloud Compute structure.
Bloomberg states:
  The model will run on Apple’s own Private Cloud Compute servers, ensuring that user data remains walled off from Google’s infrastructure.

TSMC building outside of Taiwan is a big deal these days: https://en.wikipedia.org/wiki/TSMC#Arizona https://en.wikipedia.org/wiki/TSMC#Washington https://en.wikipedia.org/wiki/TSMC#Japan https://en.wikipedia.org/wiki/TSMC#Germany

From the article:

  "about 30 percent of our 2-nanometer and more advanced capacity will be located in Arizona"
.. so it's interesting that they are moving forward with domestic 1.4nm given the geopolitical climate.

I’m a backer and can’t wait to receive the 8TB upgrade!

I had to buy an off the shelf M1 Studio due to a hardware failure, so I couldn’t wait for the lead time for one with more RAM and storage. It has been borderline unusable due to so many things requiring local storage — can’t even symlink to an external NVMe. (Many apps, but also Backblaze metadata and iMessage attachments)

On the very first page:

The internal hard drive uses SCSI with an unusual connector. Adapting it didn't seem straightforward, and we weren't confident the old file system (HFS) would be easy to read from a modern system.

We found that most proxies/firewalls (90%+ ? I forget) didn't tamper with it. The largest hurdle was working with load balancer vendors to implement it.

NUCs are a tremendous value over previous generation surplus hardware in areas where the cost of electricity has skyrocketed (SF Bay Area).

We’re talking more than one order of magnitude less power consumption when you compare to 2-3+ generations ago.

Even 10 years ago, Apple internal privacy policies prevented itself from collecting precise lat/long. We had to use HTTP session telemetry to determine which endpoints were best for a given IP (or subnet, but not ASN), which informed our own pseudo-geoIP database so we knew which endpoint to connect to based on real world conditions.

Even still, it had to be as ephemeral as possible for the sake of privacy. We weren’t allowed to use or record results from Apple Maps’ reverse geo service outside of the context of a live user request (finding nearby restaurants, etc).

Chargepoint requires you to maintain an account balance, and requires auto-refills. You can't just bill a CC for the entirety of a session through the app/site. Sometimes you can initiate a non-linked session with an EMV tap from a physical card, but that doesn't always work.

No, it is not bullshit. And no, he certainly was not excellent. Perhaps he managed to take credit for a few "good" things, but it's interesting to watch you defend someone who was ~so~ widely hated.

I could give you a list of 40 tenured engineers and leaders in Eddy's org [along with at least 20 in adjacent orgs] who physically celebrated his departure.

The only function of the box is to switch the power on and off

That is false. These are much more sophisticated than a mere relay. Sure, there is basic logic between vehicles and EVSEs which is basically a smart relay: https://en.wikipedia.org/wiki/SAE_J1772#Signaling

...but the electronics you mentioned are for onboard controls (energy monitoring, Time of Use enforcement, load balancing between multiple units, etc). Some EVSEs are very simple, but many -- including the one in the article -- also handle upstream communication like OCPP: https://en.wikipedia.org/wiki/Open_Charge_Point_Protocol https://www.chargepoint.com/files/OCPP-Fact-Sheet.pdf

Here is an example of integrations for the model in the article: https://zaptec.com/downloads/ZapChargerPro_Integration.pdf

There are also implementations of power line communication over the Control Pilot pin in J1772, which most people notice when charging via CCS at a DC Fast Charger, but that is not limited to L3 charging. Note that QCA7005 chip in the article: https://www.qualcomm.com/products/application/wireless-netwo...

See also: Plug and Charge https://en.wikipedia.org/wiki/ISO_15118

There have been a few other recommendations over the years, including putting a separate tier of forwarders first in line to perform transforms and such. There were always plenty of options for on-prem/DIY/Enterprise especially when using syslog instead of directly via HEC.

Their SaaS offering used to have said inline tier called IDM (Inputs Data Manager) where we were directed to configure filters during our POC… a key requirement for moving from Enterprise to SaaS because conf files aren’t managed the same. One month (to the day!) after we moved, they randomly decided to migrate us to a new “Victoria experience” where that tier suddenly disappeared without explanation. We filed support tickets asking 1) what happened? and 2) how do we filter things out now? and were directed to hire professional services because that was outside the scope of standard support!

The whole point of moving to SaaS was to not have to babysit our own clusters (small shop at the time), so spinning up a ton of infra in front of the freshly greenlit SaaS setup would have negated the productivity gains and financial pivot.

Ultimately, the entropy of hundreds of applications logging in disparate formats and namespaces outweighed our ability to sanitize each app within a reasonable amount of time, leading to unwanted data being indexed, ergo overages. Overages that our sales engineer originally assured us we could address by filtering things out with the snap of a finger. Bait and switch.

Ingest Actions were not available at the time, and were not functional (even in beta) until 10 months later.

I can truly empathize. I’ve never wasted so much of my time on a vendor. It’s infuriating and certainly not worth the personal stress and agony. It shouldn’t be this hard!

I was part of Orchard and miss it dearly. It had a lot of potential but it was launched as a proof of concept built on pooled resources freed up from optimizing legacy workloads (namely, moving Siri from VMware to Mesos).

It never got the love it deserved and I could absolutely believe that its Splunk cluster suffered as a result. RIP