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

But you don't have to add a docstring. Cases like this are worse than no docstring at all, because it wastes the reader's time.

If you add one, at least make the effort to provide some useful information. For example which is more severe: higher or lower numbers.


I disagree - you should have docstring and I don't think this is worse by having it... its just not ideal

Boilerplate docstrings are lint that spreads, and stale ones are worse, I've seen sevreity fields documented less clearly than the code they annotate.

I don't know much about CPU internals, but this sounds like bullshit to me. A NOP is still an instruction that uses a cycle - why should that cool the CPU down? The CPU frequency should get reduced to lower the power consumption and hence the temperature.

Not all cycles cost the same amount of power. (Not that you would want to spam nops for thermal management, you should idle the core with a pause etc that actually tells the processor what you are trying to do.)

It used to be the case with intel macs and their atrocious confluence of cooling system, thermals, and power supply system (the CPU actually was not really to blame).

But when RAPL and similar tools to throttle CPU are used, the CPU time gets reported as kernel_task - on linux it would show similarly as one of the kernel threads.


This is not a US thing, this is a bureaucracy thing. You can enjoy that worldwide (at least in every "civilized" country).

I can confirm this from France.

Everybody is formed by their experiences and genes and they act accordingly. There is no free will. If you realize that, you realize that you can never blame anyone for anything, because they had no choice to act differently. As a customer it's still hard to take, when someone who is clearly formed by years of professional deformation, treats you like shit.

    never blame anyone for anything
That's actually not quite true.

Assigning blame, via agency or otherwise, and the associated social or legal consequences are additional signals in the environment that influence and change behavior.

If the actions of an individual were involved in propagating some chain of events, then it's perfectly valid to respond to their involvement, via social stigma, punishment, etc, regardless of whether or not there is "agency". The knowledge and anticipation of a similar response changes future actor's behavior, with or without free will.

This discussion itself is exactly an example of this in practice. If there's no such thing as agency, then us talking about what someone should or shouldn't do, given whether there is free will, have any influence on anything, except that it does because interacting with these ideas themselves change behavior, with or without free will.

This is what people mean when they say we should just ignore the question of free will entirely, because it doesn't really factor into how we should design the social contract.


I agree with you, except for the blame part.

Of course people act accordingly to the system they're in. If they expect punishment for an action, or not, changes their behaviour. By defining what's punishable, we can change the course of action. But if you look at any action which already happened, you can't blame anyone for it, because it had to happen that way, given the circumstances.


That already happened is key to your idea and I think you'd have got a better response if you included it initially. It's actually quite a worthwhile concept. Blame can't change the past. The important reason we blame is to help our mind cope with the loss we suffered. But if you can succeed in coping by thinking the past is immutable, that's even better.

This. There's something about most cultures that I am slowly am realizing; we always know how to complain and shift the responsibility. And no, you're not immune to this. You're not immune to anything, really.

Medical departments aren't about helping you out anymore. When you work in a hospital, you do what your rule book says. If someone doesn't have their paperwork available, you cannot help them. That's your boss's fault, not yours. This makes it easy for you to not feel guilty, since your job is to follow da rulez.

How did we get here? Why can you not just give them their pills and charge them the real amount. Why do we need this bureaucratic hell and pretend we're here to help people. We're not. We're here to squeeze you until we cannot legally ask for more.


> Why can you not just give them their pills and charge them the real amount. Why do we need this bureaucratic hell and pretend we're here to help people

I can get my drugs from people like this but you can’t because you prefer this system. Having chosen a system with heavy import controls and an overbearing government regulatory agency, all of which you are likely a huge fan of, there’s not much point to being upset that it yields high prices through an opaque system. The thing you want creates the thing you don’t want.

One might as well rage at getting wet when you stand under the shower and turn it on.


We could have great public systems, but their is a fundamental problem that perpetually keeps these systems unstable:

The people who pay the most for these systems use them the least, and the people who pay the least for them use them the most.

At best you can have a system where the people paying for it are respected for their contribution (and likewise feel good about it), and the people using it are ever grateful for what their receive (and can shamelessly feel good about it).

But man, have you ever dealt with average humans?


> Why can you not just give them their pills and charge them the real amount.

You can, you would just end up without income at best, or charged with a crime and imprisoned at worst.

Also, all these complexities in healthcare exist due to 90% not being able to afford it, so the complexities are to paper over politically unpopular subsidies from various groups of people to other groups of people, in varying amounts. The other part of it is the nebulous costs of liability, that potentially reach into the millions for each interaction.


If you think there’s no free will then you won’t argue with me when I say I think there is.

But they will argue with you, for it was predestined.

Unless you have an Out of Body Experience and who the hell knows if physics continues to be at all having an effect in that realm and thus perform Free Will is a possibility.

i don't believe that to be the case at all

but, of course, i don't have any choice in the matter, so what's the point of talking about it?

but, of course, we don't have any choice in that matter either, do we?


I don't need blame to hunt an animal for food or slam someone who's biting me.

I don't need blame to swat a mosquito that's trying to live, to remove a cobra from my living room, or to quibble about fine print with someone in such an annoying way that I eventually get what I want.


right

> just need something that can compile cross-platform and maintain great performance.

I think Go has already taken that part of the cake.


Go is garbage collected, though. Rust and Swift still occupy a niche Go doesn't.

ARC is a form of garbage collection. Swift does not fare better than Go usually.

Set $WORDCHARS accordingly. In your case, remove / from $WORDCHARS.

https://unix.stackexchange.com/a/726014


For the bash people

  stty werase undef
  bind '"\C-w": backward-kill-word'

source: https://superuser.com/questions/212446/binding-backward-kill...

You probably know this, but shooting in color and then converting to b/w afterwards gives you more artistic options than letting the camera do the b/w conversion.

Yes this is my workflow when shooting digitally. Always in RAW & color for greater flexibility during B/W conversion.

I think b/w film has a different grain than color. It isn't identical to grayscale color

Then at least let the company that makes your niche software know that you want a Linux version of it, even if you don't use Linux (yet). We need to solve this chicken / egg problem. Nobody wants to use Windows, they want to use some specific application. If most software is available on Linux too, then consumers can actually choose their OS.

Most software is already available on Linux. I've successfully run Linux in corporate jobs where everything runs on the MS/AD/Azure stack. The issue is not that you can't do it, the issue is that you have to spend extra work at every corner to get things running, because unlike Windows Linux doesn't take your hand and hide all the nasty bits from you, while it tries to juggle a million cases in the background. Windows is really great at that - until it breaks. Then you're usually screwed. Like, if the problem is close to the kernel, you can't even fix it theoretically. Best you can do is wait for an official MS patch. On Linux things break more often, but you can usually fix them without having to resort to extreme measures. It's a fundamentally different usage philosophy that plays very hard into the strengths of techies. So non-technical users will always shy away from Linux.

> the issue is not that you can't do it, the issue is that you have to spend extra work at every corner to get things running, because unlike Windows Linux doesn't take your hand and hide all the nasty bits from you, while it tries to juggle a million cases in the background.

You may have to spend extra work to get things running; but once it's done, it runs forever without a hitch.

I know, I use Slackware. It's regarded as a very technical distribution and some manual configuration is expected but once it's done, it's done. I have configs from > 20 years ago that I still use without a hiccup.


>but once it's done, it runs forever without a hitch.

Yeah... no. If you're dealing with changing systems, you'll need continued support from maintainers. And there's a lot of stuff out there in the business world that is commonly used and breaks all the time. Stuff will break. If not, it is not getting updated. In that case I'd be more worried about security than compatibility.


Yeah... yes. There are systems which are continuously maintained but don't break all the time. Yes, stuff will break but this is way less common in Linux.

Claws-mail has all my email for over 15 years. My inbox is several gigabytes in size, which claws handles flawlessly. And the software is continuously maintained. I'm using version 4.4.0 now, which was released 16 days ago on March 9.

So... yes.


Turns out email clients are quite simple (mostly because the protocol is ancient) and also something everyone in every company uses. But many OSS clients still die eventually. And once you get into the actual business application world, you're in for a world of pain on Linux. Especially if you go near AD/Azure/Entra. Heck, the fact there is not even a stable name for this mess of a software suite tells you enough. And yet every big company relies on it.

I don't know what are these nasty bits windows is supposedly hiding, or what exactly breaks more often on Linux. For me it's exact opposite: my linux just never breaks. I don't do anything special, just plug in the hdd into new box bought when old gets too slow for new tasks, continue as nothing happened.

Uptimes of half a year are not uncommon, the record so far is 400+ days. I just don't shut it down unless there's a serious kernel or hardware upgrade.

It just works, non-kernel updates, stuff being plugged/unplugged, couple times I swapped sata hdds without turning off power (which is simple, they are hotplug by design, just don't drop the screws onto motherboard and don't forget to unmount+detach first).

