h3mb3

Previous discussion about the earlier draft: https://news.ycombinator.com/item?id=28088213

I needed to read this a couple of times before understanding what's the issue. Interesting how differently people use their devices.

For me instead, the #1 annoyance with Android 12 is that it doesn't support changing the default camera app anymore. I'm on Pixel 3, where Google Camera is artificially made shitty as the 60 fps option for the video is hidden. As a workaround, I've been running the Camera PX version of the app (from XDA Developers) which let's you change the fps and has other cool customization (while still keeping the best parts of Google Camera). Now this doesn't help as the "double tap the power button" shortcut always opens the subpar stock camera app.

I get that they want to have a generic manifesto here but concrete technologies and other practical examples would still eliminate a lot of confusion.

It's a meme on HN at this point. Lazy negative remarks about JS or other web technologies has high demand in the reader side too I guess.

They usually work where jpg and png images work too, most importantly in most places where you render Markdown. No matter how more efficient a real video file would be, often a short gif right there in the README.md is the perfect way to convey a piece of information.

Pardon my ignorance (I'm not a game developer).

I was surprised to find vertical blanking interval mentioned in the article as CRTs haven't been a common sight for years. Is it still a relevant concept when writing code for modern GPUs?

> Yet magenta exists; you can see it on this color wheel.

Am I supposed to see a color wheel somewhere on the page? Or is this referring to that stock photo with a bunch of pencils?

YouTube's latest brilliant "innovation" to hide the dislike count made this problem so much worse too. When e.g. trying to make a purchase decision, you can't quickly skim through a bunch of search results any longer. Instead you are forced to sit through so much bad content that you could've previously avoided. Maybe that was their real motivation too – to boost some watchtime metrics.

They don't. And videos like this is exactly why they still should. There is no indication to a casual viewer that this might be BS unless they carefully look at the trend in the comments.

I read the message you replied to as sarcasm btw.

For anyone interested, Technology Connections recently released two interesting videos covering B&W film development [1] and photographic printing [2] at home. Iirc he also mentioned Caffenol at some point.

I find this stuff super interesting. I recently got into film photography a little but haven't really considered developing the negatives myself, mainly due to our small apartment. Maybe some day.

[1] https://youtu.be/WpgsITqoDXQ

[2] https://youtu.be/AQC2WsvHdqw

I've been quite happy with MD770 as well! I wish a similiar 75% split board existed with an ortholinear layout though.

Where are all the 75% ortholinear split keyboards? All the super-duper ergo boards have very few keys and/or a strange layout (like this Djinn).

Currently the best keyboard for my left forearm's RSI has been Mistel Barocco MD770 [1] but I've recently been aware how the staggering maybe forces the fingers to travel in slightly unnatural ways. These videos [2][3] from Ben Vallack demonstrate this nicely.

Thus, I'd like to test an ortholinear one, but with all the normal 75%/tenkeyless board keys in place. I personally don't need to optimize the right hand keys as much so I'm not interested in learning an oherwise crazy new layout just to test out if the ortholinearity helps. And, I really like having the split since keeping two halves of the board further apart helps keeping my posture in control. But this combo seems to be difficult to find.

[1] https://www.mistelkeyboard.com/products/d11cf7a73da49468e2a5...

[2] https://youtu.be/Ho_CFfdsmc8

[3] https://youtu.be/1C2bJkzIaPE

A shameless plug of another Finnish/US hybrid: https://github.com/samulisuomi/finsi

The readme also includes comparisons to other common layouts I see Finns using.

It certainly triggers my trypophobia!

Can we at least agree that 40 hours / 5 days a week is an arbitrary amount of work? Not so long ago the norm in many countries was 6 days. So why do you think the current amount is the optimal?

In Finland, the best subtitles were and still are made at YLE (our BBC). That's because they directly employ have their own translators. Everywhere else (other networks, streaming services, home media) the quality has been going down for the last few decades, as all translations are outsourced. The cost has been pushed as low as possible. I've read subtitlers complaining about thight schedules and low pay, forcing you to spend less than a minute on average per sentence.

Netflix nowadays seems a bit better than competition though – maybe not that surprising when thinking about their budget vs some small ad-driven TV channel.

> the keyboard is atrocious.

The keyboards they've been using since the flawed butterfly mechanism are imo quite good to type on (16" 2019 model here, the first one to reintroduce the scissor switches iirc). Sure, not as good as older MacBooks (or ThinkPads, etc), but totally acceptable among the modern laptops.

> Open your macbook and clean out the dust. I do it yearly. It always helps.

I thought you couldn't do this without special skills/tools nowadays (models from the past 4 to 5 years).

Among the QMK keyboards, it's still very tricky to find a tenkeyless/ergo keyboard with mostly a normal layout (with enough keys between the spacebar and the arrow keys to host all 3 Mac modifier keys).

More importantly, I also really haven't yet found a "mechanical" keyswitch (== with a Cherry MX mount) that wouldn't be worse for my RSI than traditional rubber domes (lately I've especially liked the low travel ones, currently Logitech Ergo K860). Sure, it may also be more about the design (or lack of design) in many of these "mechanical" keyboards I've tried that is bad for my specific kind of RSI – it's hard to pin down.

Unfortunately, if you want rubber domes, the options are really scarse. I wish the religious fandom around Cherry MX style switches would decrease in the upcoming years, to give more room for new kinds of keyboard innovations.

My biggest problem is to find keyboards that would have all 3 modifiers on BOTH sides.

I use a Mac for work which means in most (split/ergo/tenkeyless) keyboards (depending on the settings applicable) either Ctrl or Alt/Opt is missing from the right side, because e.g. an Fn key or a squeezed-in left arrow is taking their place. I need all 3 modifiers constantly (Ctrl+C in Terminal, enter special characters, use app shortcuts, jump between windows/tabs...)

In the US, that might be a wise assumption for any individual to make. However, I think you still should push back on these practices as a society. Why should this be legal? What common good comes from this?

What does "agnostic" really mean here? Or, how is something like React not "agnostic"?

How does this compare to Bors NG?

https://github.com/bors-ng/bors-ng

In my experience there are a fair amount of rules in the second category of yours (anti-footguns). For instance, preventing invalid properties alone is a huge one. There are also rules like [1], a few violations of which popped up in our legacy styles. No dev of ours would've caught those.

[1] https://stylelint.io/user-guide/rules/no-descending-specific...

Hmm... I wonder why stylelint wasn't mentioned? [1] I thought it was nowadays kinda the CSS equivalent to ESLint.

We added it (in tandem with Prettier) to a codebase that uses lots of old SCSS. So far it's been a good gatekeeper as the team has been growing, blocking the most questionable .scss edits in PRs. We had to disable and ignore many of the rules to fit it together with our legacy files though.

[1] https://stylelint.io/

I think a good rule of thumb is to never prematurely apply DRY in source code BUT always try to aim for it when it comes to data and configuration unless there's a special need.

> "Choose boring technology" make a lot of sense if you are maximizing profit and don't need to work with the tech yourself.

This view feels so strange to me.

As an engineer, I find myself the happiest when I manage to build the simplest and the most maintainable thing for the business requirements. Extra happy, if it turns out we didn't paint ourselves into a corner when those requirements increase or change.

I just want to minimize my own tears in the future.

> If you are an engineer and you want to try a new technology, go for it. Even if it doesn't make sense.

Imagine how immoral this advice sounded like if it came from the mouth of a carpenter, an auto mechanic or a doctor.

Maybe this just activates my PTSD acquired from working in a startup with a long history of codecampers doing CV-Driven Development.

A PM and an engineer walk into a meeting room to discuss why the feature request cannot be implemented with their microservice architecture:

https://youtu.be/y8OnoxKotPQ

> Something somewhere in the dependencies hadn't been screwed down tightly enough, and everything was broken.

The package-lock.json file and the `npm ci` command should take care of any issues like that nowadays. Yarn has also always had its lock file. I wonder what was the root cause here? Did your repo have some deps coming from some other registry than npmjs.com?

Cases like this suggest that a serious portion of the HN users just upvote posts based on the title without ever opening them. The current title is very misleading.