Hacker Newsnew | past | comments | ask | show | jobs | submit | greenpenguin's commentslogin

In the UK a CIC (Community Interest Company) is an option, which can legally oblige the company to act in the interest of "the community they serve". I think in the USA a benefit corporation might be similar.

Alternatively if Komoot was a worker co-op a sell-out would only be possible with consent from the employees. Consumer co-ops (where users can vote too) are also an option but with more caveats.


There's a few of these floating around that are generally missing something - recent syscalls, types, etc. Thank you for such a complete one!


I'm using RocM OpenCL right now, which I believe is the approved option, or will be. Personally I've not had any issues with it - I can certainly use Blender with it, although the performance right now is so-so (I only have a cheap APU though, so hardly surprising).

I don't believe I have any blobs, other than the firmware one, which is true regardless - can you tell me what blobs you mean?



I can confirm I don't have that installed. I'm using this: https://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime

Edit: actually Blender performance is decent, but the kernels take ~10 minutes to compile.


Not via CPU heating, but a theoretical AVX Spectre attack popped up on HN recently: https://news.ycombinator.com/item?id=17711823


Conversely, I also do embedded development, and our environment is entirely Linux-based, even the RTL tools.


From the article you link: - Sea star disease: probably linked to increased sea temperatures, see https://www.frontiersin.org/articles/10.3389/fmars.2018.0007... - Warm blob: nobody seems quite sure to what extent climate change is involved here, see: https://phys.org/news/2015-04-wedge-seawater-blob-blamed-mar... but to be clear, this is literally an increase in ocean temperature

I'm not saying "hey this is definitely due to climate change", but ridiculing the suggestion that an event apparently linked to increased ocean temperatures might have something to do with climate change seems a little off.


Most DSPs I've worked with have an assortment of really specific extra instructions added for the particular application. I suspect these DSPs are similar - adding a new codec probably means adding a few more instructions, or even the odd hardware block dangling off the side.


I'm not really qualified to answer this, but I suspect the instruction decoder(s?) would be decoupled from register state as much as possible (unless x86 is even weirder than I thought).

Given this, I suspect wiring in a path all the way from the relevant versions of the relevant registers might be quite expensive. Plus part of the decode logic now needs to block on a register value - so a timing based attack might find these.

More qualified comments welcome...


i386 instruction decoding at least partially depend on what descriptor is loaded into (shadow) CS. For example the effects of 0x66 prefix are reversed between 16b and 32b code.


I think this is the paper, which is very briefly mentioned: http://advances.sciencemag.org/content/2/2/e1501466.full


This article appears to originally be from the Guardian: https://www.theguardian.com/commentisfree/2014/aug/06/scrabb...

The site also features several other Guardian articles by the same author. Seems a little iffy?


The 'comment is free' section of the guardian is their freelancer/blog bit. What you're probably seeing is the same author being paid for the same piece from multiple sources. Not all that fishy, just the way freelancing works.


Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: