rollcat

Agree. My 2017 MBP cooked its own battery (spicy pillow) by 2021.

My 2019 Thinkpad T495 (Ryzen 3600) does get hot under load, but it's still fine to type on.

I really like the principles behind AMD's chiplet design, of course they've had different design goals behind it (easier diversification of their product portfolio), but it remains a fact that you can slap a not-so-terrible GPU right next to a CPU core.

There's probably a lot still missing: Apple integrated the memory on the same die, and built Metal for software to directly take advantage of that design. That's the competitive advantage of vertical integration.

> It's a fairly common issue on Linux to be missing hardware acceleration, especially for video decoding. I've had to enable gpu video decoding on my fw16 and haven't noticed the fans on youtube.

I've worked in video delivery for quite a while.

If I were to write the law, decision-makers wilfully forcing software video decoding where hardware is available would be made to sit on these CPUs with their bare buttocks. If that sounds inhumane, then yes, this is the harm they're bringing upon their users, and maybe it's time to stop turning the other cheek.

A language model will create the market force to displace an oligopoly in the most influential sector of our society?

Hedge your bets.

> [...] someone with serious name recognition like Linus Torvalds starts to lead that kind of effort [...]

Linus is a kernel hacker, and already busy tending to his own project.

"GNU/Linux" is effectively a committee of communities, with sometimes conflicting goals. It took Canonical and Valve to put things into shape on the desktop, and that's mostly because desktop was becoming less relevant.

I see two ways for things to change here:

- A massive, for-profit corporation, someone willing and able to challenge Google and Apple on an even ground, is hell-bent on making a Linux-based phone (Microsoft failed even after acquiring Nokia);

- Another platform shift happens, making smartphones irrelevant in comparison (think: when smartphones displaced desktops).

> Maybe it's time for a third large phone OS [...].

Apple and Google conspired to never allow that to happen. They've pushed Microsoft out of that sector. Microsoft! Name a bigger challenger.

Apple is quite happy to patch & extend stuff. Their ssh-add(1) accepts --apple-use-keychain, --apple-load-keychain; vanilla OpenSSH doesn't even know what long flags are.

I think it's entirely OK for long-established programs to adhere to their conventions; it's less surprising for the users. If you're going to change how things work, do so with minimum impact on the UI.

(I wish their GUI teams understood that.)

> [...] Linus has not bothered to write them down himself [...]

He's a kernel hacker and a technical leader. He doesn't write specs for the userspace, that's the least of his concerns. Linux has very strong guarantees on syscall backwards compat - Go doesn't even use libc. This is all by design.

Even the name "GNU/Linux" was something FSF tried to impose on distributions. The distributions being distributions, were free to brand themselves as they willed, which is 100% fair under the license terms.

This ecosystem has always been a bazaar, if that's not for you - use a BSD. (e.g. macOS.)

Japan is Japan, most of their history can be summarised as isolationism/NIH.

Software developers are also not seen as "real" engineers there. They're just typing words into a computer, right?

That is my entire point. The creators fight each other in a pit, for the Emperor's amusement.

I don't mind the ads as much as all the mandatory meta-baiting. Not the MB itself, but the mechanisms behind it.

Even if you produce interesting videos, you still must MB to get the likes, to stay relevant to the algorithm, to capture a bigger share of the limited resource that is human attention.

The creators are fighting each other for land, our eyeballs are the crops, meanwhile the landlord takes most of the profits.

Engineering is making sure stuff works first, art distant second.

Even if the text is a simple article, a personal touch / style will go a long way to make it more pleasant to read.

LLMs are just making everything equally average, minus their own imperfections. Moving forward, they will in-breed while everything becomes progressively worse.

That's death to our culture.

You now need an LLM to go thru write calls?

I wonder how much money have these three companies made from FOSS in the last quarter alone. I guess they don't know either, it's easy to take all of that work for granted.

The way to handle a password:

    plaintextPassword = POST["password"]
    ok = bcryptCompare(hashedPassword, plaintextPassword)
    // (now throw away POST and plaintextPassword)
    if (ok) { ... }

Bonus points: on user lookup, when no user is found, fetch a dummy hashedPassword, compare, and ignore the result. This will partially mitigate username enumeration via timing attacks.

> I only pay $1 per month for my VPS, and even that piece of trash can handle 1000s of requests per second.

Depends on the computational cost per request. If you're serving static content from memory, 10k/s sounds easy. If you constantly have to calculate diffs across ranges of commits, I imagine a couple dozen can bring your box down.

Also: who's your webhost? $1/m sounds like a steal.

I think at this point every self-hosted forge should block diffs from anonymous users.

Also: Anubis and go-away, but also: some people are on old browsers or underpowered computers.

> Sometimes I find an odd password being probed, search for it on the web and find an interesting story [...].

Yeah, this is beyond irresponsible. You know the moment you're pwned, __you__ become the new interesting story?

For everyone else, use a password manager to pick a random password for everything.

Shoulder surfing is exactly the risk factor that biometrics are meant to mitigate.

Every time you type your PIN - that's an opportunity to snoop it.

Neither will protect you against rubber hose cryptography.

Wherever you're working with colors and text/emblems, please also consider contrast and legibility: <https://apcacontrast.com/>

That's one reason to prefer Oklab ;)

> I can’t use ctrl+C in the terminal for Copy because that’s reserved for the interrupt signal.

It's not reserved - the terminal emulator is free to handle any key, in any way, however it wants. Some examples:

1. The XFCE terminal allows you to specify whether Alt+[X] means Meta-[X], or whether it should trigger a menu shortcut.

2. macOS's Terminal.app: use System Settings to rebind Copy to Ctrl-C - when some text is selected, it copies that text; when there is no selection, it passes the ^C along.

Unfortunately, few people question the status quo of terminal emulator design. Look at all the other emulators around you: quick save/load, customisable hotkeys (including gamepads), speed up/slow down, mute specific audio channels, enable/disable sprite/layer rendering, peek/poke memory, and so on. An average GBA or SNES emulator gives you better tools than most terminal emulators, and the latter are what is actually being used to get work done.

That's a bit unfair to the modern compilers - there's a lot more standards to adhere to, more (micro)architectures, frontends need to plug into IRs into optimisers into codegen, etc. Some of it is self-inflicted: do you need yet-another 0.01% optimisation? At the cost of maintainability, or even correctness? (Hello, UB.) But most of it is just computers evolving.

But those are not rules. If you're doing stuff for fun, check out QBE <https://c9x.me/compile/> or Plan 9 C <https://plan9.io/sys/doc/comp.html> (which Go was derived from!)

I really wish we could make uniformity a trend again. GTK has basically made it a rule that applications must do whatever the heck they want.

Then next day I'm using Inkscape on a Mac. Cmd-A on the canvas selects all elements. Cmd-A in a text field selects all elements on the canvas - and whatever text was in the field, now applies to the selection, so I start typing and instantly get garbage.

How do you Select All in a text field? Ctrl-A of course! - On the only system that has a non-broken copy/paste in the terminal.

I guess props to Thunderbird for leaving some space on the title bar to drag the window around? Do not take it for granted.

> considering the system reboots in 1.2 s

That's not the point - it's about usability. You'd be constantly losing work.

> Just killing off a hanging process that doesnt yield [...]

<3 !

Gold coins were replaced by paper money. Paper money was replaced by credit cards. Now credit cards are being replaced by smartphone wallets. My phone or watch can still pay for stuff while they're offline. For the past 5 years, I didn't carry a physical wallet. I'm doing more with less, and failing safe.

If the lock freaks out - and yeah, I'm having problems with my HomeKit stuff every now and then - I need the physical key on me. That already defeats the purpose. Otherwise I need to grab the spare key from wherever I keep it. This is not a mere inconvenience, this is an emergency procedure.

The OS looks highly opinionated and I respect that. Better to have a single overarching vision than try to do too many things poorly.

However I will question some design choices!

- 32-bit only: the writing is on the wall, many vendors (HW&SW) are slowly moving to kill it off. I guess it's fine, but IMHO each ISA (regardless of pointer width) should just be considered a different ISA. Portability is good, it ensures your software doesn't hardcode too many assumptions about the platform - and weeds out bugs. Just treat an int like an int, and a pointer like a pointer. Distinct types.

- Pure co-op multitasking: it will be completely fine, until you try serious in-system development. Hard reboot any time I make a mistake in a for-loop? Mercy, please :,) Implementing a simple watchdog via a timer interrupt will still keep all of the scheduling logic simple and stupid: it's just another case for a yield call, except now involuntary. The runaway process will simply never see completion, but seeing that it would never yield anyway, I don't see a problem just killing it. And most importantly, the sanity shall be preserved.

Nothing better than being able to rely on your partner, but really - do reach out. We're all friendly folks, ready to help each other.

It looks like it could be future-compatible with a possible Euro Rack refit? Nothing cooler than DIYing a DSP for your DIY modsynth!

Heightwise, it fits: 100mm vs ER's ~128mm; trickier with depth - 180mm vs "deep" ER modules ~100mm. One option would be a rack with no back panel. Power in ER is already being distributed via a ribbon cable so this shouldn't impact the ability to install standard modules. Electrically - 12V, perfect match.

What is the width of each module? Assuming (250mm-case)/8 ~= 30-32mm?

Since we're having an impromptu ADHD club forming in this thread - I totally feel you. I've had too many ideas like this one, even some prototypes over the years.

There are many tricks to stay focused, particularly when there are no stakeholders but you. Try a body double, someone to keep you in check - you can also return the favor, like working from the same room, or just coming to their home to watch them clean while you do your stuff.

When you do get hyperfixated on something - that can be a very productive period, until you crash. Again, bring in a friend. Not to get back to it - just to make sure you're still eating. Don't push yourself to either side, find your own balance around it - I've picked up many hobbies where I've slowed down, but maintained interest over the years, decades.

Look for buddies in your local neurodivergent group, there's usually one somewhere near you. (Even here on HN, it turns out.)