HackerTrans
トップ新着トレンドコメント過去質問紹介求人

alkz

no profile record

コメント

alkz
·3 か月前·議論
Oh I used that all the time, it was so awersome! back in the day it really felt like magic...
alkz
·5 か月前·議論
[flagged]
alkz
·6 か月前·議論
go outside, talk to people
alkz
·10 か月前·議論
no
alkz
·昨年·議論
what really caught my eye is the 3d printer itself, took me a while to find the repo for it, so here it is: https://github.com/The-Soft-Robotics-Forum/flex-printer
alkz
·3 年前·議論
no
alkz
·3 年前·議論
[flagged]
alkz
·3 年前·議論
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.
alkz
·3 年前·議論
blizzard was acquired by microsoft
alkz
·4 年前·議論
this is exactly what we needed, a camera to attach to an unobtainable device
alkz
·4 年前·議論
mostly everywhere except the us from the looks of it
alkz
·5 年前·議論
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
alkz
·5 年前·議論
that should actually be porcAmadonna
alkz
·5 年前·議論
sure relational db is ok if fits in memory, but if we're talking about TBs of metrics i'd rather look for another way
alkz
·5 年前·議論
in most cases elastic is easier to scale than a relational or timeseries db
alkz
·5 年前·議論
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
alkz
·5 年前·議論
elastic 5.x is ANCIENT and no one in their right mind should still use that for any production workload
alkz
·5 年前·議論
just classic apple hostility towards their users and developers
alkz
·5 年前·議論
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
alkz
·5 年前·議論
most distributions provide signatures/checksums to verify the download eg. https://ubuntu.com/tutorials/how-to-verify-ubuntu#1-overview