16 karma · joined November 7, 2010
And that is absolutely the wrong way to approach API development. An API that is being sun-setted should never be removed, because older clients could still use it but sometimes can't be upgraded to newer clients. Removing a v1 API breaks those clients and it's a shitty thing to do to users. Yeah, people should be building NEW things with it, but there's no reason to look at the v1 API with "disgust" as "deprecated" implies - It's simply an older version that should remain functional, if your system is worth half a shit. AWS doesn't terminate older API versions, they just create new versions. Or you can be like Facebook and "deprecate" stuff and just shut it down before your official shutdown date, or not give any notice at all - that's REALLY a fun culture to work in, I guess, for them. "deprecated" is a really negative word, and doesn't even really translate to anything good in terms of software development. It's my opinion that "depreciated" is a far better word and far better outcome when used in software development instead of "deprecated". YMMV.
Deprecate: "express disapproval of."
Depreciate: "diminish in value over a period of time."
I kind of cringe when other developers say "deprecated".
Edit: Versioning and not removing APIs is kind of the way to go, so you don't break client apps that possibly can't be updated easily or at all. "Depreciated" is a far better word to use with a far better outcome. AWS versions their APIs, they don't remove old ones. "I disapprove of using this API and we're taking it away at some random date" vs "this isn't the latest API, use the current one for new development" seems like a pretty stark difference in thinking to me. YMMV.
So many comments here make it seem like we're dealing with people with a negative IQ.
Just show an appropriate message and let the user run the software. It's GREAT that there is a simple CPU fallback and it's enabled by default.
It's really an edge-case where a user would want to run the code and have it fail if there isn't a GPU - that is mostly an edge case of 1 user, the developer, except in very specialized situations where nobody would want to run it without a GPU, again an edge-case.
Why not just print out a message "Running in CPU mode" or "Running in GPU mode". There's no reason it has to be a mystery.
The comments here tell me that programmers have a narrow idea of what other programmers should/would/could do with their software.
>If you're making a hardware accelerated library, stop trying to make it "gracefully" fail. Just fail! That way people can address the root problem.
No. I want my code to run locally sometimes (possibly with a GPU), and sometimes I run the same code across hundreds of EC2 instances or just 1 instance, and I have good reasons for that. Sometimes a machine doesn't have a GPU, but I still want that code to run on it.
The "bad thing" is imagining you know every possible use of javascript, and then telling other people about how they should be running javascript (or any language).
At least android phones can still download apps from the google app store, older iOS devices are just cut off. I have a perfectly good original iPad that's basically useless. The iPad 4 is similarly useless.
>My last machine was a 10-year old 27-inch iMac that I still use as a server.
My current workstation is 10 years old, running Windows 10 like a champ. It's got one of the first 6-core CPUs in it, a recent graphics card, and 32GB of RAM which I may upgrade to 64GB because it's cheap - I have no real reason to get a new workstation, this thing is still running circles around most recent quad-core systems. Your 10 year old mac wishes it were this capable.
I feel really sorry for anyone buying a mac now, since they will be obsolete as soon as the ARM macs are out.
Apple products are often obsolete in a few years, especially iPads and iPhones. Their entire line of laptops and desktops is now practically obsolete with the move to ARM. Apple products are luxury products for people who can afford to simply throw away a device when Apple decides it's stopping support. I have several Apple devices that still boot up just fine, have capable CPUs inside, but are completely useless because Apple just decided they weren't interested in supporting them anymore.
I later got an A1200, and then an A4000 as well. While the platform updates were great, those weren't what really made the Amiga shine - it was the multitasking OS that the Mac and PC didn't really have - they were nowhere near Amiga OS, which was pretty amazing. Through AREXX any application could control any other application, which is something Windows and OSX still don't really do. I mean to some extent it's sort of possible now, but not as easily as it was with Amiga OS.
If Commodore was still around and had not gone out of business, I'd absolutely be using Amigas today. (yes, I know it sort of still exists, but it isn't really funded or widely used)
[1,2,3,4,5,6,7,8,9,0].sort(()=>Math.random()*2-1)
It didn't pan out? Well Apple buying Intel's modem chip business seems like the opposite of it not panning out, at least for Apple.
https://www.theverge.com/2019/7/25/8909671/apple-intel-5g-sm...
Which ones? Most conspiracy theories are over-thought, under-researched, pure horseshit. Out of the most well-known, "the moon landing was faked" - false, based on no real evidence and a whole lot of denying reality. "The earth is flat" - absolutely false. "5G towers cause COVID" - it's really not difficult to understand how ridiculous this one is. And the conspiracies just keep getting crazier from there...
Sorry, no, "many prove true" is just not workable.