adambatkin

People who don't enjoy sunburns on their hands put sunscreen on their hands.

My electricity and water is much more reliable than my Internet service. Then again, I've never called my ISP about an issue that wasn't 100% on them, but the HN crowd is more exceptional in that sense than most people.

My car beeps occasionally, but it certainly doesn't rise to the level you describe. Some of them represent real safety issues, even if you don't think they do in that moment. For example, my TPMS has saved alerted me to low tire pressure when I didn't know I had a leak, and the fact that it beeps a couple times every time I start the car is both helpful ("oh right, I need to get that fixed soon") and far from annoying.

Accidentally leaving a kid locked in a car on a hot Summer day is beyond horrific. How many kids should die before we think the annoyance of an extra beep would be worth it?

Put another way: Worse is Better

Prusa. Made in Europe, from quality components (or buy it as a kit from them and build it yourself, which is a really fantastic experience). Hardware is repairable and upgradable and the firmware is open source.

But they cost more than Bambu. Most Chinese things tend to cost less than alternatives, for obvious reasons.

I think as a technical term, pausless (as used here) has a specific meaning, just like real-time has a specific technical meaning (not literally 0 latency since that's generally physically impossible).

That's a great idea. Let's do that.

And until that happens, helping people file their taxes for free is a benefit to everyone (except tax prep companies).

I would be surprised if much of that funding went to constructing those fancy buildings - donors who want their name over the door like to do that. Keeping the lights on, air heated/conditioned, stockrooms stocked, etc don't come cheap. Let's also remember that the government doesn't _just_ get all the research output from that grant money, they get a pipeline of researchers (and undergraduates) that feed industry (plus world class research facilities that can do more research, beyond what the government directly funds). And that's a large part of what has made the US so economically successful, and such a desirable place for people to learn and work.

(Also professors and post docs in many areas can make a lot more in industry, so let's not knock them too much if a university wants to look at least a little attractive to them)

Programming languages are complicated. Their standard libraries are extensive. Real world application are usually not trivial, because they often model real world processes, and the real world is messy.

Anything we can do to make writing software easier and more reliable, and reduce cognitive load, is going to benefit the software developers who are involved, and will make the systems better.

I'm sorry, if you can't jump-to-definition then you are wasting the company's time. It's something that all developers need to do and there's no reason we should be wasting time navigating a codebase when what you are looking for can be found instantly.

Same with autocomplete. I can type very fast, but autocomplete can type faster. Plus with the size of most APIs (even the ones built in to most programming languages) I have better things to spend brain space on. Is it list.empty(), clear(), empty(), truncate() or something else? With autocomplete I can find the function in want in 3 seconds (and read the docs inline, so I can tell that empty() doesn't empty the list, it tells me whether or not the list is empty) without lifting my fingers off my keyboard. Should I remember which is which? Maybe, but I don't care, and a jump between languages frequently enough that it's not worth the effort to keep track of silly things like that That's a contrived example, but hopefully you get the point.

Something that Rust got _really_ right: Editions. And not just that they exist, but that they are specified per module, and you can mix and match modules with different Editions within a bigger project. This lets a language make backwards incompatible changes, and projects can adopt the new features piecemeal.

If such a thing came to C++, there would obviously be limitations around module boundaries, when different modules used a different Edition. But perhaps this could be a way forward that could allow both camps to have their cake and eat it too.

Imagine a world where the main difference between Python 2 and 3 was the frontend syntax parser, and each module could specifically which syntax ("Edition") it used...

I self-host Tiny Tiny RSS (https://tt-rss.org/). I think it will do everything you want (and more). The web UI is fine, and the Android app is great. It's actively developed, has been around for over a decade (I have been using it since Google Reader shut down) and has been super stable.

I guess the only thing it doesn't have that a SaaS offering could do would be some sort of recommendation engine (which I have no interest in).

It's great that it works for you. It doesn't work great for a lot of other people.

The hate is because the "Gnome developers" (and that's an unfair generalization on my part, but let's run with it anyway) have a long history of saying This is the One True Way to do various things, and unlike most other Linux DEs, Gnome has positioned itself as a general-purpose system, and it has the most commercial backing of any other DE. There have even been cases where every other DE wants some Wayland thing one way but Gnome devs want it another way. Gnome developers go so far as to attempt to rationalize why other use cases or desires aren't even valid (which is offensive).

In other words, the hating on Gnome isn't necessarily that Gnome itself is inferior to other systems, it's that some Gnome developers (and many interactions when it comes to standardization and interoperability) are condescending, dismissive, and they insist on imposing their (technical) will on the whole Linux GUI ecosystem.

Can confirm. Had 3 or 4 batteries replaced (under warranty) before the local dealership informed me that "some DCMs cause parasitic battery drain". I brought it in, they ran some sort of test, and ordered me a new DCM (also under warranty). It took a while for the part to arrive, so they pulled the fuse. As other posters have noted, it took out one of the speakers (music sounded only mostly normal) and both the mic and speaker for Bluetooth comms were dead.

Previously, there were times that I would drive 100 miles one day, and I couldn't even open the doors using the automatic locks on the following day. It's been about a month on the new DCM and so far I haven't had any issues, so here's hoping...

I don't believe that S3 Bucket Policies are deprecated. They are powerful, effective, and consistent with almost everything else at AWS (Resource Policy). Perhaps you are thinking of ACLs?

I believe that the concern is that it will infringe on some people's ability to use their computers to interact with some websites (something which is vital to living in our modern society). My computers all run Linux and I use Firefox so this is a personal issue for a lot of people. As someone who is only able to use sites like Netflix on my computer through the continued generosity of a bunch of large corporations (honestly it's really good fortune) this makes me extremely uncomfortable. Especially since the whole point of EME was to prevent privacy and it hasn't done that (100% of Netflix content is trivially available to anyone via a multitude of pirate sites) so...

Debugging and troubleshooting a networking problem is approximately the same on Windows vs Linux (except that there are additional powerful tools available built-in to most Linux distributions). Which is to say that anything non-trivial likely needs a command line. Windows does have some graphical network troubleshooter thing, and I've let it do it's thing a few times, and it has never done anything (at least nothing noticable).

Absolutely. As a paying Google Workspace customer (or whatever it's called this week) I have called support on a number of occasions. Zero times have they been able to help in any way (despite technical issues that they admitted were Google's responsibility), but I had a phone number.

Enforced rotation of passwords on a schedule is no longer recommend, and is advised against. Mandatory immediate expiration/rotation of all credentials that have been (or are suspected to have been) somehow exposed is a requirement of all security protocols. And there is nothing wrong with a user voluntarily rotating their credentials, that does not reduce security (as long as they don't do something silly like use less secure passwords in the interest of making them more memorable).

Exactly. In fact almost everything in the article is icing on-top. The entire experience of the McMaster Carr website is the taxonomy and the fact that the search and navigation _within that taxonomy_ are all built to work seamlessly and get you to exactly what you are looking for.

Search for "bolt" - you won't get 10,000 different bolts with a pretty little filter to whittle down, you'll end up on a page with broader categories of things that may or may not have "bolt" in the name, but are all things that are in some form bolts. From there you keep drilling down, selecting different attributes until you get to an individual product (or a grid of variations, like different lengths).

Honestly, it feels like the original authors have never actually used the site, they just browsed around, thought it was laid out nicely, etc

But I think that's the problem. For some things, the "form" is important, things like marketing sites, maybe prose. But for sites that are supposed to be highly functional, information density (function) should always win out. That's not to say that it shouldn't still be presented nicely, and that may make it more difficult. But when I'm browsing files or commit history on GitHub, the more stuff I can see at one time, the more useful it is.

Take a step back and ask "why do I need to know the length of this thing?" If it's so you know how much storage to allocate, then the process/time is the same for both (the answer is: however many bytes you happen to have). If your array is bigger than the number of valid characters (code points) and you need to search through it to find the "end" (last valid character), you can do that with almost identical complexity (you don't actually need to iterate over ever byte and Code Point with UTF-8 because of how elegantly the encoding was designed).

Why else might you need to know the length? If it's to know how much space to allocate in a GUI (or even on a console) then neither encoding is going to help.

Maybe it's because of some arbitrary limitation like "your name must be less than 50 characters" and I'll just say that if that's the case, you are doing it wrong (if you need to limit it for storage/efficiency purposes, fine, but you will probably be better off limiting by bytes and using UTF-8 since most people will be able to squeeze in more of their names).

I'm not saying there aren't reasons for needing to know the "length" (number of Code Points) of a string, and certainly many existing algorithms are written in a way that they assume that calculating string length and being able index arbitrarily into the middle of a string are fast (O( 1 ) for indexing) but in reality, for almost any real world problem beyond "how much storage do I need" almost everything you need to do actually requires iterating over a string one Code Point at a time (which is O( n ) for both, with the biggest difference being that UTF-8 may require more branching, but also it's common enough that in many cases between vectorization and just generally better optimizations because of it's popularity, UTF-8 will do just fine while usually using less storage, which can significantly benefit CPU cache locality).

And just to make sure your brain always has to concentrate when switching (beyond the fact that you now need two sets of shortcuts instead of one): Cmd+Tab cycles from most-recently-used (what you would expect) but Cmd+~ blindly switches to the next window in a cycle (not what anyone expects or wants).

It is notable that you said "Writing Ruby feels..." but made no mention of _reading_ Ruby. I think I agree with you that I enjoy writing Ruby more, but I definitely enjoy reading Python.

It's definitely easy to write unreadable Python code, just as your can write easily readable Ruby code. But I think that some of the "clever" things that the Ruby language allows (some of the things that make it fun, things that aren't considered obscure or advanced features) tend to make Ruby code more difficult to comprehend.

They have been moving toward a model where there are no more toll booths, no one slows down. If you have EZ Pass, you are scammed and your account billed. If you don't, they take a picture of your license plate and mail you a bill. Much of the NY/NJ area now operates on this model.

Can you clarify what you mean by this? The platform formerly known as Safari Books is now O'Reilly Learning, and I have every reason to believe that it is all above-board, with proper licensing from all of the included publishers.

AWS has just posted the following to their health dashboard:

> 7:21 PM PDT We are aware of intermediate DNS resolution issues for certain specific AWS names. This is due to an issue with third-party DNS provider outside AWS. DNS queries for domains hosted on Route 53 are operating without any issues at this time. We are actively working with the third-party DNS provider to resolve the issue as quickly as possible.

I'm not sure how this is relevant. Either the autopilot is safe to use (regardless of "iteration") or the feature shouldn't exist and should be illegal to use. If some "iteration" of autopilot is incapable of _X_ where _X_ is some safety-critical thing, then you shouldn't be allowed to use autopilot.

The parent asserted that Nazis are evil. While I'm sure there is a range of behaviors that constitute "evil" I don't think a drone assassination campaign in any way compares to the deliberate and systematic attempt to remove all members of certain groups (i.e. Jewish people, among others) from Earth.

And if it is May 29 and you notice an attacker has been lurking in your network for at least 2 weeks (but you don't yet know exactly when it started or how they got in) you will be very happy that you have netflow and access logs going back 30 or 60 days or a year. And that's considered an operational requirement for anyone who cares about the safety and security of their systems and networks.

I don't think the argumentative tone was warranted. No one is suggesting that anyone be forced to use a mouse or that accessibility solely using the keyboard be limited in any way. But there is definitely the appearance of an aversion to the mouse in some a older (and things that want to seem old-school) Unix/Linux tools.

For _some_ people, the mouse is easier to use, so increases accessibility for _them_. I think the OP was implying that better mouse accessibility could be added on-top of the existing keyboard support.