gfxgirl

Your painting the right as "no taxes" I think they'd paint as "quit wasting money".

As an example, SF has the highest tax revenue per capita in the USA

https://www.usnews.com/news/cities/slideshows/us-cities-with...

So why is it so dysfunctional? My guess is the right would say because so much is wasted on the wrong things.

Note: I'm not saying the right is correct. I'm only suggesting a different interpretation of their POV.

> This might be excluding anybody that cannot work after hours, for a reason or another.

Maybe I'm reading into this but I see this type of response a lot on HN.

> A: You need experience. Get some after hours

> B: I don't have any time after hours. It's not fair

Like gees! What do you expect?

B: I wanna be guitar player in a rock band

A: Well, if you don't play guitar, take lessons after hours

B: I don't have any time after hours

A: So what do you expect me to do about it? I'm not about to add someone who's never played guitar and can't demonstrate the skills as a guitarist in my band. It's not my problem that you can't play, don't have the time to learn, and yet want to be in my band.

---

Same for any company: So what do you expect me to do about it? I'm not about to add someone who's never programmed games and can't demonstrate the skills as a game programmer in my team. It's not my problem that you can't code games, don't have the time to learn, and yet want to be in my gamedev company.

as others have pointed out, the defualt photos app is designed to do the best for the average user.

If you want control of every feature and no post processing then download a different photo app like https://apps.apple.com/us/app/halide-mark-ii-pro-camera/id88...

This to me is no different than the popular digital cameras vs the pro cameras. The built in app is targeting the masses. it can never make every choice perfectly and further it doesn't need to please everyone. That's the entire point of having apps

It is close to deprecation. In fact it's already deprecated on a device ~50% of American's use (an iPhone). It's also deprecated on MacOS.

Many hardware manufactures are getting rid of it from their drivers and just using 3rd party libraries that emulated it on newer APIs.

Given that OpenGL is basically deprecated at this point this arguably is no longer "modern 3D graphics programming"

If you still want to learn OpenGL there's https://learnopengl.com

was there ever a setting for this? I always used gSwitch or gfxCardStatus to varying degrees of success

No, the problem is bad developers pulling in dependencies for trivial functionally. If there was a `for-loop` npm package bad devs would be pulling it in instead of writing their own for loops. Padding on the left is something if it doesn't exist you write it in a few lines of code yourself. You don't add a package for such trivial functionality.

it's becoming the same in rust. Here's the rust official docs

https://github.com/rust-lang/docs.rs

Follow the build instructions, then you get to `cargo build` you'll see this message

    Downloaded 448 crates (44.1 MB) 

448 crates for a static site generator!?!?!?! WTF!

curl | bash doesn't bother me because I do it like twice a year from sites I trust. On the otherhand, the node crowd uses "npx command" all the time where npx will download and execute code from the net. Unlike "curl | bash", "npx command" is something you're expected to do 10s or 100s of times a day. Each one of those times is a chance for you to have a typo and execute code from some randon source like if you type "npm commmand" or "npx comman" or "npx coomand" or "npx comman dargument", etc...

As is often commen, wikipedia is plain wrong. I've never heard this opening narration and I saw it on opening day

?? I saw it in the theater when it opened. nothing was ruined. maybe there is a second cut I'm unaware of. Certainly the cut Roger Ebert gave 4/4 stars, which is the original theatrical cut, isn't the one with spoilers

I skipped that by choosing lisp as my scripting language. took a day to implement. no complex parser required

for config I used ini files, super simple to parser (and now json so always can use an existing solution)

At the time a single seat of PowerAnimator, the predecessor to Maya, cost $50k-$60k. $30k was for the SGI machine to run it and the other half was the software license.

Microsoft bought Softimage, one of the top competitors to Maya at the time. They charged iirc $4k or $8k and a PC to run it would run $4k-$5k

Softimage is long gone but it's what Valve used for the Source Engine and Half Life 2

It's not doing what I expect. Oh? Change the spec

It's not doing what I expect. Oh? Change the code

How is that different from now?

Not to defend the OP because I agree that null is bad. But, in my limited experiecne with Swift I just add a few characters at the right place and the null's are now incorrectly ignored and the warnings go away. So, the language gave me warning, but it didn't really force me to deal with it correctly. Is Swift a bad example of a null-safe language?

