mycpuorg

@danielhanchen, can we use these steps to fine tune other qwen3 models too? like 480B coder or embeddings model?

I remember being ridiculed on reddit back when I posted this.

"Turns out, we think you are all dumb."

Shameless Plug:

I was very fortunate to have a conversation with him a few years ago. We talked a bit about his journey and a bit about his hacks, his setup, and of course a lot about Linux:

http://www.mycpu.org/interview-with-GKH/

"... Elon Musk, Jeff Bezos or Elizabeth Holmes..." LOL wut?

Go home professor, you are drunk :D

<3

Seriously, what is wrong with this? It's a for-profit private org. Does this really deserve the top spot on HN? What's next? "Toyota showroom wants you buy a Corolla instead of a used VW"?

Granted. I am not equipped to answer the question, assumption about js could be wrong too. Perhaps, I should replace javascript with HTML. The argument still holds about distractions and phishing risks etc.

True. I think the workflow will continue to be fragmented even with richer email content.

Wow! Source?

Not sure I understand your question, but in general rich web experience is close to 0. I use html2text which is good for the most part but if you receive emails with embedded javascript and you want to avoid them (a lot of phishing traps goes out of the equation with plaintext). It's a matter of your personal preference and priority. If you like the sort of things mentioned in the article you should give it a shot, at least, try taking a 2-week sabbatical from web email.

Sounds like you will :)

Hi, author of the blog here. It is not everything, but if you were optimizing for certain things like less distraction, fewer "fire fighting threads", detailed thoughts shared via email then Emacs is great. I have learnt to live in plain text for a while now and it is great because a lot the cases don't really require you to respond in html. If you are doing it often, it's probably worth attaching a 2-pager.

But if you are in a, say consultant role, where quicker email responses to clients, html support, MS Word like highlighting, then this is not it.

Trying to understand how is any this is new or different from AWS SageMaker or even Azure ML? IIUC AWS has way better tools/services to integrate with.

Most Google's Cloud Services have been very flaky and inconsistent.

You are right, scratch that and I will try this again. I meant to say:

I have configured and used mu4e on a GMail account and another account hosted on Microsoft Exchange Server (MSE).

The Linux based email client I had tried before mu4e for MSE account are: * WebMail (Outlook's less capable younger cousin on a browser) * a slew of Linux UI email clients like Thunderbird etc.

I disliked all of them equally. However, using mu4e for emails with Outlook/MSE account makes doing emails less painful and less distracting. However, using mu4e as a mail client for Google accounts may not be preferable if you have bought heavily into the Google ecosystem. I have had trouble with things like Google API authentication on Emacs.

Interesting. This is probably a very subjective thing. IMO, this is analogous to selecting a keyboard. You can read all about the tactile feedback from a mechanical keyboard but it's different to find out which one "feels" right, also since I like "test driving" features for a bit and figure how to use it along the way I prefer the 'How' articles. However, I would love to read (and write) more about the 'Why?' behind the features as well.

@rntski, I will be happy to.

I feel I get a bigger bang for buck for Work Email on Outlook Exchange since Email on mu4e makes me less distracted.

<Same response as org-mode> A resounding YES! But Org-Mode and TRAMP are so well written about that although I have "special" setup for these in my config I felt I could not do more justice than other expert write-ups. Maybe, I should add them in a separate entry.

I have tried neo-tree and undo-tree. But never really got around to using them well. Maybe, I need to be patient.

Mortals. LOL!

A resounding YES! But Org-Mode and TRAMP are so well written about that although I have "special" setup for these in my config I felt I could not do more justice than other expert write-ups. Maybe, I should add them in a separate entry.

Please look under "Meltdown - x86" section in GKH's (The Stable Kernel Maintainer) blog: http://www.kroah.com/log/