Now, when I used to and test some cross-builds for windows (win7-win10 era), I had another dedicated windows machine for that. And even though I tried to make it as stable as possible, it was a brittle piece of junk, in comparison.

So in my experience, yes, linux is fundamentally different usage philosophy: you don't need to think about what crap Microsoft will break your workflow with next Tuesday.


> Then at least let the company that makes your niche software know that you want a Linux version of it, even if you don't use Linux (yet). We need to solve this chicken / egg problem.

To solve the chicken/egg problem, the GNU/Linux distributions should generate some very (in particular binary) stable interface for writing applications (including GUI applications) on GNU/Linux - like WinAPI on Windows. With "stable" I mean "stable for at least 20-25 years". This interface must, of course, work on all widespread GNU/Linux distributions.


Even if we don't agree on a userspace ABI, this is still fine-ish, as long as you can statically link everything you need. Unfortunately the nerds maintaining the core libraries REALLY don't want you to do that, and the answer to "how do I build a portable Linux GUI program" goes more or less like:

"Build musl libc statically, set up a toolchain to use it, build libc++ for that toolchain, get libwayland, link that statically (which their build scripts don't support, roll your own), get xcb,libxau,libxwhatever and build those statically as well, and implement TWO platform layers, dynamically checking for wayland support. There's like 5 different ways to set your window icon. Yes, you need to implement all of them. Now for loading the graphics API......."

On Windows it's a call to RegisterClassW followed by CreateWindowW.


It's an old joke, but it's also accurate in this case - isn't what you are asking for just WINE?

> isn't what you are asking for just WINE

An operating system is a style of thinking about your work. WINE is a way to get Windows applications to run (by now run decently) under GNU/Linux. These Windows applications are nevertheless foreign bodies in the whole kind of thinking which GNU/Linux is built around.


The joke is that the most stable Linux API for applications is ... WIN32 via WINE.

It's sad because it's true.


I think that eventually, Win32/WoW64 will be the stable common API for Linux programs - or at least games. I won't be surprised if it outlasts Windows.

I don't want windows or linux, I want a OS where I don't notice that it's there. When I have to think about my OS, then the OS has a flaw. And currently nor Windows or Linux can deliver that anymore. Windows 7 after some customizations and Windows XP had this, but M$ destroyed it. Linux never had this and I don't expect that this will come in the future.

> I want a OS where I don't notice that it's there.

I guess you want a Mac. That's fine.

I value freedom and things not mysteriously breaking and functionality not disappearing, and am quite happy investing a the time and knowledge upfront, so I use Linux.

And then there are people who want to have a system which works out of the box initially and who don't want to learn anything and don't mind it breaking later, and they choose Windows.

To each their own.


> I guess you want a Mac. That's fine.

Have you seen liquid glass? "Don't notice it's there" does not at all apply to the latest UI changes. Everything is bouncing and jumping and sliding in ways that deliberately call attention to itself. MacOS does not stay out of the way anymore.


Company? Most of the time this stuff is years (sometimes DECADES) old. That's why it doesn't work on Linux in the first place.

With all these commandline and registry hacks to make macOS and Windows bearable, why not use Linux? You will also have to use the commandline if you want total customizability, but at least the OS doesn't actively fight you.

> at least the OS doesn't actively fight you.

That was not my experience with Linux in the slightest. I used various distros for many years, and it eventually became just a waste of time. I got fed up with trying to play whack-a-mole with fixing driver issues.

It has been some years though, so maybe things have improved in this regard. However, I felt like using Linux as my daily driver served as an outlet for procrastination when my time would have been better solved working on the tasks I needed the OS for in the first place.


From the NN/g article:

"older versions of MacOS featured a menu designed by NN/g principal Bruce Tognazzini; that menu did not exhibit this behavior, but instead, used a vector-based triangular buffer to allow users to move diagonally. Unfortunately, in the years since, Apple has reverted this excellent bit of interaction design."

But I'm on macOS 15 and the menus seem to behave that way (the good way). Did they re-implement it?


Yes, they did eventually. If I'm understanding correctly, the original design used a simple funnel shape with 45 degree sides (suitable for the resource-limited systems of the day), and when they eventually re-implemented it they used a funnel defined by the left hand corners of the submenu, as per the Amazon design. (See the large animgif halfway down https://thomaspark.co/2011/10/making-menus-escapable/ )

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

Search: