What a waste of time.
8,107 karma · joined July 22, 2011
Coding Blog: https://jl2.github.io
SmugMug: http://laroccophoto.com/
Radio Call Sign: KC0JSL
What a waste of time.
I can't speak for the OP, but I can certainly tell the difference between photos taken with my different camera gear. I have an iPhone, a Fuji T3, and a Nikon D810 to compare against.
The Nikon is 10 years old and still a lot sharper than the other ones, despite them all being years newer than the Nikon. In challenging conditions (wet, low light, etc.) the difference is even more noticeable.
https://photos.smugmug.com/Snowy-Davidson-Mesa-Ride/i-wGFDt5...
For example, a picture like that one would be difficult to take on a phone because of the snow. First of all wet fingers would make using the phone nearly impossible. Even if it didn't, there's a good chance the focus would be off due to the snow in the foreground. And the sharpness of the Nikon blows the other cameras away. In the linked photo, do a 1:1 zoom of the fire department logo above/leftleft of the front wheel and you can read the text, including the small "EMS", "Colorado", etc. around the border. Phones just won't get that detail. And that's an old camera.
Besides the image quality, the DSLR is just easier and more comfortable to use once I learned the controls. There are no dumb menus and touch screens and I can adjust settings and take pictures with big mittens on even when it's wet/snowy/raining. Meanwhile, my iPhone is completely unusable with wet fingers.
I use my phone to take pictures most of the time, but if I'm going out intentionally to take pictures, I always take a real camera.
But I don't have much faith in humanity to make things better, so I'm not sure I'd want to see a future with another 200 years of people making things worse.
I guess I would say I'm happy to live my life now and let the future can take care of itself.
It's easy to blame the companies, but if the consumers keep buying the shitty products then there's no reason for the companies to spend money fixing stuff. I stopped using Apple long ago because I thought the software quality was going to crap. A lot of people won't do that, and so they get what Apple gives them.
Still, as a software engineer, I don't see a problem closing out old, abandoned bugs. Even for a company of Apple's size, there's limited time and sometimes it can be literally impossible to fix all of the bugs in a way that satisfies the people opening them. Given that, their approach for deciding which bugs to close seems reasonable and more fair then other ways of doing it.
That's probably true, but not totally unexpected. I suspect HN readers are relatively tech savvy, and probably do an above average job avoiding the seedier parts of the internet and generally know to be cautious online.
I don't know if that matches my experience. I've seen plenty of places where the dev teams complain about tech debt and other kludges costing too much, slowing them down and causing other problems, but management don't want to "waste time re-writing working code".
But now that management read on linkedin they can jump on the AI bandwagon by having the team use AI to fix tech debt, there's suddenly time to work on it.
Finally, a profit source!
The company I work for uses a contracted recruiter for hiring, and the other day he was telling me that they're seeing a huge amount of scams, fake candidates, and "hands off" applications where people are trying to use AI to do basically the whole interview process - apprently even video interviews. We've mandated at least one on-site interview just so we can be sure we're getting actual people.
And most of these job candidates aren't even doing it maliciously, just "life hacking" the interview process. It's going to be a shit show if organized criminals start using AI.
As a software developer, I don't have any problem with this. If a bug doesn't bother somebody enough for them to follow up, then spend time fixing bugs for people who will. Apple isn't obligated to fix anybody's bug.
It's not like they were nagging him about it - it's been years, and they had major releases in the mean time. Quite possible it was fixed as a side effect of something else.
I wish they would rewind back to using Presto and being an independent Norwegian company, but I'm sure everybody who made it a great browser back then is long gone.
Jack Dorsey's layoff message last month did the same thing.
Is it some kind of "Prove you're not an AI by purposely writing like an idiot" or something?
That's silly. In general, people don't mind paying more for a product they perceive as better. Just look at Apple.
And the problems are definitely a lot more interesting.
But of course they'll leverage their connections and get high paying jobs like in this case.
There's a big difference between ChatGPT writing a prescription and a doctor double checking his diagnosis using some kind of Claude code for medicine. ChatGPT writing prescriptions and giving medical device directly to people should absolutely be prohibited for now, but the second approach should be encouraged.
SBCL (and maybe others) use a "core image" to bootstrap at startup. It's not unheard of for people to build a custom core image with the packages they use a lot from the REPL. It's become less common as computers have gotten faster, and most people use systems like Quicklisp or Roswell to automatically get updates and load from source. Of course the SBCL core image is generated from the compiler source code when building it, and the dependencies are loaded and compiled from source initially, too, so there's still going to be source code files around.
You could, in theory, start with the compiled SBCL image, exclusively type code into the REPL, save the image and exit, and then restart with the new image and continue adding code via the REPL. I really doubt anybody uses that workflow exclusively, though. At the very least most people will eventually save the code they entered in the REPL into a source file once they've debugge it and got it working.
There's also a docker package for managing containers - similar concept and UI to magit, but for managing Docker. Not as life changing as magit, but convenient.
Anyway, the problem with changing the default after all this time is that everybody would want the new default to be different, and changing it now would meaning breaking things for long time users who depend on the current default. And TBH if you're setting up a container and installing Emacs, it's very little extra work to copy over a .emacs file that fixes everything the way you like.
There are a ton of Emacs users, and it's doesn't make much sense to talk about them as a group like that, no more than if I were to say, "The list of things Windows users don't get..."
But it's easy to disable or have them created somewhere else, which is more than you can say for most software lately.
That's so out of touch.
First, you're conveniently ignoring the possibility that people actually like the job they are about to lose.
And believe it or not most people aren't toiling away at jobs they hate because it never occurred to them to do something they like more. They work jobs they dislike because it's the only choice they have because they have to pay their bills so they can survive and so that their dependents can have an acceptable life.
Sorry, but I experienced first hand Firefox's memory leaks not being taken seriously. This "bitflips" news is just released, but I fully expect anybody complaining about Firefox crashes to be met with low effort "It's your RAM," responses for the next few years now.
It used to be memory usage, now it's crashing.
The importers pay the tariffs, and they might get a refund, but it's unlikely they can distribute the money back to the people who they passed the price increase onto.
Imagine I imported 1 ton of rice and paid the tariff. Then I split that ton of rice into 2000 one pound bags and sold them to two super markets, with a higher price accounting for the tariff. Then one super market decided to absorb the price from their margins and sell it at the same price as before to avoid price shocks. Can I track down the other 1000 purchasers who paid a higher price? Is it even worth it?
The one posted to HN is better in several ways, but I was mainly interested in learning about 3Delight.
I'm really curious what bigger hashlife patterns would look like (metacell, etc.) but the visualization gets tricky with that many objects.