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

And what do windows / linux / macos do about apps getting hacked to billions of pc's simultaneously? How is that a new problem?

If libraries didn't exist could not be created today. People tend to say that "it is impossible" when it actually only needs to be well organized.

Splitting git tech-monopolies it is a survival need. Or we do it, or we will end up with a collapsed society. Entities that spy on all citizens and gatekeep access to news and services are contrary to basic human rights and democracy.


> macos

MacOS has been moving to a more locked down model over the years - increasingly difficult to install unsigned applications, SIP, etc.

> Windows

I think Windows is incredibly impressive for its ability to run binaries from many years ago, but I don't think there's much people would point to as a positive regarding Windows’ approach to app security.


> but I don't think there's much people would point to as a positive regarding Windows’ approach to app security.

Yet life in Windows land is perfectly fine in 2026 and has been for at least 2 decades.

If Windows, which started at the bottom of the barrel security wise can make it, surely we can have more modern OSes that make freedom bearable?


Still, even in the examples given, cars allow you to drive fast, but you can still sue a car manufacturer if they sells cars without airbags and a seatbelt. Doritos can make you fat, but you can still sue Frito Lay if they put overly addictive and harmful chemicals to keep customers coming back. Isn't this the same?


This needs an additional subscriptions service tier, that's even more performative and even more AI


I did NOT know the motion sensors on my phone were THIS precise, that’s surprising


There was a project from 15 years ago where you could put an iPhone on a desk and if someone was typing, you could determine the keys being pressed via the accelerometer in the phone.

The original page seems to have died but you can still find the HN entry here; https://news.ycombinator.com/item?id=3203402


Found the original article on the archive.org

https://web.archive.org/web/20111021122406/https://www.wired...


This is the full "vibe code rabbit hole" I went down, with trying to understand what is possible with the sensors. https://tautme.github.io/phone-sensors/


great idea down this thread, make a guitar tuner that listens with the accelerometer. https://tautme.github.io/phone-sensors/accel-tuner.html


intersting that phones ask for permission to camera and mic, but not always for accelerometer


The motion sensors are also usable to listen to conversations...

2021:

https://csl.illinois.edu/news-and-media/42303



You can spend a lot of time perfecting the test suite to meet your specific requirements and needs, but I think that would take quite a while, and at that point, why not just write the code yourself? I think the most viable approach of today's AI is still to let it code and steer it when it makes a decision you don't like, as it goes along.


Had the same thought, I can suggest JetBrains Datagrip (paid software), works really well for me


I'm a long time user of JetBrains myself. The reason I made Tusk was:

* JetBrains does bloated Java instead of bloated Electron. Tusk is truly native to the OS.

* JetBrains does upsell higher tiers. Tusk does not. Especially won't offer an AI service in the tool that connects to your databases.

* DevTools should not distract the user. VS Code was an OG offender, but JetBrains too has too many notifications.

* Tusk is offline, doesn't connect back to a server for telemetry, updates, Ai, or anything else.


I'm not against using Tusk by any means, native apps can be a lot nicer. I love using Rapid API’s Paw over Postman every day.

But…

> * JetBrains does bloated Java instead of bloated Electron. Tusk is truly native to the OS.

The bloat in JetBrains is negligible comparedy to what it can do and its predecessor eclipse.h

> * JetBrains does upsell higher tiers. Tusk does not. Especially won't offer an AI service in the tool that connects to your databases.

I have never really seen this as an issue except when opening a new project and even then it’s small notifications.

> * Tusk is offline, doesn't connect back to a server for telemetry, updates, Ai, or anything else.

This is probably true but JetBrains is not totally unusable offline.

I wouldn’t completely dismiss JetBrains but everyone has their preferences for whatever suits them better.


> "The bloat in JetBrains is negligible comparedy to what it can do and its predecessor eclipse.h"

Yes. It depends what you compare it with.

> "I have never really seen this as an issue except when opening a new project and even then it’s small notifications."

Tend to agree with you — but I still find it unacceptable to receive notification "ads" for upsells or plugins in a devtool.

