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

Python has some absolutely kick-ass libraries, even without C. It has Django, for those of us who like developing web apps but never could fall in love with Ruby on Rails. And Django is amazing. I've also yet to see a better language for writing quick ETL scripts and pipelines. Also, an 'I need a script for $SYSADMIN_TASK but I want to be able to read it later.' Anything dominated by external latencies (web, databases, etc) will be fast enough for many uses in Python.

Sure, it's not a language to write a web browser or game engine in. And it is slow. But it has some very strong niches outside of ML/Data science. Personally, I love it. To each their own.


> Also, an 'I need a script for $SYSADMIN_TASK but I want to be able to read it later

uv + PEP723 make this even better.


On the other end of the spectrum, today I needed to build a complicated piece of software on x86-64 Linux and all I have handy are ARM Macs. One qemu later, I have an 8-core “PC” building merrily. It won’t win speed records, but it’s entirely usable.


I know your needs were already met, but would a Docker image with a ready-to-go cross-compiler have done the job? (I've run into this task before.)


Go look at the editorial policy from Ars. Lee just writes like that; it's his style, it always has been.


This keeps getting posted and is not true. Rosetta is still present and working. It throws a deprecation warning notice but otherwise runs fine.

It's macOS 28 that will no longer run x86_64 apps, although games are exempt. Rosetta is basically going game only at that point. They haven't announced how long it will keep working in this capacity.


Have they announced how they’re going to make it game only? A whitelist based on a hash of the executable? That seems cumbersome.


The basic answer is ability to run x86_64 will still be there, but the system frameworks (apart from like OpenGL shims etc.) will no longer be shipped with x86_64 slices.


The macOS 27 release notes explain how to activate this mode. `game-test-tool`


My guess (without much to substantiate it) is that it will also keep support for running x86_64 programs in virtual machines via `container` too.


That’s correct, Rosetta for running x86_64 binaries in Linux VMs is not going away. They’re no longer branding this feature as Rosetta, so it doesn’t get lumped in with the Rosetta removal for Mac binaries (although it’s all still kinda confusing)

https://developer.apple.com/documentation/Virtualization/run...


Aha, thanks for the reference. Good to see that written down by Apple!


Have a TrueNAS server at home with a bunch of drives in a RAID-Z array. Backups go there. My pictures, which are probably my single most important item, are also there but get cross-backed up to a very good friend’s NAS in a different city. And his to mine.

My wife’s backups also go on BackBlaze because she would be much, much, much less tolerant of a local glitch than I would.

TL;DR local-first backups here. Time Machine makes it trivial except when it falls on it face and has to start over. Highly recommended if you can put up with replacing a hard drive every few years.


Just give them all ACME catalogs and watch the problem solve itself.


I do this same thing too when building archives in macOS I will unpack on Linux later.


I use FontAwesome. I bought FontAwesome subscriptions for my team. Love the product.

“We released new icons” (or a new version) is a message that has exactly zero information content for me. My workflow is “I need an icon for this,” so I open FA’s site and search. Done. Remembering that I searched for an icon that wasn’t there months ago, so that I’ll go check and see if it’s in the new release? Not going to happen.

No shade here. If you live, breathe, and devote your life to your product you’re going to be orders of magnitude more excited and attuned than the rest of us. Just… remember that we do not care to the level that you do. We buy it to be a tool in our toolkit, not the center of our lives.

If Ryobi sent me an email whenever they added a new battery-powered tool to their catalog, or upgraded a drill, I’d lose my shit. My time and attention are valuable to me. Don’t take them for granted.


People who are such fans that they want to know will find out - I refresh https://toolguyd.com/ multiple times a week because I do want to know what crazy shit Ryobi and others are up to. But I’m rare.


> We buy it to be a tool in our toolkit, not the center of our lives.

Somehow this thought evades almost all software providers nowadays. Distracting, and in equal amount, obstructing self promotions and unwanted hints are the norm, which is making life worse, not better. Then why paying them to annoy us? Somehow this very basic thought is not there, not a bit in most of the cases. They want to be the center of our attention. Idiotic. (I do not ask for forgiveness for this strong word. I believe that the costly - and eventually paid by us - marketing teams are dumb copycats senselessly pushing bad practices established elsewhere through time. I do not dare trying to find exceptions, it is hard.)


So many naysayers. I love it! So what if it doesn’t come from the Brut region of France and thus it’s just sparkling cement, it looks great and is clearly a labor of love.


People who are insecure about their expertise in many subjects, (especially within art and the humanities, in my experience,) will unfailingly use any opportunity to point out when they know something someone else doesn’t. However, if someone posted “check out my super rad FP framework,” but it was actually OO with some bolted-on FP ideas, even if it was neat in its own right, people here would be totally justified in saying “hey… about that whole FP thing...”

Even if they look similar, there’s a big difference between sour grapes ego boosting, and people with subject matter expertise pointing out common misconceptions. A major problem with Engineer’s Disease is mistaking the former for the latter based on maybe having read a few blog posts and falling down a research rabbit hole once two years prior.


Thank you!


First line of the readme: Non-functional implementation work-in-progress framework code for getting HDR10 working under X11.


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

Search: