HackerTrans
TopNewTrendsCommentsPastAskShowJobs

filereaper

no profile record

comments

filereaper
·6 個月前·discuss
>Google says creating for people rather than robots is the best long-term strategy.

Robots for thee but not for me.
filereaper
·7 個月前·discuss
As a Canadian, we should work on improving our productivity and incorporate more automation and tooling. Whatever impacts our GDP in times of tariffs and economic uncertainty.

Not collectively waste time on the useless debates on how to spell things.
filereaper
·7 個月前·discuss
Llamafile did great work on improving cpu inferencing and generosly upstreamed it into llama.cpp

Wonderful project, please check it out.
filereaper
·9 個月前·discuss
There's almost an underlying assumption that taxpayers will bail you out, or you that you won't go to jail for all these securities frauds, or miscalculating risk on pension funds assets is okay.

Rip away all these away and the Emperor is called out to be naked very quickly.
filereaper
·9 個月前·discuss
We've just started to roll out our MCP Servers and if Anthropic and the community has already moved on, we'll wait till all this churn subsides till switching over next time.
filereaper
·10 年前·discuss
A good recent real life example of this is when the POWER architecture moved to Little Endian. The API's stayed the same (think GLib C API), but LE introduced a new ABI where registers (ie r12) which had a specific purpose in BE changed in LE. This all has to do with linking/compiling.

At runtime if you're reading/writing to memory you had to ensure that you read and write using the same "stride" ie reading and writing back in 32bits is fine, but if you read in 32bits do some transforms in a register and write it out in 16bits you'd have to make sure the internal register BE representation and the written out to memory LE representation made sense.

The GCC and other compiler guys can give you lots of war stories about SIMD (VMX/VSX on POWER)

Anyways, just something I thought off the top of my head :)