I prefer zero-distractions in devtools, and this was the case mostly for a very long time.

> "This is probably true but JetBrains is not totally unusable offline."

Good point.

Not dismissing JetBrains — I was a happy paying customer for over a decade. :)

They're struggling to keep up with a rapidly evolving devtools market.

Thankfully, I / Tusk has no commercial obligations — so I can make it exactly to my liking and taste.


As much as many are against it, couldn't this be yet another argument for social network wide digital identity verification? I think that this is an argument that holds: to avoid AI slop / bots → require government ID


This reply is actually so funny lmao. But yeah, agreed


Personally, I don’t see this move as a negative. It implies that a company believes in its product and potentially wants to improve it. Usually, you can tell when a product is not used by its creator(s), and it’s not a good experience.


I would argue there is a glaring problem with the memo: it is basically written from the perspective of someone who writes memos. Computers were fantastic replacements for many uses of typewriters back then, allowing people to do much more with greater ease. Yet they were not universal replacements for typewriters.

The article pointed out one glaring problem, one that was present with the Apple II (along with other microcomputers of the era): it could only display uppercase text. It got around that by displaying capital letters in inverse. A related problem was the limited display width. While a typed page is roughly 80 characters wide, the Apple II could only display 40 characters per line. Thankfully the Apple II was expandable. 80 column cards and cards that displayed lowercase text were created, but Apple didn't introduce such capabilities themselves until the Apple IIe. Even then you needed to buy their 80 column card (but at least that standardized things).

Another hitch was actually typing lowercase letters. You needed to do a shift-key modification for applications to register the shift-key being pressed when a letter was typed. Again, Apple didn't standardize this until the Apple IIe.

Of course, those weren't the only issues. Computerization may have been taking over the world, but so were reams of paper. While most of those additional reams of paper were being generated by computers, much of that paperwork existed before. Forms, in particular, almost necessitated the use of a typewriter. While I would hate to line up forms in a typewriter, such feats were nearly impossible with printers.

So I guess you're right in some circumstances: computers were not a good experience. That doesn't negate the times when they offered a far better experience. Whether you're writing memos or novels, the ability to go back and edit text outweighs the drawbacks (never mind all of the advancements that were just around the corner). But a blanket ban on typewriters was myopic.


The uppercase/lowercase limitations and 80/40 characters don't necessarily prevent replacing typewriters. They weren’t typing text in BASIC, they were using Apple Writer [0], which did support uppercase letters. This wasn't a WYSIWYG editor, so the text on screen does not have to exactly match the printed output.

[0] https://archive.org/details/apple-writer-a2-v1.1-ph/componen...


While it's true that none of that prevents computers from replacing typewriters, it becomes more difficult to convince people that computers are better than typewriters.

Put another way, I grew up with those 8-bit machines. I preferred using those 8-bit machines for writing since it was easier to edit documents, which was important because I was young and learning to type (along with learning spelling, grammar, etc.). Using a typewriter wouldn't so much be an exercise in frustration as it would be one of mental anguish. On top of that, I wouldn't have the expectation of screen text mapping reasonably well to the printed page.

On the other hand, people who had experience with typewriters (or even 80-column terminals) would have that expectation. And they would be bumping into that mismatch whenever they were dealing with indenting or centering or lists or any number of other layout options. They would also be more accustomed to the writing/editing process with a typewriter, so they would be less inclined to view it as problematic. The flip side is that they would be unaccustomed to the writing/editing process on a computer, so they would be more inclined to view those quirks as problematic. On top of that, the process of using a word processor would be completely different from using a typewriter. Think of over-typing: (fake) bold, underlining, and so on. It is less labor intensive to do on a computer, but the average secretary would have trouble seeing that when they have to navigate the then cryptic user interfaces of software.

Proving that something is possible probably wasn't the issue here. Proving that something is better, which isn't hard to do even considering the primitive word processing software for the Apple II of that era, isn't the issue here. Dealing with the expectations of people is.


Don’t want to sound repetitive, but yes


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

Search: