Readit NewsThe world has changed.
While there certainly are some Western hackers who eschew all military applications because of their extreme pacifism, the examples in the article (e.g. pro-Palestinian activists) are not necessarily pacifist. I'd describe them more as out of alignment with their country's current governments, or perhaps actively aligned against them.
And given recent (and not-so-recent) behavior of the US government, I don't think it's irrational for hacker in the US to conclude that their own government presents a greater threat to their freedom than Putin or Xi. (I don't necessarily agree, I just don't think it's an irrational conclusion.)
I've never used a project manager and thought to myself "I want to switch because this is too slow". Even Jira. But I have thought to myself "It's too difficult to build a good workflow with this tool" or "It's too much work to surface good visibility".
This is not a first-person shooter. I don't care if it's 8ms vs 50ms or even 200ms; I want a product that indexes on being really great at visibility.
It's like indexing your buying decision for a minivan on whether it can do the quarter mile at 110MPH @ 12 seconds. Sure, I need enough power and acceleration, but just about any minivan on the market is going to do an acceptable and safe speed and if I'm shopping for a minivan, its 1/4 mile time is very low on the list. It's a minivan; how often am I drag racing in it? The buyer of the minivan has a purpose for buying the minivan (safety, comfort, space, cost, fuel economy, etc.) and trap speed is probably not one of them.
It's a task manager. Repeat that and see how silly it sounds to sweat a few ms interaction speed for a thing you should be touching only a few times a day max. I'm buying the tool that has the best visibility and requires the least amount of interaction from me to get the information I need.
Growing up my folks had an old Winnebago van that took 2+ minutes to hit 60mph which made highway merges a white-knuckle affair, especially uphill. Performance was a criteria they considered when buying their next minivan. Whereas modern minivans all have an acceptable acceleration -- it's still important, it's just no longer one you need to think about.
However, not all modern interfaces provide an acceptable response time, so it's absolutely a valid criteria.
As an example, we switched to a SaaS version of Jira recently and things became about an order of magnitude slower. Performing a search now takes >2000ms, opening a filter dropdown takes ~1500ms, filtering the dropdown contents takes another ~1500ms. The performance makes using it a qualitatively different experience. Whereas people used to make edits live during meetings I've noticed more people just jotting changes down in notebooks or Excel spreadsheets to (hopefully remember to) make the updates after the meeting. Those who do still update it live during meetings often voice frustration or sometimes unintentionally perform an operation twice because there was no feedback that it worked the first time.
Going from ~2000ms to ~200ms per UI operation is an enormous improvement. But past that point there are diminishing returns: from ~200ms to ~20ms is less necessary unless it's a game or drawing tool, and going from 20ms to 2ms is typically overoptimization.
Eight passengers while driving? Where? I don't see any pictures of that.
There’s something to be said for being distinctive, but you can do that while not looking silly (Lucid is a good example). And simply being a small electric truck is enough differentiation anyway
Personally I find the increasingly large bulbous noses tacked on to the front of US trucks ridiculous. The fact that these "codpieces" are empty on EVs is such a wild metaphor that it seems like an intentional parody.
I'll grant that the Telo may have gone a little too far in the other direction given that they have issues with the aerodynamic drag of the front wheelwells, but it still looks slightly more sensible than a normal truck.
Similarly, I can't think of a use case for preferring that processes keep running all night on a closed, unplugged laptop until the battery dies at which point they all halt anyway. But if someone needs this behavior I suppose there could be an option for it.
I'm more surprised that any application can prevent sleep _when you close the lid_.
I can understand the utility behind something like stopping sleep via timeout so a media player can tell the system "hey, they're watching a movie don't turn off even if they don't touch you for a bit".
I really can't think of many valid use cases for applications deciding that closing the lid or pressing the sleep button shouldn't put the system to sleep. Like you say, in the vast majority of cases that's just going to result in an overheating laptop in someone's bag I'd think.
Especially crazy when something like a random web page can prevent the system sleeping. Laptop won't turn off... which of my 70 tabs is it?!
Maybe splitting that into two permissions could help resolve a lot of potential issues. Sure, let lots of things disable the sleep via timeout... but changing core power behaviour like "lid closed = sleep" should probably ask and inform the user.
Absolutely. If my options are 1) halt the process when the lid closes or 2) let the battery die heating up the inside of my bag and then the process halts anyway when the laptop dies then please, please let me choose #1!
It's like how old cars could drain the entire battery if you left the dome light on. Why would they allow that?
The only thing worse than opening my laptop bag to find a hot, dead laptop a couple times a month is the inevitable response of: "Well, you must be doing it wrong, that doesn't happen to me!"
No disagreement, but does the comment meaningfully contribute to the discussion about this particular project?
Seems like a perfectly reasonable dealbreaker to me. Terminal commands are a raw UI that is neither intuitive nor discoverable -- someone must either read documentation (man pages, tutorials, blog posts, etc) to learn the behavior and syntax or they must blindly copy strings from a trusted source.
There's a reason most stories of nontechnical people using software like Linux always seem to include an expert friend, family member, or IT person in the background.