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

> just don't expect to be able to store your 4k holiday videos on them.

SanDisk's Extreme Pro range will disagree with you on that front. I have never seen a worn out card out of that range.


> This is a lack of linux driver support for firmware designed for windows laptops.

Personally, I don't care. If you don't support open drivers, you have to provide first class drivers on Linux on day 1, because NVIDIA's majority of business is running on Linux already.

On top of that, they claim to have the best Linux support, and claim to have best drivers in their class.

So, it's better to act like that and provide support. If any other company has done that, they have been incinerated with the flame of internet's hate thrice already.


Aeropress is accelerated drip coffee. It's not espresso by any means.

I hve either never had a good espresso or genuinely can't tell the difference between that as americano and an aeropress/v60. Probably best for me not to spend any more on these machines with my unrefined palette

Honestly, I'd not be that hard on myself, and making bad espresso is easy in comparison to making a good one, but you don't need to go influencer levels of rituals to get good espresso either.

A good espresso/americano has more bite in taste than a good Aeropress/V60/drip. I personally love smoother profiles (less acidity, less bite, etc.), so darker roasts and espresso on the bitter side is not my kind of thing, but preferences differ. OTOH, I can make myself a cup of instant coffee if I feel lazy.

Again, there's no need to punch yourself like that. Try, experiment and build your taste profile. These kinds of hobbies needs some kind of experience to refine what you like and what you don't.

Most importantly, don't let anyone's taste dictate yours and vice versa. I never get upset just because how someone I know prefers their coffee way different than mine, but they insist that I shouldn't drink that coffee, because that doesn't fit their taste preferences.

There's no wrong, but only things you like. You can't fail at this, because there's no way to do so.


When you get used to the microwave you have, you can hit the same spot every time. It's a formula depending on your cup, the wattage of he microwave and time.

I can hit the temperature I want every time on a Bosch microwave from 80s which has two power levels and a rotary, mechanical timer.


It’s also helpful to know where the standing waves in your microwave are. Put a layer of shredded cheese on a big tortilla (so you can eat it and it’s not a waste) and run it till it melts the cheese. Observe where the cheese is melted and not melted. Put your coffee cup along the same band of melting. That makes your heating more consistent. Fortunately, mine has it’s strongest focal point dead center (which, I suppose, is not a surprise from a design perspective… still good to know).

Also volume of liquid and temperature of liquid and cup.

I generally fill the cup to the same level, and fill it from the same source in the house in 99% of the time, so they are implicit constants in the equation, at least for me.

If you don't want to use paper filters, you can use Swiss Gold, generic all-steel or cloth ones as well. Also there's Stanley's all steel pour-over.

When you want to go low or no plastics, there are many choices now.


Yeah there are plenty of metal filters if you're ok with not having a paper filter. If you do want a paper filter (for health reasons or because you prefer cleaner coffee) there aren't that many choices.

The funny thing is the default coffee filter I always get is marked as compostable on packaging. It's probably plastic-free as well, then.

You can't PGO that code, though. Also, I'm not sure it can generate architecture specific optimized (-march, -mtune) code as well.

Considering it just pulls and remixes blocks, this is a very tall order for today's LLMs, and maybe a couple of generations as well.

Calling GCC/clang at the back and emitting ASM is both cheating and has no advantages whatsoever as well.


That is fighting the last war on the early days of 5 GLs, and taken care by agentic runtimes.

This isn't futurology, besides a few projects that already came up on Phoronix and around here, with Assembly generation, there are enough SIGPLAN papers on ML driven compilers already.


ML driven compilers are different than LLM assembly generation, and former is more sound than the latter one. I believe we both have enough experience to understand that.

However, starting with LLMs directly generating machine code and moving to ML directed optimization passes, you're moving the whole stadium with a crawler-transporter, not only the goalposts.

Helping compiler in a well defined way, and working on IR or driving it repeatedly to optimize the output is one thing, generating machine code from a training set is other. Let's not mix them.


Yeah, well as mentioned, that is where it is going.

"Compiler 2.0: Building the Next Generation of Compilers with Machine Learning"

https://eecs.berkeley.edu/research/colloquium/compiler-2-0-b...

There are other researchers if you interest yourself on the matter.

Then the whole iPaaS agentic coding environments like Workato and Boomi, that even if they might generate 3GL as intermediate step, you don't get to see it.


Thanks for the link. I have also found a small trove as a warm-up. If anyone interested, here it is:

https://github.com/zwang4/awesome-machine-learning-in-compil...

Using small, purpose built ML "things" to make things better makes sense. We use them everywhere. I never argued against it, as well.


Like inform7 but irreproducible and shitter on every iteration.

Like JIT and PGO machine learning optimizer passes more likely.

It's not their first rodeo. Their cards already need to authenticate with the driver to enable the card completely. When I last checked, Nouveau driver has received a key which only enabled the hardware, allowing enough features to see a desktop and install closed NVIDIA drivers, nothing more.

Remember, the kernel module is open source, but rest of the driver is closed source, and any kernel level code which can't be open sourced but had to be is moved to card firmware. Only the kernel module is open source. Not the libraries, not the driver, nothing else.

NVIDIA is holding to its pearls like a sloth holding to its branch, because their all business model and livelihood is dependent on that control. I still commend AMD's decision to allow full card enablement with any driver which talks the correct language.


That's older than current AI/LLM/NVIDIA wave. Many application specific DSPs probably carry their model weights in an encrypted manner. If not, we would have seen the extremely performant face recognition and tracking models extracted from professional cameras already.

Note, these models generally run 60/120/240 FPS depending on the camera range, and can command the connected lenses at ~100FPS (because physics).


I believe RHEL/Alma/Rocky has released patches today. I have a notice about they have done so.

Alma released a patch ahead of upstream again, just like they did for several other critical vulnerabilities this year.

Debian testing is way more stable than Ubuntu stable. In Debian's parlance, Testing means "release candidate", actually.

If you want real testing, you should run "unstable". If you're in for fun, try experimental.

Running Testing on my desktops and stable on my servers since forever. None of them broke, none of them created problems.

I don't care Stable running 6.x.x. It gets security updates in less than 24h, and is applied automatically before I wake up, and doesn't ship coreutils with 104CVEs, just because it's Rust.


Testing doesn't get timely security updates. It's not for serious people with production systems. It shouldn't even be a debate.

I believe I need to reiterate: Stable is for servers, testing is for desktops if you're not directly exposed to internet.

Again. Stable is for servers, testing is for personal use.

I never argued otherwise, ever.



Debian security team used to offer support for testing, but as the distro grew and attack surface increased, that was dropped. However, security incidents are patched in unstable as well and they float up to testing relatively quickly (for a desktop system, anyway). When things freeze, security updates directly land on testing as a fixup polish.

However, while Testing is "relatively secure", it's never "Server secure". I'd never use testing or testing packages in stable or any server for that matter.


The comment you're replying to makes clear that they're not using it on servers. I do the same thing (testing on my laptop(s), stable on my servers); you just have to commit to keeping track of what's going on and manually patch if you think that it's necessary.

I have to add that for me, testing definitely breaks stuff sometimes. Nothing beyond my ability to fix, though. Nothing beyond anyone's ability now that AI is around.


> I have to add that for me, testing definitely breaks stuff sometimes.

That's interesting, can you give an example? Asking as a curious Debian user.


Testing is the staging area for the new Stable release.

However, one thing that many people don't know is that Testing enters a package freeze every time a new Stable release is to come out. And this freeze can last anywhere between 4 to 7 months. So for that time period, it stops having frequent updates and becomes essentially a stable distro.


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

Search: