Okay, the article I read on HN yesterday about the ram shortage crippling inexpensive devices feels relevant here. As far as I can tell, the article treats the low memory capacity as a foolish business decision rather than perhaps a required economic decision.
Like, I didn't see a single mention of why they chose 8GB while recommending 16GB. It's like a straw man argument: why not at least explore possible causes?
In case you didn't already know or haven't considered it, you can find right-angle usb-c MagSafe adaptors that basically allow the charging cable to disconnect from the device like MagSafe.
So, hold on--the author's soul-breaking complaint isn't all of the "quirks" and inconsistencies with the Date functions, but rather the fact that it's an object? Specifically, an object with mutable properties in a language when all objects have mutable properties?
I mean, the author's conclusion is correct. But I disagree with the rationale. It's like hating an evil dictatorship because they use the wrong font in their propaganda.
Here's my brilliant idea: the longer it takes for an answer to be marked correct, or the more answers there are before one is marked correct, the more points that answer deserves.
Surely you're being hyperbolic. I've seen some atrocious UX before. Maybe what you mean is it's a good idea but the scrolling part should be list-based instead of page-based.
It's not that the product you're building is a commodity. It's that the tools you're using to built it are. Why not build a landing page using HTML and CSS and tailwind? Why not use swift to make an app? Why not write an AWS lambda using JavaScript?
This reads like "Hey, we're not vibe coding, but when we do, we're careful!" with hints of "AI coding changes the costs associated with writing code, designing features, and refactoring" sprinkles in to stand out.
When they say their battery storage capacity is 15,000 MW, do they mean MWh? Because watts are time-independent, or rather, they're like speed to Joule's (watt-hour's) distance.
I don't understand. I run a Plex instance on my home server as well. Are you referring to jellyfin not needing a centralized Plex account? Or do most Plex users rely on a plex-provided server?
What the author is missing is the metric that matters more than shipping product: how much happier am I when my AI auto complete saves me typing and figures out what I'm trying to articulate for me. If devs using copilot are happier--and I am, at least--then that's value right there.
Like, I didn't see a single mention of why they chose 8GB while recommending 16GB. It's like a straw man argument: why not at least explore possible causes?