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

A very quick search yielded Dell selling 1080p laptops today:

https://www.dell.com/en-us/shop/dell-laptops/dell-15-laptop/...

It is very, very common. Just not in the Mac world.


It's also the corporate standard for generic cubicle workstation monitors, though it's unusual to find a Mac in such a place anyway.

It’s very common for the people who got their last monitor 8 years ago.

It's still the most common resolution for people using desktop monitors today, according to: https://gs.statcounter.com/screen-resolution-stats/desktop/w...

Also for gaming too: https://store.steampowered.com/hwsurvey/

1920 x 1080 51.89%

2560 x 1440 21.20%

3840 x 2160 5.00%


OS font rendering doesn't matter for gaming.

One of the genius things about Swift is its interop with Objective C. Made the switch over considerably easier for developers. I’m not sure what that looks like in a Rust world.

Rust is also just a more complex language. I’m not convinced the benefits would have been worth it.


Not just interoperability with Objective C but with C (full) and C++ (increasingly better but not full) as well.

Swift is also interoperable with different versions of itself courtesy of the Swift stable ABI (Application Binary Interface)[0], which they invested a significant amount of time into at the expense of adding other new features to the language, which have come along later.

Rust offers a different approach: recompile everything and static linking.

[0] https://faultlore.com/blah/swift-abi/


C compatibility comes via Objective-C, because contrary to C++, Objective-C extends C, instead of being based on a C subset.

You missed Java as well.


Short answer is I don’t and it adversely affects my job satisfaction.

I’m quite sure I’ve left money on the table over the years as a result of my reluctance to manage and mentor junior developers. Disappointing that I’ve ended up managing junior AI developers who won’t even grow as a result of the time I’m putting into them.


Oh they'll grow, but mostly to the benefit of someone else.

It’ll happen eventually, it’s an economic certainty. And when it finally does it probably won’t be that bad for the American consumer buying a car.

The real loss is the international trade and the effect that’ll have on the overall economy. Mexico and Canada will already be dominated by Chinese cars and it’ll be too late to compete.


It's still present. JSON/JS parsing still has a delay. And in either case (as the author states) not everyone is using an iPhone over 5G. Heavy React apps are a miserable experience on low end Android phones, even when the connection is fast. I've seen JS/JSON parsing times in the multiple seconds.

There's 5 bars 5G and there's one bar 5G anyway... Citing connection types really is completely beside the point.

My old iPhone handles well react apps, but frequently freeze/crash on heavy advertised pages and pages with huge images/auto loading videos.

Eh, it was pretty terrible before the acquisition too...

It's way less shitty now. Though one could kill a couple beers just complaining about how many major node versions it took before it wasn't shitty.

Not really, no. Astro requires you to opt a component in to client-side rendering, React (with its server components etc) require you to opt out. Defaults matter in scenarios like this and I'd bet the average developer of crappy websites would have a much faster site with Astro than React for that reason alone.

Small correction: it's other frameworks that require you to opt-out, most notably Next.js. Although I've been seeing so many people confusing Next.js with React lately...

Astro itself works just fine with React, and it can still be HTML-only.

But you can also render React on the server yourself using renderToString, if you don't want a framework.


I think the author is suggesting that Remix was the inspiration for the renaissance, not that it's necessarily the most popular method for doing so.

I'd be curious to see the stats on how often Next.js users lean into the server component model that makes the frontend fast. My anecdotal experience is that it's an afterthought for many. By comparison, Astro (as mentioned by the author) makes you think about this stuff upfront via opt-in rather than opt-out. It's a wonderful framework.


Opt-in = action is required to opt in = off by default.

Most hackathons have been this way for a long time. I recall spending a weekend working out some really thorny data classification problem but got nowhere, all the winners had slick presentation slides and a 30 second code demo of a glorified CRUD app.

> A bad design with a good presentation is doomed eventually. A good design with a bad presentation is doomed immediately. - Akin's 20th law of spacecraft design

I always really enjoyed making a slick presentation. It was a lot of fun figuring out how to scope the hardest problem you are sure you can finish in 24hr while still having time to polish your presentation and make the app look good. I find picking a problem that lets you put a big map on the screen helps with the latter.


I get that… but that’s basically a startup pitching competition. It’s not a hackathon.

Aren't most hackathons pseudo-startup pitching competitions? At the very least, they've always been about established companies trying to extract value from newcomers.

To a large degree, this is how the real world works too.

Absolutely. Which is why the hackathon was conceived: to serve as an escape from the real world.

All good things must come to an end, I suppose.


When I first read about the hackathon concept, it was a bunch of OpenBSD developers getting together to work on stuff like cryptography or drivers. I think it was from Facebook where I first heard it as some bullshit corporate event. The idea of a "winner" seems to misunderstand what should be a goal. It's not a competition. It's collaboration.

I’ve always heard of hackathons as being a competition with judges and a winner.

Sounds like you only know the corporate or post-commercialized version, and not the original concept. The entire point of my comment.

And it drives the mini-MENSAs of the world insane.

> For OpenAI GPT-5.4 and GPT-5.5, classifier-flagged traffic will be retained for up to 30 days for automated offline abuse detection.

https://docs.aws.amazon.com/bedrock/latest/userguide/abuse-d...


It is only abuse flagged data and there too for OpenAI they're not sharing that data with them. But for Anthropic they are.

That's different though. Anthropic want everything for 30 days, not just flagged prompts/interactions.

Why can't they flag everything?

Thank you! I missed this part in all the announcements

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

Search: