pjmic

I finished my PhD about a year ago (graduating in a month finally). First and foremost, graduating won't stop you from doing a PhD later. I initially took an industry job for a year and then chose to go back to academia.

I initially went back to academia with the perspective of either staying in academia or going into research, but after those four years I basically lost the will to stick in these fields.

Honestly if you don't have a particular subject or project you want to do for your PhD it's not worth going through it. I initially felt like you, that if I didn't do it I'd regret it, but now sometimes I wonder if the time I spent doing it was worth it ( and I actually wanted to do a specific thing).

It's way more important to just find a job that fits what you currently find interesting than it is to remain in academia hoping that a PhD is anywhere near what you hope it is.

I'm not sure I understand the value of this, does this not mean that a female developer's work may be undervalued if it does not reference another female developer ?

Edit: Actually I guess it makes sense as the higher the chance of you having women call other women's functions then the more likely your workplace is going to be gender balanced.

I'm interested to see how a compiler for the Mill CPU would handle such large instruction widths. Whilst it doesn't have the restriction VLIW had of having a fixed instruction width, I'm not entirely convinced we would often see 30+ operations packed in the same instruction.

Yes but you can also build functional or cycle accurate simulator in software which can give you some information on how the processor could potentially perform. Of course having a soft-core running on an FPGA will most likely give you a more accurate idea of how the processor actually works.

This just reminds me a bit of how programmers could fiddle with memory in the Cell Processor for the PS3. IIRC memory was managed by the programmer and it only made it harder to program for.