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

Too much growth!

(Or too many people going back to Twitter.)


This makes a lot of sense. We've seen how quickly and randomly Claude Code can sour on you (if it's even up). Nobody who uses this for work wants to be reliant on that.

A lot of blood in the water for Github.

> to browser-based alternatives

And many of those tool providers could see for 10-20 years now that if they didn't provide a web based version sometime soon, they would go out of business sooner or later.

There are almost no applications that a government employee should be running natively on their machine anyway.


A bigger blocker I see in Belgium is all the corporate and government software written in Java or .NET-with-Angular and that has to be deployed via Azure because… compliance.

Except for any application you want a government employee to use efficiently

Are web apps much less efficient to use?

Yes, slower start, more memory/cpu use, likely worse UI as the transition broke desktop conventions and/or just lost some power features in the process

Eh. I suppose to each their own, but my experience as a user and developer is… that it depends on a lot of factors.

Many web apps open faster than many apps I have installed. Some of these apps have a faster mobile web app version.

And then, of course, there’s Apple’s increasingly bad choices in interaction and interface design. Some web apps are superior because they stick to simpler or more appealing design.

Linear comes to mind, their iOS app post-Liquid Glass is unappealing. Their macOS version is effectively a web app, and a very good one at that. Things is native and wonderful. Apple’s own apps can be both slow and ugly (hi App Store!).


The main reason I use Aerospace (after a thorough testing of most macOS third party window managers) is for the space management and instant space switching.

This test is good and also I'm not sure it's meant to be funny, but it is very funny.

> developers write commit messages

The people who don't write commit messages for us are the non developers.

Writing commit messages shouldn't take any time at all. If it does, then you probably have a range of other professional issues.


Nix does not really work in that even basic things are absurdly complicated and can take days of messing with poor libraries and documentation.

That's not been my experience with jj which after the initial hurdle is a breeze.


Pretty much everybody who does work at the real office where I am has a mechanical keyboard by now.

How do you get good like this?

Just keep doing stuff and gaining experience. Sometimes you'll find that you don't know how to do something, at that point don't just reach for an LLM, do your best to try and understand it, google around, and if all else fails, put it down and maybe come back to it later with fresh eyes

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

Search: