News for hackers. Stuff that matters.

zachflower

Re:YOLO-World: Real-Time Open-Vocabulary Object Detection on Saturday May 31, 2025 @07:35PM (#44147676)
Funnily enough, that was my computer science capstone project back in 2010!

I don’t know if our project sponsor ever got the company off the ground, but the basic idea was an automated system to scare geese off of golf courses without also activating in the middle of someone’s backswing.

Re:BugMeNot Is Gone on Tuesday November 15, 2022 @05:27PM (#33616008)
Looks like it's just misconfigured. The non-https is still around: http://bugmenot.com
Re:How to build an absurdly backwards-compatible website on Thursday May 05, 2022 @10:16PM (#31280508)
Oooo I like this! I’ll have to steal it.

Thanks for the tip!

Re:Please stop disabling zoom on Thursday May 05, 2022 @01:20PM (#31276095)
Ah, I see. Thanks for clarifying!
Re:Please stop disabling zoom on Thursday May 05, 2022 @12:58PM (#31275817)
I'm so sorry, I'm not 100% sure I understand this comment.

Would you mind explaining what you mean by asking others to adjust for your sake in the context of mobile web accessibility? I'm having trouble connecting it to the content of the article. I'm not the writer, but would love to better understand your point of view here.

Re:Please stop disabling zoom on Thursday May 05, 2022 @11:10AM (#31274364)
Good catch. Fixed!
Re:How to build an absurdly backwards-compatible website on Wednesday May 04, 2022 @10:02PM (#31268500)
This is great, thank you!

I’ve been living in backend-land for so long I’ve never actually used the <picture> tag. I will have to take a stab at it and see how the legacy browsers treat it, because if I don’t have to use GIFs, I won’t.

As for the @media tags, I do utilize them to a degree, just to make everything render nicely on mobile and to support dark-mode. But (to put it cheekily) I’m more concerned with backwards compatibility than forwards compatibility :p

Re:How to build an absurdly backwards-compatible website on Wednesday May 04, 2022 @09:58PM (#31268470)
> Externally linked sources introduce a backward-compatibility problem of their own. E.g, I recall early versions of IE only supporting inline JS. So, if you want to support as much as possible as far back as possible, inlining is the way to go.

That was part of the reason for inlining the CSS. The other part (which I didn’t explain in the post) actually came about because of Mosaic.

Even though it didn’t support CSS, it was aware of link tags and added a button to the top of the window for each one (literally linking to the referenced file). I couldn’t dig up a way to disable that within the code, so I went with the commented-out inline method to get the experience I was looking for.

I'm inclined to agree. Without any evidence or context, these arguments rarely serve any purpose, and are most often driven by strongly-held opinions rather than objective analysis.
Re:Ask HN: Being a technical reviewer? on Tuesday March 21, 2017 @10:57PM (#13928171)
First of all, congrats! Whether you accept it or not, it's always an honor to be recognized.

I did a technical review for a small O'Reilly e-book, so my experience is probably a "lite" version of the process, but it mostly consisted of general fact checking and verifying the completeness of the content. The process was pretty straightforward: they sent me the book, I read it a few times, added relevant comments to the document, and sent it back.

Overall a positive and interesting experience that I would definitely do again.

Older »