HN user

alkz

110 karma
Posts0
Comments38
View on HN
No posts found.

Yeah, but what is a 'computer'? For anyone not already in the know, this term doesn't mean "a machine that can be programmed to carry out sequences of arithmetic or logical operations (computation) automatically." (quote from Wikipedia), it just means nothing at all.

Guess this was one of the first implementations of greylisting :)

This was not an issue of being in a vacuum, it was an issue of not reading documentation beforehand, which for some reason is acceptable in the development world

I don't think there are so many people attempting to perform surgery or to build a bridge without reading a number of textbooks on the topic.

And this is why back in the day everyone said RTFM

About the field limit, an application shouldn't have more than 1000 fields in their structured logging.

Usually when this happens is because the source uses what could be considered user input as keys, for example in access logs with stuff such as headers o query parameter, and you make a new field for each header or query parameter. In the latter case all you need to exhaust your available fields in the index is some nasty bot trying random query strings on your site. This can be easily solved in the ingest/logstash pipeline

It is true that you have to spend time to carefully map and process the documents you're ingesting in elasticsearch, but once you do I don't think there's any other solution with the same performance and features for logs, especially considering the licensed features (like alerting from anomaly detection machine learning jobs)

The elastic stack is complex and might be hard to grasp (their own training courses are a great help though), requires significant computing resources, and managing a big deployment can be a full time job, but once implemented correctly you can do awesome stuff with it.

Loki is a simpler and slower solution which does less things, so if you don't need what elastic provides, it could be a better fit as it's probably easier to manage

Around 15 years ago I got my hands on a quadra 700 and managed to install A/UX on it. I don't remember the details but i really struggled to find an external SCSI CDROM drive compatible with the OS, if memory serves me well there were just like 2/3 specific drives supported by the installer. In the end I probably used a SUN one which looked like a mini pizza box sparcstation.

Taking also in account that that version of A/UX ran only on the quadra 700/800/950, it's probably one of the OS with less hardware support around

The OS itself was so simple, it didn't even use init scripts to start its services, but everything was (re)spawned by /etc/inittab like /bin/getty; this was so clever I started doing it with all the services I wanted to automatically restart on my other linux servers

DJI FPV 5 years ago

it informs you that you're going to crash it when you try to actually fly it, and it will break badly. fpv drone frames are usually made from thick carbon fiber, with replaceable arms, and are designed for durability and repairability and they still get wrecked in crashes. so even if i put it in a funny way, it's not as much an hyperbole as much as a fact: unless you're pretty much hovering, you're going to end up with a very expensive and unserviceable pile of broken electronics and plastic

DJI FPV 5 years ago

in this case the drone is so fragile that the only way to get 10mins of flight from it without breaking it, is to hover

I fail to see how the creation of 50K indices on elasticsearch is a meaningful benchmark, that's just not how it's supposed to be used. Also as others said, testing a distributed system on a single node makes little sense... as it is a benchmark which is not reproducible as we don't know how the data was queried and indexed