This is the equivalent to "why does modern music suck" (said by every generation of the next generation's music)

Scott Alexander posted something similar

https://astralcodexten.substack.com/p/whither-tartaria

And the response he got was arguably predictable..., others didn't agree that modern architecture is ugly.

Sure there are some ugly buildings. But, for example, for me. I went to some 1929 building that I'm sure this author and Scott would find beautiful

https://www.450sutter.com/

And it is. But it's arguably NOT functional. On the 25th floor the view would be incredible but the windows are tiny and so unless you walk directly up to the window you can't see the view. In pretty much any modern building the view would be front and center, full floor to ceiling, wall to wall windows.

I prefer that modern style. check out an old museum and a modern one. The modern one will have all kinds of amazing affordances. Places decided to highlight the view, places decide to give a sense of space, places designed for eating in unique space.

I'd much rather go to one of these

https://design-milk.com/10-modern-museums-youll-definitely-w...

Than one of these

https://artsandculture.google.com/story/the-oldest-museums-a...

Even if the contents was the same.

> The critics and audience don't always agree.

The Oscars are not decided by critics. They're decided by peers. Directors vote for best Director. Actors vote for best Actor. Composers vote for best Music. Etc...

now if it was just an executable file and didn't require a package manager or compiling to install it would be flawless.

My guess the limits are because, WebP is based on WebM (video)

I agree those limits are too small.

> you’re drawing too often killing battery.

You say this with zero proof. Checking 100s of widgets to see if they overlap, updating their damage boxes, drawing the parts of the ones that got overlapped, computing clip bounds for each one, switching graphics contexts, to do all that adds up to "killing the battery"

Retained APIs are like using a binary tree where an Immediate mode GUI is like using a vector. CS principles say the tree should be faster as insert and delete are in O(1) but in reality, cache misses and similar things kill all the perf you supposedly gained by over engineering the solution.

The same is often true of retained mode GUIs vs immediate, especially with all the transparency effects in modern UIs. Computing the minimal amount of parts can requires a ton more CPU than just drawing.

As far as caching = retained, no. The difference between an Immediate Mode and a retained mode API is if you, the user, have to create and maintain a tree of retained API widgets. No one is going to implement an immediate mode API and try to have a text widget that word wraps and expect it to have to compute all the word wrapping every frame.

Do you have any proof of this or just a gut feeling?

Immediate mode guis do cache stuff, at least Dear ImGUI, one of the most popular Immediate mode guis caches. Further, at least in my mobile usage almost everything I do with my phone re-draws the entire screen. The #1 thing to do is scroll through content. There's very few apps I run where only some tiny thing is getting updated. Maybe my music player.

I don't think it's settled that retained more GUIs are a battery win.

Irrelevant, the apps it's being used for would run fine on a 25yr old machine at 60fps.

You shouldn't need multi-threading to render a few thousand objects and most UI apps of the type Lottie is being used for animate 100 or less at a time.

Note: It's good that Lottie runs faster for its users. My point is only that the entire stack is over engineered and the solutions being used are because the stack is bloated and inefficient

you can always have your car painted or wrapped. No reason the car has to come from the factory in a more interesting style

https://www.google.com/search?q=amazing+car+wraps&source=lnm...

Also, I suspect it won't be long before you can get an LCD wrap or an e-ink wrap. Have already seen backpacks with animated displays.

https://pix.style/

https://cdn.shopify.com/videos/c/vp/d80e3679bac8476b9ee137ce...

This not remotely true. There are plenty of karaoke songs that are the original recording from the original artist. At least in Japan, where the word "karaoke" originates

for me, I can't sing along if it's not close to the original because my brain remembers every tick of the original and wants to match the key of the original as well.

Also, I had a friend who got addicted to Smule which is an online sing duets with random strangers. It uses auto-tune so that anyone can enjoy themselves. I never tried it but he said it was amazing and he got a ton of joy from it.

Me, I like the idea that I can show off my amazing singing skills so if this auto-tunes everyone then that will go away. On the other hand, it's always been frustrating that box style karaoke places rarely have a large selection of western music (most of them are targeting the subset of their local market that would actually to got a box style karaoke place). My hope is that with this more of them will support just using the room as a place to use this service and then my friends and I can sing from a larger variety of songs.

> These issues are inherent limitations of using a main-thread-bound rendering architecture.

sorry but bullshit! Sure, multi-threaded rendering can give faster results but the apps AirBnB is making could have easily rendered at 60hz with single threaded software rendering in flash in 1998!

I can only guess that too much abstraction throughout the systems has turned into death by 1000 cuts and their solution, instead of getting rid of the 1000 cuts is to apply more band-aids

I'm wondering if/how my coding experience could be enhanced with this in my code editor.

AFAIK it was Apple that first added color to fonts in a modern OS. The fonts render in Safari and Firefox. Google is just publishing some fonts.

I thought you were going to say 30 years later. Amiga had color fonts

I agree 100% with much of the sentiment here that creators deserve respect and a cut of the spoils

At the same time, it really depends.... I'm pretty confident that there are very few engineers at FAANG that can't be replaced. I'd also expect there are very few engineers at Epic, Activision, Blizzard, Naughty Dog, Sony, Rockstar, Ubisoft, Valve, etc... that can't be replaced. Sure, if 30%-70% of the team left on any particular project it would probably die, but at least for AAA titles, there's usually no one person responsible for that title's success? Or maybe there is but it's limited to a few key people and not every person on that team.

IF you're at some indie firm with 5-15 people that's probably less true.

I mostly made this comment because in 1983 most games were made by 1 to 3 people max. By the end of the 80s there weren't many games that had more than 20 people on them and usually they took less than a year to make. It was only in the mid 90s that we started getting 30+ people teams trying to fill a CD with data and it arguably wasn't until the 2000s that we had games that it was common to teams of 30-100+ people multiple years to make.