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

When I learnt that Kodak deleted that Xinjiang photo, I stopped buying their products. Fine to not post initially, but publishing then deleting and apologizing shows weak corporate backbone.

Previously discussed on HN: https://news.ycombinator.com/item?id=28024539


Or roughly average, as your username would say. :D


My iPhone, which has one of the most recent chips, is burning hot right now.


Glad to see this comment. Same happened to my iPhone and the website was laggy - was super confused at first..


Scrolling through the site (iPhone 14 Pro) was like playing a modern game at 15 frames per second.


Their license is still ambiguous, and I don't like how they communicate with those who inquire about it.


Better source; the current one doesn't mention phases: https://www.theregister.com/2025/06/13/danish_department_dum...


Your project is source-available, not open-source. Consider adding a license.


No one is against using AI or coding with agents unless you don't understand what it's doing and you're incapable of reviewing the output. The problem isn't the tool, it's "coders" who unthinkingly trust it without verification.


This is why you don't let Claude handle versioning and the release process. From v0.1.0 to v1.0.0 to v2.0.0, and then suddenly 1.2.0? Semantic versioning isn't quantum mechanics. (Even then, I'll admit it's sometimes hard for me too to decide the right increment when tagging versions. :)


> This is why you don't let Claude handle versioning and the release process.

Or anything else without reviewing it.

lol @ the issue in the repo: "module declares its path as: github.com/yourusername/ts-ssh"


In general, maybe security code (which is what this is) might not be the best place for AI.



Semantic versioning isn’t the only way of versioning. Linus Torvalds versions Linux how he sees fit.


- 0.0.1 -> improvements

- 0.1.0 -> breaking changes

- 1.0.0 -> overhaul/refactor needed

I know not every case is easy but this is my rule of thumb. I've honestly never needed a major version change


That kind of goes counter to semantic versioning, where:

- x.y.Z (patch) -> backward compatible bug fixes

- x.Y.z (minor) -> backward compatible new features

- X.y.z (major) -> breaking changes

But of course it's fine to use whatever versioning scheme you like, as long as you communicate it to your consumers.

https://semver.org/

Edit: updated the version strings for clarity.


Minor note, but since the topic is accurate semvar: rule 4 specifies 0.x.y is a special case where anything may change at any time.



Good point, if we're already being pedantic we should be accurate. I've updated the version strings in my comment, thanks!


Using a 3-digit version like semver, while assigning different semantics, is a recipe for confusion if anyone except you ever refers to a package using this "rule of thumb".


0.0.1 - I fixed a bug

0.1.0 - I rearchitected the bug

1.0.0 - The bug is integral to the codebase.


I agree, the initial set of releases were all over the place. I took the feedback from this thread and fed it to Claude along with the semver.org references that were linked here for more detailed (and pedantic) context. Makes way more sense now. Thanks for the feedback! Claude handled the cleanup. Here's the updated releases: https://github.com/derekg/ts-ssh/releases


Also, looking at abandoned blogs and old photos of people lying next to their computers from the early 2000s is so interesting. It captures a time when people truly connected with their machines and made them part of their identity.


Hmm - rather than identity, I suspect it was more of a marketing trope.

I associate this genre of photo with the photo-shoots with Gates, Jobs and others. All the interviews and full page ads in the 80s 90s had variations of sitting/lying on desks, hugging CRT monitors or the classic folded-arms lean on a CRT from behind.

https://i.pinimg.com/originals/dd/97/ed/dd97ed2a239c725ebe57...

https://i.pinimg.com/originals/13/b1/3a/13b13a8c0bc7ee256b37...

https://wolfsheadonline.com/wp-content/uploads/2007/02/Nolan...

https://alchetron.com/cdn/dan-bricklin-6a3581d7-0d8c-4413-91...

I don't recall old-school blogs doing this or really having author photos at all (photos on that bandwidth/hosting?!) but I imagine whenever a blogger was interviewed for print media they would lean on the "computer person" standards.


We have created many innovations to speed up tasks and simplify certain jobs. These improvements are always marketed as ways to create more time for family, leisure, and personal interests. But they didn't actually free up time for these purposes. Instead, the extra time is often filled with even more work.


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

Search: